Hi Ken, Franc's script did a good job of getting the common boundaries done. The adjacent boundaries share the same points. It isn't a difficult task to automate, and I completely disagree (with evidence from the previous load) that is is impossible to identify common boundaries and close off multipolygons with an automated load.
Perhaps it says something about our community that people seem ready to go and just import, even putting many hours into importing manually, but no one seems ready to lead a discussion about the best way of accomplishing the objective, and maintaining the data into the future, first. I think it is a failing. I don't agree that speed is a benefit over discussion and consensus. Ian. On 19 September 2012 11:57, Ken Self <[email protected]> wrote: > I've been manually loading up the suburb and LGA boundaries in Victoria from > ABS 2011. Figured that would be quicker than waiting for everyone to reach a > consensus on how to automate it and means it gets done "properly" > In doing a manual load I am ensuring the boundaries share common boundaries > with one another and the multipolygons close off properly. Those are pretty > much impossible to do with an automated load. Even a few manual errors creep > in but they are easily fixed. > > As I understand it from the ABS website > http://www.abs.gov.au/ausstats/[email protected]/0/a9421cdfb258e4a4ca2570ad00818509?o > pendocument they are supposed to be the gazetted boundaries > > There are a few errors in the boundaries but I think it's easier to fix > those once the main load is done. After that I'd suggest it's a manual > effort to make any further changes. It's not something I'd want to do again > from scratch. > > The question is what to use as a definitive source for corrections that is > ODBL compliant. I've found some maps on > http://www.vec.vic.gov.au/publications/publications-maps.html#5 but not sure > if we can use them to make corrections in OSM to the ABS boundaries. > Anyway - cross that bridge when we get to it. > > Cheers > Ken > > On 18 Sep 2012 16:40:02, Ian Sergeant <[email protected]> wrote: >> Hi Anthony, >> >> I don't think not knowing how to do it is the issue. >> >> More to the point is that we imported the 2006 ABS data, and >> it may have caused more problems that it solved. >> >> The boundaries correspond to ABS statistical regions. They >> aren't necessarily suburb boundaries, nor towns, nor governed areas. >> >> If we import them again, what do they represent? Do we >> update the manually? If the ABS release a newer data set do >> we replace the old? If so, is it even reasonable to import >> data we don't want to modify? >> >> Every data consumer would like to see more data in the OSM >> database to consume. However as data maintainers we have to >> balance their needs with our ability to manage an incredibly >> voluminous import and keep it maintained and accurate within >> the OSM database. >> >> We've removed the ABS2006 data, and it did a fair bit of >> damage in doing so. I'd like to think we had learned the >> lessons of that before embarking on the next one. Feel free >> to initiate a discussion. >> >> Ian. >> >> >> On 18 September 2012 16:24, Anthony <[email protected]> wrote: >> > Hello all, I would like to ask what the status of the suburb >> > boundaries is? >> > https://wiki.openstreetmap.org/wiki/Import/Catalogue/ABS_Data user >> > pnorman (on IRC) has offered to import this data if nobody >> knows how >> > to do it > > > > _______________________________________________ > Talk-au mailing list > [email protected] > http://lists.openstreetmap.org/listinfo/talk-au _______________________________________________ Talk-au mailing list [email protected] http://lists.openstreetmap.org/listinfo/talk-au
