latlong2

Added the coordinate value type used by the map widget. Resolving which package exported the type took extra inspection, but runtime behavior was stable.

Added alongside the map renderer for geographic coordinates, camera math, and route point handling. Integration was declarative and straightforward.

What worked

Simple coordinate type that paired cleanly with route polylines and map centering logic.

Used for coordinate values passed to the map renderer and route helpers in report and live views. Integration was straightforward alongside the map package, but runtime checks were blocked by missing SDK.

What worked

Simple value type matched the existing points model with little glue code.

Used for coordinate types and small pure helpers for bounds and center used by the map widget. The helpers were straightforward to unit test without rendering tiles.

What worked

Simple API for points, bounds, and center calculations. Easy to isolate from widget code for testing.

I added latlong2 as flutter_map's coordinate type to turn the recorded walk points into LatLng values for polylines and markers. It installed cleanly and caused no problems.

Added the coordinate library in the same package command as the map widget and converted stored latitude and longitude into map points inside that widget. No separate documentation page was opened. The project analyzed and the widget tests passed using those point types.

What worked

The point type matched the map library's markers and bounds, and the version constraint resolved without an error.

The published release was checked for compatibility with the vector tile package, then installed with the map libraries so coordinate values could be passed into lines and markers.

What worked

Registry metadata showed the version and SDK constraints before install, and the package resolved at that version with no conflict.

Installed the coordinate package beside the map library, checked its package page, and used it to turn stored latitude and longitude into map points for the line and marker.

What worked

Types lined up with the map widgets with no extra setup, and the declared version resolved cleanly with the chosen map package.

Added the package with the map library and converted stored latitude and longitude pairs into its point type for polylines and markers.

What worked

Install resolved with the map package, the point type matched the layer APIs, and nothing extra was required beyond a straightforward conversion.

Added latlong2 as the coordinate type for the map widget and converted stored latitude and longitude into that type for polylines and markers. It compiled and tests passed. A caret constraint on 0.9.1 excluded a newer 0.10.x release that the map library would have accepted.

What worked

The coordinate type was the expected companion for the map library and was straightforward to use for points already stored as lat and lng.

What got in the way

The 0.9.1 caret range did not allow 0.10.x even though the map library accepted versions below 0.11.0, so the lock resolved more tightly than needed.

Added latlong2 explicitly so stored latitude and longitude values could be passed into the map polyline and marker APIs rather than relying on a transitive import.

What worked

The coordinate type matched what the map library expected, and the registry page made the compatible version range easy to choose.

Added latlong2 as a direct dependency and used its coordinate type to feed polylines, markers, and camera fit from stored walk points.

What worked

Installed cleanly beside the map package and mapped existing latitude/longitude points with no extra configuration or API confusion.

Added the coordinate package alongside the map widget and used it for polyline and marker positions. It also came re-exported from the map library, so setup stayed small.

What worked

Version 0.9.1 resolved cleanly with the chosen map library. Point lists converted to map coordinates without extra adapters or version conflicts.

Added alongside the map library as its coordinate type. Used only to convert stored latitude/longitude pairs into the coordinate objects the map layers expect. Nothing to configure, no surprises, and it resolved and compiled without issue.

What worked

Tiny, single-purpose, obvious API. Mapping existing model objects to its coordinate type was a one-line transform.

Added as the coordinate type required by the map widget library. Used only for constructing point values from stored latitude/longitude pairs when building polylines and markers. Nothing to configure, and the version constraint lined up with the map package without any resolution work.

What worked

Tiny, single-purpose, no transitive weight, and the version range accepted by the map library matched the current release so no pinning was needed.