mirror of
https://github.com/zvx-echo6/navi.git
synced 2026-05-20 14:44:51 +02:00
docs: add traffic-intelligent routing and Idaho 511 planned features
- Append section 11 (On-Network Traffic Intelligence) to OFFROUTE-ARCHITECTURE.md - Create navi-feature-ideas.md with planned features: - Traffic-aware Valhalla routing via TomTom tiles - Idaho 511 incident feed integration - ADS-B/AIS tracking - TAK Server + EUD integration - Native iOS app Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
This commit is contained in:
parent
400dcbb8f2
commit
95dd4438fe
2 changed files with 123 additions and 0 deletions
|
|
@ -394,3 +394,34 @@ This system may guide people through dangerous terrain. Design constraints:
|
||||||
- GRASS GIS. `r.walk` manual. grass.osgeo.org.
|
- GRASS GIS. `r.walk` manual. grass.osgeo.org.
|
||||||
- Hoover, B. et al. (2019). CostMAP: An open-source software package for developing cost surfaces. LANL.
|
- Hoover, B. et al. (2019). CostMAP: An open-source software package for developing cost surfaces. LANL.
|
||||||
- Mapterhorn project. mapterhorn.com. BSD-3.
|
- Mapterhorn project. mapterhorn.com. BSD-3.
|
||||||
|
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
## 11. On-Network Traffic Intelligence
|
||||||
|
|
||||||
|
Two features that affect Valhalla segments (2–4) of the offroute chain, not the wilderness pathfinder (segment 1):
|
||||||
|
|
||||||
|
### Traffic-Aware Routing
|
||||||
|
|
||||||
|
- Valhalla supports time-dependent costing via traffic speed tiles
|
||||||
|
- TomTom traffic tiles already integrated in Navi at `/api/traffic/*` (currently visual overlay only)
|
||||||
|
- **Integration path:** configure Valhalla `traffic_tile_dir` to consume TomTom speed data so route calculations account for live congestion
|
||||||
|
- **Effect on offroute:** segments 2–4 (trail-to-road, road-to-road, road-to-home) would route around congested corridors
|
||||||
|
- Does NOT affect segment 1 (wilderness pathfinder)
|
||||||
|
|
||||||
|
### Idaho 511 Incident Feed
|
||||||
|
|
||||||
|
- Idaho 511 API provides real-time construction zones, accidents, and road closures
|
||||||
|
- Two integration points:
|
||||||
|
1. **Visual layer** — display incidents on Navi map as icons/overlays
|
||||||
|
2. **Routing barriers** — feed active closures to Valhalla as `avoid_locations` or edge exclusions so routes avoid closed roads
|
||||||
|
- **Implementation:** polling daemon (5–10 min interval), stores active incidents in `navi.db`, expires automatically when cleared
|
||||||
|
- Affects both standalone Valhalla routing and offroute segments 2–4
|
||||||
|
- **Stretch goal:** ingest other state 511 feeds for cross-state trips
|
||||||
|
|
||||||
|
### Sequencing
|
||||||
|
|
||||||
|
- Both features are post-offroute-core (after Phase O3)
|
||||||
|
- Can be built in parallel — traffic routing is Valhalla config, 511 is a new ingestion daemon + map layer
|
||||||
|
- Neither blocks wilderness pathfinder development
|
||||||
|
|
|
||||||
92
docs/navi-feature-ideas.md
Normal file
92
docs/navi-feature-ideas.md
Normal file
|
|
@ -0,0 +1,92 @@
|
||||||
|
# Navi Feature Ideas
|
||||||
|
|
||||||
|
Planned features and enhancements for the Navi navigation platform.
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
## Traffic & Incident Intelligence
|
||||||
|
|
||||||
|
### Traffic-Aware Routing
|
||||||
|
|
||||||
|
**Status:** Planned (post-Phase O3)
|
||||||
|
|
||||||
|
Integrate TomTom traffic data into Valhalla routing calculations:
|
||||||
|
|
||||||
|
- TomTom traffic tiles already available at `/api/traffic/*` (visual overlay)
|
||||||
|
- Configure Valhalla `traffic_tile_dir` to consume speed data
|
||||||
|
- Routes will account for live congestion on segments 2–4 of offroute chain
|
||||||
|
- Does not affect wilderness pathfinder (segment 1)
|
||||||
|
|
||||||
|
### Idaho 511 Incident Feed
|
||||||
|
|
||||||
|
**Status:** Planned (post-Phase O3)
|
||||||
|
|
||||||
|
Real-time road closure and incident integration:
|
||||||
|
|
||||||
|
- Poll Idaho 511 API every 5–10 minutes
|
||||||
|
- Store active incidents in `navi.db` with auto-expiration
|
||||||
|
- Display incidents as map overlay (icons/markers)
|
||||||
|
- Feed closures to Valhalla as `avoid_locations` for routing
|
||||||
|
- Stretch: support other state 511 feeds for cross-state trips
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
## Tracking & Situational Awareness
|
||||||
|
|
||||||
|
### ADS-B Aircraft Tracking
|
||||||
|
|
||||||
|
**Status:** Planned
|
||||||
|
|
||||||
|
Display live aircraft positions from ADS-B receivers:
|
||||||
|
|
||||||
|
- Integrate with local ADS-B receiver (dump1090/readsb)
|
||||||
|
- Show aircraft positions, altitude, callsign on map
|
||||||
|
- Useful for backcountry SAR coordination and general aviation awareness
|
||||||
|
|
||||||
|
### AIS Vessel Tracking
|
||||||
|
|
||||||
|
**Status:** Planned
|
||||||
|
|
||||||
|
Display marine vessel positions:
|
||||||
|
|
||||||
|
- Integrate with AIS receiver or feed
|
||||||
|
- Show vessel positions, heading, name on map
|
||||||
|
- Applicable for coastal/maritime navigation scenarios
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
## TAK Integration
|
||||||
|
|
||||||
|
### TAK Server + EUD Integration
|
||||||
|
|
||||||
|
**Status:** Planned
|
||||||
|
|
||||||
|
Connect Navi to the TAK ecosystem (ATAK, iTAK, WinTAK):
|
||||||
|
|
||||||
|
- TAK Server integration for shared situational awareness
|
||||||
|
- Push Navi routes to TAK clients as CoT (Cursor on Target)
|
||||||
|
- Pull team member positions from TAK into Navi
|
||||||
|
- Enable SAR/field team coordination through unified COP
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
## Mobile & Offline
|
||||||
|
|
||||||
|
### Native iOS App
|
||||||
|
|
||||||
|
**Status:** Planned
|
||||||
|
|
||||||
|
Native iOS application for offline-first navigation:
|
||||||
|
|
||||||
|
- Full offline map tile access
|
||||||
|
- Offline routing with pre-cached Valhalla tiles
|
||||||
|
- Integration with Apple Watch for turn-by-turn
|
||||||
|
- Meshtastic/LoRa mesh network support for off-grid comms
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
## Notes
|
||||||
|
|
||||||
|
- Features above Phase O3 depend on core offroute functionality being complete
|
||||||
|
- Traffic and 511 features can be built in parallel
|
||||||
|
- TAK integration useful for field coordination but not blocking core nav
|
||||||
Loading…
Add table
Add a link
Reference in a new issue