add DuckDB script for downloading monaco or a custom area from Overtu…

[bdon]

…re as Parquet file [#541]

@migurski @wipfli

This seems more minimal than demanding installation of https://docs.overturemaps.org/getting-data/overturemaps-py/ or another custom tool?

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[wipfli]

I think adding such a script is a good idea. I get the following error:

Downloading release 2026-02-18.0: 7.408446,43.722901,7.4405,43.752481 to data/sources/monaco.parquet
HTTP Error:
HTTP GET error on '/?encoding-type=url&list-type=2&prefix=release%2F2026-02-18.0%2F' (HTTP 400)
Wrote data/sources/monaco.parquet

[wipfli]

➜  overture git:(main) ✗ duckdb --version
v1.2.1 8e52ec4395

[wipfli]

I am not good at reading bash. I would prefer if we could hard-code the Overture release and the bounding box in the SQL. In the current state I would need to ask a chatbot or read about bash's syntax to know how to use this script.

[bdon]

What if we added help text?

./download-overture.sh --help
Usage: ./download-overture.sh [RELEASE] [BBOX] [OUTPUT]

Downloads Overture Maps data for a bounding box as a Parquet file.

Arguments:
  RELEASE  Overture release version              (default: 2026-02-18.0)
  BBOX     xmin,ymin,xmax,ymax in WGS84         (default: 7.408446,43.722901,7.4405,43.752481)
  OUTPUT   Output file path                      (default: data/sources/monaco.parquet)

Example:
  ./download-overture.sh 2026-02-18.0 -122.52,37.70,-122.35,37.83 data/sources/sf.parquet

[migurski]

The help text really improves it. They expire Overture releases quite quickly btw, I think keeping just two around at any given point. My Python predecessor to this script already does not work.

➜ overture git:(main) ✗ duckdb --version
v1.2.1 8e52ec4395

Do you still see this error if you upgrade to a more recent DuckDB? Version 1.4.x should work, and I recall seeing exactly your error when I was previously stuck at version 1.1.x.