Right now, I can place pins on the map by passing URL parameters for desired node name and x / y coordinates. For example:
https://tumormap.ucsc.edu/?p=Treehouse/TreehousePEDv5_April2018&node=EXAMPLE1,EXAMPLE2&x=205,180&y=255,300
However, when the view is switched between hex grid and cartesian coordinates, the x and y values, which remain the same, now point to "different" map locations and therefore different existing nodes.
It would be great to place pins (or create a temporary attribute, although pins are more visible) by passing a single URL parameter for the node IDs as they already appear on the map. The value of this would be a) user not needing to calculate the coordinates, and b) pins would would be placed properly regardless of which view was chosen.
Right now, I can place pins on the map by passing URL parameters for desired node name and x / y coordinates. For example:
https://tumormap.ucsc.edu/?p=Treehouse/TreehousePEDv5_April2018&node=EXAMPLE1,EXAMPLE2&x=205,180&y=255,300
However, when the view is switched between hex grid and cartesian coordinates, the x and y values, which remain the same, now point to "different" map locations and therefore different existing nodes.
It would be great to place pins (or create a temporary attribute, although pins are more visible) by passing a single URL parameter for the node IDs as they already appear on the map. The value of this would be a) user not needing to calculate the coordinates, and b) pins would would be placed properly regardless of which view was chosen.