shishengliang/lingniu-vehicle-ingest
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs(platform): refine vehicle center product goal

Browse Source
This commit is contained in:
lingniu
2026-07-04 17:49:06 +08:00
parent 3b817ef874
commit aa384732ef
2 changed files with 47 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

11
vehicle-data-platform/docs/product-spec.md
View File

@@ -10,6 +10,8 @@ The platform is a vehicle service center. GB32960, JT808, and Yutong MQTT are in
Every primary workflow should answer a vehicle-level question first, then allow protocol-level drill-down only when diagnosis or raw evidence is needed.
The current product goal is to evolve toward a production vehicle data management center, comparable to mature fleet IoT and telematics platforms: realtime monitoring, trajectory replay, historical evidence query, alert triggering and notification, statistics, and production operation quality all serve the same vehicle object.
## Primary Screens
The platform navigation should use vehicle-service language rather than protocol-product language:
@@ -68,9 +70,18 @@ The product uses AMap as the map provider for production map rendering.
- Alert events can highlight affected vehicle locations when the alert has valid coordinates.
- If AMap is unavailable or not configured, pages must fall back to coordinate preview instead of blocking the workflow.
AMap should be treated as infrastructure for vehicle operations, not only as a visual widget:
- Realtime monitor: bounded vehicle point loading, fit-to-result, selected vehicle highlight, online/offline/alert color semantics, and source freshness labels.
- Trajectory replay: route polyline, playback cursor, sampled map points, paginated evidence table, and raw-frame jump links.
- History query: location evidence can open the same coordinate in the map context.
- Alert events: vehicle location at trigger time should be shown when longitude and latitude are available.
- Ops quality: map key readiness, security proxy readiness, and frontend loader failures should be visible.
AMap credentials supplied by operations must be configured through ECS environment variables:
- `AMAP_WEB_JS_KEY`: public Web JS key served through `/app-config.js`.
- `AMAP_API_KEY`: server-side AMap service key for backend map/geocode/future server calls.
- `AMAP_SECURITY_JS_CODE`: private security code kept by the API service.
- `AMAP_SECURITY_SERVICE_HOST=/_AMapService`: frontend proxy path used by the AMap loader.