This is an interesting observation. I'm a Japanese and naturally
interested in this issue.

We don't usually use accented characters. I mean we don't have such
characters in Japanese.
You may see accented characters simply because it's a way to tell you
the precise pronounciation.

Takakukō (note it should be ō rather than õ) is pronounced Takakukou
or Takakukoh. But it's really strange to use an accented o in such a
context as geocoding.
I recently did some geocoding for Japanese addresses (it gave me
fairly good coordinates) and found it funny when Tokyo is written as
Tōkyō in the returned address.

"shi" means city. Adding "shi" is like writing New York City instead
of New York. So better take it away.
Similarly, "cho" means town. You may see "Nasu-cho", which means Town
of Nasu.

I know I didn't answer your question but thought this might give you a
hint.

Thanks,


On Aug 21, 8:52 pm, David Cato <[email protected]> wrote:
> I was geocoding a few Japanese addresses a couple weeks ago and had
> mixed results using transliterated English addresses. The primary
> problems I encountered were accented characters and name suffixes.
>
> For example, given a street name of Takakukõ, the geocoder could not
> locate it, but dropping the accent on the last character (changing it
> to Takakuko) allowed the geocoder to locate it. The geocoder also was
> unable to properly locate (i.e., the geocoder returned a location but
> it was wildly off the mark) an address that used Naka-shi as the city
> name, but changing it to Naka worked.
>
> On Aug 21, 1:02 pm, cmohney <[email protected]> wrote:
>
> > My company's developing an English city guide for Tokyo, to be used
> > online and mobile. We've done so for about 50 other places worldwide,
> > but Tokyo will be the first non-English-speaking destination with its
> > own character set (i.e. kanji). Is it still the case that street
> > address info can only be mapped in kanji via Google or the API? If so,
> > have other developers/companies created services, transliterations, or
> > other ways around this we could use or pay for? Any suggestions or
> > advice appreciated. Many thanks.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Google Maps API" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/Google-Maps-API?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to