I see that many cities use legacy public transport. And non-legacy doesn’t show up well.
So, should I use legacy or not?
I see that many cities use legacy public transport. And non-legacy doesn’t show up well.
So, should I use legacy or not?
Log in to leave a comment
Discussion
Comment from histor on 14 June 2015 at 07:36
What do you mean with “legacy”?
Comment from tule00 on 14 June 2015 at 10:22
In JOSM, there are ‘legacy’ options (amenity=bus_station, railway=platform, railway=tram_stop, highway=platform, etc.) and normal options (public_transport=stop_position, public_transport=platform…)
Comment from Luciano on 14 June 2015 at 10:57
I tag using BOTH schema… the legacy schema seems to render better, but for my own “peace of mind” I prefer the new schema, also because my hope is to create data-driven transport maps. I have also introduced some aspects of my own schema.
Unlike in OSM, in OGF I don’t think we need to worry about enforcing a standard, and although I think trying to stick to OSM standards is important to the extent that that is what will be supported by future updates to the rendering engines, I think it’s best to focus on what “looks good” and is useful (i.e. for storing information).
You can examine how I have been mapping my subway and tram systems in Villa Constitución, Ardisphere map. Here is an incomplete, data-driven subway and trams map, supported using some of my own additional tags: RUTA-VC
Comment from tule00 on 14 June 2015 at 14:30
I also like the new one… So legacy is better for now, for rendering purposes? Thanks. And thanks for the map. Regards