ADDRESS MAP — OCTOBER 18, 2026

Open Map.html alongside its vendor directory and the other report files. The address data and mapping libraries are local; the county background requires internet access. All 1,192 database address entries are searchable. There are 1,119 mapped entries: 1,026 parcel-address matches and 93 approximate locations. The remaining 73 appear in the unlocated list and unmapped_addresses.csv.

Search by address, recorded owner or case number. Filter by source year, recorded order/action, and location match. Click clusters to zoom and an address to see source history and original documents. List pagination does not limit the points on the map. The pending-case checkbox reflects latest recorded 2026 actions in this database, not a live open-case register.

LOCATION SOURCES
Vanderburgh County GIS parcel and composite street locators:
https://maps.evansvillegis.com/arcgis_server/rest/services/GEOCODERS/Parcels_WGS84_Locator/GeocodeServer
https://maps.evansvillegis.com/arcgis_server/rest/services/GEOCODERS/COMPOSITE_LOCATOR_VANDERBURGH/GeocodeServer
Street background:
https://maps.evansvillegis.com/arcgis_server/rest/services/BASEMAPS/BASEMAP_ESRI_COPY_NO_PARCELS_STREETLABELS_WGS84/MapServer

Raw locator responses, request metadata and hashes are retained in geocoding_sources. Match details are stored in SQLite property_locations, property_locations.csv and property_locations.json. property_locations.geojson contains every accepted point. Mapping libraries: Leaflet 1.9.4 and Leaflet.markercluster 1.5.3.

MATCH INTERPRETATION
Accepted direct matches require score at least 99, matching normalized house/street components and coordinates within the local geographic bounds. Normalization accommodates punctuation, cardinal directions and standard street suffixes. Fuzzy spelling, house-number and direction guesses are not accepted.

Parcel matches are representative parcel locations, not surveyed structures. Hollow/dashed markers identify approximate street interpolation, first-number anchors for explicitly recorded ranges or aliases, and safely cleaned address formatting. One point can represent a range; distinct database address variants can share a point. Cluster totals count address entries, not unique parcels, cases or violations.

Unlocated entries include incomplete or inconsistent source addresses, locator gaps and three parser entries about traffic signs or street-closing times rather than usable property addresses. They remain in the database for auditability and are explicitly flagged in location notes. No guessed points are plotted for them.

Historical records do not establish present ownership, property condition, whether an order was carried out, or current case status. Locations use the current GIS locator rather than a historical parcel map. Archive coverage is incomplete; see the main research notes for missing years and source limitations.

QUERY EXAMPLE
SELECT p.address_normalized, l.latitude, l.longitude, l.match_status,
       l.match_method, l.matched_address
FROM properties p JOIN property_locations l ON p.id=l.property_id
ORDER BY p.address_normalized;

For source observations and cases, join property_history to property_locations using property_id. A source observation is not necessarily a distinct case or order.