You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
When sorting search results with the near SearchParameter the usage of the manhattan distance leads to unexpected ordering of results.
We are using this to return e.g. the nearest pharmacy to a user.
To Reproduce
Steps to reproduce the behavior:
calculate euclidian distances for locations in: ResourceProviderR4DistanceTest.shouldSortPractitionerRolesByLocationNear
"PractitionerRole-Hamilton" & "PractitionerRole-Oshawa" are returned in a different order.
Expected behavior
Locations are sorted by their "real" distance. Haversine seems to be unnecessary complex, but the euclidian distance is expected by most users on _sort.
Environment (please complete the following information):
HAPI FHIR 8.0.0
The text was updated successfully, but these errors were encountered:
Describe the bug
When sorting search results with the
near
SearchParameter the usage of the manhattan distance leads to unexpected ordering of results.We are using this to return e.g. the nearest pharmacy to a user.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Locations are sorted by their "real" distance. Haversine seems to be unnecessary complex, but the euclidian distance is expected by most users on _sort.
Environment (please complete the following information):
The text was updated successfully, but these errors were encountered: