'Swingma Parc'? Met een 'c' natuurlijk… Ik vond 'Vondel Parck' al pretentieus. :)

Does your router process CEMT=* without a waterway=*? That sounds like a bug.

Changing this specific one to planned:CEMT is fine, but it is valid for a mapper to use the lifecycle-prefix only on the top-level tag (waterway=* in this case) and set the rest of the attributes as they will be when the object is finished. (Like you wouldn't use planned:name either.) To prevent ghost-routes from popping up in your router you should probably require the presence of waterway=* in addition to CEMT=*.

Ah I see! That wasn't clear to me. In that case, it may be better to use lifecycle-prefixes for the main key (waterway) and leave the other ones as they will be once the canal is dug. You used waterway:project, but the common approach is to use these prefixes:

osm.wiki/Lifecycle_prefix

So here that would be CEMT=Vb with planned:waterway=canal (or proposed:waterway=canal).

If the canal is already being dug, you could use waterway=construction with construction=canal.

By leaving the attributes like CEMT and name in the state they will be once finished, other mappers who might update the canal as parts of it are finished won't leave them in the wrong state either.

Dank je.

Hmm, maar eens een blik werpen in het voorjaar. Ik kan on-line echt niks vinden met die naam (wat niets zegt natuurlijk, maar als ze ligplaatsen verhuren zijn ze wel erg verborgen).

Bitteschön!

Is CEMT=(Vb) (between parentheses) correct? This is one of the values that stands out in Taginfo:

https://taginfo.openstreetmap.org/keys/CEMT#values

Soll der Tagwert CEMT=! vielleicht CEMT=1 sein?

Weet je nog hoe je aan de naam 'Cascadehaven' in Wergea kwam? Ik kan die nergens terugvinden on-line.

See ISO 639-2:

https://www.loc.gov/standards/iso639-2/php/code_list.php

The Flemish predominantly speak and write Dutch, which has language code 'nl' (the Walloons usually speak and write French: 'fr').

If specifically Belgian/Flemish Dutch is meant, the country code specifier can be appended: nl_BE. 'BE' means Belgium in ISO 3166 (Alpha-2), but does not refer to any language. Dutch as spoken in the Netherlands is nl_NL. In OSM we don't do this for names though (it simply isn't needed).

'be' on the other hand (note the lowercase letters) simply means Belarusian.

The country codes on number plates have nothing to do with either standard.

Is it really necessary to keep making these huge globe-spanning changesets? Could you try to keep your changesets a little smaller?

Dat nummer 2 daar vlakbij de kruising wel bij de Wergeasterdyk hoort is een historisch detail; de weg die daar nu en op de Wergeasterdyk aansluit ligt er pas sinds de jaren zeventig (of iets later).

Cheers mate.

Read this part of the sentence you quoted very carefully: “AND you don't want to put that much effort into it”.

That means that if you don't want to, you don't have to draw the parking spaces. It means YOU don't have to map them. It does NOT mean that you should delete parking spaces mapped by others if they exist and are mapped accurately. That is plain and simple vandalism, and goes against all documentation on this topic and OpenStreeMap's conventions on proper edits.

You've completely misunderstood the meaning of the documentation.

What?? It is completely fine to map individual parking_spaces within amenity=parking. In fact, that is how you are supposed to map them. Removing these is vandalism!

From the wiki:

“Use amenity=parking_space to map a single parking space on a parking lot. Mapping parking spaces is an addition, not a replacement, to mapping a whole parking lot with amenity=parking.”

Read up on the documentation of tags before you break people's work! Just how many parking lots worldwide have you ruined with your edits by now?

Dank je!

Rondom Jellum is het leuk om het verschil te zien tussen de sloten westelijk en oostelijk van de Hegedyk. De sloten in de voormalige Middelsee zijn veel rechter. Geen idee hoe dat historisch precies zit, maar het valt op.

Hij is er weer. :)

Ik heb hem er nu als proposed ingezet:

https://www.wytgaard.info/post/werkzaamheden-voorbelasting-nij-wingerd-2e-fase-pier-thomasstrjitte

De straat is waarschijnlijk alvast in de BGT gezet na de naamgeving ervan. Hij sluit straks dus aan de westkant aan op het stratennetwerk.

Klopt, maar deze oversteekplaats is ingetekend als drie footway=crossing met daar tussen andere stukjes (hier footway=traffic_island, maar dat is niet vereist, als de footway=crossing maar onderbroken is).

Het lijkt dus wat vreemd, maar het zijn drie 'crossings' die elk geen 'island' hebben (wel tussen de crossings in). Als het als één footway=crossing was ingetekend was crossing:island=no fout geweest, maar hier klopt het.

Voor data consumers is het handig om te weten of een oversteekplaats erg lang is, en of daar gelegenheid tot wachten is. Je zou kunnen denken aan een navigatietool die rekening houdt met mensen die slecht ter been zijn en lange oversteekplaatsen willen vermijden. Als je de footway=crossing los intekent weet de data consumer exact hoe lang ze zijn. Wanneer dat niet mogelijk is (door lage resolutiebeelden bijvoorbeeld) kan crossing:island=* aangeven of de hele crossing ook onderbroken wordt, maar je weet dan niet of dat een beetje halverwege is of niet, of hoe vaak.

And again: fixing the tagging for natural=wetland is a good thing, but if you focus on that problem, then don't try to fix all sorts of unrelated warnings as well.

Your changeset history page shows that you have moved on to other areas and are ignoring my comments.

I have reverted this changeset in changeset/114191379 to undo the damage.

Please have a look at my comments, and stop applying fixes for the warnings ID shows without considering that actual data. I would still like to know why you deleted those parking spaces; there's nothing wrong with them, and if I hadn't been looking at recent changesets in the area they would have just been lost.

These parking spaces were deleted by you:

https://postimg.cc/bSd3WKWF

Will you revert your changeset?