MapQuest APIs are not responding with the correct Latitude and Longitude.
I've been leveraging the place-search.js solution for when we are unable to grab coordinates from the users local machine. The problem is that results coming back from the API are dropping trailing 0's. This results in the user location shifting locations in certain scenarios. Take the following example:
- Search for 3032 Riders Pass, Odessa, FL 33556
- Response comes with the following latitude & longitude:
- When we use that latitude and longitude on the MapQuest map, the location renders as 3036 Riders Pass (or google the coordinates for that matter)
- The actual latitude and longitude is as follows:
- Note the trailing zero was dropped by the MapQuest API up front.
This problem is not isolated to places-search.js and I believe is a fundamental flaw in the MapQuest Search API. I suspect you are leveraging FLOAT for the data type which is NOT correct as that will drop all trailing zeros or Latitude/Longitude coordinates, resulting in all sorts of locations coming back wrong (especially with locations that have multiple trailing 0s).
Please let me know if there is an option for this to be patched or I will need to reach out for a refund on my account as my companies' enterprise product cannot function with this break.
Also, places-search.js has compatibility issues with IE 11 which surprises me as I'd expect that to be a supported browser. Error code below:
'URLSearchParams' is undefined
I'm quite happy with the other functionality, stability, etc... but these two bugs are simply unmanagable.