Dataverse 5.13 : Geospatial Search behavior

[Steven FEREY]

Hi Dataverse community,

We wanted to test the Geospatial Search with Dataverse 5.13  and we have a few questions about it :

Since Dataverse Demo, we couldn't use Geospatial Search because the fields westLongitude, eastLongitude, northLongitude, southLongitude don't seem to be indexed:

https://demo.dataverse.org/dataset.xhtml?persistentId=doi:10.70122/FK2/UYLYFK

Maybe this is normal behavior on the demo ?

---------

Also, during our tests since our 5.13 installation, we observed results that did not reflect the search filters :

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

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

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

Have you observed the same behavior please ?

Thank you so much,
Steven F.

[Philip Durbin]

Hi Steven,

First, thanks for all the pull requests! We appreciate them!

I wrote a test (attached) based on your parameters and unfortunately I'm seeing the same buggy behavior for the middle case (150 km). (I'm even testing with the latest Solr, 9.3.0, by the way.)

Can you please open an issue at https://github.com/IQSS/dataverse/issues about this? When you do, would you be able to add https://linestrings.com/bbox/#-2.258631,47.496346,-2.392748,47.518038 or similar URL so that we can see a map of the bounding box?

Thanks!

Phil

p.s. By the way if I change "q=template" to "q=*" I can find your dataset on demo (so it should be fine to test there, should be indexed): https://demo.dataverse.org/api/search?q=*&geo_point=48.872895,2.354527&geo_radius=400

--
You received this message because you are subscribed to the Google Groups "Dataverse Users Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dataverse-commu...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/dataverse-community/7b62227a-ca3e-4f73-a0c3-81455896c29cn%40googlegroups.com.

--

Philip Durbin
Software Developer for http://dataverse.org
http://www.iq.harvard.edu/people/philip-durbin

[Steven FEREY]

Hi Philip,

Thank you for your quick return !

Also thank you for the precision, I reproduce the problem also on the demo Dataverse in version 5.14.

I created the issue found here: https://github.com/IQSS/dataverse/issues/9798

Thanks,

Steven.

[Juan Pablo Tosca]

Hi Steven,

I hope you are doing great! I just wanted to get in touch with you since we had an interesting conversation about this on #9798. The issue is very well described in the comment from Jim Myers, in short on your data West and East are inverted and this causes it to be interpreted as a semi-ring around the globe from the west and the east. We drew the three radius 50, 150, and 400 from the search location, and here is an example of what I just said:

Our suggestion to address this would be to fix the data first, switch W with E values and reindex. Ideally, you would like to update to DV 6.2, we added on 6.1 a validation for this field that will prevent these values from being incorrectly entered. 

After that, only the search with the 400 km radius should find the data.

Please let me know if you have any questions.

Best,

Juan

[Juan Pablo Tosca]

It seems that the image was not included but you should be able to see it on the Github issue.

Best,

Juan

On May 6, 2024, at 7:06 PM, Juan Pablo Tosca <juan_...@g.harvard.edu> wrote:

Hi Steven,

You received this message because you are subscribed to a topic in the Google Groups "Dataverse Users Community" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/dataverse-community/0NynPGQAnE0/unsubscribe.
To unsubscribe from this group and all its topics, send an email to dataverse-commu...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/dataverse-community/cb8ec48e-324e-4ede-b55f-83ffe87ce92fn%40googlegroups.com.