NG112 reference
Civic Location
Structured NG112 reference page.

112 readiness
Policy, location, routing, and response quality connected in one operational model.
Location
Civic Location
A postal address is often not enough for emergency response. A large office, campus, factory, public venue or warehouse may require building, floor, wing, zone, entrance and access notes to make the location actionable.
Address fields
->Validation
->PIDF-LO civic object
->Routing/display
What it does
Civic location describes a caller using address-style fields such as country, city, street, building, floor, room or area.
Civic location helps route and dispatch when address-style data is more actionable than coordinates alone.
How it works
- Represents administrative area, street and premises fields.
- Adds finer-grained fields where supported and operationally useful.
- Can be validated against authoritative civic data before emergency use.
Key interfaces and protocols
- PIDF-LO civic fields
- LVF
- GIS/address databases
- Enterprise location records
Systems it interacts with
- LVF
- LIS
- ECRF
- PSAP GIS
- Enterprise facility data
Common failure modes
- Postal address lacks dispatchable detail.
- Room names change without database update.
- Country-specific addressing conventions are flattened.
- Translated labels obscure official local address names.
Implementation considerations
- Capture the words responders actually need.
- Keep floor and zone naming consistent with building signage.
- Validate country-specific address formats.
Standards
- IETF RFC 4119
- ETSI TS 103 479
Related NG112 technologies
Related country deployments
No country deployments are listed here until independently verified against official or high-confidence sources.
Related articles
Sources
- RFC 4119: A Presence-based GEOPRIV Location Object Format - IETF, accessed 2026-08-31
- RFC 5985: HTTP-Enabled Location Delivery - IETF, accessed 2026-08-31
- RFC 6442: Location Conveyance for SIP - IETF, accessed 2026-08-31
- RFC 5222: LoST: A Location-to-Service Translation Protocol - IETF, accessed 2026-08-31
- RFC 5031: A Uniform Resource Name for Emergency and Other Well-Known Services - IETF, accessed 2026-08-31
- ETSI TS 103 479 deliverable directory - ETSI, accessed 2026-08-31
Last verified: 2026-08-31
Advertisement