I'm not sure if you're aware, but the launch of Apple Maps went poorly. After a rough first impression, an apology from the CEO, several years of patching holes with data partnerships and some glimmers of light with long-awaited transit directions and improvements in business, parking and place data, Apple Maps is still not where it needs to be to be considered a world-class service.
Maps needs fixing.
Apple, it turns out, is aware of this, so it's re-building the maps part of Maps.
It's doing this by using first-party data gathered by iPhones with a privacy-first methodology and its own fleet of cars packed with sensors and cameras. The new product will launch in San Francisco and the Bay Area with the next iOS 12 beta and will cover Northern California by fall.
Every version of iOS will get the updated maps eventually, and they will be more responsive to changes in roadways and construction, more visually rich depending on the specific context they're viewed in and feature more detailed ground cover, foliage, pools, pedestrian pathways and more.
This is nothing less than a full re-set of Maps and it's been four years in the making, which is when Apple began to develop its new data-gathering systems. Eventually, Apple will no longer rely on third-party data to provide the basis for its maps, which has been one of its major pitfalls from the beginning.
(Score: 2) by urza9814 on Tuesday July 03 2018, @02:18PM
Eh, I've used OSMAnd for Android for several years but have been looking at switching lately. Its main advantage is that its open source, otherwise...it hasn't got much.
Three major issues:
1) Routing can take FOREVER for longer trips -- the ones you're likely to want GPS for. Adding waypoints can help...but I've been in situations where I missed the turn, and it took literally twenty minutes for OSMAnd to reroute. Marginally better than Google Maps, which just silently crashes and you don't find out until you're sitting there going "Wasn't I supposed to be turning eventually?"
2) The search sucks. It doesn't accept a full street address. It'll get you *close* to your destination, which is usually good enough, but there's plenty of times where I have to search for a map elsewhere in order to find the nearest cross street so I can plug that into OSMAnd. And for things like airports, other GPS apps will get you to a specific terminal while OSMAnd just gets you into the main airport drive after which you're on your own (which doesn't bother me any, but it DOES bother whoever I'm bringing to the airport because they always insist I put "Terminal B" into the GPS...so we end up using their phone instead.)
3) The routing kinda sucks in general. I'll have a 100 mile drive on an interstate, and it tries to drop me onto local city streets every few miles because it thinks driving five miles at 35-55MPH is better than seven miles at 70MPH. It lets you choose either the fastest route or the shortest route, and I always keep it set on fastest. I don't even want to know what kind of convoluted route it would come up with if I told it to look for the shortest one instead...
On the plus side...after a few trips using OSMAnd, I'm now very confident that I can drive from Boston to Pittsburgh without any assistance...because last time I spent most of the trip ignoring OSMAnd telling me to do stupid things which causes it to reroute forever which causes it to still be rerouting when I DID actually need it so I had to figure out those few spots on my own. Although that's a VERY simple drive when you aren't blindly trusting an idiot GPS...