QA Locate has in development a variety of industry first and company differentiating solutions.
The QA Locate API supports industry first features, like point-in-time geocoding. This allows users to query the PCIL of a street address not just at the current moment, but at some point in the past.
This is especially useful for vintage datasets containing street addresses that no longer geocode, or for which the returned information is highly suspect, and where the age of the dataset is approximately known.
**this feature is under development, development time and cost, market opportunity
Often times the age of a dataset will not be known and only a rough guess can be had. Or a dataset may contain data from across several years, or even decades. This pattern can be observed in collections of legal and historical documents that contain addresses from years past.
Through our API can you determine when a given street address may have last been valid, and what, if any, the structure’s history has since been.
**may start to need its own page, link when ready
**make placeholder page: massively improved reverse geocoding, we have microsoft data to supply footprints
**group addresses to building or campus
**join datasets at building level or at unit level, de-dupe entries, cluster and search by location, find all duplexes in an area, too much data is keyed by customer address
**blog post on why you shouldn’t key data by street address; standardization, normalization, canonicalization don’t work at scale, you hit all the edge cases
The QA Locate API opens up entirely novel use-cases by supporting contextual queries for a given PCIL.
**add diagram: house with electric meter, water meter, sewer line, A/C unit, ride share, post box, drone delivery
**can leave this one, but also duplicate with investor info
Consider the difference between a delivery driver and an automated drone both delivering packages to a single family home. While the street address is the same, the driver and the drone need to know very different things. The driver needs to know street directions, and where to drop the package in relation to the front door, all to within a few meters. The drone needs to know a safe air travel route and where to land to within centimeters. A simple street address conveys neither the relevant content for the driver or the drone; a StructureLocator™ can handle the needs of both use cases and more!
With the QA Locate API, PCILs can be annotated with contextual information to aid a variety of location-aware services, like:
- package delivery
- maintenance and repair
- riding hailing
- emergency services
- and more!