New POIs created at wrong location

[ghost]

As reported in the german OSM forum, new POIs are mapped to the wrong, yet same, position (51.28983/10.26113).
This behavior was previously reported in issue #439 .

A similar behavior was seen in #586 where a number of POIs were mapped to Taubenstrasse, Berlin.
Taubenstraße is the default location in the iOS app when GPS is not activated.
This can result in users mapping to Taubenstr. when not readjusting the marker to right position first.

[Xylakant]

It might be a bit a heavy-handed measure but we could log all API requests using these coordinates and block them/keep them for moderator approval.

[holgerd]

One OSM user mentions that the lay/Lon is close to the 'center of germany'. Wikipedia says it is not exactly. But maybe a bad default setting involved here?

[ghost]

@holgerd just checked the default location in the android app.
the location 51.28983/10.26113 is the default location in the android app, so if android users have not activated gps, their location will be shown at this location. maybe the mappers in question don't have gps activated and assume the marker is set at their current position?

[holgerd]

Update from the mobile app agency:

"Beim Anlegen eines neues POIs wird als default die zuletzt bekannte Location des Nutzers verwendet.
In dem Fall, dass gar keine Standortinformationen vorhanden sind wird eine Defaultstandort verwendet.
Dies ist die selbe Location die auch auf der Karte per default angezeigt wird.
Diese beiden Komponenten greifen hier auf die selbe Datenquelle zurück."

[wambacher]

"the location 51.28983/10.26113 is the default location in the android app"

so it's a problem of the CLIENT.
solution: Don't add POI with unknown position.

[Nakaner]

This bug has been open for almost a month. Could you please increase the priority of it?

[holgerd]

I just suggested in the OSM forum to do a manual monitoring of the given area instead of a bugfix right now:
https://forum.openstreetmap.org/viewtopic.php?pid=666652#p666652