You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When reading an Atlascope tour, it can be difficult to figure out exactly what on the map a caption refers to, and sometimes, why I'm looking at the map in front of me at all. In some cases, I am sure that is simply an issue in how the caption has been written, but in others I think it would be really helpful to have some kind of functionality to highlight a feature on the map.
Regardless of whether this is a feasible thing to implement, we should probably reckon with this feedback, which I have found to be pretty consistent among tour makers and readers.
Possible solutions
I think a solution to this would require adding an optional "points of interest" or poi key to the stops object of the tour metadata. This poi key would require a value of a WKT or GeoJSON compliant Point or Polygon object. After implementing this, maybe we could then add a WKT or GeoJSON maker – something like Placemark or wktmap – in the Atlascope Tour Generator, and ultimately display the points or polygons within tours on their parent stops. I don't think the features should be clickable. We could have a conversation about design/CSS if this is something we move forward on.
Lastly, I wonder: could the annotations functionality that Atlascope already contains be leveraged for this purpose?
The text was updated successfully, but these errors were encountered:
The problem
When reading an Atlascope tour, it can be difficult to figure out exactly what on the map a caption refers to, and sometimes, why I'm looking at the map in front of me at all. In some cases, I am sure that is simply an issue in how the caption has been written, but in others I think it would be really helpful to have some kind of functionality to highlight a feature on the map.
Regardless of whether this is a feasible thing to implement, we should probably reckon with this feedback, which I have found to be pretty consistent among tour makers and readers.
Possible solutions
I think a solution to this would require adding an optional "points of interest" or
poi
key to thestops
object of the tour metadata. Thispoi
key would require a value of a WKT or GeoJSON compliantPoint
orPolygon
object. After implementing this, maybe we could then add a WKT or GeoJSON maker – something like Placemark or wktmap – in the Atlascope Tour Generator, and ultimately display the points or polygons within tours on their parent stops. I don't think the features should be clickable. We could have a conversation about design/CSS if this is something we move forward on.Lastly, I wonder: could the annotations functionality that Atlascope already contains be leveraged for this purpose?
The text was updated successfully, but these errors were encountered: