we have items that use a-loc:long and a-loc:lat for longitude and latitude.
a-loc: long 9.26176
The fields are always filled, but if I check the mapping tab of the item, the item is not on the map.
I think the items were imported in Bulk, so we could not use the location options which I think can be found in csv import (even though we do have the Mapping module installed).
We would like to correct them in bulk, as most items are in the same building and have the same location, but we do not know how to go around it.
Maybe we should change the datatype? It is currently set to Text. I do not know which data type we should choose though.
Or maybe we should add new location fields with the same values but different datatypes and /or properties?
The Mapping module stores coordinates separately from property values. It does not come with the ability to copy coordinates from properties to mapping markers. There is a third-party module named DataTypeGeometry that claims to do this, but it is not formally registered so we cannot vouch for it.
Hi, thank you.
So basically we have three options:
- reimport the csv from scratch, using different settings (I seem to understand we need to add extra columns for latitude and longitude which are NOT properties)
- use the Datatypegeometry module
- map the objects one by one?
If your items have unique identifiers you should be able to append the latitude and longitude information-- rather than redoing the import-- by creating a CSV file with three columns – (1) item identifier; (2) longitude; (3) latitude-- and then running that through CSV Import. See this section of the CSV Import manual: CSV Import - Omeka S User Manual and refer to this section of the Mapping module manual for further guidance: Mapping - Omeka S User Manual. You might try appending data to just two or three items to make sure you’ve set up everything correctly before trying it with your full dataset.
The Omeka team is currently working on a batch update option to copy coordinates from property values to Mapping markers. It’s a complicated addition which will require quite a bit more development and testing, so we can’t commit to a release date just yet. You can follow along with our progress here.
@kprtll and @jimsafley, thank you!
In the end we fount another mapping mistake and had to reimport the CSV from scratch, but I will save @kprtll’s solution in case we need to do it again, while we wait for the new module.