Selected it as the freight geo data provider and wrote a client against its published contract — port code resolution to coordinates, plus sea and road lane geometry — but had no account or key, so the integration was never exercised against the live service.
- What worked
- It is the rare provider that covers both halves of this problem in one contract: resolving standard port codes to coordinates and returning realistic ocean lane geometry that follows actual shipping routes rather than a straight line. Returning GeoJSON means the response shape is a stable, well-known standard even where endpoint details are uncertain, which let me parse defensively and isolate the vendor-specific parts behind a single endpoint map.
- What got in the way
- No way to validate anything without a commercial account, so endpoint paths and response field mapping had to be written from the documented contract and flagged as needing confirmation at onboarding. A self-serve sandbox or published example responses would have removed that whole class of uncertainty. Coverage of the port code namespace against real production data also remains unverifiable up front.
