An experiment in packaging location data
The aim of this repository is to:
- recommend new ways to publish location data on data.qld.gov.au
- provide feedback on the Open Knowledge Spatial Data Package Investigation recommendations to the Frictionless Data specification.
There are many tabular location datasets published on data.qld.gov.au, that describe location using:
- points (longitude and latitude coordinate pairs)
- boundary identifiers or names
These datasets could be linked to spatial boundary data.
A subset of point location datasets describe service locations, e.g. the locations of hospitals, schools and fire stations.
These are not published in a consistent way making it hard to combine the data. Some location datasets also include services available at the location and opening times, e.g. Transport and motoring customer service centres.
Some datasets are messy e.g.
- missing column headers
- column headers with no dataset
- inconsistent data types in columns
- markdown in columns
- html fragments in column to support a specific use case
In some cases these datasets drive the display of service locations on qld.gov.au. While it's great to see organisations using their own open data to deliver information, this should not be at the expense of others wanting to use the same information.
This repository for point data:
- collects service location point data from data.qld.gov.au
- analyses the headers in the source data and groups common headers to help design a template.
- suggests a template to capture service location and related data. The template uses the recommendations from the Spatial Data Package Investigation and explores refinements discussed on the Open Knowledge Forum
- repackages the service location data into point data data packages in line with the recommendations
This repository for linked boundary data:
- collects csv files with a link to boundaries and repackages the linked boundary data into data packages that reference spatial boundary data
This repository for non-spatial boundary data:
- collects boundary names and packages then so they can be used to validate boundary names in other csv files.
This repository for spatial boundary data:
- converts the data to GeoJSON
- packages the data into data packages in line with the recommendations
Based on the validation settings in goodtables.yml the tabular data is
As highlighted in the User Stories, Software is needed to implement spatial functions for discovering, validating and displaying:
As part of the work we will also explore leveraging existing concepts, data, and services, e.g.