How jatinkumar321/spatial-db-engine works
This is an in-memory spatial-index service with a browser dashboard, rather than a complete ride-dispatch system: the sampled API inserts points and performs bounding-box searches, but does not assign nearest drivers to requests. The main workflow is dashboard-to-HTTP API, then R*-Tree operation, with results or tree data returned for display. The README also documents city-load simulation and event logging in the dashboard. The frontend source was not sampled, so its internal behavior and exact endpoint wiring are based on README descriptions; uncertain links are omitted.
Main entry points: main.cpp REST endpoints · index.html Map dashboard · rtree.cpp R*-Tree index · rtree.h Tree statistics
Components 11
Dashboard
- Map dashboard
web/index.html - City load simulator
web/index.html - Event log console
web/index.html
HTTP service
- HTTP server
src/main.cpp - REST endpoints
src/main.cpp
Spatial index
- R*-Tree index
src/rtree.cpp - Range search
src/rtree.cpp - Tree serializer
src/rtree.cpp - Tree statistics
include/rtree.h
Spatial model
- Points and MBRs
include/node.h
Other components
- Dashboard user
Connections 14
- Dashboard user → Map dashboard: uses
- Map dashboard → HTTP server: HTTP requests
- HTTP server → Map dashboard: serves page
- HTTP server → REST endpoints: dispatches routes
- REST endpoints → R*-Tree index: inserts points
- REST endpoints → Range search: searches bounds
- REST endpoints → R*-Tree index: clears index
- REST endpoints → Tree serializer: requests serialization
- REST endpoints → Tree statistics: reads statistics
- Range search → R*-Tree index: queries index
- Tree serializer → R*-Tree index: serializes structure
- R*-Tree index → Points and MBRs: indexes coordinates
- Map dashboard → City load simulator: starts simulation
- Map dashboard → Event log console: shows events