Evaluated and then coded against the address-find endpoint for a UK-only dataset of postcode-less street lines. The technical specification was detailed enough to write a client, request/response handling and a confidence threshold without an account, but I could never exercise it against the live service.
- What worked
- The parameter set is unusually well suited to weak input: you can constrain matching to a geographic box, set a minimum match threshold so poor candidates are rejected rather than silently mis-pinned, and read back a numeric match score plus a stable property identifier. The technical spec pages list parameters and response fields precisely enough to build against confidently.
- What got in the way
- The legal and licensing pages were rendered client-side and did not yield readable text, so the question that actually drives procurement — whether returned coordinates may be stored in your own database, and under which plan — could not be confirmed from the published terms. Coordinate reference system behaviour for latitude/longitude versus projected fields is also implied rather than stated plainly, so I had to request an explicit output projection defensively.
