OpenStreetMap logo OpenStreetMap

Changeset When Comment
122031612 about 3 years ago

*correction: from way/39934144 and tweaked ways.

121626824 about 3 years ago

Hola Juan,

Has movido un nodo (y puede que estés moviendo otros también) por accidente, quizás sin saberlo.
osm.org/node/416872932

He movido manualmente el nodo (de vuelta) a su posición correcta.
osm.org/changeset/121826353

Este es un problema común con iD. Como ya deberías conocer los fundamentos de iD, considera cambiar a JOSM.
osm.wiki/JOSM

--

Hey Juan,

You have moved a node (and may be moving others too) by accident, maybe without knowing it.
osm.org/node/416872932

I have manually moved the node (back) to its proper position.
osm.org/changeset/121826353

This is a common issue with iD. Since you should already know the basics of iD, consider switching to JOSM.
osm.wiki/JOSM

94145421 about 3 years ago

osm.org/node/8120878114/history
This seems to be a service way with a pedestrian crossing, not[1] a footway with steps. See cars parked to the south.
[1]; (or no longer since Mapillary (2018))

Imagery: Latest available ortho geoportail.lu

121691997 about 3 years ago

Hey stadtvermesser,

In your twitter screenshot, I saw a vertical bar in front of the save message. Let me know if this is your mouse cursor and if you continue having your mouse cursor moved in front of the save message on your next edit. I have created a GitHub ticket just in case.
https://github.com/openstreetmap/iD/issues/9137

Regards,

Daniel

121672761 about 3 years ago

Related changesets (excuse them being seperate);
- osm.org/changeset/121672867
- osm.org/changeset/121672888

121581585 about 3 years ago

Hey B-Rabbit,

It's ok you added these parkings, eventhough they were partially obscured. However, you should mark estimations with a fixme tag (eg. "fixme=rough outline")

Just fyi; if you haven't yet, you should read the following wiki pages:
- osm.wiki/Good_practice#Mark_estimations_with_fixme
- osm.wiki/Armchair_mapping#Disadvantages_and_controversy
- osm.wiki/Verifiability#Verifiable_geometries
- osm.wiki/Accuracy#Refining_accuracy_wiki-style
(tldr; objects without proper source (imagery/knowledge/survey) preferably shouldn't be mapped.)

Regards,

Daniel

101394495 about 3 years ago

Hey Hiausirg,

At least two buildings seem to have been added with little or no adjustments to account for their actual geometry. They are both circular buildings, not anywhere near their current shape. As you should already know, this is considered poor quality mapping, which does not belong on OSM.
- osm.org/way/919717882/history
( in osm.org/changeset/101389279 )
- osm.org/way/919754078/history
Do fix these, please. And, if possible, review other changesets where this issue may have occured.

Sidenote: This is an old changeset.

Regards,

Daniel

74482352 about 3 years ago

This changeset has been reverted in
osm.org/changeset/121386013

Do neither redundantly reduce existing detail nor duplicate it. Make sure you zoom in enough so everything is clearly visible.

121296503 about 3 years ago

Hey Wetterhorn,

Why should this road be tagged as unclassified? It doesn't seem to connect two settlements, nor does it seem intended to be used by traffic as a throughway (surface etc.). Its main use seems to be a minor land access road, so highway=track.
osm.wiki/Tag:highway=track
( Ok, if turning left now we do get to a house using
osm.org/way/372944081/history but it is also a track..)

Why not the other way which does run along a house?
osm.org/way/46907712/history

(ofc a single house does not classify a road as unclassified or above usually, but that's not the point.)

Regards,

Daniel

121284496 about 3 years ago

Hey Arnout,

Als het adres klopt, tag je dan even bij op de adresnode, ipv apart?
osm.org/node/4131251505/history

Ter herinnering, je gaf een tijd terug aan Vespucci te willen gebruiken voor dit soort wijzigingen. Wss ben je dat onderhands vergeten ;-)
osm.org/changeset/113330246

Groet,

Daniel

121151418 about 3 years ago

Thanks for the reply. Yea, tagging such a thing can get slightly complicated..
osm.org/changeset/121182569
Here, I've made it a
bicycle repair shop + fee=no. You can choose to merge this with the indoor=room + room=workshop and remove these earlier mentioned tags, as most indoor workshop rooms are not also specified as a shop or similar, as access is usually restricted. Tagging it as a shop is somewhat tagging for the renderer -and search engines- as well, which is not appropriate.
(tagging only to have it show up.)

121151418 about 3 years ago

Hey Barry,

Re-tagged to bicycle repair station in
osm.org/changeset/121165272

You can find these and more on
https://mapcomplete.osm.be/
and complete their details ;-)

