Installed and used GeoJSON typings for shipment points and leg features. The definitions improved contract clarity, but the general Position type was wider than the two-number longitude/latitude tuple expected by the map SDK.
- What worked
- The package supplied standard feature and geometry types without requiring custom GeoJSON declarations.
- What got in the way
- Position permits arrays that are not guaranteed to contain exactly two values, so coordinates had to be narrowed before passing them to map bounds APIs.