I don't really agree. I think we need suburb boundaries to be as accurate as we can make them at the time we create them, and not do a mass import leaving us with thousands of FIXMEs. Importing data we know is wrong at the time we import it is the wrong thing to do.
I've created manysuburb boundaries in Sydney after checking ABS, the GNB, the gazette, Wikipedia and council websites. They aren't perfect, but some are direct ABS copies, some amended with textual information available in other sources, and some abandoned because the information just isn't available in an open format and the ABS data is wrong. I have all the boundaries from ABS in OSM format in single file by suburb. If anyone would like a copy of the zip file, just drop me a note. I think Andrew has much the same on his website somewhere. You can pull each one straight into JOSM, and after checking accuracy, fixing coastline, etc, you can simplify/upload. Hopefully we will have access to the accurate and official suburb boundaries in Sydney in an open format sometime in the future (like we have for other cities). Then this problem will go away. Ian. On 21 April 2014 18:24, Ben Kelley <ben.kel...@gmail.com> wrote: > 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" <daniel.ocon...@gmail.com> 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 >> Talk-au@openstreetmap.org >> https://lists.openstreetmap.org/listinfo/talk-au >> > > _______________________________________________ > Talk-au mailing list > Talk-au@openstreetmap.org > https://lists.openstreetmap.org/listinfo/talk-au > _______________________________________________ Talk-au mailing list Talk-au@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk-au
