Get Full Government Meeting Transcripts, Videos, & Alerts Forever!
Get email alerts on the Data Quality Address Validation topic
No spam. Unsubscribe anytime.
Utah to make address validations fatal in data collector; districts urged to fix invalid addresses
Summary
State data staff warned LEAs that district‑of‑residence and invalid address validations will become non‑loading fatal errors on Feb. 3; they summarized failure counts, geospatial workarounds and next steps.
State data staff told LEAs that address validations in the state data collector will change from warnings to fatal, non‑loading errors on Feb. 3 if unresolved, and urged immediate attention to affected student records.
Cliff (staff member) explained that two validations — "invalid address" (address cannot be validated) and "invalid district of residence" (address not found inside reported district boundaries) — will become fatal errors on Feb. 3. He said the state uses a location database derived from county surveyors (provided through the Utah Geospatial Resource Center) to validate addresses and district boundaries; that database can lag behind U.S. Postal Service listings because surveying and county updates are not always frequent.
Current scale and impact As of the meeting, Cliff reported 2,793 student records across 72 districts with invalid address warnings and 64 records across 17 districts flagged as invalid district‑of‑residence warnings. If left unresolved after the switch to fatal errors, affected students already in the state system will stop receiving updates, may be excluded from state program loads (such as assessments or child nutrition reporting), and may prevent LEAs from meeting submission requirements tied to funding and reporting.
Geospatial fields and validation priority Staff reviewed three optional geospatial fields LEAs can use when physical addresses fail validation: GPS latitude/longitude, a geocode that can be selected via a browser map interface, and a geocode derived from the address itself. The state’s priority when resolving an address is: (1) geocode (browser map selection), (2) GPS (if available), then (3) physical address validation against the location database. Cliff said the geocode is often the quickest way to resolve an address that fails a postal validation.
How to resolve Cliff advised LEAs to first check for typographical entry errors; if the address is correct but still fails, use the geocode or GPS fields to resolve the validation. He encouraged LEAs to work with county surveyors to update the Utah Geospatial Resource Center if the address is new or in a recently developed area. Staff also offered support via help tickets and walkthroughs.
Why it matters: The change to fatal validations will block records from updating in other state applications and can affect assessments, funding eligibility, and program enrollment. Staff urged districts to prioritize resolving flagged addresses before the Feb. 3 enforcement date.
Ending: Staff said they would provide support and asked LEAs to submit tickets for difficult cases; they repeated the Feb. 3 timeline and recommended local conversations with county surveyors for newly built or rural addresses requiring survey updates.
