DuckDB rewrite: adapt project metadata

Author: derhuerst

Dockerfile

@@ -1,10 +1,10 @@
 FROM node:alpine
-LABEL org.opencontainers.image.title="gtfs-via-postgres"
-LABEL org.opencontainers.image.description="Process GTFS using PostgreSQL."
+LABEL org.opencontainers.image.title="gtfs-via-duckdb"
+LABEL org.opencontainers.image.description="Analyze GTFS datasets using DuckDB."
 LABEL org.opencontainers.image.authors="Jannis R <mail@jannisr.de>"
-LABEL org.opencontainers.image.documentation="https://github.com/public-transport/gtfs-via-postgres"
-LABEL org.opencontainers.image.source="https://github.com/public-transport/gtfs-via-postgres"
-LABEL org.opencontainers.image.revision="4.0.0"
+LABEL org.opencontainers.image.documentation="https://github.com/public-transport/gtfs-via-duckdb"
+LABEL org.opencontainers.image.source="https://github.com/public-transport/gtfs-via-duckdb"
+LABEL org.opencontainers.image.revision="5.0.0"
 LABEL org.opencontainers.image.licenses="(Apache-2.0 AND Prosperity-3.0.0)"
 
 WORKDIR /app

LICENSE-APACHE

@@ -176,7 +176,7 @@
 
    END OF TERMS AND CONDITIONS
 
-   Copyright 2020 gtfs-via-postgres contributors
+   Copyright 2020 gtfs-via-postgres & gtfs-via-duckdb contributors
 
    Licensed under the Apache License, Version 2.0 (the "License");
    you may not use this file except in compliance with the License.

LICENSE-PROSPERITY.md

@@ -2,7 +2,7 @@
 
 Contributor: Jannis R
 
-Source Code: https://github.com/public-transport/gtfs-via-postgres
+Source Code: https://github.com/public-transport/gtfs-via-duckdb
 
 ## Purpose
 

docs/analysis/active-trips-by-hour.md

@@ -2,7 +2,7 @@
 
 Do you want to know how many trips are running at a specific point in time?
 
