[Imports] Building & Address Import - Lexington, KY

[Michael Reichert]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Hi Ryan,

Am 25.02.2016 um 20:47 schrieb Ryan Cooper:
> The two datasets we'll be working with are 2007 impervious surfaces
> <http://data.lexingtonky.gov/dataset/impervious-2007> and address
> points <http://data.lexingtonky.gov/dataset/address-points>. On the
>  former, we will be importing only those polygons classified as 
> "Building".

Do you want to import the building outlines automized at areas where
no buildings exist at OSM yet? I hope not. The data has been derived
from an 2007 aerial image while Bing images at Lexington have been
captured in 2012, according to Bing. This means you hereby propose an
import of outdated data.

Example: https://www.openstreetmap.org/#map=17/37.98484/-84.39793
The city dataset lacks lots of buildings there which are shown on Bing
Aerial. (They look like being rather new)
If you want do compare Bing and the shapefile at JOSM, first do a

ogr2ogr -f "ESRI Shapefile" -spat -84.4333 37.969 -84.3799 37.9951
- -where "Imperv_Typ='Building'" DESTINATION_DIRECTORY/ Impervious_2007.sh
p

to reduce the file size and load it afterwards into JOSM using Open
Data plugin.

I think it would be better to use the shapefile as an additional
source in combination with Bing imagery. You could set up a Mapserver
(or an alternative like Geoserver) which serves a TMS or WMS map
showing the buildings of the dataset. Mapper can use both Bing and the
TMS/WMS together at the same time [1]. Setting up a WMS is rather simple
.

Adding only buildings and addresses just to be added to OSM does not
add any value to OSM. It just increases the file size of the planet
file. But the value of OSM increases if you not only add buildings but
also other details (e.g. parking areas, traffic lights, pedestrian
crossings etc.) while tracing buildings from the TMS/WMS and comparing
them with the newer Bing image.

Best regards

Michael


[1] My favourite editor can make layers half-transparent.

- -- 
Per E-Mail kommuniziere ich bevorzugt GPG-verschlüsselt.
(Mailinglisten ausgenommen)
I prefer GPG encryption of emails. (does not apply on mailing lists)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQIcBAEBCAAGBQJW1KymAAoJEB87G9rMCMyIGwYP/3tJvm0NKGo7ZuhdpncGrLtl
T48tD1P7JxDEIzK+EDzy3qctWqmbUn2M/Uo73hj7AnRVZMCmTt9D5vCGezLKjLXk
/ImOC834PbVe0oi4RGgernSOLI1ElfcYLuVl49TAEK+0AKrrmHkzkrTEySbDGsvG
xOpzx0e/es8fT9iQfCNMYvxjzplSnC8KYs/CH+g1aimNZZwW1lbMNKdFFc3w/Vfy
lhYEK72Ls8Frlkp/nsgtYYUyD5EMlfPorK8JWwQMpsmSunD5cKaxskL3/TmWOJ1r
I/nwXW617T+UWgvhqyXYtwPeWoiaVquhQviIIW4wOrKOsJ2eHS6uXDIlW5Xsc3Uy
zDhubXJdQW+jSF3nY8gbxzlJIS6ISnu/XBXGIMsonA5ZdJZEeGlOOcxDXTiIUQ3e
aDWZxjVWjg3ofgQgmzDYdSTyZRWPqX6u4QzAPDZzJ9+QObLeA0sC4r/d0zLlCVWD
eaIlBA+YatpQnthhF6nd9BYJNYkkt3bQC6VQBGt/rbmKM1pH9yxDWN6V4y+VQfAF
mJrPlZWDX5MsD9tONCdEQ60Jz5jnM0GqO/afGVm9cymU8YaapgKSvXL/xtokFz8L
tUXm+wGzoakaxZ4eBFVA0pq6HVR0/btY35zLgAtDGYxc603v/Ps9QpAu1mXdy/vc
Br3GKOKgzS/IKd96E6DD
=+KYV
-----END PGP SIGNATURE-----