OpenStreetMap Forum

The Free Wiki World Map

You are not logged in.

#76 2018-11-24 18:10:34

SafwatHalaby
Member
Registered: 2017-04-10
Posts: 446
Website

Re: Automated incremental Bus Stop (GTFS) updates

anonymous_gushdan_mapper wrote:

Considering this, I don't see how keeping the "platform number" is useful to OSM in any way, and I suggest you ignore this in your automated imports, and only have one OSM node per GTFS stop_code.

Agreed. The "platform number" is currently ignored.

______________


The deletion of stops is slowly making the OSM dataset deviate from the MOT dataset. I propose preventing users from deleting stops. Non existing stops would have to be reported upstream to MOT, just like renaming. Comments?

As a reminder, here are the current conflict handling rules: https://wiki.openstreetmap.org/wiki/Use … or_mappers

I am essentially proposing replacing "You may delete a bus stop" with "you may not delete a bus stop directly. Contact MOT instead".

Offline

#77 2018-11-24 18:20:05

SafwatHalaby
Member
Registered: 2017-04-10
Posts: 446
Website

Re: Automated incremental Bus Stop (GTFS) updates

I just completed a bus stop update in #64848970.

This is a normal update, except that it's bigger than usual, because the last update was 4 months ago.

Click here to see the full history, or here for more info regarding bus stop updates.

Offline

#78 2018-11-24 21:52:56

Sanniu
Member
Registered: 2017-04-19
Posts: 27

Re: Automated incremental Bus Stop (GTFS) updates

SafwatHalaby wrote:

I am essentially proposing replacing "You may delete a bus stop" with "you may not delete a bus stop directly. Contact MOT instead".

"Contact MOT" is not enough - the exact web address/email should be added, otherwise this will be useless...

Offline

#79 2018-11-27 18:26:08

Reuven Kost
Member
Registered: 2015-08-18
Posts: 4

Re: Automated incremental Bus Stop (GTFS) updates

@SafwatHalaby Great job You do! Thank you smile
I believe the last changes are good improvements, relaying on MOT/GFTS data is more clever, although it has its own mistakes.

What about adding the bus numbers (Mispar Ha Kav) as a new tag to each bus stop?

It will give useful information for passengers and trip planners
The data is available as route_short_name in routes.txt in GFTS database.

Offline

#80 2018-11-30 19:42:33

dsh4
Member
Registered: 2017-06-24
Posts: 66

Re: Automated incremental Bus Stop (GTFS) updates

@Reuven Bus numbers shouldn't be mapped as new tags on the bus stops but as new relations of which the bus stops are members; see the schema: https://wiki.openstreetmap.org/wiki/Buses#Bus_routes

Your suggestion makes sense; in fact, I made a similar suggestion in this very thread some time ago; see discussion starting at https://forum.openstreetmap.org/viewtop … 96#p682596

Offline

#81 2018-12-07 08:22:08

SafwatHalaby
Member
Registered: 2017-04-10
Posts: 446
Website

Re: Automated incremental Bus Stop (GTFS) updates

To summarize the main objection raised by some of the mappers:

  • The MOT route data cannot be relied upon, so an import would include the stops a bus goes through, but not the exact route or the street names.

  • The route=bus relation mandates routes, so an import must invent a new relation and not use route=bus.

  • The import needlessly bloats the map and complicates the import/conflict resolution code without adding much practical value to OSM, "because importing the bus stop data without the roads and routes / because importing the data in any form" isn't of much use to OSM.

Sanniu wrote:

"Contact MOT" is not enough - the exact web address/email should be added, otherwise this will be useless...

Of course! The exact address can already be found at the page, and if the deletion change is ever added it would also link to the address.

Last edited by SafwatHalaby (2018-12-07 08:22:59)

Offline

#82 2018-12-07 08:30:59

SafwatHalaby
Member
Registered: 2017-04-10
Posts: 446
Website

Re: Automated incremental Bus Stop (GTFS) updates

SafwatHalaby wrote:

Since address duplication is dangerous and may cause unknown behavior in client address lookup, I have decided to move addr:housenumber to gtfs:addr:housenumber in the meantime, even before the discussion is finished. Please feel free to post your opinions on what should be done with addr:housenumber and addr:street.

Changesets: #60009323, #60010547

https://forum.openstreetmap.org/viewtop … 10#p704210

Pinging this old issue. Suggestions appreciated.

Last edited by SafwatHalaby (2018-12-07 08:31:30)

Offline

Board footer

Powered by FluxBB