54fd1e470467a39839759850546c691a732bfc6c
How it works/features
- vector tileserver (martin) delivers tiles
- martin needs postgis
- needs a job which fills database with OSM data
- layers need to be defined
- style for tiles (via maputnk)
- maplibre framework brings tiles and style together and draws on website
- map shows various outdoor relevant features (clickable)
- routing requests will be forwarded to (local) graphhopper
- graphhopper needs osm pbf file
- responses from graphhopper will be drawn on map via maplibre
Structure
- maputnik to edit map style(s)
- postgresql database to hold osm data
- regular imports via osm2pgsql tool from pbf download
- vector tileserver (marting) to deliver vector tiles with data from db
- graphhopper with api to deliver routing data
- regular imports from pbf download
- pilgrim to glue tiles and routing together
- asks tileserver via maplibre-gl-js (https://github.com/maplibre/maplibre-gl-js/) for tiles (map.pilgrim.home.spacedon.de)
- asks graphhopper api via api client (https://github.com/graphhopper/directions-api-js-client) for routing (routing.pilgrim.home.spacedon.de)
Glyphs
Roboto font (Apache Licence)
- Get fonts from https://github.com/openmaptiles/fonts
- package fonts to PBF with
npm installfollowed bynode ./generate.js - copy Roboto glyphs from
_outputdirectory to desired place where it can be accessed from map lib
Alternative repo https://github.com/orangemug/font-glyphs/
Description
Languages
JavaScript
59.8%
Java
20.6%
HTML
18.6%
Shell
1%