Azure Maps API Returns Same freeformAddress for Different Nearby Properties

Question

Azure Maps API Returns Same freeformAddress for Different Nearby Properties

Selva 20

I'm using the Azure Maps Forward Geocoding API to retrieve normalized addresses (freeformAddress) for a set of properties. However, I've noticed that the API returns the same freeformAddress — "South Forum Drive, Grand Prairie, TX 75052" — for multiple distinct properties, even though they are clearly different apartment complexes located close to each other.
Here are the addresses I queried:
2045 S Forum Dr, Grand Prairie, TX 75052
2015 S Forum Dr, Grand Prairie, TX 75052
2105 S Forum Dr, Grand Prairie, TX 75052
1661 S Forum Dr, Grand Prairie, TX 75052
2030 S Forum Dr, Grand Prairie, TX 75052
Endpoint : https://atlas.microsoft.com/search/address/json?api-version=1.0&subscription-key=xxxxxx&query= 1661 S Forum Dr, Grand Prairie, TX 75052
When I look them up in Google Maps , these are clearly separate buildings/properties. But Azure Maps returns the same generic freeformAddress for all of them.
My Questions:

Why does the Azure Maps API return the same freeformAddress for nearby but distinct addresses?2. Is there a way to improve address granularity or force the inclusion of street numbers in the freeformAddress?
Why the Map Api didn't recognize the street number?

VSawhney 715 Reputation points Microsoft External Staff Moderator

2025-06-09T16:07:09.35+00:00
Hello Selva,

It sounds like you’re experiencing some issues with the Azure Maps Forward Geocoding API returning the same freeformAddress for different properties that are nearby. Here’s what you can consider:

API Behavior: Azure Maps attempts to normalize addresses based on the geospatial data it has, which can lead to similar addresses being grouped under one freeformAddress. This is especially common in areas with many buildings sharing similar elements in their addresses.

Granularity Improvement: Unfortunately, at this time, users can't force the Azure Maps API to include street numbers directly in the freeformAddress. If you're not seeing the desired granularity, consider appending the street number directly in your queries as you're already doing, and see if the API can return more distinctive results.

Why Street Numbers Aren't Recognized: The API may not recognize the street number based on its data sources or the way it processes the incoming requests. It primarily focuses on the underlying spatial data, which may reflect historical or standardized address data that could miss nuances like distinct apartment complexes.

Here are a few things you can try:

Use Structured Queries: Instead of using the plain address, format it according to structured input methods as described in the Azure Maps documentation.

Batch Requests: If querying multiple addresses, consider using the Batch Address API to handle multiple requests in one go, which might yield more precise outputs.

Location Parameters: Use parameters like countrySet in your API calls to limit the results to a specific region, as this might help refine what the API considers similar addresses.

Hope this helps you troubleshoot the issue!
Thank you!
VSawhney 715 Reputation points Microsoft External Staff Moderator

2025-06-11T05:16:46.7366667+00:00

Hello Selva,

Following up to check if the responses provided helped you. Please feel free reach us for further help.

Thank you!
Manas Mohanty 5,700 Reputation points Microsoft External Staff Moderator

2025-06-12T23:30:07.07+00:00

Hi Selva,

Good day.

I think Autosuggest sample azure maps would suit more towards you need. It is prompting lot more option against above inputs.

https://samples.azuremaps.com/rest-services/fill-address-form-with-autosuggest

Source code -https://github.com/Azure-Samples/AzureMapsCodeSamples/blob/main/Samples/REST%20Services/Fill%20Address%20Form%20with%20Autosuggest/Fill%20Address%20Form%20with%20Autosuggest.html

Hope it helps.

Thank you.

Accepted answer

0 additional answers

Your answer

VSawhney 715 Reputation points Microsoft External Staff Moderator

2025-06-09T16:07:09.35+00:00

Hello Selva,

It sounds like you’re experiencing some issues with the Azure Maps Forward Geocoding API returning the same freeformAddress for different properties that are nearby. Here’s what you can consider:

API Behavior: Azure Maps attempts to normalize addresses based on the geospatial data it has, which can lead to similar addresses being grouped under one freeformAddress. This is especially common in areas with many buildings sharing similar elements in their addresses.

Granularity Improvement: Unfortunately, at this time, users can't force the Azure Maps API to include street numbers directly in the freeformAddress. If you're not seeing the desired granularity, consider appending the street number directly in your queries as you're already doing, and see if the API can return more distinctive results.

