Details
-
Bug
-
Resolution: Fixed
-
Major
-
None
-
None
-
1
Description
A recent RFC change for search has changed the ordering of latitude/longitude values such that where previously we would accept them from the user as lat/lon and then dispatch to the server as lon/lat, we will not simply accept them from the user as longitude first, latitude second.
Ex:
Before: new GeoDistanceQuery(lat, lon, distance)
After: new GeoDistanceQuery(lon, lat, distance)
Attachments
Issue Links
- is cloned by
-
NCBC-2105 Ensure SDK represents all geopoint's as LON/LAT rather than LAT/LON
- Resolved