Response:
"candidates": [ { "address": "Bangalore, Karnātaka, India", "location": { "x": 77.593686440000511, "y": 12.971936200000471 }, "score": 100, "attributes": { "City": "", "Region": "Karnātaka", "Country": "IND", "Postal": "" } } ]
Response:
" candidates": [ { "address": "560037", "location": { "x": 77.6929203250005, "y": 12.96380000600044 }, "score": 100, "attributes": { "City": "", "Region": "", "Country": "IND", "Postal": "560037" } } ]
If you append "Loc_name" as an additional outField in your requests you'll see which specific locators are producing the match.
Its just my two cents, but I don't think its appropriate to expect matches produced by IND.Postal or Gaz.WorldGazetteer.POI1 locators to always include values for City or Region. For example, postal codes don't have a 1:1 correspondence with administrative boundaries.