I've been trying to find some information on this IFOPT reference. What is not clear to me is whether 2 stops, each on a side of the street get 2 different IFOPT identifiers. What if there is a bus/tram and a metro station with the same name, do they all share the same IFOPT identifier?
If that's the case, maybe IFOPT should go on the stop_area relation, instead of the node. Jo 2013/12/17 Jason Remillard <[email protected]> > Hi Andreas, > > This all looks good. I have one more request. Could you update the > public transport wiki pages to include the ref:IFOPT tag. It looks > like you will be the first person using this tag. > > Thanks > Jason > > On Mon, Dec 16, 2013 at 6:23 AM, Andreas Uller <[email protected]> wrote: > > Dear List, > > > > I have taken into account your comments as well as those from the > talk-transit mailing list ( > https://lists.openstreetmap.org/pipermail/talk-transit/2013-December/001663.htmland > answers), so the following has changed since my last message: > > > > - No automated import, instead upload all platforms "by hand", so they > can be checked for plausability and the stop_positions and stop_areas can > be created right away. This way, one can say afterwards that all public > transport stops are present in OSM in the way they should be. > > - The global ID will be kept as ref:IFOPT, an internationally used ID > for public transport, all other IDs will be dismissed. > > - The is_in is dropped, instead the village in which the platform is, is > added as alt_name="Village Name_of_stop". > > > > I have made a test run in the city of Bruck an der Mur (chosen because > some bus stops were already mapped (by different mappers) and some were > missing) to look for any problems, which I didn't find (Changeset: > http://www.openstreetmap.org/changeset/19479901). > > > > I think this is a good way to improve the data in OSM. > > > > Andreas > > > > > > Gesendet: Donnerstag, 28. November 2013 um 04:09 Uhr > > Von: "Andreas Uller" <[email protected]> > > An: [email protected] > > Betreff: [Imports] Import of public transport platforms in Styria > (Austria) > > Dear List, > > > > We have received the position of all public transport platforms in the > Austrian province of Styria from the company responsible for managing > public transport ("Steirische Verkehrsverbund GmbH"). > > > > I have put together all information on the following page in the wiki: > http://wiki.openstreetmap.org/wiki/WikiProject_Austria/Import_Haltestellen_Steiermark(with > all relevant information in German and English). > > > > A short outline of the plan: > > All positions where no platform in a certain area (e.g. 100 m) around > the available points are present in OSM, would be imported directly into > OSM, probably using JOSM. All others will have to checked and merged > manually. This has already been successfully done with an import of all > doctors in Styria. > > > > A downside of the data provided is, that there are some platforms > included which are no longer used (they were used during a detour of a > route or the route has been dismissed). However, most of this disused > platforms will be in the capital city of Graz, where I and other users > know, which stops are the ones disused, so they can be excluded during the > manual import (all platforms in Graz should already be mapped, so this area > can be excluded from an automated import). In the end, there will probably > only be a handful of disused platforms in the end. On the long run, all bus > routes should be mapped; then it will be easy to find unused platforms. > > > > Also included on the wiki page is a suggestion on how to use the > provided attributes and turn them into OSM-key/value pairs. > > Here, a point is unclear to me: There are varoius IDs provided, one is a > "global, unique" ID for each platform (Europe-wide normed "IFOPT" number). > Should this be imported to OSM (as ref=* or something different?) in case > we later receive open timetable or realtime data which needs to be > connected to the stops? Or are there other ways to match timetable data to > platforms? These IDs are not visible to anyone standing at the bus stop and > I have not yet encountered them anywhere else than in that file - from what > I've read so far this is a strong reason not to include them. However, I > want to be sure we don't need them later. > > > > Any feedback is welcome. > > > > Andreas > > > > _______________________________________________ > > Imports mailing list > > [email protected] > > > https://lists.openstreetmap.org/listinfo/imports[https://lists.openstreetmap.org/listinfo/imports] > > > > _______________________________________________ > > Imports mailing list > > [email protected] > > https://lists.openstreetmap.org/listinfo/imports > > _______________________________________________ > Imports mailing list > [email protected] > https://lists.openstreetmap.org/listinfo/imports >
_______________________________________________ Imports mailing list [email protected] https://lists.openstreetmap.org/listinfo/imports
