How notbot999/fap-map works
Franc Map Desktop is an offline-capable Slovenia GIS explorer. The user opens the map, selects layers or searches for locations, and can then route, inspect POIs, draw or import features, record tracks, and view elevation profiles. The desktop app serves the web interface locally; the shared API/backend path handles requests and caches map and query data for offline use. The README documents several capabilities whose implementation was not sampled, so those are represented without inferred internal call chains.
Main entry points: api.js API adapter · map.js Map rendering · route.js Route planner · search.js Location search
Components 23
App runtime
- Desktop host
app.py - Interface bootstrap
web/js/main.js - Settings and state
web/js/state.js
Map and layers
- Map rendering
web/js/map.js - Layer controls
web/js/panels/layers.js - Layer comparison
web/js/panels/compare.js
Explore and analyze
- Location search
web/js/search.js - POI browser
web/js/panels/poi.js - Feature details
web/js/popup.js - Weather and map info
web/js/special.js - Route planner
web/js/panels/route.js - Elevation profiles
web/js/profile.js
Create and record
- Drawings and measures
web/js/panels/draw.js - Track library and GPS
web/js/panels/tracks.js - Geospatial file exchange
web/js/geoio.js - Offline area manager
web/js/panels/offline.js
Persistence and services
- API adapter
web/js/api.js - Web backend
web/js/webbackend.js - Local cache and data
app.py
Other components
- Map user
- BRouter
- Nominatim
- Overpass API
Connections 33
- Map user → Interface bootstrap: uses
README.md - Interface bootstrap → Map rendering: initializes
web/js/main.js - Interface bootstrap → Settings and state: loads
web/js/main.js - Map rendering → API adapter: requests tiles
web/js/map.js - Map rendering → Web backend: gets tile URLs
web/js/map.js - Layer controls → Map rendering: controls layers
web/js/panels/layers.js - Layer comparison → Map rendering: compares layers
web/js/panels/compare.js - Settings and state → API adapter: loads and saves
web/js/state.js - API adapter → Web backend: delegates web calls
web/js/api.js - Desktop host → Local cache and data: stores requests
README.md - API adapter → Local cache and data: uses local service
README.md - Location search → API adapter: geocodes via
web/js/search.js - Location search → POI browser: searches loaded features
web/js/search.js - Location search → Feature details: shows result
web/js/search.js - Location search → Nominatim: queries
web/js/search.js - POI browser → Overpass API: fetches category data
web/js/panels/poi.js - POI browser → Map rendering: renders features
web/js/panels/poi.js - Weather and map info → API adapter: fetches map info
web/js/special.js - Route planner → API adapter: requests route
web/js/panels/route.js - Route planner → BRouter: requests route geometry
web/js/panels/route.js - Route planner → Map rendering: draws route
web/js/panels/route.js - Route planner → Elevation profiles: opens profile
web/js/panels/route.js - Route planner → Drawings and measures: saves as drawing
web/js/panels/route.js - Elevation profiles → API adapter: looks up elevation
web/js/profile.js - Drawings and measures → Map rendering: renders and edits
web/js/panels/draw.js - Drawings and measures → Geospatial file exchange: imports and exports
web/js/panels/draw.js - Drawings and measures → API adapter: persists features
web/js/panels/draw.js - Track library and GPS → Map rendering: renders tracks
web/js/panels/tracks.js - Track library and GPS → Geospatial file exchange: imports and exports
web/js/panels/tracks.js - Track library and GPS → Elevation profiles: calculates track stats
web/js/panels/tracks.js - Track library and GPS → API adapter: persists tracks
web/js/panels/tracks.js - Offline area manager → API adapter: downloads map data
README.md - Map user → Desktop host: launches
README.md