Addresses API V2.11
Introducing Match Governance: Confidence in Address Matching with Geoscape's Addresses API
We've heard you loud and clear! At Geoscape, we're committed to continuously improving our services based on your valuable feedback. We're excited to introduce an enhancement to our Addresses API that addresses one of your most common concerns: inconsistent match confidence explanations. Say hello to Match Governance - the new feature that brings greater clarity and precision to address matching results.
What is Match Governance?
Match Governance is our response to your input on the need for clearer explanations of match confidence in our Addresses API. We understand that accurate address matching is crucial for various applications, from logistics optimization to customer data validation. With the rebuilt matching engine and the introduction of Match Governance, we're taking a significant step forward to provide you with even more reliable and understandable match results.
Enhancing Match Confidence Explanations
No more ambiguity! Match Governance goes beyond just providing match results – it empowers you with detailed insights into why a specific match was made. Read the docs HERE.
Better First Matches, Every Time
Address matching is the cornerstone of location-based services. With Match Governance, we've harnessed the latest technology and methodologies to deliver improved first matches consistently. We understand that accuracy and speed matter, which is why we've fine-tuned our matching engine to prioritize delivering the most accurate result right from the start. No more digging through multiple matches – we're committed to providing the best match for your needs upfront.
How to Experience Match Governance
If you're already using our Addresses API, as of today, you're already using Match Governance. You'll find that the Match Governance feature is applied to Address, streetLocality, and Locality matches.If you're new to Geoscape's Addresses API, now is the perfect time to explore its capabilities. With Match Governance, you can trust that you're getting the most accurate and understandable match results for your geospatial needs.
Other Features
- DS-4265 - Enhancement > Return Dataset Property. A comma-separated list of datasets the address is found in.
- DS-4279 - Enhancement > Filter by GeoFeature. You can now filter matched addresses by the GeoFeature attribution.
- To use this feature, use the minGeoFeatureLevel query parameter. It accepts the values address, approximate streetLocality and locality. This is an optional parameter. For more information, see the parameter here and the definition here.
- DS-4298 - Enhancement > Support for new Street Type “BIDI”
Bug Fix
DS-4373 - BUG > Complex unit description but no type. Some addresses didn’t have a complex_unit_type. This has been corrected. "complex_unit_type": null, "complex_unit_type_description": "UNIT"
DS-4299 - BUG > Locality and Street Locality matches don't return geoFeature
DS-4295 - BUG > Some Tasmanian addresses were not matched without the use of the state filter.
We're Here for You
If you have any questions, need assistance, or want to learn more about how Match Governance works, our dedicated support team is here to guide you every step of the way.Stay mapped, The Geoscape Team
