Madison County fiscal court hears lengthy presentation on proposed GIS hosting with Richmond

Judge Taylor and county staff presented a proposal for Madison County to host the City of Richmond’s GIS data in the county’s standardized database, arguing it would improve emergency response accuracy, meet NextGen 9‑1‑1 data standards and reduce duplicative effort. County staff said Richmond would retain its employees and input its own data into the hosted system under agreed parameters.

The presentation, led by Chris (county staff) with technical examples from Austin (GIS coordinator), laid out what GIS comprises—hardware, software, data and people—and walked the fiscal court through local examples where mismatched or out-of-date data has routed responders to incorrect locations. “We wanted to put together a little presentation to show you all so that it would give you all the opportunity to make the right decision,” Judge Taylor said when introducing the topic.

County staff described the technical and operational benefits of a single hosted database: live Esri REST services that allow computer-aided dispatch (CAD) systems and mobile data terminals to pull current address points and road centerlines directly from the source, enforcement of required address and attribute fields, and the ability to align city and county map endpoints so roads and intersections resolve consistently in dispatch systems. Staff warned that periodic file-sharing (shapefile exchanges) has frequently produced incomplete, out-of-date or misaligned records and that meeting Kentucky’s NextGen 9‑1‑1 roadmap and 9‑1‑1 board requirements is contingent on clean, standardized data.

Austin demonstrated map mismatches: address-range overlaps, non‑intersecting road centerlines where city and county datasets did not align, and examples that county staff said had caused ambulances to travel past incidents. Staff said the county’s data center—hosted in the Emergency Operations Center (EOC)—would store the authoritative dataset, while Richmond employees would continue to work from city facilities and enter edits into the hosted database. Staff estimated Richmond’s share would be small (presented as roughly $4,000–$6,000 annually) and said the arrangement would reduce cost and staff time overall.

Multiple fiscal court members and elected officials supported the proposal on public-safety and efficiency grounds. Several speakers emphasized the county’s need to remain compliant with NextGen 9‑1‑1 standards to continue receiving CMRS-type 9‑1‑1 funds. Concerns raised by members centered on data quality controls; county staff said parameters and validation rules would be added so Richmond could not save entries that lacked required fields.

No formal vote was taken. Judge Taylor asked staff to return a resolution for formal consideration at the court’s next meeting; the court agreed to place the item on the next agenda.