You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
CSV formats have been explored for use in applications which adopt the WESCML conceptual models, however, rules for their encoding is not captured anywhere currently other than use of the attributeNames for each featureType as column headings.
Meanwhile, there is a CSV specification called csv-geo-au (see https://github.com/TerriaJS/nationalmap/wiki/csv-geo-au) with the feature of spatially associating columns with region mapping names like State, or postcode. The advantage of doing it this way is support for the data in applications like TerriaJS instances and NationalMap (https://nationalmap.gov.au)
This issue is to explore documenting examples of WESCML data with the csv-geo-au specification.
The text was updated successfully, but these errors were encountered:
CSV formats have been explored for use in applications which adopt the WESCML conceptual models, however, rules for their encoding is not captured anywhere currently other than use of the attributeNames for each featureType as column headings.
Meanwhile, there is a CSV specification called
csv-geo-au
(see https://github.com/TerriaJS/nationalmap/wiki/csv-geo-au) with the feature of spatially associating columns with region mapping names likeState
, orpostcode
. The advantage of doing it this way is support for the data in applications like TerriaJS instances and NationalMap (https://nationalmap.gov.au)This issue is to explore documenting examples of WESCML data with the
csv-geo-au
specification.The text was updated successfully, but these errors were encountered: