Organic Maps creates unnecessary notes?

When I am clearing out notes in Norway and I often see notes created by Organic Maps where the mapper has already done the required change. Have others observed the same? I wonder if it’s a bug

Most recent: Note: 4657378 | OpenStreetMap

And the github of Organic Maps is now a “public archive”, so I can’t discuss it there or create an issue… :slight_smile:

1 Like
1 Like

In this case Organic Maps worked and was used as intended. The user created a note to request the deletion of the old outdoor shop and added the cafe.

The confusing thing is that another mapper then deleted the outdoor shop without closing the note (Changeset: 163738510 | OpenStreetMap)

I’ve seen that quite a bit with one specific Organic Maps user in Switzerland. Each of their changesets was accompanied by an OSM Note. I don’t want to blame the user, and thought I made a GitHub issue for it, but cannot find one on OM GitHub repo.

In general the unnecessary notes problem is/was caused by misleading description fields in the Organic Maps editor. I fixed that for Android in https://github.com/organicmaps/organicmaps/pull/6173, but iOS wasn’t changed yet.

The issue for iOS is [iOS] Rework descritions in the editor to match Android UI · Issue #9236 · organicmaps/organicmaps · GitHub.

Thanks, that would indeed explain it. However the user I noticed it on is using Android…

I don’t think this is going to improve unless there’s two fields:
One for describing what you changed (i.e., changeset comment)
One for describing things you don’t know how to change (i.e., note)

And maybe they should be totally separate functions within the app?

Did you see Organic Maps creates unnecessary notes? - #4 by map_per? Your sample note was not unnecessary as the was a shop that needed to be removed.

The user had 6-7 notes opened in Norway in the past weeks, I may have picked the bad example :slight_smile:

On this note they did the change themselves

Haha, this is getting a funny ride through Organic Maps bugs. This editor was and still is so buggy.

This example is not a problem with the UI, but a different bug (Editor: existing object is updated instead of creation of a new one · Issue #2298 · organicmaps/organicmaps · GitHub) that was fixed in the March release. The user did the same pattern as in the first node you shared (create a note to request the deletion of the old restaurant and then added the pub), but the new POI got merged into the old OSM node by mistake.

1 Like