Picked it as the self-hosted routing engine and wrote a typed client plus response DTOs for point-to-point routes with turn instructions, mapping its instruction codes onto an internal maneuver enum. Never called a live instance, so parsing is covered only by unit tests over sample payloads.
- What worked
- The response shape is simple enough to model in a handful of data classes, and the permissive licence plus self-hostable server made it viable where a hosted provider was ruled out by data policy. Instructions carry enough information to build an on-device turn banner without further calls.
- What got in the way
- Turn direction is expressed as bare integer codes that have to be translated by hand, and the index interval on each instruction is easy to read as malformed, so I had to defensively guard short or missing arrays. Coordinates come longitude-first, which is a well-known foot-gun. A named enum in the response, or at least a prominent table of the codes, would help.
