… 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 :-)

Hi Bottlecap,

welcome on board.

It usually doesn’t take much time for an update of the map. Maybe you can use “reload” or “Ctrl-R” to clear the Browser’s cache.

Have fun Toni

Gut beschrieben und macht wirklich Sinn.

Im Prinzip sind diese oneway=alternating wie Fähren über Flüsse zu behandeln. Man könnte als auch im Umkehrschluss auch bei Fähren oneway=alternating benutzten, oder? Bei Seefähren entsprechend mit oneway=reversible? Analog mit Abfahr- bzw. zu erwartenden Warte-Zeiten.

Von Baustellenampeln muss hier ja nicht geredet werden, oder? Das sind ja temporäre oneway=alternating mit Betonung auf “temporär”.

Gruß Toni

Geht mir auch so. Auch ich lasse Bahnhöfe links liegen wenn’s um KeepRight, OSM Inspector, JOSM Validator oder ähnliche Qualitätssichernde Tools geht - mehr als schade drum.

No, it doesn’t seem to support turn-restriction relations.

See example,

http://graphhopper.com/maps/?point=48.099178%2C11.648083&point=48.093861%2C11.654584

where no_left_turn is set and drivers have to ride a bit further to the south and then do a 180° turn.

;-))

Netter Aprilscherz. Hoffentlich interpretiert das keiner als Handlungsanweisung.

Toni

Hi Joe,

do you think of something like this here?

osm.org/?mlat=48.064753&mlon=11.664235&zoom=18&layers=M

or

http://www.openstreetbrowser.org/N495120180?zoom=18&lat=48.06475&lon=11.66423&basemap=osb&categories=leisure[leisure_gastro]&layers=&overlays=

For your region, this kind of information is quite dense or at least missing at all.

Hmm, everyone is invited to add missing data to OSM, feel free to do so - it does not hurt ;-)

Toni

Hi ratorst,

"Platform Status Mostly running (Few services degraded due to maintenance)"

ist womöglich der Grund.

Toni

Keep building=yes and add

building:use=*

building:use=residential
building:use=garages
building:use=retail
...

see: osm.wiki/Tag:building%3Dyes

Salut,

c'est bon. If faut complete ca avec "highway=unclassified". Apres, on peut voir le ronde-point.

ToniE

Oops: links were delete (caused by $lt; and $gt; around it?)

1.) osm.org/go/0JAwSt0h

2.) osm.org/go/0JAzUbhkG-

What's "landuse=residential" for me?

Well, an area where there are predominantly houses, where people live.
It does not imply any administrative or other structure to my.
It can even stretch over several villages that are close to each other.
The boundary of a single village/city/... or community should not be
mapped by landuse=xxx, name=yyy.

Please have a look at: where I mapped an
area=yes, name="Wasserschutzwald Deisenhofen" in a forest (protected
area for water supply of Munich). barrier=fence is a different way that
uses the same nodes as the area.

But I also have a different example: 5 * landuse=residential, name=xxx

And I'm thinking about a single landuse (joined with the rest at the buttom)
with 5 * area=yes, name=xxx

Let's think also about: a community that includes residential, retail and forest
landuses inside their boundary. An area with name="Community of ..." including
these and maybe also boundary=civil and border_type=???.

BR
Toni

I use the same:

"landuse=residential" and "name=xxx"

and sometimes instead of that (if area inside a residential landuse)

"area=yes" and "name=xxx"

Hi und willkommen,

Problem? Nur Geduld. Das System (Mapnik/Osmarender) erkennt, dass was geändert
wurde und 'malt' die Seiten neu, aber nicht bis zur letzten Zoomstufe runter.
Spätestens am Mittwoch danach sollte alles durchgängig neu 'gemalt' sein.

Und es gibt noch den 'Data' Layer, oben rechts das '+' und dann
'Data' anklicken.

Gruß,
Toni