Name should only be tagged if signed. loc_name could be tagged if that is what it is called locally. Otherwise, it is a descriptive name, which does not add to the map.

Covered could be tagged covered=yes. With the available imagery it may be hard to indicate whether an amenity=shelter and/or building:part=roof as part of the building is available, as this would usually be mapped seperately.

Regards,

Daniel

119564272 about 3 years ago

Ok, j'ai re-ajoute le noexit ici. :-)
osm.org/changeset/121113315

120882369 about 3 years ago

Hey Casper,

Omdat ze er vlak naast liggen, zou ik het volgende aan het woongebied toevoegen:
- osm.org/way/266928346/history
- osm.org/way/297636389/history
- Achtertuin van
osm.org/way/297652171/history
- osm.org/way/297652342/history
Is er een bepaalde grens die je hebt aangehouden op deze plekken?

Er ligt verder nog een vlakje dubbel, dat je zou kunnen verwijderen:
osm.org/way/1023339986/history

Groet,

Daniel

119564272 about 3 years ago

Merci pour la réponse. Peut-être si vous l'abordez de l'autre côté, là où le sol est visible sur les images aériennes.

120936116 about 3 years ago

Beste jaap,

Als mede-mappers overleggen we met elkaar wat het beste past, niet of een enkele mapper wel of niet gelijk heeft.
Je zegt zelf DHL alleen als los punt in te tekenen, dus dacht ik dat ik wellicht iets over het hoofd gezien had en het in Nederland misschien wel gewoonte is om het zo te doen. Ik heb het dan ook nagevraagd.

Als het helpt zal ik in het vervolg wat meer uitleg proberen te geven, maar dit staat veelal al uitgelegd op de wiki-pagina voor deze tags; ik zou dan mogelijk overbodig lange berichten schrijven, wat niet nodig zou moeten zijn, om het met elkaar erover te hebben. Ik kan ook blijven doorvragen waarom je de ene tag wel en de andere tag niet gebruikt, maar ik merk nogal eens dat dit leidt tot verwarrende situaties, die ik graag zou willen voorkomen.

Ik hoop dat we er in het vervolg beter uitkomen samen.

120936087 about 3 years ago

Beste Jaap,

De workshops ging over training=yes, dus dat kunnen we ter zijde laten.
Ik vind shop=craft voor een hobby/handwerkwinkel persoonlijk wel passen, het is wel logisch dat een winkel voor een enkele hobby(/soort handwerk) slechts datgene verkoopt wat daarvoor nodig is. Je kan altijd nog in de beschrijving, of met een eigen tag, aangeven voor welke hobby er verkocht wordt.

119564272 about 3 years ago

Bonjour glacasa,

osm.org/changeset/121093961
On uitilise noexit=yes seulement en points noeuds.
osm.wiki/Key:noexit
J'ai aussi remarque que le chemin continue sur la droite des arbres en orthophoto.

Merci,

Daniel

120936087 about 3 years ago

Zelfde pagina... Goed om te weten dat de winkel in Oosterbeek nieuw is, dat had ik zo snel niet gezien.

Als je een reden hebt waarom shop=craft hier niet past, laat het me dan weten. Daar worden ik, en anderen die dit terug kunnen lezen, ook wat wijzer van.

121057438 about 3 years ago

(continuing from rendering support best practice);
Mainly regarding floating barriers, as they were not previously considered:

There are plenty of ways people can contribute to adding new features to [any map style] that do not involve having to write and test style changes.
- analyze practical use of tags; and
- document it (in a factually accurate way, disregarding if the observations help the idea of rendering the tag or not of course).
Such documentation helps any data users -also outside of map styles- who want to know how to interpret tags.
- Documenting how other maps render this tag (or in general for non-OSM maps; how they show and differentiate said tag's rendering from existing tags.