Elysia Tools
Navigation
Workflow Playbook
Check GPX segments and coordinates, render a reviewed SVG route map, and deliver legible PDF or PNG copies with source files and a traceable review record.
Hubs
This workflow serves event organizers and travel editors handing off one reviewed route illustration, not a turn-by-turn navigation product. Keep the original GPX, record its SHA-256 and agree which tracks, routes, waypoints and segments belong in the drawing. Obtain permission before uploading location data. A home address or private meeting point may be present even when the track itself looks harmless. Make an authorized working copy for any exclusions and retain a controlled record of the changes rather than overwriting the original.
Write down the intended region, direction, checkpoints, output size and reviewer. If a background is required, obtain authorized contextual GeoJSON separately and record its source and date. The renderer draws supplied features in an OSM-inspired style; it does not download a complete street map, terrain or fresh access restrictions. A blank background around a route is not evidence that no roads or obstacles exist.
Convert GPX to GeoJSON and compare the original structure with the resulting features. This converter creates a separate LineString for each track segment, plus lines for routes and points for waypoints. For example, two track segments containing 12 and 8 points should remain two lines with those respective counts, not one 20-point line that draws a false bridge across a recording gap. Exclude or resolve one-point segments explicitly because the renderer cannot draw them as lines. Preserve the original timestamps and extensions: the conversion is not a complete metadata round trip and should not underpin speed or duration claims.
Use your own compatible JSON Schema to check the agreed feature and coordinate structure. A schema does not establish geographic truth. Inspect raw GPX coordinates too: a missing value can become zero in conversion, which may still pass a numeric range check. Confirm finite values, longitude and latitude ranges and selected checkpoints against a trusted reference. GeoJSON uses longitude before latitude, while a coordinate form may ask for latitude first. Converting a checkpoint's DMS notation helps interpretation but does not independently prove its location.
Use great-circle distance between selected checkpoints to catch obvious location errors, not as the track's total length. Endpoints of a loop can be close together despite a long route. The renderer sums distances along supplied route lines; sparse sampling, duplicated lines and GPS noise affect the result, and elevation is not included. Do not infer travel time, accessibility or field safety from either number.
Keep segment boundaries and direction visible. Inspect the entire extent: a stray waypoint can shrink the useful route to a tiny corner. Do not delete an inconvenient outlier without checking its origin. Add only approved contextual features, avoid counting a duplicated route as background, and verify labels and arrows by eye. Nominatim queries are optional external place lookups, not a road-data download; verify returned places and retain warnings. Leave queries blank when geocoding is unnecessary. This avoids that external lookup, not all server-side processing. Use another GIS workflow for polar or antimeridian-crossing data rather than accepting a stretched Web Mercator picture.
Save the SVG and record source hashes, selected segments, point counts, corrections, contextual sources, geocoding choices and rendering dimensions in a separate ledger. Check checkpoint names, intended direction and all required attribution. A screen preview alone is insufficient: open the actual exported PDF or PNG and inspect the full route at the intended print or display size.
The current SVG-to-PDF tool rasterizes before placing the image on a page. Choose suitable density and a fit mode that preserves aspect ratio; inspect for clipped labels and blurred attribution. Page resizing also changes physical scale, so do not claim a fixed print scale without separate verification. PNG has a fixed pixel size; SVG remains the source drawing, not a substitute for GPX data. Archive the approved GPX copy, GeoJSON, SVG, chosen exports and final hashes locally, with unresolved issues and reviewer decision. Use the related geographic workflow for broader format conversion, the comparison workflow for version changes and the print-layout workflow for page assembly. This package communicates a reviewed route, not permission to travel it.
Workflow playbook
Hash the GPX, identify its tracks, routes, waypoints and segments, and record the exact subset authorized for sharing.
Convert GPX to GeoJSON, validate it with a supplied compatible schema and compare selected segment and coordinate counts against the original. Resolve invalid or missing coordinates before rendering.
Normalize representative coordinate notation, respect GeoJSON longitude-first order and compare checkpoints with trusted references. Use two-point great-circle distance only as a sanity check.
Render the approved GeoJSON and separately sourced context. Check segment gaps, arrows, labels, extent and attribution; preserve geocoding warnings and record all rendering options.
Stop for missing coordinates, unexplained jumps or inconsistent segments. A one-point segment cannot draw a line. Polar or antimeridian-crossing routes need suitable external GIS handling instead of forcing this renderer.
The renderer draws supplied features; it does not fetch a road basemap or calculate a route. Add authorized contextual GeoJSON separately. Leave Nominatim queries blank to avoid external geocoding; this does not imply all platform processing is on-device.
Keep SVG as the editable drawing, PDF for a checked page layout and PNG for a fixed-resolution image. The current PDF converter rasterizes SVG, so do not promise a fully vector PDF.
Create the required PDF and/or PNG from the saved SVG. Inspect actual-size legibility and cropping, then hash final files and archive sources and the review ledger.