It certainly does sound like importing massGIS data was a very tedious process. The difficulty I had with adding the nodes as a separate layer was that I could not select the address node to merge.

I do like your idea about providing the data for local users which would be very useful. Essentially the output I am currently able to produce is an xml file that can be opened into JOSM containing all geolocated address nodes for a specific town. Is this what you had in mind?

Example xml for address nodes:

<?xml version=’1.0’ encoding=’UTF-8’?>

Hi Simon,

Thank you for your thoughts and the link.

Perhaps my post is being missunderstood or I am missreading the import guidelines. The data I was using is derived from the same data source as the massGIS L3 parcel import osm.wiki/MassGIS and the wiki page states that it can be used as long as it is sourced.

The idea behind my method was to simply assist in the addition of address data (still manual) and not be an automated bulk import.

In the past, I simply added the background layer of the L3 parcel data in JOSM and added address information one by one to each house within a parcel. Using my method above, I have made it easier to copy this same data into a buildings attributes by placing the address data into a temporary node that will be copied, merged with the building, then deleted. The data is coming from the same source and in the end the address data will be the same if either method is used only quicker with the temporary nodes.

Do you think this would still fall under the bulk import bucket as I am only working on a section of a town at a time? Either way I have joined the imports-us mailing list and will gather thoughts on that list as well.

Thank you for your feedback. In the meantime I will hold off on using this method before I have gathered general concensus from the mailing list.

Frederick