Redirected page to California/Import/Los Angeles County parks
← Older revision
Revision as of 23:46, 26 September 2013
Line 1:
Line 1:
−
==Goals==
+
#
REDIRECT
[[California/
Import
/
Los_Angeles_County_parks
]]
−
To add significant useful land use detail to Los Angeles County. Specifically, the county is lacking polygons for a majority of schools, parks, hospitals, town halls, and retail land use. There is also a small amount of data available for cemeteries, colleges, and golf courses.
+
−
+
−
==Schedule==
+
−
* Start sometime October 2013
+
−
* Finish by January 2014
+
−
+
−
==Import Data==
+
−
=== Background ===
+
−
'''Source site:''' http://egis3.lacounty.gov/dataportal/2011/02/22/la-county-land-types/ <br>
+
−
'''Data license:''' Public Domain, the source site doesn't list it explicitly (they have a disclaimer instead) but I emailed to confirm
+
−
<blockquote>"I need to be clear, specifically is it public domain?" - Aaron Lidman</blockquote>
+
−
<blockquote>"Yes – this data is public domain." - Mark Greninger, Geographic Information Officer, County of Los Angeles</blockquote>
+
−
+
−
===Derived Data Files===
+
−
The derived files are broken up into each land use type, I would like to import one feature set after another seperately, not simultaneously. So all parks must be finished before moving on to schools, then hospitals, etc... Verifying all the data before continuing to the next type. It would just makes giving instructions and QA-ing easier.
+
−
+
−
These are already conflated, useless attributes have been removed, and ready to be converted to a database for OSMLY.
+
−
Right click download:
+
−
* [https://gist.github.com/aaronlidman/6721248/raw/8b5726598b6b0f23a7c3e9102131612f9eb5b0f7/cemeteries.geojson 12 cemeteries]
+
−
* [https://gist.github.com/aaronlidman/6721248/raw/282e71daa5511dd7eb47aaeaa6f69eff8f567d6b/colleges.geojson 21 colleges]
+
−
* [https://gist.github.com/aaronlidman/6721248/raw/c710a87343fee45dd0dc55b375e5d0f6bca092d4/golf.geojson 48 golf courses]
+
−
* [https://gist.github.com/aaronlidman/6721248/raw/1911e070b3fdac0d9a9ab682916f67aaa5e5831f/hospitals.geojson 108 hospitals]
+
−
* [https://gist.github.com/aaronlidman/6721248/raw/f3444af2998e0e25a9a28577ddd690f1e0940161/parks.geojson 737 parks]
+
−
* [https://gist.github.com/aaronlidman/6721248/raw/4ed1690158231be872922904355b48cc12a8b34f/retail.geojson 269 retail landuse]
+
−
* [https://gist.github.com/aaronlidman/6721248/raw/1939eab10fabe221fdc822474399c9484ce73a9b/schools.geojson 2419 schools]
+
−
* [https://gist.github.com/aaronlidman/6721248/raw/9ae81dc8c330da2d6c4955b8a158f9d2ced91c6b/townhall.geojson 82 townhalls]
+
−
+
−
===Import Type===
+
−
* One time import, no plans for updates.
+
−
* Tools:
+
−
** OSMLY - majority of editing, planning, reporting problems, QA-ing
+
−
** JOSM - as needed
+
−
+
−
==Data Preparation==
+
−
===Data Reduction & Simplification===
+
−
#each land use type (parks, schools, etc..) is conflated separately against an OSM extract to prevent mapping features that are already in OSM
+
−
#* this is done in QGIS with a simple spatial query
+
−
# geometry is simplified as it goes into the OSMLY database via Shapely to a tolerance of 0.0001
+
−
* source attributes that are '''removed''':
+
−
** DESCRIPTIO - mostly NULL, the rest aren't useful
+
−
** CAT1, CAT2, CAT3 - categorizations, 'Arts & Recreation' and the like, no use to OSM
+
−
** SOURCE - internal agency that created the data
+
−
** LMS_ID - ids, irrelevant and mostly 0
+
−
** DATE_UPDAT - all NULL
+
−
** Shape_area - area
+
−
** Shape_len - length
+
−
+
−
===Tagging Plans===
+
−
* name="NAME"
+
−
+
−
* tags to be appended:
+
−
** for parks: leisure=park
+
−
** for schools: amenity=school
+
−
** for golf courses: leisure=golf_course
+
−
** for hospitals: amenity=hospital
+
−
** for retail land: landuse=retail
+
−
** for townhalls: amenity=townhall
+
−
+
−
* seems like source is no longer done in individual objects? right?
+
−
+
−
===Changeset Tags===
+
−
* import=yes
+
−
* source=LA County GIS Data Portal - Land Types shapefile - 5/2013
+
−
* source_ref=http://egis3.lacounty.gov/dataportal/2011/02/22/la-county-land-types/
+
−
* OSMLY also applies some changeset tags automatically:
+
−
** created_by=OSMLY
+
−
** osmly:version=1.0.0
+
−
** osmly:import=*unique_database_name*
+
−
** imagery_used=Bing
+
−
+
−
===Data Transformation===
+
−
# source data is conflated as described above (Data Reduction & Simplification)
+
−
# remaining geometry is saved to GeoJSON in EPSG:4326/WGS84 projection
+
−
#
GeoJSON gets processed through an OSMLY preparation script,
[
https://github.com/aaronlidman/osmly-server/blob/master/build.py build.py]
+
−
#* simplifies geometry, marks anything too complex for OSMLY (multipolygons), builds the OSMLY database
+
−
# in OSMLY, data is transformed from GeoJSON to OSM and OSMChange formats with
[
http://github.com/aaronlidman/osm-and-geojson osm-and-geojson]
+
−
#* if opening in JOSM, converts to OSM
+
−
#* if submitting to OSM API, converts to OSMChange
+
−
#* this is done after the user clicks 'submit' to reflect any modifications they may have made on the map
+
−
+
−
===Data Transformation Results===
+
−
*TODO: post sqlite databases
+
−
+
−
==Data Merge Workflow==
+
−
===Team Approach===
+
−
I made OSMLY to try and involve more users than imports previously had but also users that typically aren't involved in imports because of the required technical skills. As OSMLY resolves some of those technical hurdles I'd like to open this up to more users. I've created a list of users among the top contributors in Southern
California
by going over their [http:
//
hdyc.neis-one.org stats
]
and [http://yosmhm.neis-one.org heatmaps
]
, and just people whose names I've noticed come up again and again while editing in the area myself. I've specifically included users who, have lots of experience in time and # of edits, seem local to or knowledgeable of Southern California, are active on a regular basis, and have some variety in editing (not just highways or buildings, etc..). Even if we only get a couple of these users to help it would be nice to get others involved. I'd like to contact them after the import is available and ready to go, simply by sending them a message through OSM.org with a link to the import.
+
−
+
−
List of users:
+
−
Aaron Lidman, nmixter, jerjozwik, AM909, techlady, StellanL, Chris Bell in California, California Bear, Rockear, ctr112280, widesays, Brian@Brea, ponzu, dima, vvvexp97, Al Pascual, evil saltine, Sat, SimMoonXP, happy5214, DMaximus, msebast, DamienRoz, mattmaxon, RexTCA, palewire
+
−
+
−
Anything that needs to be handled more manually (QA, fix reported problems, take on more difficult objects) will be handled by Aaron Lidman. User nmixter has also offered to help as needed.
+
−
+
−
===References===
+
−
* Local knowledge
+
−
* Bing aerial imagery
+
−
* Nearby existing OSM data
+
−
+
−
===Workflow===
+
−
# Log in to OSMLY
+
−
# Get a random geometry
+
−
# Review the surrounding area for conflicting OSM data or necessary adjustments relative to Bing aerial imagery
+
−
# As appropriate: edit geometry, edit tags, report a problem for follow up, open in JOSM or submit directly to OSM.
+
−
# Once the item has been submitted it is available for other users to confirm in QA mode.
+
−
+
−
==QA==
+
−
OSMLY has a QA mode which displays data that has been imported by another user. The surrounding OSM data is downloaded and displayed on a separate layer, allowing a different user to confirm differences between the original data and uploaded data that currently exists on the OSM server. This is a quick and simple means of seeing any immediate problems.
+
−
+
−
In addition all changeset created with OSMLY create a tag unique to that import, if needed we always have the ability to go back and find anything created for this import across any user.
+