SEA CHART /Community
← Back to community
Released
p
pine
Add Routes, Waypoints, GPX/KML Import/Export, and Future Cloud Sync Foundation Add a new route-management feature area for SeaChart. The feature should support local route recording, planned routes, waypoint management, GPX/KML import/export, and prepare the data model for future server upload/download sync. Scope: Add a Routes entry button on the top-left of the map screen. Create a dedicated Routes screen/page. Support recording actual GPS tracks. Support managing saved routes/tracks. Support waypoint management. Support GPX import/export. Prepare KML import/export support. Prepare route/waypoint data for future cloud upload/download. Core Concepts: TrackRecord: an actual recorded GPS track. PlannedRoute: a user-created or imported planned route. Waypoint: an independent saved point that can also be referenced by routes. MVP Requirements: User can start, pause, resume, and stop route recording. Recorded tracks are saved locally. User can view saved tracks in a list. User can show/hide saved tracks on the map. User can rename and delete saved tracks. User can create, edit, and delete waypoints. User can import GPX files containing tracks, routes, and waypoints. User can export selected tracks/routes/waypoints as GPX. KML support can be added after GPX if needed. Future Cloud Sync Preparation: All route and waypoint entities should include fields for future server sync: localId serverId name description createdAt updatedAt deletedAt syncStatus lastSyncedAt version isPublic source Suggested sync statuses: LOCAL_ONLY PENDING_UPLOAD SYNCED PENDING_UPDATE PENDING_DELETE CONFLICT Architecture Notes: Keep the feature offline-first. Store all route and waypoint data locally first. Imported GPX/KML data should become local route/waypoint records. Server upload/download should be added later through repository methods without requiring a database redesign. Cloud sync UI can be hidden initially. Auto Route Notes: Auto Route should not be implemented as full automatic safe navigation in the first version. For the first phase, it should be treated as assisted route planning: User selects start/end/intermediate points. App generates editable route segments. App shows distance and estimated travel time. App clearly warns that the route must be manually checked against depth, hazards, restricted areas, and local navigation rules. Acceptance Criteria: Routes button appears on the top-left of the map screen. Routes screen is reachable from the map. Track recording works offline. Saved tracks persist locally. Waypoints persist locally. GPX import/export works for basic tracks and waypoints. Data model includes future cloud-sync fields. Existing navigation mode and Auto Follow behavior are not broken.
+
↳ Reply 1 6 views

Discussion

p
pine
This issue has already been fixed in version 1.5.0.
+

Reply

Sign in