eclipse-sumo
use technical IDs of stops for GTFS mapping
some providers (for instance VBB) provide this ID (see ref:IFOPT e.g. in https://www.openstreetmap.org/way/398043251#map=19/52.434920/13.541183) and it is much more precise than mapping by name
https://en.wikipedia.org/wiki/Identification_of_Fixed_Objects_in_Public_Transport
Unfortunately, the quay identifier doesn't show up reliably in OSM.
For the linked platform, it seems to fit: de:11000:900193002:1:50 can be found in the GTFS: de:11000:900193002:1:50,S Adlershof (Berlin)...
However, the stop_position node (from which we built the <busStop>) only has a local_ref (3) which might be linked via the ref (also 3) of the platform that carries the ref:IFOPT.
Looking at another stop we only have a single IFOPT for both quays in OSM.
While the linked platform does only feature the ref:IFOPT for the entire station
ref:IFOPT | de:12061:900260004:1, which, according to my investigation, equates to the parent_station field in the GTFS records.
The relations making up the aforementioned platform as outer include the platform edges for Platform 3 and Platform 4 which do feature the ref:IFOPT of the particular platform by appending :50 and :51 to the end of the parent stations ref:IFOPT tag. These can than be mapped to the stop_position using ref/track_ref, or more extensively, additionally using the platform field in the GTFS data.
In my testing, some stations appeared that did not allow using ref:IFOPT directly.
Some stations only have the identifier of the local agency, e.g. Waßmannsdorf using ref:VBB
Have a list of identifiers identifying both platform and platform edge e.g. Thyrow
