Government · head-to-head

City, Nantes Open Data vs Open Government, ACT

City, Nantes Open Data

Nantes Métropole's open-data portal runs OpenDataSoft; the stored record's `API Key` requirement is stale — a live keyless GET against the v2.1 Explore API (`data.nantesmetropole.fr/api/explore/v2.1/catalog/datasets`) returned full JSON catalogue metadata with a wildcard `Access-Control-Allow-Origin` header, and dataset exports in GeoJSON and CSV worked the same way with no key. An API key is only required for OpenDataSoft's write/administration endpoints, not for reading the catalogue's 590+ datasets.

Open Government, ACT

Data.act.gov.au is the Australian Capital Territory's open-data portal, run on Socrata; its catalog discovery API at `www.data.act.gov.au/api/catalog/v1` answers keyless GETs with full dataset JSON and a wildcard `Access-Control-Allow-Origin` header (the bare `data.act.gov.au` apex briefly redirects through plain HTTP before landing back on the `www` host over HTTPS, so link to `www` directly). Individual datasets are queryable through Socrata's SODA API in JSON or CSV, covering ACT government services, planning, and community data.

City, Nantes Open DataOpen Government, ACT
AuthenticationNoneNone
Pricingfreefree
FormatsJSON, CSV, GeoJSONJSON, CSV
CORSyesyes
HTTPSYesYes

City, Nantes Open Data supports 3 response formats, while Open Government, ACT offers fewer — pick City, Nantes Open Data for more integration flexibility.

More comparisons