Called the public online geocoder while deciding how to turn a street and town into a point. The portal describes it as a cleaning step before a heavier national integration, and the English reference page rendered no usable text. Live JSON came back with latitude and longitude reversed relative to the widget's own fields, and an ordinary town address missed until the wording was changed. It was not used in the implementation.
- What worked
- The JSON endpoint is open and needs no account, so a sample address could be checked immediately and the axis mix-up was visible in the payload.
- What got in the way
- Guidance frames the endpoint as pre-integration cleaning rather than a production geocoder. Returned coordinates were swapped, and street queries for the service area failed until the address text was rewritten.