e-lo/forecastcards

Issues

• Create a sanitize script

  #46 opened 6 years ago by e-lo
  0

• Put on PyPi

  #45 opened 6 years ago by e-lo
  1

• Scale ADT variables by time

  #6 opened 6 years ago by e-lo
  0

• validate start time is before end time

  #44 opened 6 years ago by e-lo
  0

• Clarify that Forecast Agency and Forecaster Type can be "unknown" by leaving blank

  #37 opened 6 years ago by e-lo
  1

• From/To should include A node and B node

  #16 opened 6 years ago by e-lo
  0

• Add check_cards script

  #14 opened 6 years ago by e-lo
  0

• Create Cards Notebook

  #43 opened 6 years ago by e-lo
  0

• More options for forecast system type

  #27 opened 6 years ago by e-lo
  0

• Build new schema documentation upon completing CI

  #42 opened 6 years ago by e-lo
  0

• Add CI for forecastcards package

  #41 opened 6 years ago by e-lo
  0

• How many area types?

  #35 opened 6 years ago by e-lo
  1

• Is jurisidiction field necessary?

  #36 opened 6 years ago by e-lo
  1

• forecast_variable field is redundant if we are just working with volumes

  #38 opened 6 years ago by e-lo
  1

• Equipment type field isn't helpful

  #39 opened 6 years ago by e-lo
  0

• Consider lessening # of CSV files

  #32 opened 6 years ago by e-lo
  1

• Why are forecasts and observations in two separate folders?

  #33 opened 6 years ago by e-lo
  1

• Add required value list for facility type

  #34 opened 6 years ago by e-lo
  1

• Fix merge to assume only project_ID is universally unique

  #10 opened 6 years ago by e-lo
  1

• Allow multiple sources of data in order to combine local private data with public data

  #4 opened 6 years ago by e-lo
  1

• Fix issues with "open with colab"

  #13 opened 6 years ago by e-lo
  3

• Adding multiple projects is ballooning dataset with multiple entries.

  #40 opened 6 years ago by e-lo
  1

• Clarify Start and End point documentation

  #31 opened 6 years ago by e-lo
  1

• Use County field instead of the Jurisdiction.

  #30 opened 6 years ago by e-lo
  0

• Document what start and end time should be for daily volumes

  #29 opened 6 years ago by e-lo
  0

• Allow multiple options for some fields

  #28 opened 6 years ago by e-lo
  1

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

  #26 opened 6 years ago by e-lo
  0

• Require data validation on input, not as a separate step

  #25 opened 6 years ago by e-lo
  0

• Don't make functional class or improvement type "required" fields.

  #23 opened 6 years ago by e-lo
  2

• Add "ramp" and "unknown" to functional class

  #24 opened 6 years ago by e-lo
  1

• Create template for agency card repo

  #9 opened 6 years ago by e-lo
  0

• Data validation should validate foreign key requirements.

  #11 opened 6 years ago by e-lo
  0

• Clarify directionality; allow variable for bi-directional AADT

  #15 opened 6 years ago by e-lo
  1

• Make import flexible to local locations

  #2 opened 6 years ago by e-lo
  1

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

  #1 opened 6 years ago by e-lo
  3

• Test system with converted forecast cards

  #21 opened 6 years ago by gregerhardt
  0

• Convert existing data to forecastcard format

  #20 opened 6 years ago by gregerhardt
  1

• Shorter field names

  #18 opened 6 years ago by e-lo
  0

• Add GIS info

  #17 opened 6 years ago by e-lo
  1

• Allow reading from xls

  #8 opened 6 years ago by e-lo
  0

• Make import work on s3

  #3 opened 6 years ago by e-lo
  0

• Clarify approaches by privacy levels

  #19 opened 6 years ago by e-lo
  0

• Create template for CSVs

  #7 opened 6 years ago by e-lo
  0

• Add CI tests for submitting a new project or adding forecasts or observations

  #12 opened 6 years ago by e-lo
  0

• Allow public, community forecastcards datastore to be a mirror

  #5 opened 6 years ago by e-lo
  0