census-bds/usdot-phmsa-hazmat-parser

Issues

• env setup -- README + requirements.txt

  #21 opened 4 years ago by cmoscardi
  2

• deal with sections that have hyphens in them (i.e. 178.338-19)

  #26 opened 4 years ago by chankrista
  0

• All rows in all tables should explicitly reference precisely where in CFR they came from.

  #24 opened 4 years ago by cmoscardi
  0

• Nit: `/` endpoint on app should nicely redirect to `/packaging` landing page

  #22 opened 4 years ago by cmoscardi
  0

• All fields containing the same information across all tables should have the same name

  #25 opened 4 years ago by cmoscardi
  0

• An E-R diagram of the database as it exists and as we want it to look

  #16 opened 4 years ago by chankrista
  0

• Instructions for using the database with example queries

  #20 opened 4 years ago by chankrista
  0

• Documentation should include clear instructions on setting up + connecting to DB without app

  #23 opened 4 years ago by cmoscardi
  1

• distinguish the highlight color for packaging codes by performance vs specification vs tank car vs cylinder

  #19 opened 4 years ago by chankrista
  0

• Include links/tooltips in the web app and database between each subpart of the cfr and any interps

  #18 opened 4 years ago by chankrista
  0

• Once the new eCFR is out of beta, use the API to pull text from the CFR

  #17 opened 4 years ago by chankrista
  0

• Incorporate spec packaging into front end code lookup

  #9 opened 4 years ago by chankrista
  1

• Parse "conditionals" to classify whether codes are required, recommended, or prohibited. Use that to create a training set for future classification.

  #10 opened 4 years ago by chankrista
  0

• Rows in the hazmat table with shipping name that say "see.." should copy the other shipping name.

  #11 opened 4 years ago by chankrista
  0

• Parse definitions in 171.8, make them show up in tooltips

  #12 opened 4 years ago by chankrista
  0

• Mistake in CFR: NA1760 shows up twice with two different shipping names.

  #13 opened 4 years ago by chankrista
  0

• Incorporate special provisions and exceptions into front end

  #14 opened 4 years ago by chankrista
  0

• An interface for viewing stowage requirements

  #15 opened 4 years ago by chankrista
  0

• Modify the form so that successive questions after UNNA code are asked depending on what options exist.

  #7 opened 4 years ago by chankrista
  0

• Parse DOT cylinder codes and cargo tank codes

  #6 opened 4 years ago by chankrista
  0

• Modify regex to only parse packaging codes with 1 or 2 leading digits (i.e. positive lookbehind of blank space or beginning of string)

  #4 opened 4 years ago by chankrista
  0

• debug: not all packaging groups are being parsed

  #8 opened 4 years ago by chankrista
  0

• Integrate the database as it currently exists with the frontend

  #3 opened 4 years ago by chankrista
  0

• Database should include reference to which section of CFR each piece of info came from.

  #1 opened 4 years ago by cmoscardi
  0

• Need to modify hazmat table parser to fill in values from previous rows

  #2 opened 4 years ago by cmoscardi
  0