Source for this changeset is actually: Maxar Premium imagery

Hi Tony,
Can you help me understand based on which criteria you changed the classification of Seoul Street? Both the built as well as the importance as a connector of Northern Tehran to the city's business center deem its classification as a primary road.
Best,
Claudius

Hi,
Thanks for your work to improve the map. You have stated that you traced some elements from Bing, but I cannot find any trace of those ways on the Bing satellite imagery in the West of Babol:
way/892186002
way/892186003
Also a secondary dual carriage way would be at a very odd location here. Can you validate that these ways exist?

I am terribly sorry for that. I was comparing Bing and Maxar in some parts and wrongly identified Bing as the newer imagery. I did revert the trunk road changes in changeset/96764761
I would appreciate if you would find the time to validate if it is correct again now.
Sorry once more for causing additional work.

I just reverted tagging at Spilve to follow the proposal.

Danke highflyer74 für deine PN. Ich bin gerade dabei, für mehr Konsistenz und vor allem Dokumentation der Tags für Flughafeninfrastruktur zu sorgen. Dazu Besuche ich virtuell zahlreiche Flughäfen global, um das Tagging besser zu verstehen und Korrekturen vorzunehmen. Ich habe meine Änderung in Bremen evertiert, da ich vor einigen Wochen noch nach einem anderen Schema angepasst habe. Ich freue mich über Input zu dem Proposal hier: osm.wiki/Proposed_features/runway%3Ddisplaced_threshold

I have just started a draft for a tagging proposal to tag both stopways/blast pads and displaced thresholds. I would appreciate if you would find the time to review and share your feedback:
osm.wiki/Proposed_features/aeroway%3Dstopway
osm.wiki/Proposed_features/aeroway%3Ddisplaced_threshold

On the stopway proposal discussion page there's already a discussion around whether to use the runway=* sub-tag scheme: osm.wiki/Talk:Proposed_features/aeroway%3Dstopway

Looking forward to hear your point of view and work towards creating a good proposal to present the wider OSM mapper audience.

Hi Jeroen,
I think the existing use of aeroway=runway is ambiguous and have therefor created proposals for two extensions to the airport infrastructure tagging:
osm.wiki/Proposed_features/aeroway%3Dstopway
osm.wiki/Proposed_features/aeroway%3Ddisplaced_threshold

On the stopway proposal discussion page there's already a discussion around whether to use the runway=* sub-tag scheme: osm.wiki/Talk:Proposed_features/aeroway%3Dstopway

Looking forward to hear your point of view and work towards creating a good proposal to present the wider OSM mapper audience.

Indeed stopways and runway displaced threshold elements are currently not rendered.

I am about to submit a tagging proposal around stopways and displaced_thresholds and based on that will work on getting the carto style on openstreetmap.org updated. The previous data tagging was incorrect as it suggested stopways were parts of the runway which they are not. This leads to misinterpretations e.g. about runway lengths.

Thanks for your understanding. I've updated the tagging in changeset changeset/91965792

Some good news: There is a relatively new tagging that allows to specify that this is a rubber tyres monorail by adding monorail=rubber_tyres - I have added this information to the infrastructure.

Hi,
In OpenStreetMap so far the consensus has been to use railway=monorail for most automated people movers also like the APM100 model used in Guangzhou: See also this quote osm.wiki/Railways#Types_of_railway_line
"railway=monorail - A railway with only a single rail, often inner city and above street level. Also used for monorail-like automated people-mover systems"

The thinking is that APMs have more in common with monorails (because there is one [==mono] central guiding rail on the track and rubber tires are just running on a road like surface) than light rail infrastructure (which is usually iron/steel tracks). I would therefor recommend to revert your tagging change and use monorail tagging instead.

Ouch. Thanks for pointing this out and sorry for my wrong tagging.

You're welcome. This Subway validator is a great tool to ensure the tagging is correct and complete: http://osm-subway.maps.me/portugal.html
I used that to spot that this was incomplete before.

Thanks. I've changed the tagging to emergency exit here: changeset/89777262

Please see my response at changeset/82826905

Regarding the layer=-1 for the tunnel=building_passage section: You are right, it's not necessary most of the time. In this example there are building:part of the Colorade Convention center that are partially crossing the tracks. The layer helps to reliably tell which element is below (tracks in this case).

Regarding the network: The original network name "Regional Transportation District (RTD)" is both full name and abbreviation. I've moved operator to the dedicated tag and use RTD as the network. Probably one could also use "RTD Bus & Rail" or even "TheRide" https://en.wikipedia.org/wiki/RTD_Bus_%26_Rail - I've decided for "RTD" since it seems to be the more commonly used branding and logo across.

There is no real documentation on which name to use for the network apart from "use best judgement for what is used on the ground" :P AndI find that a bit challenging in Denver. It's easier e.g. in Paris where it's just called "Paris Metro" or Leipzig where it's "S-Bahn Leipzig".

I didn't change any of the subway or light_rail tagging in this changeset, but just unified conflicting network tags between route and route_master relations.
Looks like you already cleaned up the infrastructure and ways.

Ach ja: "Weißrussland" ist als deutscher Alternativname immer noch hinterlegt.

Hallo, Zuerst: OpenStreetMap ist keine Landkarte, sondern Sammlung freier Geodaten. Eines unserer wichtigsten Empfehlungen ist hierbei die "on the ground"-Regel. Wir erfassen also Daten, wie sie vor Ort vorzufinden sind, bzw. verwendet werden. Bei Ländernamen ist es mit der Verifikation "am Boden" natürlich etwas schwierig. Aber dein Link zum AA bietet da schon einen ersten Ansatzpunkt. Weitere Beispiele:
* Länderseite "Belarus" des deutschen AA: https://www.auswaertiges-amt.de/de/aussenpolitik/laender/belarus-node
* Eigenbezeichnung der Botschaft der Republik Belarus: http://germany.mfa.gov.by/de/
* Eine nachvollziehbare Erklärung im Stern: https://www.stern.de/politik/ausland/belarus-oder-weissrussland--wie-heisst-das-land-wirklich--9378414.html
* Auch im deutschsprachigen Alltag hat der Begriff Einzug gehalten: Deutsche Post Länderseite: https://www.dhl.de/de/privatkunden/pakete-versenden/weltweit-versenden/land/belarus.html
Aus Respekt vor der Belarussischen Bevölkerung, die offenbar diesen Begriff bevorzugt halte ich es für angemessen, den modernen deutschen Begriff in OpenStreetMap zu hinterlegen.

Hi,
In this changeset and a bunch of others you re-tagged subway stop positions in metro networks across Iran into stations. This results in multiple station objects to be present in the stop area for these stations, e.g. see in the stop area relation for Shahid Bahonar: relation/7643627
Please review the documentation for public_transport=stop_position public_transport=stop_position and public_transport=stop_area at public_transport=stop_area

A public transport stop should consist of a stop position on the track/highway, optionally platform(s) next to the track and a station object (either as area or node). These are linked together using a stop_area relation.

I would appreciate if after reviewing the documentation you can restore the correct public transport tagging. The subway validator will help you on the right track: http://osm-subway.maps.me/iran.html

Please let me know if I can be of help to restore the tagging.

Best,
Claudius