Import of DeKalb County Georgia address and building data

Import of DeKalb County Georgia address and building data is an import of DeKalbGIS::address-points-1 and DeKalbGIS::building-footprints-1 datasets which is of type address points and building footprints respectively covering DeKalb County Georiga, USA. The import is currently (as of 2025-10-09) at the planning stage.

Goals

The current state of address information for the Atlanta area and specifically DeKalb County is patchy at best, making navigation tools based on OSM difficult. The goal here would be to combine the two datasets to improve existing building information in OSM for DeKalb County in addition to adding missing addresses to the database.

Schedule

October 2025 - Get approval to use the data from DeKalb County GIS and start developing scripts to batch the data for QA.

Import Data

Background

Provide links to your sources.

Address Point Data source site: https://opendata.atlantaregional.com/datasets/DeKalbGIS::address-points-1/about

Data license: TBD

Type of license (if applicable): TBD

```Building Footprint Data source site:``` https://opendata.atlantaregional.com/datasets/DeKalbGIS::building-footprints-1/about

Data license: https://creativecommons.org/licenses/by/4.0

Type of license (if applicable): CC-BY-4.0

Link to permission (if required): TBD

OSM attribution (if required): http://wiki.openstreetmap.org/wiki/Contributors#yourdataprovider TBD

ODbL Compliance verified: no

OSM Data Files

Provide a link to the data files you have prepared for import.

Import Type

This will be a one time data load. OSM files to be created. Upload will likely be through JOSM to allow for manual QA review of batches as well as AI based QA.

Data Preparation

Data Reduction & Simplification

Address points are split into two kinds:

1. primary addresses for the parcel that appear to generally be on top of buildings, and 2. secondary addresses for subdivisions such as apartment units that are somewhere in the area of where the unit is.

Building Footprint data does include areas for some external features like decks or courtyards separate from the primary building. There is no way to differentiate which is which.

We'll have different sets of change set batches to allow for easier conflation.

1. Primary addresses where the point is contained in a buliding footprint. Imported as a new way or a modified way if one already exists in the area (if needed). 2. Primary addresses where the point is not contained in a building footprint. Imported as a node. 3. Secondary adddresses. Imported as a node. 4. Addresses that cannot be determined what should happen. Imported in bulk for an area as a note for more mapping.

Tagging Plans

Describe your plan for mapping source attributes to OSM tags. To be determined.

Changeset Tags

Fill in the values your changesets will use.

Key	Value
comment
import	yes
source	name of the source dataset
source:url	dataset link
source:date	age of dataset at time of import, if known.
import:page	link to this wiki page
source:license	license of source dataset, using this format.

Data Transformation

Describe the transformations you'll need to conduct, the tools you're using, and any specific configurations or code that will be used in the transformation.

Data Transformation Results

Post a link to your OSM XML files.

Data Merge Workflow

Team Approach

Describe if you'll be doing this solo or as a team.

Workflow

Detail the steps you'll take during the actual import.

Information to include:

• Step by step instructions
• Changeset size policy
• Revert plans

Conflation

Identify your approach to conflation here.

QA

Add your QA plan here.

Discussion

The post to the community forum was sent on YYYY-MM-DD and can be found here