Ecosyste.ms: Issues

An open API service for providing issue and pull request metadata for open source projects.

GitHub / e-lo/forecastcards issues and pull requests

#46 - Create a sanitize script

Issue - State: open - Opened by e-lo over 5 years ago

#45 - Put on PyPi

Issue - State: closed - Opened by e-lo over 5 years ago - 1 comment
Labels: flow improvement

#44 - validate start time is before end time

Issue - State: closed - Opened by e-lo over 5 years ago
Labels: bug

#43 - Create Cards Notebook

Issue - State: closed - Opened by e-lo over 5 years ago

#42 - Build new schema documentation upon completing CI

Issue - State: open - Opened by e-lo over 5 years ago
Labels: enhancement

#41 - Add CI for forecastcards package

Issue - State: open - Opened by e-lo over 5 years ago
Labels: enhancement

#40 - Adding multiple projects is ballooning dataset with multiple entries.

Issue - State: closed - Opened by e-lo almost 6 years ago - 1 comment
Labels: bug

#39 - Equipment type field isn't helpful

Issue - State: open - Opened by e-lo almost 6 years ago
Labels: schema

#38 - forecast_variable field is redundant if we are just working with volumes

Issue - State: open - Opened by e-lo almost 6 years ago - 1 comment
Labels: schema

#37 - Clarify that Forecast Agency and Forecaster Type can be "unknown" by leaving blank

Issue - State: closed - Opened by e-lo almost 6 years ago - 1 comment
Labels: Documentation

#36 - Is jurisidiction field necessary?

Issue - State: open - Opened by e-lo almost 6 years ago - 1 comment
Labels: schema

#35 - How many area types?

Issue - State: open - Opened by e-lo almost 6 years ago - 1 comment
Labels: schema

#34 - Add required value list for facility type

Issue - State: open - Opened by e-lo almost 6 years ago - 1 comment
Labels: schema

#33 - Why are forecasts and observations in two separate folders?

Issue - State: open - Opened by e-lo almost 6 years ago - 1 comment
Labels: schema

#32 - Consider lessening # of CSV files

Issue - State: open - Opened by e-lo almost 6 years ago - 1 comment
Labels: flow improvement, schema

#31 - Clarify Start and End point documentation

Issue - State: open - Opened by e-lo almost 6 years ago - 1 comment
Labels: Documentation

#30 - Use County field instead of the Jurisdiction.

Issue - State: open - Opened by e-lo almost 6 years ago

#29 - Document what start and end time should be for daily volumes

Issue - State: open - Opened by e-lo almost 6 years ago
Labels: Documentation

#28 - Allow multiple options for some fields

Issue - State: open - Opened by e-lo almost 6 years ago - 1 comment
Labels: enhancement

#27 - More options for forecast system type

Issue - State: open - Opened by e-lo almost 6 years ago
Labels: schema

#26 - Automagically match POI, observations, and forecast rather than using forecast-match-id

Issue - State: open - Opened by e-lo almost 6 years ago
Labels: flow improvement

#25 - Require data validation on input, not as a separate step

Issue - State: open - Opened by e-lo almost 6 years ago
Labels: flow improvement, low priority

#24 - Add "ramp" and "unknown" to functional class

Issue - State: closed - Opened by e-lo almost 6 years ago - 1 comment

#23 - Don't make functional class or improvement type "required" fields.

Issue - State: closed - Opened by e-lo almost 6 years ago - 2 comments

#22 - Refactor to classes to add robustness; add local file reading capability

Pull Request - State: closed - Opened by e-lo almost 6 years ago
Labels: enhancement, flow improvement

#21 - Test system with converted forecast cards

Issue - State: open - Opened by gregerhardt almost 6 years ago
Labels: high priority

#20 - Convert existing data to forecastcard format

Issue - State: open - Opened by gregerhardt almost 6 years ago - 1 comment
Labels: high priority

#19 - Clarify approaches by privacy levels

Issue - State: open - Opened by e-lo almost 6 years ago
Labels: Documentation

#18 - Shorter field names

Issue - State: open - Opened by e-lo almost 6 years ago
Labels: flow improvement

#17 - Add GIS info

Issue - State: open - Opened by e-lo almost 6 years ago - 1 comment
Labels: enhancement

#16 - From/To should include A node and B node

Issue - State: closed - Opened by e-lo almost 6 years ago
Labels: Documentation

#15 - Clarify directionality; allow variable for bi-directional AADT

Issue - State: closed - Opened by e-lo almost 6 years ago - 1 comment
Labels: Documentation, high priority

#14 - Add check_cards script

Issue - State: closed - Opened by e-lo almost 6 years ago
Labels: enhancement

#13 - Fix issues with "open with colab"

Issue - State: closed - Opened by e-lo almost 6 years ago - 3 comments
Labels: flow improvement, high priority

#12 - Add CI tests for submitting a new project or adding forecasts or observations

Issue - State: open - Opened by e-lo almost 6 years ago
Labels: flow improvement

#11 - Data validation should validate foreign key requirements.

Issue - State: open - Opened by e-lo almost 6 years ago
Labels: bug

#10 - Fix merge to assume only project_ID is universally unique

Issue - State: closed - Opened by e-lo almost 6 years ago - 1 comment
Labels: bug

#9 - Create template for agency card repo

Issue - State: open - Opened by e-lo almost 6 years ago
Labels: flow improvement, high priority

#8 - Allow reading from xls

Issue - State: open - Opened by e-lo almost 6 years ago
Labels: enhancement, flow improvement, low priority

#7 - Create template for CSVs

Issue - State: closed - Opened by e-lo almost 6 years ago

#6 - Scale ADT variables by time

Issue - State: closed - Opened by e-lo almost 6 years ago
Labels: bug, high priority

#5 - Allow public, community forecastcards datastore to be a mirror

Issue - State: open - Opened by e-lo almost 6 years ago
Labels: flow improvement

#4 - Allow multiple sources of data in order to combine local private data with public data

Issue - State: closed - Opened by e-lo almost 6 years ago - 1 comment
Labels: flow improvement, high priority

#3 - Make import work on s3

Issue - State: open - Opened by e-lo almost 6 years ago
Labels: flow improvement, low priority

#2 - Make import flexible to local locations

Issue - State: closed - Opened by e-lo almost 6 years ago - 1 comment
Labels: flow improvement, high priority

#1 - Create helper scripts to convert from common-ish data formats.

Issue - State: open - Opened by e-lo almost 6 years ago - 3 comments
Labels: flow improvement, low priority