Re: [Talk-us] [Imports] Import of Orange County, California Buildings and Addresses
Tod, You might want to look into Paul Norman's ogr2osm.py [1] python tool which can translate shapefiles into .osm files that can be uploaded using JOSM. It's simple to use, just need to create a translation file for shapefile fields to OSM tag. I'm in the process of doing an import of building and addresses for Marysville, WA. Way smaller than you import. The import page is https://wiki.openstreetmap.org/wiki/Marysville_Import which has links to my code including the ogr2osm.py translation scripts. Feel free to contact me offline if you have any questions. Best, Clifford [1] https://github.com/pnorman/ogr2osm On Tue, Jul 28, 2020 at 3:06 PM Tod Fitch wrote: > I'm planning an import of buildings and addresses for Orange County, > California. Information on the proposed import can be found on the wiki at > https://wiki.openstreetmap.org/wiki/Orange_County_Building_and_Address_Import > > This is a one time import using JOSM. > > A links to the data being imported given on the wiki and the data is > marked as public domain. > > Note: There is an effort by ERSI to make this same dataset available to > mappers working with the RapiD data via MapWithAI. For a description of > that, see > https://wiki.openstreetmap.org/wiki/Import/Orange_County,_California_Buildings > > This is my first attempt at an import so gentle guidance on following best > procedures will be appreciated. > > Regards, > Tod > > ___ > Imports mailing list > impo...@openstreetmap.org > https://lists.openstreetmap.org/listinfo/imports > -- @osm_washington www.snowandsnow.us OpenStreetMap: Maps with a human touch ___ Talk-us mailing list Talk-us@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk-us
[Talk-us] Import of Orange County, California Buildings and Addresses
I'm planning an import of buildings and addresses for Orange County, California. Information on the proposed import can be found on the wiki at https://wiki.openstreetmap.org/wiki/Orange_County_Building_and_Address_Import This is a one time import using JOSM. A links to the data being imported given on the wiki and the data is marked as public domain. Note: There is an effort by ERSI to make this same dataset available to mappers working with the RapiD data via MapWithAI. For a description of that, see https://wiki.openstreetmap.org/wiki/Import/Orange_County,_California_Buildings This is my first attempt at an import so gentle guidance on following best procedures will be appreciated. Regards, Tod signature.asc Description: Message signed with OpenPGP ___ Talk-us mailing list Talk-us@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk-us
[Talk-us] National Forest refs/names
In https://www.openstreetmap.org/changeset/59418875, seems we've hit on some inconsistency in the documentation. https://wiki.openstreetmap.org/wiki/United_States_roads_tagging#Tagging_Forest_Roads suggests that the ref should go in the name for national forest roads, when this is directly contradicted by the common use of name, which is that the name is only the name, as outlined at https://wiki.openstreetmap.org/wiki/Names#Name_is_the_name_only Also specifically about that road in that changeset, name=Dufur Valley Road got moved to alt_name, though I can confirm firsthand that the addresses along it are Dufur Valley Road and it's signed as such at least at the east end. Could we get the US Road Tagging page updated to reflect common name practice instead of encouraging the duplication of the ref in the name? Or is that going to spark drama? ___ Talk-us mailing list Talk-us@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk-us
[Talk-us] Orange County, California Building and Address Import
I became aware that Orange County, California has released building outline and address data to public domain [1] and started prep work for import to OSM. In reading through the import guidelines [2] it seemed the process was: 1. Create a workflow (but don’t do any actual importing at this stage). 2. Document the workflow in both a dedicated wiki page and in the import catalog [3] 3. Announce to the tagging list and the list for the area, in this case talk-us, the proposed import. 4. Once comments on the proposed import have been addressed, commence the import (documenting progress along the way). To that end, I have reviewed the data. Processed sample portions to the point just short of uploading to OSM to verify I think the workflow is okay. This is where I am at present: 1. I’ve reviewed the data and decided that a rather slow manual process is needed because of the low quality of the building outlines. 2. I’ve created a workflow and tested to the point where I think it will result in a good quality import. 3. I’ve created a GitHub project containing the description and scripts I am using [4]. 4. I started to create a wiki page containing the same description but found an existing import page for the same data [5] At this point I am paused and looking for guidance as there is another import proposed for this data. I don’t see evidence that this other import has actually started. I have added a discussion item to that import page expressing my concern about building footprint quality and the steps that will be needed to bring it up to standard and given my GitHub project page link. But I am confused. I thought that imports needed to be added to the catalog. This import is not in the table at present. I thought that import specific user IDs were required. This import pages states “The plan is for most OSM mappers to use their standard OSM accounts if they are editing with RapiD and JOSM editors. . .” I thought that imports needed to be announced in this import list. Looking though the archives [6] for the last few months, I don’t see it. So, do I continue with my import plan with the next step being creating a new wiki page for it? Or do I wait for ERSI to do an import then verify the quality? I don’t see a way to participate with ERSI listed in the import wiki page they’ve created. Thanks for the guidance! Tod Fitch [1] https://data-ocpw.opendata.arcgis.com/datasets/8db4b58e6bbf4f6cac676f477348be48_0 [2] https://wiki.openstreetmap.org/wiki/Import/Guidelines [3] https://wiki.openstreetmap.org/wiki/Import/Catalogue [4] https://github.com/n76/OSM_OC_Buildings [5] https://wiki.openstreetmap.org/wiki/Import/Orange_County,_California_Buildings [6] https://lists.openstreetmap.org/pipermail/imports/ signature.asc Description: Message signed with OpenPGP ___ Talk-us mailing list Talk-us@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk-us
