Hi Brian, - I agree with Serge, the attribution and source tags should go on the change set. In general, I think anything that makes the import stand out as an "import" is probably not ideal. Strive to make the data look just like it was mapped by hand.
- I have code here that might be some help. https://github.com/jremillard/osm_building_import https://github.com/jremillard/osm-import-toolkit Specifically, upload script and the split script could be useful to you. Its kind of borderline for uploading with JOSM. Ideally, you will have around 10,000 nodes/ways per change set. You are looking at around 25 change sets for the entire upload. It will be 10 minute each, about 4.5 hours for the entire upload. - watch out for schools. People tag the building amenity =school, and leave out the building tag. If you have code that checks for overlap, it will miss it. - The license is kind of weird. They have a disclaimer of liability, but nothing else. - On the addresses. You should put the addresses on the houses if possible. I believe the following rules will work. combine parcels that are at the same address if one address on a parcel, put the address on the largest structure if the structure is not also in another parcel. if more than one address on a parcel and the parcel has only one building that is not shared with another parcel put the address on the building. else, put it on the "center" of the parcel on an address node (ST_PointOnSurface). You also need to figure out how you are going to tag multiple addresses, etc, etc. - You should make sure you load in your OSM file in JOSM, and validate it. JOSM is really good at finding problems. Ideally, it should be clean. You will want to download all of the data after the import, and repeat the validation. Anything that is double imported by accident will get flagged. - make sure to de-node it in postGIS, ST_SimplifyPreserveTopology(the_geom,0.20) in your select statement (assuming your data is in meters). - When you get an OSM file, please post it to the list. We can take a look at it. Thanks Jason. On Sun, Jun 9, 2013 at 4:06 PM, Brian H Wilson <[email protected]> wrote: > I am working on getting the Benton GIS buildings data into the right shape > to do a mass import. > > I have not done an import before so I am looking for comments. > > At this point I have done lots of processing for fun learning PostGIS but I > think the building footprint tags will be relatively minimal. > I also have address point data which I will be loading and think the more > advanced tagging (situs etc) belongs there. > > building=yes > attribution="Benton County, Oregon GIS services" > source="Buildings shapefile, 11 May 2013" > > I have yearbuilt and bedrooms=N in the parcel data but can't connect that to > the building so I will probably leave it out. Likewise I can't positively > determine which building is residential. > > I have names for every building on OSU campus but might exclude that area > because it's already got buildings in OpenStreetMap. Will just double check > that it's correct. > > Does anyone have an opinion on the minimal size I should pull in? My data > includes sheds and outbuildings that are very small. I was thinking of > cutting it off at 200 sq ft since buildings smaller than that do not require > permits. (My 6x8 greenhouse and 6x6 shed are in the database which is > derived from air photos) > > Comments in the Wiki say importings of parcels is "bad" but don't have any > comments as to WHY that's bad. (It's TBD) If I knew why I would update the > Wiki. > > Brian Wilson > Corvallis Oregon > > _______________________________________________ > Imports-us mailing list > [email protected] > http://lists.openstreetmap.org/listinfo/imports-us _______________________________________________ Imports-us mailing list [email protected] http://lists.openstreetmap.org/listinfo/imports-us
