adapt GTFS links/references to its latest website 📝

derhuerst · derhuerst · commit 9502912159d7 · 2025-04-06T16:57:16.000+02:00
diff --git a/lib/agency.js b/lib/agency.js
@@ -1,6 +1,6 @@
 'use strict'
 
-// https://gtfs.org/schedule/reference/#agencytxt
+// https://gtfs.org/documentation/schedule/reference/#agencytxt
 const beforeAll = (opt) => `\
 CREATE TABLE "${opt.schema}".agency (
 	agency_id TEXT PRIMARY KEY,
diff --git a/lib/calendar.js b/lib/calendar.js
@@ -1,6 +1,6 @@
 'use strict'
 
-// https://gtfs.org/schedule/reference/#calendartxt
+// https://gtfs.org/documentation/schedule/reference/#calendartxt
 const beforeAll = (opt) => `\
 CREATE TYPE "${opt.schema}".availability AS ENUM (
 	'not_available' -- 0 – Service is not available for Mondays in the date range.
diff --git a/lib/calendar_dates.js b/lib/calendar_dates.js
@@ -1,6 +1,6 @@
 'use strict'
 
-// https://gtfs.org/schedule/reference/#calendar_datestxt
+// https://gtfs.org/documentation/schedule/reference/#calendar_datestxt
 const beforeAll = (opt) => `\
 CREATE TYPE "${opt.schema}".exception_type_v AS ENUM (
 	'added' -- 1 – Service has been added for the specified date.
diff --git a/lib/deps.js b/lib/deps.js
@@ -56,7 +56,7 @@ const getDependencies = (opt, files) => {
 			// > pathways
 			// > levels
 			// > attributions
-			// https://gtfs.org/schedule/reference/#translationstxt
+			// https://gtfs.org/documentation/schedule/reference/#translationstxt
 			// todo: respect opt.*!
 			// these are soft dependencies, they are not depended upon, they must only be imported first
 			// todo: only specify dependencies here if the files are not in use
diff --git a/lib/feed_info.js b/lib/feed_info.js
@@ -1,6 +1,6 @@
 'use strict'
 
-// https://gtfs.org/schedule/reference/#feed_infotxt
+// https://gtfs.org/documentation/schedule/reference/#feed_infotxt
 const beforeAll = (opt) => `\
 -- The MobilityData GTFS Validator just uses Java's Locale#toLanguageTag() to validate *_lang.
 -- https://github.com/MobilityData/gtfs-validator/blob/31ff374800f7d7883fd9de91b71049c2a4de4e45/main/src/main/java/org/mobilitydata/gtfsvalidator/validator/MatchingFeedAndAgencyLangValidator.java#L82
diff --git a/lib/frequencies.js b/lib/frequencies.js
@@ -2,7 +2,7 @@
 
 const {formatTime} = require('./util')
 
-// https://gtfs.org/schedule/reference/#frequenciestxt
+// https://gtfs.org/documentation/schedule/reference/#frequenciestxt
 const beforeAll = (opt) => `\
 CREATE TYPE "${opt.schema}".exact_times_v AS ENUM (
 	'frequency_based' -- 0 or empty - Frequency-based trips.
diff --git a/lib/levels.js b/lib/levels.js
@@ -2,7 +2,7 @@
 
 const {formatTime} = require('./util')
 
-// https://gtfs.org/schedule/reference/#levelstxt
+// https://gtfs.org/documentation/schedule/reference/#levelstxt
 const beforeAll = (opt) => `\
 CREATE TABLE "${opt.schema}".levels (
 	level_id TEXT PRIMARY KEY,
diff --git a/lib/pathways.js b/lib/pathways.js
@@ -2,7 +2,7 @@
 
 const {formatTime} = require('./util')
 
-// https://gtfs.org/schedule/reference/#pathwaystxt
+// https://gtfs.org/documentation/schedule/reference/#pathwaystxt
 const beforeAll = (opt) => `\
 CREATE TYPE "${opt.schema}".pathway_mode_v AS ENUM (
 	'walkway' -- 1
diff --git a/lib/routes.js b/lib/routes.js
@@ -231,7 +231,7 @@ const routeTypesSchemes = Object.assign(Object.create(null), {
 	'tpeg-pti': tpegPtiExtendedRouteTypes,
 })
 
-// https://gtfs.org/schedule/reference/#routestxt
+// https://gtfs.org/documentation/schedule/reference/#routestxt
 const beforeAll = (opt) => {
 	if (!(opt.routeTypesScheme in routeTypesSchemes)) {
 		throw new Error(`invalid opt.routeTypesScheme, must be one of these: ${Object.keys(routeTypesSchemes).join(', ')}.`)
diff --git a/lib/shapes.js b/lib/shapes.js
@@ -1,6 +1,6 @@
 'use strict'
 
-// https://gtfs.org/schedule/reference/#shapestxt
+// https://gtfs.org/documentation/schedule/reference/#shapestxt
 const beforeAll = (opt) => `\
 CREATE TABLE "${opt.schema}".shapes (
 	id SERIAL PRIMARY KEY,
diff --git a/lib/stop_times.js b/lib/stop_times.js
@@ -2,7 +2,7 @@
 
 const {formatTime} = require('./util')
 
-// https://gtfs.org/schedule/reference/#stop_timestxt
+// https://gtfs.org/documentation/schedule/reference/#stop_timestxt
 const beforeAll = (opt) => `\
 CREATE TYPE "${opt.schema}".pickup_drop_off_type AS ENUM (
 	'regular' -- 0 or empty - Regularly scheduled pickup/dropoff.
diff --git a/lib/stops.js b/lib/stops.js
@@ -1,6 +1,6 @@
 'use strict'
 
-// https://gtfs.org/schedule/reference/#stopstxt
+// https://gtfs.org/documentation/schedule/reference/#stopstxt
 const beforeAll = (opt) => `\
 CREATE TYPE "${opt.schema}".location_type_val AS ENUM (
 	'stop' -- 0 (or blank): Stop (or Platform). A location where passengers board or disembark from a transit vehicle. Is called a platform when defined within a parent_station.
diff --git a/lib/transfers.js b/lib/transfers.js
@@ -1,6 +1,6 @@
 'use strict'
 
-// https://gtfs.org/schedule/reference/#transferstxt
+// https://gtfs.org/documentation/schedule/reference/#transferstxt
 const beforeAll = (opt) => `\
 CREATE TYPE "${opt.schema}".transfer_type_v AS ENUM (
 	'recommended' -- 0 or empty - Recommended transfer point between routes.
diff --git a/lib/translations.js b/lib/translations.js
@@ -1,6 +1,6 @@
 'use strict'
 
-// https://gtfs.org/schedule/reference/#translationstxt
+// https://gtfs.org/documentation/schedule/reference/#translationstxt
 const beforeAll = (opt) => `\
 CREATE OR REPLACE FUNCTION "${opt.schema}".table_exists(
 	t_name TEXT
@@ -94,7 +94,7 @@ COMMENT ON TABLE "${opt.schema}"._translations_ref_cols IS E'@omit';
 -- > - None for shapes.txt
 -- > - start_time for frequencies.txt
 -- > - to_stop_id for transfers.txt
--- https://gtfs.org/schedule/reference/#translationstxt
+-- https://gtfs.org/documentation/schedule/reference/#translationstxt
 INSERT INTO "${opt.schema}"._translations_ref_cols (
 	table_name,
 	record_id_col,
@@ -238,7 +238,7 @@ COMMENT ON FUNCTION "${opt.schema}".is_valid_translation_ref IS E'@omit';
 -- https://docs.oracle.com/javase/7/docs/api/java/util/Locale.html
 -- related: https://github.com/google/transit/pull/98
 
--- https://gtfs.org/schedule/reference/#translationstxt
+-- https://gtfs.org/documentation/schedule/reference/#translationstxt
 CREATE TABLE "${opt.schema}".translations (
 	-- > Defines the table that contains the field to be translated. Allowed values are:
 	-- > agency, stops, routes, trips, stop_times, pathways, levels, feed_info, attributions
@@ -325,7 +325,7 @@ CREATE TABLE "${opt.schema}".translations (
 	),
 
 	-- > Primary key (table_name, field_name, language, record_id, record_sub_id, field_value)
-	-- https://gtfs.org/schedule/reference/#translationstxt
+	-- https://gtfs.org/documentation/schedule/reference/#translationstxt
 	-- PostgreSQL doesn't allow NULL values for primary key columns, so we use UNIQUE.
 	UNIQUE (
 		table_name,
diff --git a/lib/trips.js b/lib/trips.js
@@ -1,6 +1,6 @@
 'use strict'
 
-// https://gtfs.org/schedule/reference/#tripstxt
+// https://gtfs.org/documentation/schedule/reference/#tripstxt
 const beforeAll = (opt) => `\
 CREATE TYPE "${opt.schema}".wheelchair_accessibility AS ENUM (
 	'unknown' -- 0 or empty - No accessibility information for the trip.
diff --git a/readme.md b/readme.md
@@ -1,6 +1,6 @@
 # gtfs-via-postgres
 
-**Import [GTFS Static/Schedule](https://gtfs.org/schedule/) datasets into a [PostgreSQL database](https://www.postgresql.org)**, to allow for efficient querying and analysis.
+**Import [GTFS Static/Schedule](https://gtfs.org/documentation/schedule/reference/) datasets into a [PostgreSQL database](https://www.postgresql.org)**, to allow for efficient querying and analysis.
 
 [![npm version](https://img.shields.io/npm/v/gtfs-via-postgres.svg)](https://www.npmjs.com/package/gtfs-via-postgres)
 [![binary build status](https://img.shields.io/github/actions/workflow/status/public-transport/gtfs-via-postgres/publish.yml?label=binary%20build)](https://github.com/public-transport/gtfs-via-postgres/actions)
@@ -96,10 +96,10 @@ Importing will take 10s to 10m, depending on the size of the feed. On an [M1 Mac
 
 In addition to a table for each GTFS file, `gtfs-via-postgres` adds these views to help with real-world analysis:
 
-- `service_days` ([materialized](https://www.postgresql.org/docs/13/sql-creatematerializedview.html)) "applies" [`calendar_dates`](https://gtfs.org/reference/static/#calendar_datestxt) to [`calendar`](https://gtfs.org/reference/static/#calendartxt) to give you all days of operation for each "service" defined in [`calendar`](https://gtfs.org/reference/static/#calendartxt).
-- `arrivals_departures` "applies" [`stop_times`](https://gtfs.org/reference/static/#stop_timestxt)/[`frequencies`](https://gtfs.org/reference/static/#frequenciestxt) to [`trips`](https://gtfs.org/reference/static/#tripstxt) and `service_days` to give you all arrivals/departures at each stop with their *absolute* dates & times. It also resolves each stop's parent station ID & name.
-- `connections` "applies" [`stop_times`](https://gtfs.org/reference/static/#stop_timestxt)/[`frequencies`](https://gtfs.org/reference/static/#frequenciestxt) to [`trips`](https://gtfs.org/reference/static/#tripstxt) and `service_days`, just like `arrivals_departures`, but gives you departure (at stop A) & arrival (at stop B) *pairs*.
-- `shapes_aggregates` aggregates individual shape points in [`shapes`](https://gtfs.org/reference/static/#shapestxt) into a [PostGIS `LineString`](http://postgis.net/workshops/postgis-intro/geometries.html#linestrings).
+- `service_days` ([materialized](https://www.postgresql.org/docs/13/sql-creatematerializedview.html)) "applies" [`calendar_dates`](https://gtfs.org/documentation/schedule/reference/#calendar_datestxt) to [`calendar`](https://gtfs.org/documentation/schedule/reference/#calendartxt) to give you all days of operation for each "service" defined in [`calendar`](https://gtfs.org/documentation/schedule/reference/#calendartxt).
+- `arrivals_departures` "applies" [`stop_times`](https://gtfs.org/documentation/schedule/reference/#stop_timestxt)/[`frequencies`](https://gtfs.org/documentation/schedule/reference/#frequenciestxt) to [`trips`](https://gtfs.org/documentation/schedule/reference/#tripstxt) and `service_days` to give you all arrivals/departures at each stop with their *absolute* dates & times. It also resolves each stop's parent station ID & name.
+- `connections` "applies" [`stop_times`](https://gtfs.org/documentation/schedule/reference/#stop_timestxt)/[`frequencies`](https://gtfs.org/documentation/schedule/reference/#frequenciestxt) to [`trips`](https://gtfs.org/documentation/schedule/reference/#tripstxt) and `service_days`, just like `arrivals_departures`, but gives you departure (at stop A) & arrival (at stop B) *pairs*.
+- `shapes_aggregates` aggregates individual shape points in [`shapes`](https://gtfs.org/documentation/schedule/reference/#shapestxt) into a [PostGIS `LineString`](http://postgis.net/workshops/postgis-intro/geometries.html#linestrings).
 - `stats_by_route_date` provides the number of arrivals/departures by route ID and date. – [read more](docs/analysis/feed-by-route-date.md)
 - `stats_by_agency_route_stop_hour` provides the number of arrivals/departures by agency ID, route ID, stop ID & hour. – [read more](docs/analysis/feed-by-agency-route-stop-and-hour.md)
 - In contrast to `stats_by_route_date` & `stats_by_agency_route_stop_hour`, `stats_active_trips_by_hour` provides the number of *currently running* trips for each hour in the feeds period of time.
