Could you share the script you used to do this? Others might find it useful.

I'm also interested in videomapping, and might get to working on the plugin someday. Could you share your opinions on what you'd like to see?

Thanks! I've put a link to this diary entry on the wiki:
osm.wiki/Manual_conflation

Awesome site, great job!

Hey, too bad I missed this one (due to the RSS feed being messed up). I'm interested in this, as I've been mapping my HOA (rather large, around 6000 units), have created the HOA article on the wiki, and am interesting in tagging specific to HOAs. I'd love to preview your site.

As for the conversion, there's sadly no OGR driver for OSM yet, so your best bet is to go from OSM->Shapefile->WKT (refer to osm.wiki/Shapefiles and ogr2ogr), or maybe try this which I just found but have never tried: http://www.tm.kit.edu/~mayer/osm2wkt/

I would strongly encourage you to read the following page and discuss this on the imports@ mailing list before importing any further parcels:
osm.wiki/Import/Guidelines

Welcome! Sorry no one did this sooner. Glad to have you!

Very interesting, and all good points. Thankfully I've found the Bing imagery to be very accurate in my area.

Thanks for your post, I've found this to be one of the most useful plugins. This reminds me that I've been meaning to create a list/review of the most useful plugins.

I couldn't find a ticket with your patch on TRAC, have you created one? I would be interested and willing to merge this change since the original author is too busy, and it is functionality that I've been wanting for a while.

From osm.wiki/Remapping#Imaging_Background, you can view the license layer in JOSM with:
tms:http://tools.geofabrik.de/osmi/tiles/wtfe/{zoom}/{x}/{y}.png

And Potlatch2 with:
http://tools.geofabrik.de/osmi/tiles/wtfe/$z/$x/$y.png

Great work!

Welcome! Glad to have you, and hope you enjoy OSM.

Pink Duck, Chaos99: If you wish to discuss/debate abbreviations more thoroughly, consider reading and responding to the recent thread on the talk@ list with the subject "shortened names", which you can read here on Nabble, all 94 messages (!).

I hope any further comments will consider the design of a general tag transformer, rather than focusing on one specific transformation (such as un-abbreviation).

Chaos99: Yes, this would basically be a find-and-replace function for JOSM, with preview. It would be a little more than that, because it would allow you to remove a tag and add a new one (e.g. changing a key name).

I did just discover that the CommandLine plugin for JOSM does provide a regular expression search and replace, however I think it's worth having a dedicated dialog to make the functionality available to an average user.

I wasn't planning on getting into the politics or technical details of un-abbreviating, as there is quite a bit to it, especially if you keep up with the mailing lists. Conventions and exact implementation will vary by country, which is why in my example I made it clear that each region (country, state, city, etc.) will need their own un-abbreviating script/dictionary.

For the US, I would likely use the logic from balrog-kun's script, using the USPS abbreviation list. For ambiguous cases I can mark them such that they can't be changed en masse, but rather must be individually reviewed (selected).

And keep in mind that the design of this tool is such that changes are reviewed before being made. Also this is meant for the average user to run over a small region that they're working on, not a bot that requires technical expertise and is run over entire countries or the world.

Glad to see another Virginia mapper, thanks for your contributions!

I've added these to the table on the wiki, but I'm not sure if relations exist for them yet:
osm.wiki/WikiProject_U.S._Bicycle_Route_System

There's no reason you can't do both, accept the CT's so that your contributions can continue on in OSM (because Nearmap has explicitly allowed this), but all future contributions will be to FOSM (because you want to use the Nearmap imagery). If you read the list archive, the representative from Nearmap made it abundantly clear that users who mapped using Nearmap imagery are allowed to agree to the CT's so that contributions can remain in OSM (however future mapping in OSM via Nearmap is not allowed). If you don't want to agree to the CT's because you dislike ODbL or something, that's one thing, but don't try and use the Nearmap (non-)issue as an excuse. Your contributions are certainly valued and I hope you allow them to continue in OSM, even if future contributions go to FOSM.

Very cool! I'd love to see this kind of elevation profile service for other types of routes, like bicycling and hiking. I tried to use a relation ID for this type of route, but it failed, so I'm guessing it only works with route=mtb. Would you consider expanding the service to work with other routes, or perhaps sharing the source code so others could setup similar services? Great work!

Sorry to see you go, but glad you've decided to accept the terms for your existing contributions. I'm not happy with the CT/license process myself, but all I really care about is the map. If they wanted to go PD it wouldn't matter to me. If a CC-BY-SA fork is more successful than OSM (though I doubt it), then I'll switch to that project. Thanks for all your contributions!

Very cool, I can't wait to try it out!