Comment from a Julia newb:
I was previously using Python 3 & Folium on top of OpenStreetMaps to generate valid HTML for web-based mapping. Folium is a Python wrapper for the LeafletJS library, which is an excellent library for all sorts of visualisations: charts, graphs, vectors and maps.
Based on the information I have read in relation to the Julia project, the aim is not merely to be an “alternative” to Python for general computing. However, with an ever increasing Julia code base across networked and inter-networked devices, I believe that the concept of visualising data in context of it’s geolocation, is increasingly needed.
While the PlotlyJS solution is workable, it produces (AFAIK) static images with overlaid and contextualised data of pre-defined sections of a map.
Whereas the Python/Folium/OpenStreetMaps or Python/Leaflet/OpenStreetMaps solutions produce valid HTML for use in a web app, existing web server or can even output a static image.
It is not that the Python solutions are better per se but they do seem to offer flexability (Multiple and variable data layers & data-related attributes), easy modification and almost real-time updating whereas the Julia solution(s) currently do not.
I’m happy to try and use Julia to call Python & Folium as a workaround but perhaps this needs a real developer assessment to judge the merits of this thread and identify or at least indicate a sane direction of progress for Julia & Mapping.