Hi,

This change is fully supported by Openstreetmap, which is the database. It was published on the changelog page: osm.wiki/Changelog

Third-party software, including OSM Carto, which is just a map that is featured on the website of Openstreetmap, not Openstreetmap itself, and the software you're using, should be updated to support new features.

Of course deprecated features can stay in the database after a change, because nobody has updated the feature. However in this case the highway tag had been updated to busway. This change incorrectly reverts this to highway=service. So a correct tag is being changed to a deprecated tag. That shouldn't be done.

The problem isn't whether this should be changed now, the problem is that a correct tag is changed to an incorrect tag.

Hello,

In the past the tag highway=service was used on busways, because there wasn't a better tag. This can be considered more as a workaround than proper tagging.

To resolve this, the tag highway=busway was proposed at the start of this year. This tag was approved in April, so it's the correct tag for busways for that time on.

These busways clearly meet the definition stated on the page of highway=busway, so they are supposed to be tagged that way, not with the former workaround highway=service.

Software using Openstreetmap data should be following the definitions in the Wiki. This page clearly states that bus=designated is implied for highway=busway: highway=busway

The problem therefore seems to be in the planning software, not the data in Openstreetmap. Therefore it's supposed to be resolved there, not by changing the Openstreetmap data.

The correct tag for busways is highway=busway. See highway=busway

The rendering problem on the OSM Carto map is known by the developers: https://github.com/gravitystorm/openstreetmap-carto/issues/4226

The correct highway tag for a busway is highway=busway, see the wiki page of this approved tag: highway=busway

Busway is a road type that buses can use. The tag even implies bus=designated.

Therefore I've restored the highway tag.

Because this reason, I've reverted this changeset and thereby I've restored the correct highway tag.

The correct highway tag for a busway is highway=busway, see the wiki page of this approved tag: highway=busway

So this changeset changes the correct highway tag to highway=service.

The rendering problem on the OSM Carto map is known by the developers: https://github.com/gravitystorm/openstreetmap-carto/issues/4226

Het water overlapt hier nu met het gras. In het water is natuurlijk geen gras.

Dit kun je oplossen met een multipolygoon. In JOSM kun je die gemakkelijk maken door zowel het water als het gras te selecteren en op CTRL+B te drukken.

From a more practical perspective: the member list of this relation (relation/2938) is very clear at the moment. There are 10 members, with for each the country clearly stated. If the name of the entire route would also be used on each segment, this list would be 10 times the same name, so totally unusable.

The current system with discriptive naming on the country segments is the established scheme for EuroVelo routes.

I think the way to change this would be to propose a new scheme for either the naming of EuroVelo route segments or the naming of route segments in general.

Changing a the naming scheme of just a few segments in the system is wrong in my opinion, as it makes the entire system inconsistent.

Dat verkeersbord is bord C6. Volgens de Wiki zijn dan de correcte tags:
- motor_vehicle=no
- motorcycle=yes
- moped=yes & mofa=yes
- traffic_sign=NL:C6

osm.wiki/NL:Overzicht_Nederlandse_Verkeersborden#C:_Geslotenverklaring

The segments of the route are tagged in a consistent way:
EuroVelo 6 - Atlantic-Black Sea - part <country>
This is the way all segments of EuroVelo routes are tagged, so it's inconsistent to deviate from this for one route segment in one country.

This is a single segment of the route, not the entire route. The full name can be found on the superroute, that contains all segments of the EuroVelo6: relation/2938

Dit eenrichtingsverkeer geldt niet voor (brom)fietsers en bussen volgens de bron. Ik heb die uitzonderingen toegevoegd.

Op dit moment staat het oude gebouw nog in de BAG. Er zijn ook nog geen sloop- en bouwwerkzaamheden. De tagging als proposed:building (toekomstig gebouw) lijkt me dus de correcte manier.

Dit wegsegment: way/417392665 heeft drie rijstroken, niet twee. Er hier zijn twee voorsorteervakken rechtdoor en één rechtsaf.

Als ik de website lees, dan heet het gebouw '1221', waarin huurwoningen komen. Het gebouw heet dus niet 'Huren in 1221', zoals nu is ingevoerd.

I think you should ask the original mapper:
changeset/99669124

The road was originally mapped with vehicle=no, bicycle=designated. So I think motor_vehicle=no is the correct access tag.

Hallo,
De naam 'Van Emdenpad' staat in de BGT op dit pad. Aangezien het niet aansluit op de rest van het pad en er volgens jou waarschijnlijk geen straatnaambordjes staan, zal ik de naam weer verwijderen.

Bedankt! Ik heb het verbeterd.

Er waren erg veel routes hier. Deze was ik blijkbaar vergeten.