-`gtfs-via-postgres` optionally provides a **(materialized) view `stats_active_trips_by_hour` to answer this. Use the `--stats-active-trips-by-hour` flag to enable it**:
+`gtfs-via-duckdb` optionally provides a **(materialized) view `stats_active_trips_by_hour` to answer this. Use the `--stats-active-trips-by-hour` flag to enable it**:
 
 - If you run `gtfs-to-sql` with `--stats-active-trips-by-hour=view`, `stats_active_trips_by_hour` will be a "regular" non-materialized view. Use this option if you want to import the GTFS data quickly, and if you only query `stats_active_trips_by_hour` rarely or in time-uncritical scenarios.
 - If you pass `--stats-active-trips-by-hour=materialized-view`, the `stats_active_trips_by_hour` view will [be materialized](https://www.postgresql.org/docs/14/rules-materializedviews.html). Use this option if you need fast queries, and if you can tolerate significantly longer import times (a minute for small feeds, many hours for large feeds).

docs/analysis/feed-by-agency-route-stop-and-hour.md

@@ -1,5 +1,5 @@
 # analysing a GTFS dataset by route ID, stop ID and/or hour
 
-With the `--stats-by-route-and-stop-and-hour` option, `gtfs-via-postgres` provides a view `stats_by_agency_route_stop_hour`. Just like [`stats_by_route_id_and_date`](feed-by-route-and-date.md), it aggregates all arrivals by `agency_id`, `route_id`, `stop_id` and `effective_hour`.
+With the `--stats-by-route-and-stop-and-hour` option, `gtfs-via-duckdb` provides a view `stats_by_agency_route_stop_hour`. Just like [`stats_by_route_id_and_date`](feed-by-route-and-date.md), it aggregates all arrivals by `agency_id`, `route_id`, `stop_id` and `effective_hour`.
 
 Note: As a materialized view, `stats_by_agency_route_stop_hour` takes up a significant amount of space, e.g. 13GB with the 2023-05-02 VBB GTFS feed.

docs/analysis/feed-by-route-date.md

@@ -6,7 +6,7 @@ Are you trying to answer a question like those below?
 - Has the number of stop time events decreased, compared to the last dataset version?
 - Do specific routes stop running during certain time periods?
 
-`gtfs-via-postgres` optionally provides a **(materialized) view `stats_by_route_date` to help with such SQL queries. Use the `--stats-by-route-date` flag to enable it** in the generated SQL:
+`gtfs-via-duckdb` optionally provides a **(materialized) view `stats_by_route_date` to help with such SQL queries. Use the `--stats-by-route-date` flag to enable it** in the generated SQL:
 
 - If you run `gtfs-to-sql` with `--stats-by-route-date=view`, `stats_by_route_date` will be a "regular" non-materialized view. Use this option if you want to import the GTFS data quickly, and if you only query `stats_by_route_date` rarely or in time-uncritical scenarios.
 - If you pass `--stats-by-route-date=materialized-view`, the `stats_by_route_date` view will [be materialized](https://www.postgresql.org/docs/14/rules-materializedviews.html). Use this option if you need fast queries, and if you can tolerate significantly longer import times (3m for the 64mb 2023-03-05 SNCB/NMBS GTFS feed, 1h15m for the 540mb 2023-02-27 VBB GTFS feed).

docs/multiple-datasets.md

@@ -5,13 +5,13 @@ Using `gtfs-via-postgres`, you can import more than one dataset into a single Po
 As an example, let's compare two datasets from [Paris](https://en.wikipedia.org/wiki/Île-de-France_Mobilités) and [Berlin](https://en.wikipedia.org/wiki/Verkehrsverbund_Berlin-Brandenburg).
 
 ```shell
-wget -U 'gtfs-via-postgres demo' -O paris.gtfs.zip 'https://eu.ftp.opendatasoft.com/stif/GTFS/IDFM-gtfs.zip'
+wget -U 'gtfs-via-duckdb demo' -O paris.gtfs.zip 'https://eu.ftp.opendatasoft.com/stif/GTFS/IDFM-gtfs.zip'
 unzip -d paris.gtfs paris.gtfs.zip
 gtfs-to-sql --require-dependencies \
 	--schema paris -- paris.gtfs/*.txt \
 	| sponge | psql -b
 
-wget -U 'gtfs-via-postgres demo' -O berlin.gtfs.zip 'https://www.vbb.de/vbbgtfs'
+wget -U 'gtfs-via-duckdb demo' -O berlin.gtfs.zip 'https://www.vbb.de/vbbgtfs'
 unzip -d berlin.gtfs berlin.gtfs.zip
 gtfs-to-sql --require-dependencies \
 	--schema berlin -- berlin.gtfs/*.txt \

package.json

@@ -1,7 +1,7 @@
 {
-	"name": "gtfs-via-postgres",
-	"description": "Process GTFS using PostgreSQL.",
-	"version": "4.10.4",
+	"name": "gtfs-via-duckdb",
+	"description": "Analyze GTFS datasets using DuckDB.",
+	"version": "5.0.0",
 	"main": "lib/index.js",
 	"bin": {
 		"gtfs-to-sql": "cli.js"
@@ -22,8 +22,8 @@
 		"public transport",
 		"transit",
 		"convert",
-		"postgres",
-		"postgresql",
+		"duckdb",
+		"data analysis",
 		"sql"
 	],
 	"author": "Jannis R <mail@jannisr.de>",
@@ -32,12 +32,12 @@
 		"Magnus Burton <magnus.burton@me.com>",
 		"smohiudd <saadiq@developmentseed.org>"
 	],
-	"homepage": "https://github.com/public-transport/gtfs-via-postgres/tree/4.10.4",
+	"homepage": "https://github.com/public-transport/gtfs-via-duckdb/tree/5.0.0",
 	"repository": {
 		"type": "git",
-		"url": "git+https://github.com/public-transport/gtfs-via-postgres.git"
+		"url": "git+https://github.com/public-transport/gtfs-via-duckdb.git"
 	},
-	"bugs": "https://github.com/public-transport/gtfs-via-postgres/issues",
+	"bugs": "https://github.com/public-transport/gtfs-via-duckdb/issues",
 	"license": "(Apache-2.0 AND Prosperity-3.0.0)",
 	"funding": [
 		{