So, I might spend an hour or two generating a few .osm files with imported data, so we can get an picture of what it looks like without doing an import.
https://github.com/CloCkWeRX/data.gov.au-qconnect-gtfs is a quick repo I added with all of the data extracted, and an initial.osm which shows every bus stop in QLD, roughly. On Thu, Dec 26, 2013 at 1:53 PM, Jason Ward <[email protected]> wrote: > Hi Daniel, > > Wow that is a lot. I looked at > http://taginfo.openstreetmap.org/search?q=qroti#keys and was considering > these as candidates for removal and replacement with the new gtfs data / > positioning. > > I presume nodes tagged without these key:value tags would come under the > standard duplication checks you've described. That said I expect that the > qroti tagged nodes could also be handled in the same way with an extra step > for this dataset to remove those key:value tags as a post process step (OR > as a pre-process step if that is more appropriate). > > Importantly, we'd need to update the qroti wiki page ( with information > about this import and the actions taken to remove this information). > > I've just signed up to the import list too. > > Re: Go-Sync I note that one of the assumptions that software operates > under is "that few bus stops have already been mapped in OSM for the city > served by the agency" with a bolded section directly under that assumption > in the Wiki noting "*GO_Sync should not be used in areas where the local > OSM mapping community has already mapped a substantial number of the > agency's bus stops."* > > > Cheers, > > Jason > > > On 26 December 2013 12:14, Daniel O'Connor <[email protected]>wrote: > >> >> >> >> >>> Bus stops sounds great although there is a stack load (thousands) of >>> existing Brisbane Stops imported from a no longer accessible source (QROTI) >>> https://wiki.openstreetmap.org/wiki/QROTI >>> (Here is a quick example: http://www.openstreetmap.org/changeset/739929) >>> >> >> http://overpass-turbo.eu/s/1RH - JOSM tells me there's 8,000+ >> >> >>> >>> I'm more than happy to help out with importing although I don't know >>> which way to jump on this because of potential route degradation the >>> removal of existing stops will bring with it but I also acknowledge that >>> the existing data is potentially incorrect given it is no longer maintained. >>> >>> If there is any way to review routes that have stop nodes >>> (highway:bus_stop and public_transport:platform) associated to them that >>> would be a good indicator of impact to these relations. >>> >> >> http://overpass-turbo.eu/s/1RI >> >> >>> If the ratio of stops to route relations is low enough then it would >>> be grounds for removing all stops and adding them back into the route >>> relations once the import was complete. Here is one of my local routes >>> with stops associated to it: >>> http://www.openstreetmap.org/relation/3316448 (The stops would be >>> removed from that route if my suggestion was adopted) >>> >>> I suspect that might be more damaging than not. >> >> Perhaps the best steps might be to try a tool like go-sync, or something >> that can example the GTFS data and find existing bus stops by lat/long. >> >> We'd want a few reports - OSM bus stops that aren't matched to a gtfs >> stop (manual deletion candidates), new gtfs stops, and of course, the ones >> that are a quick/simple match. >> >> Let's start a write up and take it to the imports list for further advice. >> > >
_______________________________________________ Talk-au mailing list [email protected] https://lists.openstreetmap.org/listinfo/talk-au
