ANTBYTES GIS — E911 REFERENCE COMPARISON 2026-10-22T01:14:16.910441+00:00 (UTC query timestamp) OUTCOMES Exact address match: 64 Address difference — review: 17 Multiple address points: 6 No address match: 9 ZIP difference — review: 3 Input needs cleanup: 1 SOURCE https://arcgis.tampagov.net/arcgis/rest/services/Address/AddressPoints/FeatureServer/0 City of Tampa GIS; service describes current address points within Hillsborough County METHOD Read-only current-point lookup. Normalize case, punctuation, common street types and cardinal directions; require matching street number, street text and ZIP for automatic match. Multiple exact points are not auto-selected. Suite/STE wording is normalized; base-address candidates never establish an unlisted unit. Alternative/truncated input text is flagged for cleanup. Follow up nonmatches by house number and distinctive street tokens without a ZIP constraint. Fuzzy similarity only proposes review candidates, never accepted points. No operational E911 systems queried. SERVICE NOTE The county EGIS-Admin endpoint returned metadata/counts but record queries failed; the public Tampa GIS current-address-point service was used instead. FILES Comparison CSV: all 100 original record IDs with lookup status, exact-match coordinates where accepted, point type, capture method, source IDs, and query timestamp. Review candidates CSV: alternatives only, not approved matches. GeoJSON: 64 exact street/ZIP reference matches; RFC 7946 longitude/latitude coordinates in EPSG:4326. Summary JSON: outcome and per-ZIP counts plus methodology. An exact reference-address match does not verify current facility identity, postal deliverability, building entrance, or surveyed accuracy. Multiple current points at one address remain ambiguous. Base-address matches do not establish a missing suite. A no-match result is not proof that an address is invalid. The original source inputs were not changed. No operational E911 or dispatch system was accessed.