[Imports] Burlington VT Building Footprints

[William Morris]

For lack of a JOSM option, I just cleaned the data using the Python field
calculator in QGIS, then ran it all back through ogr2osm. It looks like the
leading/trailing spaces were a data type artifact, and "integer" fixed
them. Here's the latest:

https://dl.dropbox.com/u/23616645/Geosprocket_Share/btv_prints_011513.osm

-Bill



----------
William Morris
Cartographer
(802)-870-0880
wboykinm at geosprocket.com
Twitter: @vtcraghead

GeoSprocket LLC, Burlington VT
www.geosprocket.com


On Tue, Jan 15, 2013 at 9:38 AM, William Morris <wboykinm at geosprocket.com>wrote:

> 1. trim trailing (and leading) spaces from values
>
> Weirdly, these are being added when I pipe the shapefile through ogr2osm
> (both Paul's and Andrew's versions). I'm not sure what's going on there.
>
> 2. housenumber should be '69', integer
>
> Agreed.
>
> 3. Use natural capitalisation for street names, 'Catherine', not all caps
>
> On it.
>
> 4. height should be '8 m', trim the .00000 and add unit. You could skip
> 'm' as this is the default
>
> I'll set it without units; consensus was definitely that meters are
> default.
>
> 5. name tag should not be address, there is addr:full tag for this. Name
> is for buildings which have really own special name, e.g. 'City hall'
>
> Gotcha. Good to know that addr:full is an option; I had thrown those in
> name for lack of a better location.
>
> The world of XML being fairly alien to me, I find myself wishing for a
> JOSM feature similar to the field calculator in QGIS. Basically anything
> that lets me manipulate "attribute" values with python or javascript to
> trim spaces and concatenate strings. Is there any talk of such a feature?
>
> -Bill
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/imports/attachments/20130115/cf225d52/attachment.html>