Thanks again Ilya,

1 and 3 are also not too complicated, badly sorted relations.

2 is not so easy and does not fit everywhere: “platform_entry_only” has a lift whereas “platform_exit_only” does not have a lift (at Munich Marienplatz for instance) - difficult for wheelchair users and others who can’t use stairs or conveying steps.

Thanks, I’ll fix asap. Toni

Sorry for nagging …

• Angle between stops around “Grafing Bahnhof” is too narrow, 0 degrees (relation 1794891, “S-Bahn S4: Geltendorf => Ebersberg”)

  I don’t know what this means and how this should be

• Multiple platforms for a station “München Hauptbahnhof (tief)” (w43338429) in a route relation (relation 1782541, “S-Bahn S2: Petershausen => Erding”)

  This is OK, it is called the “spanisch solution”: single track between two platforms

    leave the train on the right
    enter the train on the left
  

• Route does not have a return direction (relation 1843976, “S-Bahn S8: Herrsching => Flughafen München”) and Route does not have a return direction (relation 1843975, “S-Bahn S8: Flughafen München => Herrsching”)

  hmm, first is the return direction of the second and vice versa and they are members of a common route_master

Thanks Zverik,

so it is more an indirect connection through a common stop_area relation. Well, not too complicated though, I will keep an eye on it.

Hi Zverik,

in Europe -> Germany -> Munich S-Bahn I can see many erros like

stop node 737174134 is not connected to a station in route (relation 1844089, “S-Bahn S20: Pasing => Höllriegelskreuth”)

What does this actually mean and how can I fix that, i.e. “connect a stop node/platform to a station?”

“public_transport=station” can be Node or closed Way (area) but not simple Way or Relation.

Any suggestion?

Thanks Toni

+1 (or even more) from my side.

I’ve been using JOSM for more than 10 years now - great tool.

@ClipArtJoel: try the “turnrestriction” plugin.

Toni

Thanks, but no. Still not working.

Hi,

4th try now and still:

http://hccvgi.informatik.uni-bremen.de/users/new

says the same when I click on “Start”.

Doesn’t work though:

“We’re sorry, but something went wrong.

If you are the application owner check the logs for more information.”

Regards Toni

@lonvia: really brilliant. I never assumed that you sort the routes. @Tomas Straupis: and it allows calculating the elevation profile.

Toni

I have the same problems with my 1GBit/sec DSL upload speed.

I do the following:

• prepare the images using mapillary Python script on my PC
• rsync the images to my Raspberry-Pi
• limit the upload speed to mapillary to 30KB/sec (by a traffic monitor on the Pi)
• use the mapillary Python scripts on Pi to upload to mapillary
• have a module for the RPI-Monitor to remotely monitor the progress

works fine for me. But for 5,000 images it might take 2-3 days to upload all images.

Wow, another oldie! Congratulations.

Good concern. Having stops and platforms is recommended, not mandatory.

I’ll change that to “all or nothing”: if there is at least one stop or platform, the full check for stops or platforms is started

• first and last node of the entire way have to be stop positions of the relation, the first and last stop in the list.

• stop positions have to be nodes of the ways.

• stop positions have to be ordered respecting the way, i.e if I follow the entire way, I will pass stop#1, stop#2, … of the list of stops (ignoring all other stop positions on the way of course)

Toni

Hi Polyglot,

good point and less error-prone. I try to change my habit towards this - may take a while.

BTW: my Perl script will also check the sequence: stop/platform, … stop/platform, way,… , way

The original idea for the script was to have a wiki page, listing the state of all routes of a region/operator/network, so that we can easily check and start JOSM for those who show problems.

Toni

… and another hint:

Exit the JOSM “relation editor” before splitting a way which is already member of that relation. Otherwise you will have to fight with conflicts.

Best regards Toni

Thanks to you too, Sarah for developing, hosting, maintaining “Waymarked Trails”. A great, the best place to search for trails!

And of course thanks to OpenTopoMap for adding this feature.

Toni

Hi Jothirnadh,

thanks for summarizing this. I have have stepped into this trap many times.

Also a good trap …

Downloading only the public transport relation and then try to split a way. This might end up in spoiling other relations that have not been downloaded so far.

Always download the surrounding data before splitting!

Another hint:

Have a look at JOSM ticket #14711: JOSM does not consider “oneway=yes” or “junction=roundabout” when sorting.

I’m currently working on a script for the analysis of public transport relations of a region/city/network. Kindly have a look at the Munich/Germany analysis: some parts are in German but errors (Fehler) and notes (Anmerkungen) are in English.

osm.wiki/M%C3%BCnchen/Transportation/Analyse

Best regards Toni

Yes, you can use maxspeed:forward= and maxspeed:backward= where the direction is according to the Way in OSM. Editors like JOSM will also take care of this if you reverse the direction of the way for instance. Cheers Toni

Ich habe nichts mehr gehört.

Yep: https://lists.openstreetmap.de/pipermail/bayern/2017-March/001333.html

Wir hatten vor Kurzem auf der Bayern-Mailingliste eine Anfrage vom ADAC bezüglich der Milestones auf den Autobahnen.

Die Stauberater auf ihren Motorrädern sollen OSM-baiserte Information über die Kilometersteine bekommen.

Der ADAC will die Information u.U. selber in OSM einpflegen :-)