Also, only the MS buildings that contain my address point are included at them moment. The address point isn’t always centered on the rooftop so those are left off until i figure out how to include them. I will probably query by parcel data and scape those with only one address on the parcel to include more.

Thanks for the feedback. I check the existing ways by getting the centroid of its bounding box and see if it exists or intersects with the bounding of the MS building. So far that method has worked pretty well. I will include it in my write up and include a geoJSON of the import for review.

You can download a “in-progress” geoJSON here: https://www.dropbox.com/s/qv7m2ivnf1v8v70/Columbia_County_FLA_Buildings.geojson?dl=0

My diary entry is a place to get my thoughts together, obtain valuable feedback (thanks guys :), refine my process. Testing will be done on the dev server and when I feel like it’s ready, I’ll draw up a wiki and see if I can get approval from the community.

I’ve been thinking about data duplication from the start, even though i failed to mention it in my entry.

I’ve pre-processed my data in a sql table. The next step is to identify existing nodes and ways that match my address/building dataset and update my records with the node_id or way_id that already associate with it. I’ll do this by downloading a recent OSM of my county, extract the nodes and ways and compare them to my data set. I’ve not come up with the exact method, but it will probably include using a buffer for nodes with address tags and centroids for existing buildings.