[Imports] Orange County, California Building and Address Import

Wed Jul 29 16:59:47 UTC 2020

Hi Tod,

I wanted to respond to your questions below from my Esri perspective.

> 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. <

Esri is not planning to do a bulk import of the Orange County Buildings.  We processed the Orange County Buildings, along with some other open GIS datasets, to make the data available through new tools in a couple OSM editors (RapiD and JOSM) for OSM mappers to manually review and edit individual features.

We created the import page(s) so we could explain the work that was done to prepare the data, share the processed data with other OSM mappers to review, and explain how the data could be added to OSM through the new tools.  If you’d like to work with that data, I would suggest trying the new tools in RapiD or JOSM.  They should work well for you to manually review and edit individual features with fields that have been pre-processed for use in OSM.  I added some more detail to the wiki page with direct links to the tools to make easier to access.

If you’d prefer to do a bulk import for some or all of the Orange County Buildings data, then I believe you’d want to proceed with the steps you mention to document the import plan, update the import catalogue, setup specific import accounts, etc.  That is what we did for a couple large-scale imports (i.e. Redlands, CA and Flagstaff, AZ) we performed earlier this year, and will do again for any more we want to do going forward.

Feel free to ping me directly if you have any trouble accessing the tools or data.

Thanks,
Deane

---------- Forwarded message ---------
From: Tod Fitch <tod at fitchfamily.org<mailto:tod at fitchfamily.org>>
Date: Tue, Jul 28, 2020 at 10:58 AM
Subject: [Imports] Orange County, California Building and Address Import
To: <imports at openstreetmap.org<mailto:imports at openstreetmap.org>>

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<https://urldefense.com/v3/__https:/wiki.openstreetmap.org/wiki/Import/Guidelines__;!!CKZwjTOV!l_KV9WaK5fP7Y887vWEHxM_5r3pxh_bQRtWGRs5R2xucKHR5aK4VnLJUf_rr$>
[3] https://wiki.openstreetmap.org/wiki/Import/Catalogue<https://urldefense.com/v3/__https:/wiki.openstreetmap.org/wiki/Import/Catalogue__;!!CKZwjTOV!l_KV9WaK5fP7Y887vWEHxM_5r3pxh_bQRtWGRs5R2xucKHR5aK4VnGmPv_Kj$>
[4] https://github.com/n76/OSM_OC_Buildings<https://urldefense.com/v3/__https:/github.com/n76/OSM_OC_Buildings__;!!CKZwjTOV!l_KV9WaK5fP7Y887vWEHxM_5r3pxh_bQRtWGRs5R2xucKHR5aK4VnGENTEvp$>
[5] https://wiki.openstreetmap.org/wiki/Import/Orange_County,_California_Buildings<https://urldefense.com/v3/__https:/wiki.openstreetmap.org/wiki/Import/Orange_County,_California_Buildings__;!!CKZwjTOV!l_KV9WaK5fP7Y887vWEHxM_5r3pxh_bQRtWGRs5R2xucKHR5aK4VnIKSHpdK$>
[6] https://lists.openstreetmap.org/pipermail/imports/<https://urldefense.com/v3/__https:/lists.openstreetmap.org/pipermail/imports/__;!!CKZwjTOV!l_KV9WaK5fP7Y887vWEHxM_5r3pxh_bQRtWGRs5R2xucKHR5aK4VnPJ4ScMv$>
_______________________________________________
Imports mailing list
Imports at openstreetmap.org<mailto:Imports at openstreetmap.org>
https://lists.openstreetmap.org/listinfo/imports<https://urldefense.com/v3/__https:/lists.openstreetmap.org/listinfo/imports__;!!CKZwjTOV!l_KV9WaK5fP7Y887vWEHxM_5r3pxh_bQRtWGRs5R2xucKHR5aK4VnB5EIJ5f$>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/imports/attachments/20200729/9cf68e5d/attachment-0001.htm>