Hi. OSM data is not only for deficient PT routes. Think about a user who would see 2 bus stops on the map where there is only one in reality. Or about a user for whom a search query in some app would produce two features at the same location when only one expected. Don’t you worry about renders, search engines, etc. which would stop working properly due to data duplication?
After all, PT routes in OSM are defined by sequence of stops added into route relations as members, and not defined by gtfs stop_id of any feed producer. — Alexey > 28 янв. 2021 г., в 14:45, Janko Mihelić <[email protected]> написал(а): > > čet, 28. sij 2021. u 12:19 Mateusz Konieczny via Talk-transit > <[email protected] <mailto:[email protected]>> > napisao je: > Is it one bus stop? Then it should not be mapped as two separate bus stops > due to artefact in gtfs data. > > If bus stop stop would have 10 bus lines, each with separate gtfs stop_id - > would we map 10 bus stops? > > I agree with that, I put semicolons for now. But if I put in a semicolon, and > some future router stops working and refuses to support semicolons, I'll be > forced to put in multiple stations. Maybe it's ugly, but it's not so ugly to > stop routers from working. There can only be 2 bus stops at most, at least in > this case. > > Anyway, I wanted to see if other transit mappers had the same problem, and if > we can get to a unique solution. > _______________________________________________ > Talk-transit mailing list > [email protected] > https://lists.openstreetmap.org/listinfo/talk-transit
_______________________________________________ Talk-transit mailing list [email protected] https://lists.openstreetmap.org/listinfo/talk-transit
