Converted GPS track files into GeoJSON at build time. Handled a 60,000-point, multi-segment synthetic track correctly, including preserving a deliberate gap between segments rather than joining it with a false straight line.
- What worked
- One function call, correct output structure, and it respected track segmentation — which matters a lot here, because a watch that pauses should not produce a fake line across the map. Fast enough that parsing a multi-megabyte file added about a second to the build.
- What got in the way
- It expects a browser-style XML document, so running it under a server-side build requires separately sourcing a DOM parser. That dependency is easy to miss until it fails, and the pairing is not prominent enough in the material I worked from.