Add Amsterdam traffic and ANPR camera positions to the Data Library

The City of Amsterdam's verkeersinformatiesystemen register lists where
its ~500 traffic and ANPR cameras stand, with type and asset number, but
publishes no pictures. That fits a Data Library dataset better than a
CCTV pack: the register answers GeoJSON in WGS84 with CORS headers, so
the entry fetches it browser-direct with no proxy code.

The register names no licence ("public unless stated otherwise"), so the
entry stays operator opt-in, as #251 had it. The dataset and the
position-only camera idea come from @Maher-Reven's #251, which this
replaces; the entry lists them as maintainer and in its attribution.

Co-authored-by: Maher Kurdi <[email protected]>
This commit is contained in:
Said TurkseverandMaher Kurdi committed 2026-11-12 12:26:45 +00:00
1 parent db80d82b8d
commit 11706a68cb
6 files changed
+48 -2

No files matched your search

+2
View File
@@ -12,6 +12,7 @@ import ledgerRows from './ledger.json' with { type: 'json' };
import akStatewideImagery from './entries/ak-statewide-imagery.json' with { type: 'json' };
import arStatewideImagery from './entries/ar-statewide-imagery.json' with { type: 'json' };
import azStatewideImagery from './entries/az-statewide-imagery.json' with { type: 'json' };
import amsterdamTrafficCameras from './entries/amsterdam-traffic-cameras.json' with { type: 'json' };
import bangorMe from './entries/bangor-me.json' with { type: 'json' };
import basemapAtOrthofoto from './entries/basemap-at-orthofoto.json' with { type: 'json' };
import bayernDop40 from './entries/bayern-dop40.json' with { type: 'json' };
@@ -119,6 +120,7 @@ import wvStatewideImagery from './entries/wv-statewide-imagery.json' with { type
/** Raw manifests in file-name order; the validated form is below. */
export const LIBRARY_MANIFESTS = Object.freeze([
akStatewideImagery,
amsterdamTrafficCameras,
arStatewideImagery,
azStatewideImagery,
bangorMe,