Removed access tags in osm.org/changeset/53830517 due to lack of response

Removed access tags in osm.org/changeset/53830517 due to lack of response

Partially reverted due to lack of response: osm.org/changeset/53830720

Hi Udi, is there a parking lot here?

It is likely that there are remains below the dome.
.
I don't think there are visible remains.

SafwatHalaby_Bot

All consequent automatic GTFS updates will be performed from SafwatHalaby_Bots.

ddx_del: 1
ddx_nothing: 0
dxd_create: 5
dxx_update: 0
xdd_nothing: 0
xdx_delete: 16
xxd_create: 2
xxd_nothing: 2
xxx_update: 27536
update: 27536
update_touched: 0
update_not_touched: 27536
update_distanceTooFar_skipped: 0
update_distanceTooFar_ignored: 0
create: 7
del: 17
nothing: 2
touched: 24
total_newGTFS: 27545
total_oldGTFS: 27556
total_OsmBeforeRun: 27553
total_OsmAfterRun: 27543
New file download date (IDT): 2017-11-12_212149_Sun
Old file download date (IDT): 2017-11-09_215746_Thu

It may be easier for you to see the stops here: https://osmcha.mapbox.com/changesets/53722151 (You can then click a stop, click "osm" on the right, and then edit or delete it).

I reverted all your stop changes here: osm.org/changeset/53722151
.
Please delete the bad stops when you have the time. This revert should make it easier for both of us, because it decouples the tags, allowing easier deletions on your side and allowing the bot to run on my side.

Thank you!

Sorry. My bad. Apparently you've actually moved it to the other side of the road and not just randomly shifted it.

You've moved the bus stop osm.org/node/1803056935 25 meters. Is this based on some measurement or is it just to nicely fit the current road? Presumably, the MOT gtfs is usually accurate, and so I don't think randomly moving stops is a good idea.

Well done, but it looks like you added footways inside water

Hi, there are now two buildings tagged as 53. (The second one is on the right). Perhaps this is an error?

In other words: simply map what's on the ground exactly, without any ref hacks, and the bot will know how that is different from the GTFS, and we will report the differences. If something is not there, don't map it / delete it. If something is there, map it.

Hi Matt, the bot is very tolerant of most edits in general, but it cannot cope with refs that have ";".
.
I think there's only a single database that all apps draw from: the MOT gtfs.
.
I would suggest the following:
- Do not keep refs that do not exist. If a stop does not exist, completely remove it.
- If two stops exist and are really close to one another, make two close nodes, not a single merged node.
.
The bot would then properly understand your intentions and would mark the proper stops here: http://www.safwat.xyz/stops/.
.
I would then contact MOT and telling them about the error, hopefully they'll then fix it in the GTFS files and it'd be fixed for everyone.
.

Hi MattKaza,
You have merged 12 stops that have different refs, and you seperated the refs with a ";", so now we have 6 stops with two refs each. I am not sure this is correct tagging, and it's also absolutely confusing for the bus import bot. Could you unsplit these stops back into separate nodes?
.
Node list:
osm.org/node/1803052555
osm.org/node/1803053894
osm.org/node/1803068858
osm.org/node/1803033079
osm.org/node/1803033031
osm.org/node/1803053215

Or more simply: The bot marks suspect duplicates with fixmes. Those are the ones to be removed.

Next time please delete the one that does not have "ref" and no "source=israel_gtfs". You can also freely move the remaining one.
.
Thank you for the feedback.