Oklahoma/Import/Garvin
See Import/Guidelines and Automated Edits code of conduct for more information. Imports/automated edits which do not follow these guidelines might be reverted!
Garvin County NG911 local-road project
This is a proposed, phased project to reconcile local-road names and add individually confirmed missing public minor/local roads throughout Garvin County, Oklahoma. The disclosed consultation scope is Garvin County, but editing would begin with a ten-road pilot and pause for review. It is not a statewide upload, a highway replacement project, an automated geometry update, or a deletion/replacement of existing OSM roads. No OpenStreetMap edits have been made under this proposal.
Goals
- Add only roads that are confirmed to exist, are public, are missing from OSM, and can be assigned an observable OSM functional classification.
- Add an NG911 `FullName` to an existing unnamed OSM local road only after confirming that the source and OSM geometries represent the same road corridor.
- Preserve all existing OSM objects, history, relations, restrictions, and mapper improvements.
- Establish a conservative, auditable review process before considering any broader Oklahoma work.
Source
- Provider: Oklahoma 9-1-1 Management Authority
- Catalog: https://okmaps.org/OGI/search.aspx
- Layer: public road centerlines only
- Garvin source agency: Garvin County 911 (`psap.8274.ok.gov`)
- Source snapshot date for the proposed missing-road candidates: 2026-07-06
- Oklahoma NG911 standard:
https://okmaps.onenet.net/documents/OK_ADDRESS_STANDARDS_3_APPROVED_05-02-2024.pdf
Address points, address ranges, ESZ data, and all nonpublic layers are outside this pilot.
Permission evidence
The Oklahoma 9-1-1 Management Authority provided the following written statement:
The centerline and map point data that we have on the public facing side of OKMaps is open to anyone that wants to use it. The ESZ data is not for public release.
The public road-centerline layer is the only Authority data used by this project. OSM community review of this permission statement for ODbL compatibility is pending. Proposed attribution is to the `Oklahoma 9-1-1 Management Authority` on this page, the OSM Contributors page as appropriate, and relevant changesets.
Data screening
The source was screened against a checksum-verified Geofabrik Oklahoma extract containing OSM data through `2026-08-30T20:21:06Z`.
| Disposition | Segments |
|---|---|
| County-tagged source records | 5,000 |
| Expired records excluded | 9 |
| Unique active records screened | 4,991 |
| Likely existing local-road matches | 1,735 |
| Local name-conflict review | 1,714 |
| Nearby unnamed OSM-road review | 371 |
| Same-name alignment or partial-gap review | 56 |
| Numbered highways excluded | 576 |
| Major OSM-road matches excluded | 324 |
| Private, driveway, or placeholder names excluded | 115 |
| Apparent missing local-road source segments | 100 |
The 100 apparent missing segments total 66.7 km and form 66 named review groups. They are review candidates, not approved imports.
Road-name audit and candidate tiers
The following counts mix source-row and unique-OSM-way units and are diagnostics, not additive totals or approved edits.
| Diagnostic | Count | Treatment |
|---|---|---|
| Source rows with the same primary OSM name, ignoring case | 1,776 rows | No primary-name change |
| Primary-name attention queue | 2,100 rows; 945 unique OSM ways; 377 NG911 names | Further conflation screening |
| OSM ways associated with multiple NG911 names | 110 ways | Ambiguous; defer or resolve individually |
| Unnamed OSM way associated with exactly one NG911 name | 308 ways | High-confidence name-only screening queue |
| Above unnamed/one-name ways with all matched source segments within 5 m | 240 ways | Additional relation, access, classification, version, and visual checks required |
| Named OSM way with one OSM name versus one NG911 name | 535 ways | Manual name-conflict review; no automatic overwrite |
| Apparent missing-road groups | 66 groups | Full individual geometry, access, classification, imagery, and topology review |
Source-name formatting
The Garvin data contains 862 distinct NG911 `FullName` values. All are uppercase, none contains periods, and none uses standard road-type abbreviations such as `RD`, `CR`, `ST`, `AVE`, `BLVD`, or `HWY`. An accepted source name therefore changes letter case only for OSM presentation. Abbreviation normalization is used only to compare complete NG911 names with abbreviated legacy OSM or TIGER names.
Project scope
The requested consultation scope is Garvin County local-road name reconciliation and individually confirmed missing public local roads. The project will be performed in small documented phases beginning with the ten-road pilot. No other Oklahoma county is included in this consultation.
Scope exclusions
- Interstate, US, Oklahoma state, turnpike, ramp, and other major roads
- Existing-road geometry replacement
- Private roads and driveways
- Service drives, alleys, parking lots, trails, and vehicular trails
- Address points and address-range interpolation
- ESZ or other nonpublic emergency-service data
- Automatic translation from NG911 `RoadClass` to OSM `highway=*`
- Automatic or unattended uploading
Conflation
The read-only preparation tool compares source primary and alternate names against OSM `name`, `alt_name`, `official_name`, `old_name`, `loc_name`, and `ref` values. It uses nearby-geometry screening and conservative name normalization. Common Oklahoma rural-grid forms such as `North County Road 3200` and `N 3200 Road` are treated as name variants for screening only.
The NG911 `FullName` is the authoritative local road name for an approved feature. Normalization is used only for detecting matches and never to choose the uploaded name. For example, `NORTH COUNTY ROAD 3258` becomes `name=North County Road 3258`, not a shortened legacy TIGER form. If a matching OSM way has a different name, it is conflated and preserved rather than duplicated or deleted. The former OSM name is retained as `alt_name=*`, `old_name=*`, or another appropriate tag only when evidence supports that meaning.
Each apparent gap must be reviewed individually against current OSM data and OSM-permitted imagery or local survey. A reviewer must confirm:
- the road physically exists;
- the road is public rather than a driveway, track, or paper road;
- it is not already represented under another name or with offset geometry;
- its functional `highway=*` value is observable; and
- its topology and county-boundary connections are correct.
Uncertain features will be rejected or deferred.
For a proposed name-only addition to an existing unnamed OSM way, automated screening must first confirm one source name, close geometric correspondence, local-road scope, and no detected conflicts. A reviewer then confirms that the existing way represents the same complete road corridor. Only `name=*` is proposed; the existing geometry, tags, nodes, relations, and history are preserved.
Reviewed ten-road pilot
All ten road-level cases passed an initial user visual review on 2026-08-31. This is not upload approval. The three geometry cases remain held for independent topology, access, classification, endpoint, and imagery checks. The seven name-only cases are ready for proposal review.
| Case | Proposed name | Proposed action | Related OSM way | Current state |
|---|---|---|---|---|
| P-001 | North County Road 3258 | Add possible missing road | — | Second review required |
| P-002 | East County Road 1500 | Add possible missing continuation | 14763489 | Second review required |
| P-003 | Alvera Lane | Add locally confirmed new extension | 676767064 | Second review required |
| P-004 | Butler Road | Name existing unnamed way | 14762516 | Ready for proposal review |
| P-005 | North County Road 3025 | Name existing unnamed way | 14762878 | Ready for proposal review |
| P-006 | North County Road 3230 | Name existing unnamed way | 14761025 | Ready for proposal review |
| P-007 | North County Road 3382 | Name existing unnamed way | 14762474 | Ready for proposal review |
| P-008 | North County Road 3160 | Name existing unnamed way | 14767266 | Ready for proposal review |
| P-009 | East County Road 1565 | Name existing unnamed way | 14765535 | Ready for proposal review |
| P-010 | East County Road 1632 | Name existing unnamed way | 14760596 | Ready for proposal review |
Tagging
There is no bulk tag conversion. Candidate tags require individual review.
| Source information | Possible OSM tag | Rule |
|---|---|---|
| Verified residential street function | `highway=residential` | Only when observable |
| Verified minor public road function | `highway=unclassified` | Only when observable |
| Oklahoma NG911 `FullName` | `name=*` | Authoritative local name; change only capitalization and punctuation for OSM presentation |
| One-way, access, surface, bridge, tunnel, layer | Corresponding OSM tags | Only with independent verification |
| NG911 IDs, PSAP/ESN, ranges, maintenance metadata | none | Do not copy to OSM object tags |
Proposed editing process
- Complete community and license review and wait at least the required import-review period.
- Refresh the OSM extract and rerun the screening.
- Begin, if approved, with only the documented ten-road pilot and pause for community review.
- Process high-confidence one-name/unnamed-way candidates only after automated conflict, relation, access, classification, version, and visual checks.
- Review existing-name conflicts individually without automatic overwriting.
- Review the 66 apparent missing-road groups individually for existence, access, classification, imagery, endpoints, and topology.
- Defer ways associated with multiple NG911 names unless they are resolved individually.
- Use geographically coherent changesets containing approximately 10–25 road-level changes initially, adjusted according to community feedback.
- Record source NGUIDs, decisions, OSM IDs, and changeset IDs outside OSM.
Proposed changeset metadata:
- `source=Oklahoma 9-1-1 Management Authority; survey/approved imagery as applicable`
- `source:date=2026-07-06`
- `import=yes`
- `comment=Garvin County NG911 local-road reconciliation, batch [ID]; see [approved wiki URL]`
A dedicated import-only account named below will perform every project edit. The exact changeset policy will follow the community-approved plan.
Quality assurance
JOSM validation and post-edit routing/topology checks will cover:
- duplicate and overlapping geometry;
- disconnected or nearly connected endpoints;
- unintended at-grade crossings;
- county-border seams;
- improper road classifications and names; and
- unexpected relation or restriction changes.
Revert plan
Work will stop immediately if a material problem is found. Because changesets will be small and recorded in the review queue, the affected changeset can be identified and reverted promptly in coordination with the community. No further group will be edited until the cause is understood and the process documentation is corrected.
Importer and schedule
- Proposer and forum account: GeoSafe-Moshe
- Wiki account: GeoSafe-Moshe
- Dedicated import-only account: GeoSafe-Moshe_Import
- Code/sample repository: https://github.com/GeoSafe/oklahoma-ng911-osm-import/tree/main/counties/garvin
- Earliest start: only after permission acceptance, community approval, and the required review period