This issue is being tracked at https://github.com/openstreetmap/operations/issues/867

It uses C-MAP data. Attribution is provided in the C-MAP Terms of Service (ToS); https://appchart.c-map.com/tos.html

Additional details provided by Navionics / Garmin, with no mention of OSM. (Sidenote: Some Garmin products use OSM.)

Note, it is also possible to download maps for such devices, for example osm.wiki/AT5-OpenSeaMap-Chart_for_Lowrance_Simrad_B%26G

I personally find it a failure of the Code of Conduct if it is possible for a mapper to steadfast ignore all hints and attempts at communication on concrete mapping issues, without a working group intervening.

See https://wiki.osmfoundation.org/wiki/Data_Working_Group#I’ve_seen_a_problem;_what_should_I_do?

The working group consists of volunteers. They do check for suspicious changesets and discussions too, but they can’t cover everything. So, if you see something, report it -after contacting the user-.

YouthMappers have their own contact channels, some of which can be found on https://openstreetmap.community/ (which is kept up-to-date manually) You can always browse the internet if you find a group’s name, as most have a Facebook or Twitter page.

No problem.

After we talked about it, I asked for it to finally be added to the wiki. It’s been added here; osm.wiki/w/index.php?title=Quality_assurance&diff=2204097&oldid=2185601 (on the page “Quality assurance”, use ctrl+f if you can’t find it) I’ve suggested for it to be mentioned on Good practice as well.

No, this is because sometimes the developers saw that a tag was descibed as the “accepted” tag on the wiki or elsewhere and then thought it was the one to use. People complained, but initially they didn’t know better and eventually they might have been focused on other things. Anyhow, those (two) developers were fired/left the project (there was a high amount of issues being reported and only so many being fixed) and those issues still exist. People complain these are issues with the editor and the developers didn’t discuss or document the tag correctly, but it is actually an issue with the way the tags themselves are discussed and documented. For some issues -in general- people simply haven’t had the time to add in a pull request or fix the issues with their pull requests.

I am refering to this comment (which was given multiple times): “OSM suggested adding a healthcare=hospital tag, so I did that, too.” ( osm.org/note/2772009 )

These warnings/issues displayed in the editor (the app you edit with; when editing on the OSM website itself, you are using the iD editor) should not be accepted if you don’t know what the change means. In the case of adding healthcare=hospital, it isn’t really needed, as it essentially means the same as amenity=hospital or building=hospital -which are the important tags-, it just depends whether you prefer adding this tag or want to show support for this tagging scheme (how a certain feature is tagged). It sounded like you did this without looking at the tag’s description. Luckily, adding such a tag isn’t always harmful. There are, however, warnings in the editor which, if blindly accepted (without looking at what tags they add or what objects they change), can result in inaccurate (bad quality), such as when adding bridges and culverts, or incorrect mapping, such as when they add outdated tags (editors are not always using the newest tag).

- Get in touch with the OpenStreetMap community

Hey -and welcome- Sebastian,

Good thing you encountered a more complicated building. You can still work around this in iD, but once you get the hang of this editor, you can start working with JOSM and its plugins, which will help you to avoid some of these issues. For buildings with clearly non-square corners, you can leave it as is of course.

Be sure to submit feedback to the project’s github (otherwise, feedback and/or other contact info is usually listed in the app’s settings or on their website). First do look at the readme at the bottom and always check if a similar issue might not exist already. Then just hit “Add issue” and turn on notifications for replies, if they are not by default. https://github.com/streetcomplete/StreetComplete/issues/1913

1) already has an issue submitted Add clarifications / details for quests #1913.

2) should be available as a button in the bottom left, as explained in the FAQ (except for the author of this issue). I assume you did not see it, as did another user. If you have suggestions on how to improve visibility, feel free to create an issue.

If you don’t see the note under your Profile; osm.org/user/SebastianHelm/notes chances are it did not upload.

Regards,

Daniel

PS: Regarding the notes you responded to; (if you did,) do not blindly accept editor warnings in i.e. iD/JOSM. These are meant for experienced mappers who are familiar with these tags. In the case of healthcare=hospital it’s relatively harmless and also kind of pointless, since it is just another tag for the same thing (there’s multiple tagging schemes here, there’s no decision on which one to use).

ねえ地図山彼方、

どのアプリを使用していますか？ アプリにはサポート/フィードバック機能が組み込まれている場合があることに注意してください。

–

Hey 地図山彼方,

What app are you using? Note, the app may have a built-in support/feedback feature.