--
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 post to this group, send email to dataverse...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/dataverse-community/221c5073-0b61-49c9-b253-483e162753e8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
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 post to this group, send email to dataverse...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/dataverse-community/d753b1d2-b88d-4877-a6ab-7a1aa91cc681%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Dear Durbin,
Thank you for your response. I wanted to ask if the Dataverse structure has recently changed regarding the upload of files—such as an XLS or CSV containing latitude and longitude columns—so that the system correctly recognizes them as georeferenced data.
I have installed Dataverse 6.10 and tested the same process on demo.dataverse.org, but the outcome is identical. I am unsure how to specify to the system that a file within a dataset is georeferenced.
I greatly appreciate any support you can provide.
To view this discussion visit https://groups.google.com/d/msgid/dataverse-community/aea5772d-31b2-4bd7-a893-ad5d77e65c5cn%40googlegroups.com.