Change GIS library? #29
Labels
No labels
big job
blocked
bug
documentation
duplicate
enhancement
good first issue
help wanted
invalid
maybe
meta
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
ian/field-spotter#29
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
As discovered in #28, Field Spotter's display of spots doesn't work very well for users outside Europe. Leaflet.js handles longitude wrapping pretty badly, and there have been lots of ultimately fruitless discussions about this, e.g.:
There are suggestions online, however none are entirely satisfactory, e.g.:
worldCopyJumpfrom Leaflet's options, but this still only shows one copy of the markers, it just jumps them all when the centre of the projection crosses 180 longitude.All this leads me to wonder if Leaflet.js might not be the right library for us. Consider whether something like Cesium, which is inherently 3D, might be a better fit for Field Spotter's global scope. OpenLayers should also be considered as it is more mature.
Spiderfying/clustering might be an issue in Cesium:
Consider MapLibre: https://maplibre.org/maplibre-gl-js/docs/
Definitely has a spiderfy plugin: https://github.com/nazka/map-gl-js-spiderfy
Need to determine if/how it solves the main problem