Hi. My memory of the last abs import was that it was reasonably accurate, but not always totally accurate.
As such it is definitely worth importing from a data quality point of view. A way to deal with updates would be good though. Is there an ID that from abs for the boundaries that could be kept in OSM? Perhaps a tag like tiger has to show if the boundary has been edited. - Ben. On 21/04/2014 5:44 PM, "Daniel O'Connor" <[email protected]> wrote: > > > This is interesting. Looking at < > http://wiki.openstreetmap.org/wiki/Contributors#Australian_government_public_information_datasets>, > it seems ABS data should already be fine to use, and is indeed already in > use for suburbs. However from the import plan page < > http://wiki.openstreetmap.org/wiki/Import/Catalogue/ABS_Data>, the import > doesn't seem to have gotten too far, and also questions the accuracy of the > data. > > > > Given that many suburbs in NSW are currently indicated by nodes, would > an import of the ABS boundaries, however inaccurate, be better than nothing? > > Possibly, but to go further than the concerns in the abs data page - > these aren't suburbs, just approximations for statistics at a fixed point > in time. That means there are areas where the population count is low and > distorts the reporting area. > As you would expect that's more remote areas, but it does make the data > different from the gazetted suburb lists. > > If you had a process mapped out to migrate/redraw these when local data or > updated abs data is avail, it'd be a lot more valuable than a one time > import. > Given its been raised before, might be worth checking the imports and > talk Au archives for more nuanced opinions too. > > _______________________________________________ > Talk-au mailing list > [email protected] > https://lists.openstreetmap.org/listinfo/talk-au > >
_______________________________________________ Talk-au mailing list [email protected] https://lists.openstreetmap.org/listinfo/talk-au
