TAMU GeoServices
About Services Pricing Support News
Log In Sign Up
  • Address Processing
  • Geocoding
    • Platform Details
    • Interactive Geocoding
    • Batch Processing
    • Geocoding API
    • Desktop Client
    • Esri ToolBox
    • Other Geocoders
  • Geocode Correction
  • Census Intersection
  • k-Nearest Search
  • Reverse Geocoding
  • Drag & Drop Mapping
  • Privacy & Security
  • Terms of Use
  • Get Started Now!
    Platform Summary
    • Overview
    • Publications
    Technical Specs
    • Geographic Coverage
    • Reference Data Sets
    • Feature Matching
    • Feaure Interpolation
    Quality Metrics
    • TAMU Quality Metrics
    • NAACCR Quality Metrics
    Bugs, Requests & Issues
    • Known Bugs

Known Bugs

Services › Geocoding › Platform Details› Known Bugs

The following list contains the set of known bugs for this release of the geocoding service. We are constantly working to improve the service and will be addressing these bugs in future releases. If you discover or suspect another bug, please report it.



ID Type Description
1 Input data Street intersection data are not supported
2 Feature matching A state is required to obtain any type of street- or parcel-level match
3 Feature matching Probabalistic feature matching is not supported
4 Feature matching/Feature interpolation Street centroids are not returned for street level matches without address numbers
5 Address parsing/Feature matching Zip codes with leading zero's get the leading zero's removed
6 Address parsing/Feature matching City portions of an address are not normalized so you should pre-normalize them if possible, e.g., use "East Hanover" instead of "E Hanover"
Texas A&M University © 2022 · GeoInnovation Service Center · B-GSVCSWEB | Version-20240612.5 | Release-122
About Contact Careers Security Policy Privacy Policy