Je corrige "noexit=fallen trunk"!

Salut Julien, le tag
"noexit=fallen trunk" est une erreur de manipulation de ma part avec JOSM. JOSM propose les dernières entrées dans un champ de clé et valeur pour travailler plus vite, mais je voulais plutôt enregistrer "note=fallen trunk". Ce n'était aucunement pour utiliser barrier avec noexit. ;)

Oui je le connais déjà le tag "barrier=log". Merci quand même pour me transmettre l'information mais je n'apprécie pas trop ce tag parce que il fait double emploi avec "barrier=block", qui est certes plus général en terme d'objet bloquant le passage. En plus, il n’apparaît pas encore sur les cartes des différents services... Il y a une spécificité que tu as peut-être déjà croisée: si jamais il s'agit d'un arbre avec branches qui barre le passage, généralement c'est assez large pour bloquer aussi les piétons, je rajoute alors le tag "natural=tree" et précise avec "note=fallen tree". Je ne rajoute pas le tag "access=no" parce que éventuellement piétons et cyclistes peuvent toujours contourner. Je ne le fais uniquement que lorsque ça devient très laborieux. Par exemple: osm.org/#map=18/49.75221/5.65651 J'en ai ajouté 4 mais de mémoire il y en avait certainement plus.

Je voulais discuter de tout ce ceci dans la page "barrier=log" depuis un bail, je vais le faire aujourd'hui.

Hello! Where is this tunnel passage? osm.org/way/588466396/history I went there yesterday but i only found a kind of passage between rocks, no trail though and even crowded with vegetation.

Area is mainly a private residential domaine, the fact that it includes a garden is secondary

Hi! It's forbidden to create temporary events. Also please avoid to create so many nodes for unnecessary precision which won't even be rendered since there is a limitation on the map zoom and also on straight lines. This adds useless data in OSM. I corrected. Apparently you are not new to OSM contributions, i'm astonished! Please, check OSM's wiki for the adopted consensus before creating/editing any element to avoid further spread of mistakes. Thanks for your comprehension!

completed partially the Sentier de la Haute-Sûre

Thank you for your feedback! Greatly appreciated! :)

The aborted upload and this upload got mixed up by JOSM and server... Looks like the server accepts/registers the data of a changeset even if it gets aborted.

noexit=yes tags need to be on the last node of the according way otherwise there will be no notification on routings if any third party service builds such feature and we don't know from which way it belongs if there are multiple ways going around.

I've done recent observations of this area and clearly you have messed up the positions of the paths... I admit there are many and it's somehow difficult to survey them all if we don't have the time but if there are hesitations, contributors shouldn't change the elements. In such complex network it's important to make things clear and right, so that people don't get mistaken or have to stop during their activity. I don't know why you had changed the paths and why you thought you were right, you hadn't even replied... Let's hope you improved your observations kills.

Forgot that if you create mostly dedicated sidewalks, you have also to integrate the hiking routes otherwise this will introduce conflicts.

Well, i don't know if you're wrong and i said i don't recall any change yet i'm unsure, that's why i'm asking you for the reason why the change. ;) OK I'll change it then since i don't recall any change, the image sat shows the crossway being on the other place and this GPS heatmap shows the path being different : https://drive.google.com/file/d/1GPWaGPfp1d4a2OM9qc4YQSI6fD665_a_/view?usp=sharing

* I don't know if you have much experience with these kind of mobile devices for a certain activity but these are the issues i have found when the maps gets overly detailed and complex.

There are consequences you may not realize when the map gets a certain level of complexity / many elements per "screen" :
- specially on mobile devices like dedicated GPS devices which use also vectorized OSM data, the mobile device is very much slowed down due to its limited processor not being able to handle the amount of data.
- also on the rendered image maps, the amount of detail gets over crowded. I find that we have to zoom in closer to make things clear, making us have a narrower map at the same time, even on a desktop computer i found myself zooming in/out several times when i created routes. In bigger cities it is OK and kind of obligatory because the sidewalks are much bigger and we need to connect specific ways like those going to tunnels in Royal Hamilius. In Lux city, you only see sidewalks on boulevards or avenues. Somehow, this issue is like the parking spots along roads you had created, they are rendered on the map, overloading it with "P" icons whereas someone is more interested in searching for a parking area. It would be OK if the area is rendered in a different color like in the past, but now on Mapnik it's also a shade of grey.
- the straightforward directions in terms of viewing the routing can get broken or lets's say zigzagged because some routing engines do not care about the type of way, they just take the shortest direction, which makes the routing jump from roads to sidewalks and vice versa. On bicycles or even running, if you look quickly on the GPS, the user may think he has to turn whereas he just has to go straight.

I don't know if you have much experience with these kind of mobile devices for a certain activity but these are the issues i have found when the maps gets

If you really have a good reason for creating so many independent sidewalk ways, then you have to make sure that any of it is interconnected to allow a routing choice. You had created so many isolated ways (islands) or contours not connected in a network fashion which forces the routing to go around certain directions instead of taking the shortest direction.

...add parking spots along the road with that element and tag otherwise the map will be overloaded with parking signs everywhere. We all know that often we can find parking spots along the roads. There is a specific tag, check here:
osm.wiki/Key:parking:lane
I already commented in one of your previous changesets that you should check the OSM's Wikipedia to respect the community consensus and you neither answered, cared, checked and have redone the same mistake.

You do not

Hi HAL, did the crossing that was here osm.org/node/321536339 (also visible on any Geoportail.lu image sat.) moved where you placed it here
osm.org/node/1555778496 ? Some months ago, i had a ride there and i don't recall any changes of the trail and your edit is 10 months old. Can you clear the situation please? Thanks! :)

Bonjour, où avez-vous trouvé les images sat. IGN de 2018? Celle dans la liste du logiciel JOSM date de 2014-2015 selon mes comparaisons avec d'autres images sat. aux environs de la frontière France, Belgique, Luxembourg.

Parc à Pokemon GO... HAHAH

Hello juminet! :) Est-ce que tu sais si cette zone est vraiment un parc osm.org/way/562891289 Gauvain Servais l'a t'agé en tant que tel et j'ai un énorme doute, je dirait plutôt que ce sont des espaces résidentiels privés. C'est un risque de désinformation/violation de propriété privée. Je lui ai fait note aussi d'autres erreurs (voir ses edits).