[Imports] Fwd: Importing West Virginia State Forests Boundary

[Attila Kun]

I just noticed this in Seneca State Forest this close call of boundary 
overlapping to Rimel WMA, but because i'm doing the raw import where i 
check any data issues like self-intersections, incomplete boundaries 
etc, maybe me on the main account or someone else should fix this issue.

I thoroughly checked the borders so where it was possible i said "yeah, 
this is OK" or "this should be fixed at certain points".

https://www.openstreetmap.org/relation/13087452

Also, for some reason Nominatim haven't cached the recently imported 
boundaries yet, but i hope it will do once.

About the two existing forest boundaries i mentioned, they will be kept, 
since i have some uncertainty on the forest boundaries of it when 
compared the both, and the USGS version seemed to be more accurate, 
because that was only in the forest, the WVGIS boundary was overlapping 
a property.

To be honest, most of the imports didn't even say a word if there's 
something wrong with them, so that's why i gave this attention.


On 8/13/2021 6:21 PM, Minh Nguyen wrote:
> There seems to be an assumption that the boundaries aren't defined in 
> a way that don't overlap by a smidgen. I know very little about this 
> specific example, but as someone who used to live on a property parcel 
> that accidentally overlapped with two others, I find it less alarming 
> than I probably should. Perhaps Attila could check if there are any 
> close calls like this so we could discuss what to do about them here 
> or in other forums where locals are present.