The first question is what is appropriate consultation, and that will vary on a case by case basis with the type of data, complexity of import, type of object being imported, where it's being imported, existing data, experience of importer, feedback received, etc.
I missed adding the link to the appropriate wiki page in the catalogue. It was supposed to part of my pre-import checklist, but got missed. The import was from an account dedicated to imports. There are also some CanVec imports on the same account. I re-organized my accounts somewhat. Being on the DWG I do a very large number of reverts so my account situation is complicated. Most people don't have that issue. From: Jeff Meyer [mailto:j...@gwhat.org] Sent: Thursday, December 27, 2012 11:10 AM To: Toby Murray Cc: impo...@openstreetmap.org; OpenStreetMap US Talk Subject: Re: [Imports] [Talk-us] Proposed import: Alaska Boroughs/CPDs Paul - I'm grateful for your efforts here. I'd like to use this import as a test case for further discussing our current import guidelines and policies. In particular: - Is 3 days a suitable duration for reviewing proposed imports? - Should there be an entry for this import on the Import Catalogue page? - Should the Alaska import use a separate account from other imports you've coordinated? Yes, these q's may sound a little snarky (hopefully in a friendly way ; ) ), but I am sincerely interested in resolving answers to these questions so we can help clarify guidance moving forward. (my take on the answers are: no (2 weeks minimum), no (that page is a disaster), and no clue.) Thanks, Jeff On Thu, Nov 29, 2012 at 8:28 AM, Toby Murray <toby.mur...@gmail.com> wrote: On Thu, Nov 29, 2012 at 3:58 AM, Paul Norman <penor...@mac.com> wrote: >> From: Paul Norman [mailto:penor...@mac.com] >> Subject: Re: [Talk-us] Proposed import: Alaska Boroughs/CPDs >> >> Given that the comments received have been generally positive and the >> concerns raised are addressed I'm going to go ahead and start post- >> processing the data so I can merge it in as well as figuring out how the >> heck to identify all the existing imported borough/CPD boundaries, all >> tagged differently. > > Completed successfully. Because the boundaries are now much less "nodey" the > boundaries went from about 170k nodes to 25k nodes. > > I added wikipedia=* and website=* tags as applicable. Wikipedia tags should > help Nominatim determine importance when there are two places with the same > name. > > As most states aren't adding counties at the rate that Alaska has added > boroughs I doubt it'll come up again but I documented the SQL I used to > identify and delete the existing boundaries without conflicts on deleted > nodes at http://wiki.openstreetmap.org/wiki/Alaska/TIGER_Counties. Thanks for cleaning this up. Toby _______________________________________________ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us -- Jeff Meyer Global World History Atlas www.gwhat.org j...@gwhat.org 206-676-2347
_______________________________________________ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us
