You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
an enhancement to the geocoder would be to return whether the matched address is residential or commercial.
This would only apply to address-point matches, but it would be a useful enhancement. A great use-case is geocoding voters and also 911, for dispatch purposes.
This info can be found in the location.address_points' pttype field. It will require a little standardization of the existing values (casing, etc). Here are the existing, distinct values in that field:
The text was updated successfully, but these errors were encountered:
@gregbunce is this still something you would like to see us pursue? It seems a little out of stride for geocoding and a little janky that it would only be on address points. But if there is still a strong enough case for voting/911 then we can figure something out.
Currently doing a search for address points would give you this data so it's not impossible. Maybe the GQL API would make this request redundant.
an enhancement to the geocoder would be to return whether the matched address is residential or commercial.
This would only apply to address-point matches, but it would be a useful enhancement. A great use-case is geocoding voters and also 911, for dispatch purposes.
This info can be found in the location.address_points'
pttype
field. It will require a little standardization of the existing values (casing, etc). Here are the existing, distinct values in that field:The text was updated successfully, but these errors were encountered: