OpenStreetMap

SHARCRASH

Mapper since: November 16, 2013

 

Introduction

Hello, I'm from Luxembourg and i map essentially natural elements. I'm also interested by historical elements in nature such as former industrial zones, archeological sites, folklore... Sometimes specific urban elements I am aware of. My main motivations for mapping are exploration, mountain biking/hiking/trail running and share interesting places.

Feel free to contact me, i am opened to any discussion. If you have recommendations or you think that I am mapping incorrectly a type of element, please do not hesitate to tell me (kindly ^^). Nevertheless, most often i check OSM's Wiki.

 

Mapping & personal statistics

Areas on map and statistics.

Areas that I mapped extensively along other users are :

● Terres Rouges (Redlands) ins South of Lu (Lu / Fr side)

● South western region nearly filled up since i'm from that area (Lu)

● Grengewald (Lu)

● Petite Suisse (Lu)

● Mamerdall (Lu)

● some Bambesch (Lu)

Areas that i mapped nearly alone :

● former industrial zone Micheville (Fr)

● Bois de Butte (Fr)

Areas that i plan developing/detailing:

● Bois de Gaume (Be) & other Southern Forests/Woods

● North of Luxembourg

● North of Trier (De, meantime a lot of Germans have already done a great work)

 

Recommendations

● Before any edit, make sure that your background tiles (satellite imagery, topographies, data, etc) are correctly aligned. After having compared several sources, as a reference the Luxembourgish imageries seem consistent and efficient.

● Use tags (key=value) properly according what they refer in real (check OSM's wiki). Not using proper references counterfeits the map and misleads its use. If unsure add a "fixme" tag. Example: Imagine an accident in a forest, often rescues use tracks with an all terrain vehicle to reach the person, confusing paths and tracks is noxious. Imagine this may be used for you, one day...

● Services which provide the planning of route directions already add default access properties to all the types of highway tags. No need to add obsolete access properties which may mislead via the map tiles. Example: adding tag access=no (access to any means of mobility) and foot=yes on a highway=footway is unnecessary since by default this type of highway is an element only for pedestrians, this tag combination will grey out the way as inaccessible on the rendered map tiles and mislead users who will think it's not accessible at all.

● Access=no, is mostly used when the element exists but isn't anymore accessible by its default means of mobility and for anyone (think of a building in ruins or a way having collapsed rocks), access=private is accessible though only for the owners and eligible users, access=permissive is not officially a public element but the owner allows access until further notice.

● Apps... If you are experienced and make many complex edits, use JOSM. If you are beginner and make small contributions of areas or ways, use iD. Editing areas is tedious though (use JOSM + plugins such as Improve way accuracy & Merge contour instead). Potlatch is outdated.

 

Bugs

● 8 shaped MP, in other words several areas part of the same MP but touching themselves only at 1 node (hence the "8 shape" name i gave) some of the areas will sometimes not render, depending of some factors (size, tagging...?)

● area and line elements inside highway areas will not render, normal for highway lines but barriers etc should definitely be rendered, you can still make sure to render areas such as buildings by making the highway area as MP and adding an inner relation. My guess for this bug is that these highway areas follow the code structure of the highway lines, so they have also the highest priority of rendering over all other elements.

 

Rants (mmmmyeah)

● People not using tags (key=value) properly according reality. See "Recommendations" above why.

● Too many people contributing without precision up to a point you must wonder if some areas are worth trusting, even with simple polygons. My guess is that they don't want to disconnect/reconnect all the nodes which in iD and Potlach is tedious.

● Automations (JOSM plugins) and other importations without post processing: area intersections, awkward plotings (UE SOeS CORINE Land Cover is totally useless), large areas having a huge offset, buildings having multiple tiny polygons whereas it's a single building adds loads of futile data...

● People who do not check back the results of their contributions, introducing errors, OSMinspector is (was) your friend.

● Intolerant people not faithful to the open source philosophy, trying to forbid other users to use features extensively allowed in OSM, forcing these users to also use another workflow which may not meet their expectations, in my opinion this is unfair, dictatorial and discriminatory. I've experienced this problem with MP being discriminated in favor of simple areas but in iD it's HELL to work only with areas interconnected with other elements. If you feel the same way about anything, you're welcome to contact me.

● I won't comment anymore my changesets for 3 reasons... First, because some people think they are above the open source philosophy and force other users to use a certain workflow and tools to match their egocentric needs, so i want to impact this issue and make things more complicated for them. Second, I often make big edits so commenting them will not be pertinent anyhow. Third, many people don't do it anyway. Pessimist, no! Retribution, yes!

Cheers! :)