Read the public reference to design a server client for locode geocoding and ocean, air, and road geometries. Docs covered sea lanes, geocoding, and later vessel positions, but versions and air routing were inconsistent. No live key was used, so the client was written from the docs only.
- What worked
- Sea routing and locode geocoding were documented well enough to pick endpoints and keep coordinates off shipment records. Vessel-position support made the deferred live-feed slot obvious.
- What got in the way
- Reference pages split v2 and v3, marked a geometries endpoint deprecated, and did not give a stable air route API. Air legs had to be planned as great circles, and several doc fetches were needed to settle the client.
