[@OKau] Standard format for publishing CSV spatial data on data.gov.au - feedback, comments?

Rosie Williams budgetaus at hotmail.com
Tue May 5 08:01:06 UTC 2015

At the NSW State Library event last week, the topic of geo-coding came up for discussion due to the goegraphic aspects of many of the collections they are now digitising. Perhaps you could contact then to see if they have any feedback? They have just set up an email for the DX Lab DXlab at sl.nsw.gov.au

Rosie Williams BA (Sociology)________________________________________

 NoFibs.com.au - Open Data Reporter InfoAus.net - Founder and Developer 
 From: Steve Bennett [mailto:stevage at gmail.com] 
Sent: Tuesday, 5 May 2015 4:10 PM
To: OKFN-AU mailing list
Subject: [@OKau] Standard format for publishing CSV spatial data on data.gov.au - feedback, comments? Hi all,  By day, I work on National Map, which scours data.gov.au and other portals for open spatial data from state and federal open data portals (including local government data). It lets you choose which of these datasets to view on the map, primarily supporting quick assessment of value in a dataset or to answer basic questions. Now, we'd like to get a bit more systematic about harvesting CSV data. There are two main types:1) Point data described by latitude and longitude2) Administrative region described by reference to a known region such as a suburb, postcode, local government area (LGA), ABS statistical area etc. (Arbitrary line and polygon features are out of scope for now - they're better published as GeoJSON in any case). We'd really like to have an agreed standard that data providers can publish to, that is both supported by National Map (and other instances of Terria), but is a generally good, reusable format for data that will be used for other applications as well (including Excel, leaflet, CartoDB, QGIS...) ["We" in this case is NICTA, but I have a strong personal interest in this, as an Open Knowledge volunteer...] I'm tentatively calling it "Aus-Geo-CSV". I've started writing it up here:  https://github.com/NICTA/nationalmap/wiki/Aus-Geo-CSV-standard-(proposed) It's probably best to comment here. Things I'd particularly like to know:- feedback on which fields are widely in use (particularly any history around why that's the case)- feedback on any likely difficulties in following the standard- what else should be in there? Should we be encouraging .vrt files to be provided? Do we need to mention character encodings, line endings, quoting, etc?- has someone else already done this, and better? - are there other administrative regions that are important to support? (I'm obviously focusing the spec on what National Map can and will support, but it can certainly be broader than that.) To make commenting easier, I'll quote the important bits here, but please do read the whole thing. (It will probably have changed since I write this...) In data.gov.au, datasets that conform to this standard SHOULD be tagged "aus-geo-csv". The dataset MUST NOT contain CSV files that do not conform (but may contain other non-CSV files). Latitude/longitudePreferred field names: lat, lon [the only format currently supported]Accepted field names: latitude, longitude; lat, lngDiscouraged: x, y;Avoid: WKT (single column with data in POINT(-37.8 144.9) format); easting,northingEach MUST be a number in decimal degrees (EPSG:4326). Numbers SHOULD NOT be enclosed in double quotes. PostcodeA four digit postcode.Preferred field name: au:postcodeAcceptable field names: postcodeDiscouraged: poaFor greater precision, additional fields suburb and state MAY be provided. For example: postcode 3068, suburb Clifton Hill, state VIC.Local Government AreaBy name·         Preferred field name: au:lga·         Acceptable field names: lgaThe contents MUST be the short form of the LGA name, with no "City of", "Council" etc. For example: "Melbourne", "Greater Geelong". It SHOULD be capitalised like this.A separate state column MUST be provided, as LGA names are not unique across states. A separate au:lga_code column SHOULD be provided.By ID·         Preferred field name: au:lga_code·         Acceptable field name: lga_codeThis MUST be the 5 digit code described by the ABS. For example, Brisbane is 31000. Complete lists are available here.State·         Preferred field name: au:state·         Acceptable field names: state·         Discouraged: steThe contents MUST be the two or three-letter form of the state or territory ("VIC", "NT").KM: Case-sensitive?Other administrative regionsThese region types are also supported:·         sa4: "Statistical area level 4" (ABS)·         sa3: "Statistical area level 3" (ABS)·         sa2: "Statistical area level 2" (ABS)·         sa1: "Statistical area level 1" (ABS) [not currently supported by Terria]·         ced: "Commonwealth electoral division" (ABS)·         sed: "State electoral division" (ABS)·         ssc: "State suburbs" (ABS)·         cnt2: "Two letter country codes" (ISO 3166-1 Alpha 2)·         cnt3: "Three letter country codes" (ISO 3166-1 Alpha 3)For our latest news visit http://www.spatialvision.com.au This e-mail is privileged and confidential and intended only for the addressee(s). If received in error advise Spatial Vision by return e-mail and then please delete. Please consider the environment before printing this email. _______________________________________________okfn-au mailing listokfn-au at lists.okfn.orghttps://lists.okfn.org/mailman/listinfo/okfn-auUnsubscribe: https://lists.okfn.org/mailman/options/okfn-au

okfn-au mailing list
okfn-au at lists.okfn.org
Unsubscribe: https://lists.okfn.org/mailman/options/okfn-au 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.okfn.org/pipermail/okfn-au/attachments/20150505/e4bec594/attachment-0004.html>

More information about the okfn-au mailing list