It uses Mapbox GL JS v2.x, which is no longer open-source and is tied to the TOS, so the distinction of using Mapbox tiles or not doesn't seem to matter. Just loading the library requires a token from Mapbox.
Can someone elaborate on the word "slippy" in this context? It seems to refer[0] to maps that can be dragged and zoomed. But isn't that all digital maps?
The first one I've interacted with was Google Maps almost two decades ago, which seems to meet the criteria (as well as every alternative I have tried). So I'm not sure what a non-slippy map would be like (or why the word is a necessary qualifier in this context).
As others mentioned there are also many maps meant for printing. There are also map servers that will generate a viewport-specific image (typically meaning no on-the-fly rendering) on demand.
This website is effectively a very powerful game engine (written in Rust and compiled to wasm) running in the browser - I can't easily add a GeoJSON ovrlay, or geolocation, or other web map patterns.
It's come to mean interactive maps web maps, usually tiled image based. This is still a very specific thing in GIS where most published maps are still static documents - and often meant for printing on large format printers in the ALEC world.
“Slippy” was coined by the early OpenStreetMap community (specifically Steve Coast, I think) to mean draggable. It was in contrast with the previous generation of webmaps which had buttons for panning N/S/E/W, each of which would trigger a new page load with a new set of tiles.
Readit News
I feel like your site is so smooth and really works well.
I wish mapcomplete could work as well but instead it's quite laggy when zooming out a decent amount. https://mapcomplete.osm.be/cyclofix.html?z=13&lat=50.84031&l...
https://safecyclingmap.com is currently using Mapbox GL JS because I wanted to tinker with the Mapbox Directions API and geocoding. It also works great with Maplibre GL JS, I've got a branch ready to go: https://github.com/jakecoppinger/safe-cycling-map/tree/mapli...
The replies are also correct - I'm using the CyclOSM tiles (https://www.cyclosm.org), and the lane shapes are generated by osm2streets, which Dustin Carlino (https://github.com/dabreegster) wrote in Rust! (https://github.com/a-b-street/osm2streets).
The first one I've interacted with was Google Maps almost two decades ago, which seems to meet the criteria (as well as every alternative I have tried). So I'm not sure what a non-slippy map would be like (or why the word is a necessary qualifier in this context).
[0] https://wiki.openstreetmap.org/wiki/Slippy_map
Example video showing terraserver: https://m.youtube.com/watch?v=uaQNdMQ3NNk
As others mentioned there are also many maps meant for printing. There are also map servers that will generate a viewport-specific image (typically meaning no on-the-fly rendering) on demand.
Maybe it's easier to define what I don't mean by a "generic slippy map": https://play.abstreet.org/0.3.37/abstreet.html
This website is effectively a very powerful game engine (written in Rust and compiled to wasm) running in the browser - I can't easily add a GeoJSON ovrlay, or geolocation, or other web map patterns.
The "street explorer" demo (https://a-b-street.github.io/osm2streets/#18.37/-33.88071/15...) loads a slippy map (OpenStreetMap) and then loads in a debug segment of the map data.
but i guess as long as it's tiled it's slippy
Deleted Comment