Skip to content

Issues: e-lo/forecastcards

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

29 Open 16 Closed
29 Open 16 Closed
Author
Filter by author
Label
Filter by label
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Projects
Filter by project
Milestones
Filter by milestone
Assignee
Filter by who’s assigned
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

Create a sanitize script
#46 opened May 29, 2019 by e-lo
Build new schema documentation upon completing CI enhancement New feature or request
#42 opened Jan 4, 2019 by e-lo
@e-lo
Add CI for forecastcards package enhancement New feature or request
#41 opened Jan 4, 2019 by e-lo
@e-lo
Equipment type field isn't helpful schema Something with the schema itself
#39 opened Dec 13, 2018 by e-lo
@gregerhardt
forecast_variable field is redundant if we are just working with volumes schema Something with the schema itself
#38 opened Dec 13, 2018 by e-lo
@gregerhardt
1
Is jurisidiction field necessary? schema Something with the schema itself
#36 opened Dec 13, 2018 by e-lo
@gregerhardt
1
How many area types? schema Something with the schema itself
#35 opened Dec 13, 2018 by e-lo
@gregerhardt
1
Add required value list for facility type schema Something with the schema itself
#34 opened Dec 13, 2018 by e-lo
@gregerhardt
1
Why are forecasts and observations in two separate folders? schema Something with the schema itself
#33 opened Dec 13, 2018 by e-lo
@gregerhardt
1
Consider lessening # of CSV files flow improvement schema Something with the schema itself
#32 opened Dec 13, 2018 by e-lo
@e-lo @gregerhardt
1
Clarify Start and End point documentation Documentation
#31 opened Dec 13, 2018 by e-lo
@gregerhardt
1
Use County field instead of the Jurisdiction.
#30 opened Dec 13, 2018 by e-lo
@e-lo @gregerhardt
Document what start and end time should be for daily volumes Documentation
#29 opened Dec 13, 2018 by e-lo
@gregerhardt
Allow multiple options for some fields enhancement New feature or request
#28 opened Dec 13, 2018 by e-lo
@e-lo
1
More options for forecast system type schema Something with the schema itself
#27 opened Dec 13, 2018 by e-lo
@gregerhardt
Automagically match POI, observations, and forecast rather than using forecast-match-id flow improvement
#26 opened Dec 13, 2018 by e-lo
@e-lo
Require data validation on input, not as a separate step flow improvement low priority
#25 opened Dec 13, 2018 by e-lo
Test system with converted forecast cards high priority
#21 opened Dec 7, 2018 by gregerhardt
@gregerhardt @daves1997
Convert existing data to forecastcard format high priority
#20 opened Dec 7, 2018 by gregerhardt
1
Clarify approaches by privacy levels Documentation
#19 opened Dec 2, 2018 by e-lo
Shorter field names flow improvement
#18 opened Dec 2, 2018 by e-lo
@gregerhardt @daves1997
Add GIS info enhancement New feature or request
#17 opened Dec 2, 2018 by e-lo
@e-lo
1
Add CI tests for submitting a new project or adding forecasts or observations flow improvement
#12 opened Nov 28, 2018 by e-lo November 30
@e-lo
Data validation should validate foreign key requirements. bug Something isn't working
#11 opened Nov 28, 2018 by e-lo
@e-lo
Create template for agency card repo flow improvement high priority
#9 opened Nov 28, 2018 by e-lo November 30
@e-lo
ProTip! Exclude everything labeled bug with -label:bug.