[Imports] Fwd: Importing West Virginia State Forests Boundary

[Attila Kun]

Hi Frederik,

Alright, then i'm going do the import myself., since I'm kindof good in 
importing stuff (I know how to tag State Forests as such after i had to 
fix some of  the tagging of bad imports in Connecticut and 
Massachusetts, good luck other mappers fixing the rest),  however that's 
why I ask first instead of making any fault (especially after the case 
of using an imagery that is not well licensed). I know i'm not from West 
Virginia but i got the proper contacts if anything goes wrong or I just 
want to have some QA, which I probably am going to ask on OSMUS Slack if 
they are willing to help me in this. (Yeah, i don't want this a one man 
show)

I checked out the dataset by the way, and it's not a big deal, it 
contains only 7 State forests, of which i see 2 completely imported and 
one partially to OSM already, the rest of it is only a node. I would 
import the forests in small batches, so which are nearby, because i 
don't want to  have one changeset span the whole state.

And yes, i checked what you sent me, i see your concern.

I'm always open for any advices, so if you have something to add, feel 
free to do it.

Attila


On 8/11/2021 10:15 PM, Frederik Ramm wrote:
> Hi,
>
>
> On 8/11/21 21:42, Attila Kun wrote:
>> I don't know if it's enough to email here(so don't have to forward to 
>> import list), but me and Zelonewolf(Brian Sperlongano) are planning 
>> to import West Virginia State Forests. I'm doing the paperwork*, 
>> Brian the import.
>
> I am a little skeptical about a single person who isn't even from West 
> Virginia, doing the import in the whole state. I have also looked at 
> ZeLoneWolf's data import in Rhode Island and I find that there are 
> serious quality issues with that, which lead me to conclude that I 
> wouldn't want ZeLoneWolf run any more imports.
>
> Looking at 
> https://www.openstreetmap.org#map=17/41.83847/-71.78954&layers=D
>
> I find that
>
> * There's a bunch of bubbly residential areas that nobody tracing from 
> aerial imagery would classify as such. For example, why is 
> https://www.openstreetmap.org/way/863679643 shaped the way it is and 
> why does it have this little hole in the South? If that is the 
> "official" data then maybe OSM is better off without it.
>
> * Why do neighbouring large landuse polygons duplicate tens of 
> thousands of nodes instead of being modelled as relations both sharing 
> one way?
>
> Furher east, I find https://www.openstreetmap.org/way/685277039 which 
> is an older forest that was simply overlaid with new data without any 
> attempt at proper conflation.
>
> Where was that huge Rhode Island import even discussed? I notice that 
> after the import there have been quite a few fixes and cleanups which 
> might have been avoided had there been a proper previous discussion. I 
> must say, I've found so many bugs with that in just ten minutes of 
> looking, I wonder if it needs to be reverted altogether and re-done 
> properly.
>
> And no, as I said above, please no further ZeLoneWolf imports given 
> how badly that has gone - at least none without the community taking a 
> very close look at the exact import plan *before* anything is 
> executed. (For example, since it appears that the plan is to import 
> boundaries here, I would be interested to learn of any conflation 
> plans with existing administrative boundaries if/where state forests 
> should coincide with them?)
>
> Bye
> Frederik
>