Goede punten, ja ten onrechte Obligue aangezien als de huidige werkelijkheid.

Even op de Luchtfoto 2023 Quick Ortho 8cm RGB gekeken maar het terrein lijkt niet meer in gebruik.

Changeset maar gerevert.

Thanks for correcting!

Did you open a thread?

Any conclusion?

Hi Alex,

I think it is not a good idea to remap the area's within Cayton Bay Holiday Village from landuse=residential to tourism=campsite because there are now 12 campings within the Cayton Bay Holiday Village camping.

osm.wiki/One_feature,_one_OSM_element

Emvee

Mwwh, oui, encore une fois tout à fait juste.

Il est probable que j'ai déjà édité relation/15691132 et que les choses se sont mélangées d'une manière ou d'une autre.

Corrigé également.

No, I did not mass change things, I did update about 15 campings one by one. Now only camp site in France are left and before changing those I did contact you.

Before that there were 109 campings mapped with tents=\d+ and capacity:tents was used 870 times.

Can you include me on the thread?

Merci, corrigé en changeset/139209787

Emvee

Bonjour,

Dans ce jeu de modifications, vous avez remplacé maxtents=X par tents=X.

Aujourd'hui, capacity:tents=X + tents=yes est utilisé pour cela, voir maxtents=*.

Que diriez-vous de changer à nouveau cela en capacity:tents=X + tents=yes ?

Emvee.

NB: Translated into French using deepl.com

Your edits typically adds spaces although that is according to ISO3166-2 although E.164 (without spaces) would also be fine. That is what made me question if removing the space after the ";" is logical.

I can live with it removed but I think the default should be not to remove it.

Good to fix phone number in general, one comment on a specific change.

I had a look at this change for this object, way/1189992346

It is changing "+31 6 30898025; +31 6 55334879" to "+31 6 30898025;+31 6 55334879" so (only) removing the space after the ";"

I do not think that is needed or better.

Hi Ator,

Good to update the map after your hike, I hope it was a nice trip. Always nice to see this kind of information mapped.

Some feedback on the changes itself.

* Please do not name a path as "new way 2023". If it is really a new path that was not there before, use "start_date=2023", a path with no name is also fine.
* The number of tents should go into "capacity:tents="
* These camp_sites look are likely without facilities. If so, it is good practice to add backcountry=yes, see backcountry=*

Greetings,

Emvee

I did further update the disused camping, see https://overpass-api.de/achavi/?changeset=138295256 (enable relations)

For tents not allowed, tents=no should suffice.

I would add a note indicating "anyone can access these camps and legally sleep there, BUT no fire and no tents are allowed." and if possible a link (website=) where that information can be found.

Yes, better to check what the legal status is.

Just realized, also "backcountry=yes" is probably relevant.

Zou zeker kunnen, @Peter_Elderson had aangesproken feedback richting rustpunt terug te leveren en dit komt er zeker in.

Het eigenlijke probleem is/was dat het rustpunt coördinaat dicht in de buurt van Engelenburgstraat 57 zit en de afstand tot het goede punt is 380 meter.

I think you are a local expert and Czech is not my natural language.

I used Deepl.com to translate https://trampskekempy.com/ and that made me think you are allowed to camp there, but like said, you are the local expert so I leave it to you.

access=no?

I did check https://trampskekempy.com/ but it looks to me normal people are allowed to camp here.

I guess also "caravans=no" and likely "shower=no"

Ja, je hebt helemaal gelijk.

Waar ik ben fout gegaan is op het huisnummer 57, maar net even gekeken, het is Engelenburgstraat 57, niet Koppelstraat 57.

Ik heb deze changeset terug gedraaid.
changeset/137439915

Why did you change traffic_signals:direction=forward/backward into raffic_signals:direction=both?

traffic_signals:direction=*