Rockbridge County, Virginia Address Import
Rockbridge County, Virginia Address Import is an in-progress is a completed one-time import of Virginia Address Points, covering Rockbridge County, VA.
Goals
Realizing the necessity of accurate and complete map data, the user of this account desires to improve OSM in Rockbridge county by maintaining up to date address points, driveways, & routes; so that OSM can be counted on as a dependable source of routing for everyone, specifically first responders.
Schedule
Background
Proposal started: 2023-08-17
Data formatting complete: 2023-08-29
Import begun 2023-09-02
Import complete 2024-05-19
Since the intention is to be capable of provided accurate address data to first responders, error on the side of leaving an address point rather than removing it, is given when there is uncertainty if an addressable object exists on-the-ground. To clarify this, the address data source is authoritive. Meaning, any address could absolutely be dispatched as a 911 address. When an address is assigned to an open field or parcel of land, where no signs of construction are taking place, it is often removed.
Import Data
Virginia Address Points: https://hub.arcgis.com/datasets/VGIN::virginia-address-points/about
Type of license: Public Domain
When question arise, refernce can be made from the Rockbridge interactive GIS. There are a few addresses in Vesuvious, which are listed both in Rockbridge GIS and Augusta County GIS, with conflicting addr:number tags. On these examples, a decision was reached viewing property data. Rockbridge's land card had $0 valuation, While Augusta County's Real Estate site had taxation assesment. Thus, used Augusta County's addresses for these conflicts.
Import Type
One Time Import.
Status
Import begun 2023-09-02. The data is split in 67 "chunks" of 200 addresses each. View the data.
| Chunk | Changeset | Date |
|---|---|---|
| 1 | 140737819 | 2023-09-02 |
| 2 | 140762043 | 2023-09-03 |
| 3 | 140764043 | 2023-09-03 |
| 4 | 140909342 | 2023-09-06 |
| 5 | 140910971 | 2023-09-06 |
| 6 | 140912740 | 2023-09-06 |
| 7 | 141035939 | 2023-09-09 |
| 8 | 141060318 | 2023-09-10 |
| 9 | 141611912 | 2023-09-22 |
| 10 | 142155820 | 2023-10-04 |
| 11 | 142157447 | 2023-10-04 |
| 12 | 142158266 Part 1 142158540 Part 2 | 2023-10-04 |
| 13 | 142161743 | 2023-10-04 |
| 14 | 143835801 | 2023-11-09 |
| 15 | 144009121 | 2023-11-14 |
| 16 | 144011828 | 2023-11-14 |
| 17 | 140731299 | 2023-09-02 |
| 18 | 140736108 | 2023-09-02 |
| 19 | 140736390 | 2023-09-02 |
| 20 | 140736738 | 2023-09-02 |
| 21 | 140737316 | 2023-09-02 |
| 22 | 141793569 | 2023-09-26 |
| 23 | 144026768 | 2023-11-14 |
| 24 | 144150543 | 2023-11-17 |
| 25 | 144151047 | 2023-11-17 |
| 26 | 144303206 | 2023-11-21 |
| 27 | 144304002 | 2023-11-21 |
| 28 | 144604083 | 2023-11-29 |
| 29 | 144668721 | 2023-12-01 |
| 30 | 145011522 | 2023-12-11 |
| 31 | 145019430 | 2023-12-11 |
| 32 | 145448852 | 2023-12-23 |
| 33 | 145891468 | 2024-01-04 |
| 34 | 145902317 | 2024-01-04 |
| 35 | 146039752 | 2024-01-08 |
| 36 | 146040275 | 2024-01-08 |
| 37 | 146040995 | 2024-01-08 |
| 38 | 146186816 | 2024-01-12 |
| 39 | 146188370 | 2024-01-12 |
| 40 | 146965034 | 2024-01-12 |
| 41 | 147580841 | 2024-02-17 |
| 42 | 147585259 | 2024-02-17 |
| 43 | 147830077 | 2024-02-23 |
| 44 | 147830803 | 2024-02-23 |
| 45 | 149628741 | 2024-04-05 |
| 46 | 149793136 | 2024-04-09 |
| 47 | 150091995 | 2024-04-16 |
| 48 | 150843609 | 2024-05-03 |
| 49 | 150850620 | 2024-05-03 |
| 50 | 150882598 | 2024-05-04 |
| 51 | 150937313 | 2024-05-05 |
| 52 | 151011358 | 2024-05-07 |
| 53 | 151013025 | 2024-05-07 |
| 54 | 151015551 | 2024-05-07 |
| 55 | 150934529 | 2024-05-05 |
| 56 | 151377596 | 2024-05-15 |
| 57 | 151382423 | 2024-05-15 |
| 58 | 151556395 | 2024-05-19 |
| 59 | 151197597 | 2024-05-11 |
| 60 | 151197077 | 2024-05-11 |
| 61 | 151023171 | 2024-05-07 |
| 62 | 151022286 | 2024-05-07 |
| 63 | 151018874 | 2024-05-07 |
| 64 | 151016656 | 2024-05-07 |
| 65 | 140778686 | 2023-09-03 |
| 66 | 140771003 | 2023-09-03 |
| 67 | 140765337 | 2023-09-03 |
Data Preparation
Tagging Plans
| Tag | Example Data |
|---|---|
| addr:housenumber | 68 |
| addr:street | West Railroad Avenue |
| addr:city | Craigsville |
| addr:state | VA |
| addr:postcode | 24430 |
| addr:unit | Contains unit Identifier |
| Key:addr:unit:label | Contains unit designator |
| Names | Fairfield Elementary School |
| Key:fixme | review name *Only when the name tag exists |
A dedicated user account is used for the import.
Data formatting
Download Text data from VGIN address points. Note: as of Q2 data 2023, only the .txt export contains complete data. The shapefile download is missing data including post code. Added the data as a layer in QGIS, and added an additional layer with the county boundary. Exported the points within the boundary to a csv file. Used Chat GPT to format the data. See the chat here. Next, used Chat GPT to split the data into managble chunks, chat here. See the resultant data in Dropbox. Chat GPT, although very helpful, had some problems that rendered using it not appropriate for OSM. See the community discussion for details.
Credit to @tekim for writing a Python script to format the data. The script used can be found in the Dropbox data folder, or on github.
Data Merge Workflow
Conflation
Using JOSM, with the conflation and mapwithai plugin. This preserves the existing nodes or buildings of currently mapped POIs and structures. If a single address is assigned to a building, it is merged with the building. If multiple addresses or units are assigned to a building, they are left as nodes on the building. If the addr:unit is the only differentiator, the building is tagged with the address number only.
Discussion
QA
Manual QA by JOSM review plugin.