I recently purchased some very rural land with a cabin that I put on AirBnB. The address is a different road than the driveway is and all the maps took drivers around 1 mile away with no way to find the actual driveway. I had to go through the process of fixing this on Google, Apple, and open street maps. OSM was by far the easiest and my updates propagated within minutes. Google was the second easiest but still took me deep into the “feedback” menu and then a week or two of waiting. Apple was by far the worst as I had to sign up for an Apple business account, upload incorporation docs, and then go through multiple rounds of back and forth with some approval agent.

▲

mayneack a day ago | parent [-]

Another option for apple would have been to just wait for a few months. They are downstream of osm but updates are slow. Likely your "propagated within minutes" was misleading. Almost no app, certainly not a mainstream app your customers might use, is reading osm live. They're all days to months behind on periodic batch updates.

▲

seb1204 a day ago | parent [-]

Months behind is not fair. Apps like Komoot, OSMAnd or CoMaps have monthly refresh cycles. Others are shorter and yes there are longer (mostly obscure) update cycles such as apple maps, Uber, https://transportnsw.info/

▲

mayneack a day ago | parent | next [-]

In my experience, the bigger the app, the longer the update cycle. They likely have a QA and integration process to deal with how osm combines with other sources. Something like osmand is basically just an osm wrapper, so they can be fast.

	▲	reddalo 19 hours ago \| parent [-]
		I think bigger apps are also slowing down updates to prevent vandalism from appearing to a wide number of users.

▲

technothrasher 15 hours ago | parent | prev [-]

I don't know what the heck map data Uber uses, but it always sends cars to a road behind my house which would require them to drive through a swamp and then up a heavily wooded hill to get here. OSM had the exact same issue, but I fixed it a couple years ago and it propagated just fine to the various OSM nav apps a long time ago. Neither Google nor Apple maps ever had the issue. But now DoorDash, which never before had an issue, last night attempted to send the driver up a gas line easement to get here. No idea what that's about. The entire issue appears to be that I'm on a long shared driveway and the various nav systems are afraid of it.