Why Street Numbers Aren't Recognized: The API may not recognize the street number based on its data sources or the way it processes the incoming requests. It primarily focuses on the underlying spatial data, which may reflect historical or standardized address data that could miss nuances like distinct apartment complexes.

Here are a few things you can try:

Use Structured Queries: Instead of using the plain address, format it according to structured input methods as described in the Azure Maps documentation.

Batch Requests: If querying multiple addresses, consider using the Batch Address API to handle multiple requests in one go, which might yield more precise outputs.

Location Parameters: Use parameters like countrySet in your API calls to limit the results to a specific region, as this might help refine what the API considers similar addresses.

Hope this helps you troubleshoot the issue!
Thank you!
VSawhney 715 Reputation points Microsoft External Staff Moderator

2025-06-11T05:16:46.7366667+00:00

Hello Selva,

Following up to check if the responses provided helped you. Please feel free reach us for further help.

Thank you!
Manas Mohanty 5,700 Reputation points Microsoft External Staff Moderator

2025-06-12T23:30:07.07+00:00

Hi Selva,

Good day.

I think Autosuggest sample azure maps would suit more towards you need. It is prompting lot more option against above inputs.

https://samples.azuremaps.com/rest-services/fill-address-form-with-autosuggest

Source code -https://github.com/Azure-Samples/AzureMapsCodeSamples/blob/main/Samples/REST%20Services/Fill%20Address%20Form%20with%20Autosuggest/Fill%20Address%20Form%20with%20Autosuggest.html

Hope it helps.

Thank you.

Answer 1

Best solution is to use the latest version of the geocoding service. You are using version 1 which is pretty outdated. https://learn.microsoft.com/en-us/rest/api/maps/search/get-geocoding?view=rest-maps-2025-01-01&tabs=HTTP

Here is an example query and the result:

https://atlas.microsoft.com/geocode?api-version=2025-01-01&query=1661%20S%20Forum%20Dr,%20Grand%20Prairie,%20TX%2075052&subscription-key=<Your_AZURE_MAPS_KEY>

Note that you should encode the query value to ensure no special character's cause issues in the URL.

Result:


  "type": "FeatureCollection",
  "features": [
    {
      "type": "Feature",
      "geometry": {
        "type": "Point",
        "coordinates": [-97.021471, 32.680958]
      },
      "bbox": [-97.0275897202524, 32.6770952824293, -97.0153522797476, 32.6848207175707],
      "properties": {
        "type": "Address",
        "confidence": "High",
        "matchCodes": [
          "Good"
        ],
        "geocodePoints": [
          {
            "calculationMethod": "Rooftop",
            "usageTypes": [
              "Display"
            ],
            "geometry": {
              "type": "Point",
              "coordinates": [-97.021471, 32.680958]
            }
          },
          {
            "calculationMethod": "Rooftop",
            "usageTypes": [
              "Route"
            ],
            "geometry": {
              "type": "Point",
              "coordinates": [-97.0212128, 32.6816142]
            }
          }
        ],
        "address": {
          "addressLine": "1661 S Forum Dr",
          "streetName": "S Forum Dr",
          "streetNumber": "1661",
          "postalCode": "75052",
          "neighborhood": "South Dallas",
          "locality": "Grand Prairie",
          "formattedAddress": "1661 S Forum Dr, Grand Prairie, TX 75052",
          "countryRegion": {
            "name": "United States",
            "ISO": "US"
          },
          "adminDistricts": [
            {
              "shortName": "TX"
            },
            {
              "shortName": "Dallas County"
            }
          ]
        }
      }
    }
  ]
}

Selva 20 Reputation points

2025-06-11T12:32:40.41+00:00

I have more data . I used geocode batch api in the latest version. I still have the problem.
rbrundritt 20,836 Reputation points Microsoft Employee Moderator

2025-06-11T15:58:37.1633333+00:00

There is a new version of the batch geocoding service as well: https://learn.microsoft.com/en-us/rest/api/maps/search/get-geocoding-batch?view=rest-maps-2025-01-01&tabs=HTTP

If you are still seeing issues, please provide some details on which addresses/queries you are seeing issues with.
VSawhney 715 Reputation points Microsoft External Staff Moderator

2025-06-12T14:27:29.95+00:00

Hello Selva,

Following up again to check if the response provided by rbrundritt helped you. Please feel free reach us for further help.

Thank you!

Share via

Azure Maps API Returns Same freeformAddress for Different Nearby Properties

Here are a few things you can try:

0 additional answers

Your answer