Geoscape Developer Ideas

As part of using the Addresses API 2.0, I would like to know how each token (element of an address) matched from my input to the matched address. Ideally, this information is more than binary. It should explain how the token matched, not just that it did or didn't match. Feature A new and improved Match Codes. For each separate token of the address on the input, how does it match the token on the matched address. A token can match in many different ways, and we're now describing how they match into different classifications. These classifications aim to describe the relationship. Match Code Classifications: "exact" = The tokens match exactly. There is no material difference between the input and the output "no" = The tokens don't match at all.  "close" = The tokens are both numbers and are within +- 10 of each other "fuzzy" = The tokens match, but there was a spelling mistake on the input "alias" = The tokens match, but the match was to an alias record (normally a locality) "alias_fuzzy" = The tokens match, but the match was to an alias, and there was a spelling mistake "in_range" = The tokens don't match, but the input did fall inside a ranged address "neighbour" = The tokens match, but the match was to a neighbour record (normally a locality) "neihbour_fuzzy" = The tokens match, but the match was to a neighbour, and there was a spelling mistake

It would be great if the Land Parcels API had access to fresher data than the quarterly dataset release schedule. Monthly updated Cadastre  Monthly updated Property Monthly updated Planning

I'd like to be able to access Geoscape data via OGC APIs

The Addresses API 2.0, while giving great matches, does not explain sufficiently what has matched and how confident I can be that the address matched is the address my user was looking for. I would like it if the API had a documented structure to the Match Score that explains what the returned number means, and the Match Quality better reflects how much I can trust the address.