add todo comments

Author: derhuerst

lib/prerequisites.js

@@ -12,6 +12,15 @@ LOAD icu;
 -- identifiers with "_", not with "-", so we use pg_collation instead.
 -- see also https://duckdb.org/docs/sql/expressions/collations#icu-collations
 -- todo: Also, entries like "de_DE" are missing.
+-- todo: it *seems* that just \`no\` (as used by Entur) is valid:
+-- > langtag       = language
+-- >                 ["-" script]
+-- >                 ["-" region]
+-- >                 *("-" variant)
+-- >                 *("-" extension)
+-- >                 ["-" privateuse]
+-- – https://www.rfc-editor.org/rfc/bcp/bcp47.txt
+-- see https://github.com/duckdb/duckdb/issues/20672
 CREATE TABLE valid_lang_codes (
 	-- As of DuckDB v1.2.0, referring to this table via either a subquery or a plain foreign key doesn't work because
 	-- - subqueries are prohibited in CHECK constraints, and

lib/stop_times.js

@@ -206,6 +206,9 @@ WITH stop_times_based AS NOT MATERIALIZED (
 		drop_off_type,
 		shape_dist_traveled,
 		timepoint,
+		-- todo: simplify?
+		-- see https://github.com/MobilityData/gtfs-validator/issues/130
+		-- see https://github.com/MobilityData/gtfs-validator/blob/2919b7c76b299058f06a486feb987d9f3f6e23a2/main/src/main/java/org/mobilitydata/gtfsvalidator/validator/AgencyConsistencyValidator.java#L83-L92
 		agency.agency_timezone as tz,
 		arrival_time,
 		(

lib/stops.js

@@ -34,6 +34,8 @@ const importData = async (db, pathToStops, opt, workingState) => {
 		'platform_code',
 	])
 
+	// todo: support new columns, e.g. tts_stop_name
+
 	await db[RUN](`\
 CREATE TYPE 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.