Difficulties
============

## Australia - REST API via data.gov.au

Data produced by Geoscape AU
Locality boundaries:

https://data.gov.au/api/v0/search/datasets?query=locality%20boundaries

There is a wild difference in catalog for the locality/boundary:

- https://data.gov.au/dataset/09276b8e-1447-4892-99a3-0f67c421f327/resource/95be2deb-2050-4ef3-b549-4e8a83421bfc/download/ot_locality_polygon_shp.zip
- https://data.gov.au/data/dataset/af33dd8c-0534-4e18-9245-fc64440f742e/resource/4d6ec8bb-1039-4fef-aa58-6a14438f29b1/download/vic_locality_polygon_shp-gda2020.zip
- https://data.gov.au/data/dataset/af33dd8c-0534-4e18-9245-fc64440f742e/resource/3b946968-319e-4125-8971-2a33d5bf000c/download/vic_locality_polygon_shp.zip
- https://data.gov.au/data/dataset/bcfcfc9a-7c8d-479a-9bdf-b95ca66ad29a/resource/8937ec5b-69d5-4d8c-86e0-687e61a02903/download/sa_loc_polygon_shp_gda2020.zip

Why did not data.gov.au implement named resource locations and enforce that? Good question.

I would love to see enforced semantics like:

https://data.gov.au/data/provider/geoscape/set/boundaries/locality/nsw/[gda/[94|2020]|geojson]]

## New Zealand

## ..