Merci pour l'info! Bon weekend à vous!

J'ai reconnecté en attendant au cas où d'une mise à jour tierce à lieu.

Bonjour! QUID de ce chemin: way/58694957 ? Normalement il se connectait sur ce pt node/4878556371/ et allait jusqu'à ce carrefour node/940803529 or maintenant le track est une voie sans issue. Pas logique, pas conforme à ce que j'ai vu à chaque fois que j'y suis passé, ni aux données satellitaires (Strava heat map). Le chemin a été détruit? Ce qui me semble vraiment invraisemblable.

Please, do not make cliffs a closed round way, or they won't render in Mapnik and other maps. I think this is the case also with other elements. That's why i created all those rocky cliffs with 2 seperate lines.

Revert of changeset/48939009. User had created superMPs (MP with split perimeters). Contacted also the user via private message explaining the reasons and suggestion him a solution for further edits.

Usually if i don't, it's because there is a reason.

Example(s)?

¬¬

Well, elementary my dear RicoTricko! But see, the page is in Polish and not everything on that page, like images or some words, get properly or at all translated by online translators and i don't speak polish... Unless you expect people to understand polish, even if it's mostly spoken in Poland. Thank you for you precious time and comment!

Hello! I notice that you have plotted some paths with access=no, yet they make a loop, so you you must have accessed the path somehow unless you have some kind of high-end echo radar device. Like this one for example: way/292453603 I can guess some, like the path can't be used because tehre is a marge chasm on the way or large blocks of stone... Anyway, can you explain further, please? I'm curious and would like to understand the possibilities. :)

Hi! Please take note that you've added many empty lines that have no real application in OSM. Here is the report : http://tools.geofabrik.de/osmi/?view=tagging&lon=5.87910&lat=49.81454&zoom=12&opacity=1.00&overlays=node_with_short_or_long_key,way_with_short_or_long_key,ways_without_tags

Please, avoid this in the future. Thanks!

That makes totally sense! :) Thanks!

Hello! How come there are buildings inside the larger building?

I corrected already. But please check the Wiki since you have been contributing in OSM for a long time. Thanks!

Please make sure you are using the right tags for every element... Check the Wiki! Tracks are more adapted for rural zones since these ways are often unmaintained (no asphalt, partially or if asphalt they are dirty, have stones left by tractors, etc). They can also be flat and compacted, check tracktype description in Wiki

highway=track

tracktype=*

highway=service

Hello,
Please, check these nodes:
- node/4716252292
- node/4716252042
- node/4716252039
- node/4716252300
Nothing wrong?
That's not trail optimization, that's breaking the elements. :)
Since i don't see any deeper historic of those all the elements and you are quite new to OSM, i suspect the errors were introduced by you.
Please, correct all those nodes because like it is now those ways can't be routed anymore. And there are many more than those i listed...

Also, since you haven't done many edits, i would recommend you to second check backwards your previous edits.

If you need any help, please let me know.

Tous ces changements de "Tracks" vers "Paths" sont faux. Et cette Tertiary road en plein milieu du bois et entre 2 "Tracks"? C'est totalement illogique même sans connaitre le lieu en réalité. Je connais très bien ce bois, j'y ai grandi, je le visite régulièrement et j'ai enregistré la plupart des chemins sur OSM. Ca n'a rien à voir ou alors vous vous trompez sur les tags à utiliser. S'il vous plait, veuillez remettre les bons tags exactement dans l'état précédent et dans le future referez-vous à cette page wiki d'OSM pour vos contributions sur OSM highway=* . Sinon je devrai soumettre une plainte auprès d'un admin. Il est primordial que les gens se tiennent aux références pour connaitre exactement ce qui est représenté. Merci de votre compréhension!

Hi, This is not a MP but a simple relation to relate several parts of the remnants from a building in ruins, therefore the exact shape is unknown.
If you were rather reported here because of a building key being set on an unclosed line element well in my opinion this is a flaw of the tag itself.
By logic, the tag building=ruins should be allowed on unclosed lines since ruins are most often partial remnants, but that's up to the OSM community to vote first and then developpers to fix it.

By the way, in your edit you did not close any line and neither the line was self intersecting. According the history you just removed the building=ruins tag, still you left it on the other element of the relation. That's an inconsistent process between those 2 elements.

So in the end i added it back, since i think it's useful to know that the element was a building but all what is left is some walls without knowing what's was the exact shape.

Hello! Doesn't the "Camp de Lagland" actually include the "Champ de Tir" polygon, the new area you recently added and even isn't it bigger? I found this source, but it might be outdated: http://haminfo.be/
Not sure what is the situation of the zone today because i heard by a Belgian friend that the military budget has consequently decreased.

I know that Andy. But why should i be forbidden to use MPs to ease my contributions within iD while i respect in general real features and what's been ruled out in Wiki! This editor doesn't have the complex plugin tools that JOSM has! Using only polygons would slow tremendously the workflow since i would have to connect to each node, displace node by node or even disconnect and then reconnect node by node to create accurately or edit with better precision different. This used to drive me crazy and waste huge time in my early ages as OSM contributor. But since i work with MPs i'm the only one who has been contributing so much in such a short time. Just look all the southern region of Luxembourg for proof! I also cared to explain these reasons in my profile.