Right now in AtoM 2.4 there are 2 built-in ways to link resources to a dynamic Google map.
The first, for repositories, uses the latitude and longitude fields in the Contact area of your repository record. You need to first request a Google Maps API key
, and add it to the Google Maps API Key field
in Admin > Settings > Global
See more instructions here:
If you have a lot of repositories, and you don't want to manually look up and add lat/long values to each one, there is a command-line task that you can use, which will attempt to automatically populate the lat/long fields based on the rest of the Contact area's address data. You can read more about this command line task here:
We do have a repository CSV import added in 2.4 - however, we've noticed that some fields are missing on import and export. We're currently addressing this, and will be adding fixes in an upcoming 2.4.1 bug fix release. You can keep an eye on this ticket for further details if you are interested:
The second way you can currently add dynamic Google maps is for the geolocation of digital objects. For example, let's say you have a photograph of a house or a street, and you want to show its exact location on a map. This can be done by first adding your API Key to AtoM, as above. Note that you will also have to navigate to Admin > Settings > Default page elements and enable the "Digital object map" - i.e. make sure the box is checked. See:
Now you should be able to add latitude and longitude values to your digital objects, and see a map appear in the digital object metadata area. For more information, see:
There is one other map option available in AtoM at present, though it was added a long time ago and is not being actively maintained. However, if you want you can generate a static (aka not zoomable, etc) Google map associated with a Place term (i,e. for place access points). You can do this by navigating to Browse > Places, clicking on a term, entering edit mode, and then adding the lat and long values in the "Code" field.
Note that Google has made changes to its API since this feature was first implemented (and in fact this affects all map options) - so for all maps currently supported in AtoM, you need to use the Signed degrees format (e.g. DDD.dddd) for the data to work! Degree and cardinal based formats (e.g. DDD MM SS + compass direction) will not work and the map will not be generated properly.
When only one field is provided (such as in the Terms edit page's "Code" field), latitude values should be entered first
, followed by a comma before the longitude values.
Here is an example of the latitude and longitude for Vancouver, BC, Canada:Correct format:
(signed degrees)Will not work in AtoM:
- 49° 14’ 46.6512” N, 123° 6’ 58.4136” W
Finally, it's possible you've seen other maps in some portal sites, such as the maps on the homepages of these portal sites:
For these maps, users have generally used third-party tools (like Google My Maps, https://mymaps.google.com/
) to create their maps, and then are either embedding them on an AtoM static page
(in these examples, the homepage, which is a special type of static page) using an iframe, or uploading an image of the map and using HTML to link that image to a full version of the map.
I hope this helps!