title: Google Maps Geocoding API: How to get city/region names *consistently* in English or local language?
body: <p>When I make the following request (note the <code>language=en</code> part!) with latitude &amp; longitude for Warsaw, Poland,</p>
  
  <p><code>https://maps.googleapis.com/maps/api/geocode/json?latlng=52.23,21.01&amp;language=en</code></p>
  
  <p>I get a result list which includes the following:</p>
  
  <p><strong>Result 3 (neighborhood):</strong></p>
  
  <pre>
      {
              "address_components" : [
                 {
                    "long_name" : "Śródmieście Północne",
                    "short_name" : "Śródmieście Północne",
                    "types" : [ "neighborhood", "political" ]
                 },
                 {
                    "long_name" : "Śródmieście",
                    "short_name" : "Śródmieście",
                    "types" : [ "sublocality_level_1", "sublocality", "political" ]
                 },
                 {
                    <b><i>"long_name" : "Warszawa",   &lt;-- city in Polish</i></b>
                    "short_name" : "Warszawa",
                    "types" : [ "locality", "political" ]
                 },
                 {
                    "long_name" : "Warszawa",
                    "short_name" : "Warszawa",
                    "types" : [ "administrative_area_level_3", "political" ]
                 },
                 {
                    "long_name" : "Warszawa",
                    "short_name" : "Warszawa",
                    "types" : [ "administrative_area_level_2", "political" ]
                 },
                 {
                    <b><i>"long_name" : "mazowieckie",  &lt;-- region in Polish</i></b>
                    "short_name" : "mazowieckie",
                    "types" : [ "administrative_area_level_1", "political" ]
                 },
                 {
                    "long_name" : "Poland",
                    "short_name" : "PL",
                    "types" : [ "country", "political" ]
                 }
              ],
           [...]
           "place_id" : "ChIJjaxkh4rMHkcR1lza9qbbnrU",
           "types" : [ "neighborhood", "political" ]
      }
  </pre>
  
  <p><strong>Result 4 (sublocality_level_1):</strong></p>
  
  <pre>
        {
           "address_components" : [
              {
                 "long_name" : "Śródmieście",
                 "short_name" : "Śródmieście",
                 "types" : [ "sublocality_level_1", "sublocality", "political" ]
              },
              {
                 <b><i>"long_name" : "Warsaw",   &lt;-- city in English</i></b>
                 "short_name" : "Warsaw",
                 "types" : [ "locality", "political" ]
              },
              {
                 "long_name" : "Warszawa",
                 "short_name" : "Warszawa",
                 "types" : [ "administrative_area_level_3", "political" ]
              },
              {
                 "long_name" : "Warszawa",
                 "short_name" : "Warszawa",
                 "types" : [ "administrative_area_level_2", "political" ]
              },
              {
                 <b><i>"long_name" : "Masovian Voivodeship",  &lt;-- region in English</i></b>
                 "short_name" : "Masovian Voivodeship",
                 "types" : [ "administrative_area_level_1", "political" ]
              },
              {
                 "long_name" : "Poland",
                 "short_name" : "PL",
                 "types" : [ "country", "political" ]
              }
           ],
           [...]
           "place_id" : "ChIJ8e41PvbMHkcRit4n8qe36Ns",
           "types" : [ "sublocality_level_1", "sublocality", "political" ]
        },
  </pre>
  
  <p>The main problem with this is the inconsistency for the same address components (locality, administrative_area_level_1) - sometimes English (as requested), sometimes the local language. Without some other ID to know that these refer to the same administrative reality, I can't be sure of that, unless I used another source of English &amp; local geo names and did some pattern matching.</p>
  
  <p>Is there a way to get around this problem? Or could someone suggest a reverse geocoding service not having such issues?</p>
  
  <p>Many thanks!</p>