Refine map
Closed this issue · 8 comments
My thoughts on the map:
- Label points on the map with the modern names
- Distinguish label styles with the
map_levelfield: "sites and cities", "region", "country", "sea" - On click, the pop-up should display their ancient name (I have to confirm with Claire which field/version to use) and the Pleiades URI or ID, linked to Pleiades itself. The Pleiades ID number is stored in the geojson in the
pidfield, and the links are constructed as: http://pleiades.stoa.org/places/{{ "pid" }} - For the places called out in the catalogue TOC, the map labels should be graphically called out, and the pop-ups should include a link to the relevant catalogue grid (if possible?) and perhaps also some sample object images from that area? They should feel special. I'll add South Italy and Taranto regional info into the geojson for this.
Other ideas?
Also, I need to reconcile our use of Pleiades URIs in the geojson and Getty TGN URIs in the catalogue datasets for location. Going to reach out to the GRI vocab folks ...
An update. Ruth, Claire and I are sitting down Tuesday afternoon to look at the location data for both the map and the dataset to check for consistency, and to make some determination about what we want to include within the catalogue. I also spoke with the GRI and they're eager to make a connection for us between TGN and the Pleiades geolocation vocabulary, so we should be able to reference both/either within Terracottas.
Q for @egardner: How straightforward is it to use the TGN and Pleiades URIs as we'd record them in the geojson file, to reach into those resources and pull out data to display on the map? Both have JSON versions of the data. Here are two examples for Canosa:
Some progress here made as of: 72eecb8
Going to try and see if we can come up with a solution that does not necessitate treating "regions" as "points" in order to make them clickable.
As of the latest commit, things are mostly working. The key was using Leaflet's DivIcon class for region markers – these allow the use of an unstyled <div> element instead of an icon for map markers. Crucially, you can set the inner HTML of DivIcon layers pretty easily, allowing for labels that sit on the map and respond to clicks.
As of this morning, the map seems to be mostly up to spec. I'm going to consider the ability to go directly to a pre-filtered catalogue grid from the map (eg. by clicking on "Taranto Region", going to the catalogue grid of only Taranto objects) an enhancement for now, since it requires the addition of client-side routing to the project.
@geealbers as far as images go, do we still want images inside of pop-up elements? Showing all objects would be too much for places like Taranto. Let me know how you were imagining this would work if so.
What do you think about having one highlight image for each that Claire could pick? I wouldn't mind enlivening those pop-ups a bit more
That works. I think the highlight image should be added directly into the
GeoJSON as a new field in that case.
Also short descriptions for the regions (1 sentence or so) would help more
casual visitors understand what they were looking at. I don't think we'd
need that for all sites, just the 5 major regions.
Once I have more content in the JSON I'll figure out how to display it.
On Wed, Nov 11, 2015 at 9:39 AM, Greg Albers notifications@github.com
wrote:
What do you think about having one highlight image for each that Claire
could pick? I wouldn't mind enlivening those pop-ups a bit more—
Reply to this email directly or view it on GitHub
#22 (comment)
.
With the addition of the Leaflet clustering plug-in and the use of simple dots + labels for map markers, I think this is good to go.