Skip to content

Latest commit

 

History

History
74 lines (55 loc) · 2.85 KB

readme.md

File metadata and controls

74 lines (55 loc) · 2.85 KB

Review of US NTD GTFS weblinks

The files in this subdirectory relate to reviewing the US NTD release of GTFS weblinks and using it to update and add coverage to Transitland Atlas.

Background

See:

Files in this subdirectory

  • 2023-gtfs-weblinks-checked.csv - CSV of feeds that have been checked against Transitland contents in late 2024. The Status column indicates:
    • "Success" - URL returns valid GTFS data
    • "Success (Retried with HTTP/HTTPS)" - URL works after protocol change
    • "No results" - URL is not accessible or doesn't return valid GTFS
    • Note: Agencies that did not provide a URL are not included in the check results. We welcome help to politely contact these agencies directly to ask for public URLs for their GTFS feeds.
  • 2023-gtfs-weblinks.dmfr.json - a JSON file containing proposed DMFR records for potentially unmatched records

Help wanted

To help, review the contents of 2023-gtfs-weblinks.dmfr.json:

  1. Look for records that may be missing in Transitland Atlas
  2. Check for likely_match_operator_link and likely_match_full to see if the script successfully found an existing match, or if it's just noise
  3. Also browse the Transitland map and website for an existing feed record in the same location but a different name (sometimes agencies change their brand name, or use a different name when reporting to NTD)
  4. When adding a feed to Transitland Atlas, you can also delete the relevant portion of 2023-gtfs-weblinks.dmfr.json in the same pull request

Notes

To recreate these files:

wget https://www.transit.dot.gov/sites/fta.dot.gov/files/2024-10/2023%20GTFS%20Weblinks.xlsx

in2csv 2023\ GTFS\ Weblinks.xlsx > 2023-gtfs-weblinks.csv

pipenv run python check-ntd-urls.py 2023-gtfs-weblinks.csv > 2023-gtfs-weblinks-checked.csv

pipenv run python check-ntd-urls.py

NTD IDs in Transitland Atlas

Operator records in DMFR files that correspond to US NTD-reporting agencies can include a us_ntd_id tag with the agency's NTD ID. For example:

{
  "feeds": [
    {
      "id": "f-c23-metrokingcounty",
      "spec": "gtfs",
      "urls": {
        "static_current": "http://metro.kingcounty.gov/GTFS/google_transit.zip"
      },
      "operators": [
        {
          "onestop_id": "o-c23-metrotransit",
          "name": "King County Metro",
          "website": "http://metro.kingcounty.gov",
          "tags": {
            "us_ntd_id": "00001"
          }
        }
      ]
    }
  ]
}

This will be useful for ongoing cross-referencing between Transitland and US NTD datasets.