We are experiencing a critical issue with location data in reports exported from Scalefusion. Scalefusion support has confirmed the problem is not coming from their side and has indicated the issue may be related to OpenStreetMap (or the geocoding service) used by our systems.
Problem: exported location reports sometimes show an incorrect postal address while the GPS coordinates and map pin are correct. This inconsistency is appearing in multiple user reports and is impacting operational reporting.
Impact: this affects location-based reporting across teams and creates risk for operations that rely on accurate addresses. We request this be treated as high priority.
I suspect that the OP here has been sent to this forum by the support desk of a third-party organisation, and is actually asking about that third party’s use of OSM. It would be helpful if answers could explain a bit about what OSM is and politely ask a bit about what the third party is doing.
Dear @ASupport,
OpenStreetMap is a collaborative spatial database of our world. If you have any examples of wrong data, we invite you to fix it, as everyone can do it. Simply go to osm.org, login with your account, zoom in to the area with the error, and click on the edit button on the top bar.
If you have issues when trying to fix the data, please report in this thread with more information, so we can help you in a better way.
note that in addition to other raised comments: you mention no specific info which address are missing/wrong and they expected location, which makes impossible to take any specific action anyway
If the “postal address” is the result of reverse geocoding of GPS coordinates using Nominatim, then please be aware of how this works: Reverse - Nominatim 5.2.0 Manual
is that OSM doesn’t have such a “priority system” for edits. It relies on people voluntarily mapping stuff when they can, and that means they can also map what they can - sometimes the imagery quality is too low to make out detail just by looking around.
I’ve hidden a bunch of posts that were reported as being offtopic because they didn’t really contribute toward either answering the original question here or even try and tease out what that was.
With regard to the latter part of that, we know that the OP is a customer of Scalefusion, and that Scalefusion is a UEM system (also called Mobile Device Management and various other things). Personally I’m familiar with various UEMs/MDMs via $dayjob, but alas not that one. However, we know that the problem is related to geocoding.
What we don’t know is whether:
Scalefusion is using OSMF resources (website, OSMF-hosted Nominatim or something else)
Scalefusion is using OSM data and is hosting Nominatim (or perhaps something else) to do geocoding.
We also don’t know the journey that the OP took through Scalefusion’s support and how they got here - it may be that the people best placed to answer the OP’s question are within Scalefusion’s helpdesk, but we don’t know that until we know what they actually said, and a public forum might not be the best place for that conversation.
A public forum might not be appropriate for example problem data, since it likely refers to employee physical locations.
What @ASupport might be able to provide is an “anonymised” example - choose a real physical location that does not correspond to an actual employee location and give an example of the “the sort of thing that the Scalefusion report gets wrong”. Screenshots would also be useful if they could be cropped in such a way as to not show anyone’s personal data or business sensitive data.
