The Apple Maps Japanese product has always suffered from poor quality local data suppliers. The situation improved a little in late 2016 with the addition of quality public transit data from Jourdan, the same Japanese supplier for Google Maps.
If you go back over this blog and follow my recounting of the history of Google’s attempts at developing a quality mapping service, you will notice that they initially tried to automate the entire process and failed miserably, as has Apple. Google learned that you cannot take the human out of the equation.
Has Apple learned that lesson? In Japan the answer is no. Their product still fails because they don’t have (enough? any?) Japanese humans coordinating, vetting, and editing Japanese 3rd party data.
The problem is easy to see in the unnecessarily long and verbose Japanese place-names deployed everywhere, especially in schools, hospitals, clinics, police stations, fire stations, and similar public institution names. Long place-names obscure important underlying map detail and degrade map quality. In short they get in the way of what you are looking for.
Problem Place Names
Here is a standard view of Ikegami, Tokyo from Apple, Google and Yahoo Japan. Right away you see that Apple uses much longer place names.
The Japanese name for Ikegami General Hospital have been underlined in all three. Note the different text string lengths:
- Apple Maps: 15 kanji characters
- Google Maps: 6 kanji characters
- Yahoo Japan Maps: 6 kanji characters
The actual Ikegami General Hospital sign pictured below has the same six big bold kanji characters used in Google and Yahoo Japan maps. The extraneous information of the smaller kanji characters above the bold name is what Apple Maps uses in place-name.
The proper way to display extraneous information is where it belongs, the info card, not directly on the map.
Unfortunately the fix is not so simple as reporting a map issue. Even if you do submit a map correction, in my experience there is a 50-50 chance any correction will be lost when the data supplier refreshes the data set, or when Apple switches out the data point from different supplier.
The only way to fix the problem is the old-fashioned human way: an experienced team of editors who know how to intelligently edit Japanese map names for every situation.
It comes down to two questions: is this something Apple wants to do for the Japanese product, and is the effort sustainable?