Overview
The error "Azure Maps batch geocoding returns incorrect coordinates due to missing street information" occurs when custom field mappings are not respected in batch geocoding requests. This was identified as a defect in Aurea CRM version 15.24.2, where the batch geocoding process ignored custom fields like StreetGeoCoding. The issue has been resolved in version 15.25.4, ensuring that custom street fields are correctly transmitted to Azure Maps.
Solution
Follow these steps to resolve the issue of incorrect coordinates due to missing street information in Azure Maps batch geocoding:
-
Verify Your Current Version:
- Check if you are running version 15.24.2 where this defect was present.
- Navigate to your admin panel → System Information.
-
Upgrade Your Instance:
- Upgrade to version 15.25.4 or later where the fix was implemented.
- Follow your standard upgrade procedures.
-
Post-Upgrade Steps:
- Ensure that your GEOCODING_FIELDMAPPING configuration is correctly set up.
- Verify that the custom field StreetGeoCoding is mapped properly in your configuration.
-
Verify Resolution:
- Run a batch geocoding process for a sample record.
- Confirm that the street information is correctly transmitted and coordinates are accurate.
Note: If you continue to experience issues after upgrading to v15.25.4 or later, please contact support for further assistance.
Frequently Asked Questions
- 1. How do I know if this error applies to my situation?
- You'll notice incorrect coordinates being returned during batch geocoding, and the street information will be missing in the Azure Maps request.
- 2. What if the issue persists after upgrading?
- Ensure that your GEOCODING_FIELDMAPPING configuration is correctly set up. If the issue persists, contact support with specific examples of the geocoding requests that are failing.
- 3. How can I verify that the fix is working?
- After upgrading to v15.25.4, run a batch geocoding process and check the Azure Maps request to ensure the street information is included and coordinates are accurate.
Priyanka Bhotika
Comments