turf VS Leaflet

to measure distances and convert between our parameters I'm using TurfJS, for which binding is even more trivial:

Turf.js is an open-source geospatial analysis library that can process various location data, such as the center of gravity and distance calculations.

Isochrones are manually calculated using turf.js assuming 1.2m/s walking speed after the subway trip. These are simple buffers around each station/prior isochrone and do not take the street network into account.

Not to take away from you learning, which I think is awesome, I was wondering if you know about http://turfjs.org/ which provides a lot of simple modules … and is surprisingly hard to find. Their `distance` modules may be relevant in this case.

you can use client side libraries like Turfjs to do buffers https://github.com/Turfjs/turf/tree/master/packages/turf-buffer

Tools: custom Javascript (with heavy use of turf.js) for data processing and creating the 3D model, Blender, 3D printing, lost wax casting

I've integrated https://turfjs.org/ with mapbox before and it was pretty fun

References Amazon Location Service Turf.js MapLibre GL JS Leaflet OpenLayers Cesium Mapbox GL JS

9. Leaflet

Leaflet is the most famous open-source map library, with lots of plugins. 2 of them are used to animate a marker on the map:

Leaflet stands out as one of the top open source JavaScript libraries for crafting interactive maps. Optimized for both mobile and web devices, it is relatively small (around 42KB) and offers a ton of features, plugins, and a straightforward API. It works across all browsers and platforms.

Finding maplibre 'better' was more valid at the time than today, and is also subjective. The creators and maintainers of both libraries have done some great work (and are still doing so).

Back in January 2022, the stable version of leaflet, v1.7.1, was from September 2020, and was affected by some small bugs degrading the user experience. Although the release of following version seemed close, there was no clear schedule for it, and I had concerns about how maintained the library would remain.

As of today, the bug from 2015 where there is some white space between map tiles on fractional zoom levels [0] is still open.

Also, leaflet was a pain to integrate in Svelte Kit framework, because it depended on `window` and-or `document`, not available at server side.

Maplibre, on the other hands, with a feature set roughly equivalent to Leaflet, benefited from much more frequent releases, and seemed more stable across browsers and devices. It was also easier to make it work in Svelte kit.

[0]: https://github.com/Leaflet/Leaflet/issues/3575

For a personal project, I had to use Leaflet with Svelte, and I faced some problems during development.

Do anyone have any workaround on how to get leaflet js to work inside notion, either as an embed or as code, or widget? https://leafletjs.com/

None of those things are what most in the GIS space would consider "complex", so you could go with any of the options you selected. For lightweight maps, I like Leaflet

https://leafletjs.com

I have a special place in my heart for Leaflet and it’s documentation: https://leafletjs.com

Its suppose to be free: like with map data providers there's Leaflet, OpenStreet Maps and many more which are all for free.