For what it's worth an 18 wheeler carrying gas crashed into an overpass which caused the entire thing to be torn down over here. Overpass has been closed for months yet still remains open on Apple Maps.
I reported the issue to both Google and Apple at the same time. Google had it fixed within hours. Apple has yet to fix it.
Additionally here is a video from the department of transportation showing them blowing the bridge up to prepare for its rebuild[0]. Still the bridge remains open on Apple Maps.
For what it's worth I have 6 open bug reports on iOS submitted around Beta 2 and 3 of iOS 8. All 6 bugs made it to the 8.0 GM release, the 8.0.1 update, and the recent 8.1 release. All tickets remain open and have no acknowledgement from Apple.
I'm convinced Apple has either given up, or is simply ignoring all requests from my account.
Nope. I reported the fact that what's shown as a coffee shop here in Melbourne (Australia) is in fact a parking lot, and has been forever, and couldn't feasibly be a coffee shop under any circumstances due to its location.
Two years ago.
And it's still a coffee shop. Corner of Flinders & Spring, if you're interested.
In my experience, data issues aren't taken seriously at all, before you want to talk about where the responsibility of having accurate data lies.
It took 3-4 months to maybe fix an issue I repeatedly reported about Maps thinking that a location was in the middle of a highway. Yesterday I checked that the suggested route was correct but Maps decided to reroute to the "shortcut" when I was nearing the destination. Depending on how you enter the destination (direct address vs search bar result) it's iffy.
The address is a 6 month old hospital and ER. The first time I routed there to go to the ER my eyes almost popped out of my head at the suggestion of a 2-3 mile detour by getting back on the freeway. Later on I looked at Yelp and saw a reviewer talking about how they took that detour by accident on their way to the ER too. I hope this stupidity didn't end up hurting anyone seriously.
My favorite Apple Maps stupidity, as of a couple of years ago: look up "hospital" while driving northbound on I-405 into Bellevue, WA, and it will give you a massive list of every vet clinic and animal hospital in the area. The nearest actual hospital will be buried in the list somewhere.
Hopefully they've put some new people on this product, post-Scott Forstall. If it's still that badly broken, then it's about time for lawyers to get involved.
His point is that he shouldn't have to report it. It's a major city. If they are going to make a product that competes at the highest level, they ought to have something in place that looks for, while rare, street changes in major cities.
It doesn't seem like it should be that hard. Calculate the percentage of traffic that uses a street in each direction. If more than 10% of it is going in the opposite direction on a one-way street, flag that street for human review.
It took over a year to move a local city to the right island. (Langley, WA, really on Whidbey Island was listed on Hat Island, a private island with no roads)
This actually really bugs me as a Crashlytics user. I'd much rather they stop trying to bundle it themselves and just list these so they can be used by the already established package management out there - Gradle/Maven and Cocoapods. Having to install an IDE plugin just to get a library feels like the dark ages.
Releasing libraries tied to IDEs sound like an absolute nightmare to have to maintain over time. Package managers exist for exactly this reason - I have no idea how anyone at Twitter could have ever thought this was a good idea.
I wonder if this could be used to allow ASL input to a computer - automatic transcription of conversation and such? I think it really depends on how accurately it can sense actual finger position rather than just motion in that muscle
As an example, this would be a constructive way of saying something similar in my opinion, though some may still find it close to the line:
"I have found my own solution to this problem that involves piping these commands together, so this project isn't for me, but good job for creating a simpler solution for people who don't necessarily need control over every step of the solution, but rather just care about the final result."
This indicates why it's not useful for the poster, but it acknowledges that not everyone is a CLI genius and that the new solution could work for people with different tools requirements.
