feat: Enhance track model and import functionality
- Added new fields to TrackModel: status, is_bidirectional, and coordinates. - Updated network service to handle new track attributes and geometry extraction. - Introduced CLI scripts for importing and loading tracks from OpenStreetMap. - Implemented normalization of track elements to ensure valid geometries. - Enhanced tests for track model, network service, and import/load scripts. - Updated frontend to accommodate new track attributes and improve route computation. - Documented OSM ingestion process in architecture and runtime views.
This commit is contained in:
6
TODO.md
6
TODO.md
@@ -17,9 +17,9 @@
|
||||
- [x] Implement an import script/CLI that pulls OSM station data and normalizes it to the PostGIS schema.
|
||||
- [x] Expose backend CRUD endpoints for stations (create, update, archive) with validation and geometry handling.
|
||||
- [x] Build React map tooling for selecting a station.
|
||||
- [ ] Enhance map UI to support selecting two stations and previewing the rail corridor between them.
|
||||
- [ ] Define track selection criteria and tagging rules for harvesting OSM rail segments within target regions.
|
||||
- [ ] Extend the importer to load track geometries and associate them with existing stations.
|
||||
- [x] Enhance map UI to support selecting two stations and previewing the rail corridor between them.
|
||||
- [x] Define track selection criteria and tagging rules for harvesting OSM rail segments within target regions.
|
||||
- [x] Extend the importer to load track geometries and associate them with existing stations.
|
||||
- [ ] Implement backend track-management APIs with length/speed validation and topology checks.
|
||||
- [ ] Implement track path mapping along existing OSM rail segments between chosen stations.
|
||||
- [ ] Design train connection manager requirements (link trains to operating tracks, manage consist data).
|
||||
|
||||
Reference in New Issue
Block a user