I made some comments based on lessons learned in Seattle. On Sun, Jun 9, 2013 at 3:49 PM, Brian H Wilson <[email protected]> wrote:
> >> For now I immediately eliminate CONCRETE, DECK, POOL, RUINS and > "BUILDING INTERIOR" (which is the donut hole in buildings with atriums, > since the BUILDING polygon has a hole it's redundant) > For buildings with openings I'd make sure that you import it as a multipolygon. For one it helps mappers distinguish the building, it is also more accurate and third, it looks good! > > > > Should I tag MISCELLANEOUS STRUCTURE and UNDER CONSTRUCTIONS as > "building=yes" and be done with it? MISC does not tell me anything and > UNDER CONSTRUCTION says it will be a building... could be a greenhouse but > I doubt it. I think those are probably all permitted building projects. > I would verify that the buildings under construction are either showing up on Bing image or on site survey. You may want to exclude them from the import for manual import later. > > > I started this page some time ago. It is for Corvallis but comes up if you > do a search for Benton County too -- > http://wiki.openstreetmap.org/**wiki/Corvallis,_Oregon<http://wiki.openstreetmap.org/wiki/Corvallis,_Oregon> > > Most of the county data are online here: > http://gis.co.benton.or.us/**GISDataDownload<http://gis.co.benton.or.us/GISDataDownload> > > > One of the questions for me, for example, is the data license. >> > > 2. Are these buildings addressed? >> > > I have taxlots and I have already added address data from taxlots to the > buildings in PostGIS for exampe > > situs building > ------------------------------**-----------------------+------**------ > 428 NW 26TH ST CORVALLIS, OR 97330-5423 | yes > 4500 SW CAMPUS WAY CORVALLIS, OR 97333 | > 900 SE CENTERPOINTE DR CORVALLIS, OR 97333 | no > 3516 SE SHORELINE DR CORVALLIS, OR 97333 | no > 3519 SE SHORELINE DR CORVALLIS, OR 97333 | greenhouse > 2860 NW POLK AVE CORVALLIS, OR 97330 | no > > I intend to conflate the addresses as the streets are already done. > > TO me it seems a little bit odd to tag a 100 sq ft shed with an address > pulled from the taxlot data. > > I tend to think the address should go on a point feature placed on the > centroid of the taxlot and then manually adjusted as needed. > In Seattle we agreed on the following: if a single node was in the middle of the structure we added the address to the building. If there were two or more address nodes inside the building outline, we left the address as nodes. We did see a number of addresses that are just outside of the building outline. In those cases we left it for the importer to manually determine what to do with the node. While most of the nodes ened up being combined with the building, there wasn't a pattern that we could see. > I have a 'houses' point layer containing situs data too but it looks like > it covers only about 10% of the actual structures and all outside city > limits. > >> >> I also would encourage you to work with local community for a hybrid >> import, of the type that's being done in Seattle. >> > > I just checked their page > http://wiki.openstreetmap.org/**wiki/Seattle_Import<http://wiki.openstreetmap.org/wiki/Seattle_Import> > > I can handle most of this with python and sql scripts, it's what I do for > fun as I am forced to do C# programming right now in my day job. :-) Then > we can get some volunteers to look at the results. I found that PostGIS/QGIS were my friend. It allows for queries to get information with just the columns you want to deal with. QGIS allow you to overlay your proposed import over the existing OSM map. You catch problems before you import. > > > I promised to show how to do data import at my next local meeting. I will > probably choose something simple for demo / community engagement as a > starting point, such as city parks. I have a shapefile that we can use to > double check existing hand drawn data and to add any parks that have not > already been drawn in by my friend MapJunkie. > Try to enlist as many people as possible. It makes for a great community building project. There is some definite gratification from seeing the city fill up with buildings. Even if you import the low hanging fruit, getting the community to import buildings is a great opportunity to teach people JOSM. We are hoping that the imports people did will result in more ownership of a neighborhood. I don't fully agree with Serge and Jason on the source tag. Like others I think it could be useful. A change set tag is appropriate. Until we have agreement on new import guidelines, I think that is up to you and your community to decide what is best for you. Also, I didn't see it, but if you do an auto import, you'll need an import account. -- Clifford OpenStreetMap: Maps with a human touch
_______________________________________________ Imports-us mailing list [email protected] http://lists.openstreetmap.org/listinfo/imports-us
