How el-hadj10/transas works
TransAs is an offline-first Android delivery-route planner. A driver imports or enters parcels, then requests optimization: the UI controller geocodes addresses, obtains road distances (falling back to Haversine), runs the local hierarchical optimizer, and persists the resulting tour. The screens present stops and map context and support delivery status, voice entry, and current-location re-optimization. Edges reflect the provided excerpts, SOURCE INDEX references, and README; some UI service wiring is known only through those references, not full source inspection.
Main entry points: safe_screen.py Route planner UI · optimize_controller.py Optimization controller · db_manager.py SQLite manager · main_screen.py Parcel list
Components 23
App and screens
- App bootstrap
main.py - Route planner UI
ui/screens/safe_screen.py - Parcel list
ui/screens/main_screen.py - Import screen
ui/screens/import_screen.py - Map screen
ui/screens/map_screen.py - Parcel card
ui/components/parcel_card.py - Route overview
ui/components/route_overview.py
Route planning
- Optimization controller
ui/controllers/optimize_controller.py - Address geocoder
core/geocoder.py - Distance matrix
core/router.py - Tour optimizer
core/optimizer.py - Nominatim
- OSRM
Local data
- SQLite manager
database/db_manager.py - Local database
Field services
- Batch import
ui/services/batch_import.py - Device location
ui/services/location.py - Voice input
ui/services/speech.py - OSM tile map
ui/services/tile_map.py - Navigation launch
ui/services/navigation.py - URI utilities
ui/services/uri_utils.py - Map renderer
ui/services/folium_renderer.py
Other components
- Driver
Connections 30
- Driver → App bootstrap: opens app
README.md - App bootstrap → Route planner UI: creates screen
main.py - App bootstrap → Optimization controller: creates controller
main.py - App bootstrap → SQLite manager: creates database
main.py - Driver → Route planner UI: uses planner
README.md - Route planner UI → Optimization controller: requests optimization
ui/screens/safe_screen.py - Optimization controller → SQLite manager: loads and saves tours
ui/controllers/optimize_controller.py - Optimization controller → Address geocoder: geocodes stops
ui/controllers/optimize_controller.py - Optimization controller → Distance matrix: requests distances
ui/controllers/optimize_controller.py - Optimization controller → Tour optimizer: optimizes order
ui/controllers/optimize_controller.py - Address geocoder → Nominatim: queries addresses
README.md - Distance matrix → OSRM: requests road matrix
core/router.py - Tour optimizer → Distance matrix: uses distance matrix
- Distance matrix → Tour optimizer: returns distances
- SQLite manager → Local database: reads and writes
database/db_manager.py - Import screen → SQLite manager: stores parcels
ui/screens/import_screen.py - Parcel list → SQLite manager: loads parcel list
ui/screens/main_screen.py - Parcel list → Parcel card: renders stops
ui/screens/main_screen.py - Parcel list → Route overview: renders route
ui/screens/main_screen.py - Parcel list → Optimization controller: starts optimization
ui/screens/main_screen.py - Map screen → SQLite manager: loads tour
ui/screens/map_screen.py - Map screen → Map renderer: renders map
ui/screens/map_screen.py - Route planner UI → Batch import: imports parcels
ui/screens/safe_screen.py - Route planner UI → Device location: gets current position
ui/screens/safe_screen.py - Route planner UI → Voice input: accepts dictation
ui/screens/safe_screen.py - Route planner UI → OSM tile map: renders basemap
ui/screens/safe_screen.py - Route planner UI → Navigation launch: launches navigation
ui/screens/safe_screen.py - Navigation launch → URI utilities: builds map URI
ui/services/navigation.py - Parcel list → URI utilities: builds map URI
ui/screens/main_screen.py - OSM tile map → OSRM: uses OSM tiles