Geospatial Search behavior

[stevenferey]

entrepot.recherche.data.gouv.fr team

What steps does it take to reproduce the issue?

Populate a dataset with geospatial data (Geographic Bounding Box)

• When does this issue occur?

When we search for this dataset with the search API and with the geo_point and geo_radius parameters

• Which page(s) does it occurs on?

The search API result page

• What happens?

For example for a Geographic Bounding Box = westLongitude "-2.258631" eastLongitude "-2.392748" northLongitude "47.518038" southLongitude "47.496346"

Link for details : https://linestrings.com/bbox/#-2.258631,47.496346,-2.392748,47.518038 Example in dataverse demo : https://demo.dataverse.org/dataset.xhtml?persistentId=doi:10.70122/FK2/UYLYFK

and a search from Paris (about 400km): geo_point=48.872895,2.354527

Search results do not reflect reality: https://demo.dataverse.org/api/search?q=&geo_point=48.872895,2.354527&geo_radius=400 => result found (OK) https://demo.dataverse.org/api/search?q=&geo_point=48.872895,2.354527&geo_radius=150 => result found (KO) https://demo.dataverse.org/api/search?q=*&geo_point=48.872895,2.354527&geo_radius=50 => result not found (OK)

• To whom does it occur (all users, curators, superusers)?

all users

• What did you expect to happen?

A more precise search result, depending on the geo_point and the geo_radius given as query parameters.

Which version of Dataverse are you using?

5.13, 5.14

Any related open or closed issues to this bug report?

Google Group topic : https://groups.google.com/g/dataverse-community/c/0NynPGQAnE0