Re: [Talk-us] Trouble with getting Superior National Forest boundary to render on standard map

[stevea]

On Sep 1, 2020, at 2:46 PM, Kevin Kenny  wrote:
> 'Private' vs 'public' hits near the mark, but not in the gold.  I was trying 
> to be precise when I said that the property line determines the protected 
> status and the public access constraints. A public-access nature reserve 
> operated by an NGO (such as a private conservancy or land trust - there are 
> quite a few in my part of the world) deserves the same treatment as a 
> government-run one.

Thank you for pointing out this distinction, Kevin.  It certainly exists, such 
as in abundance in New York state where you have mapped these distinctions 
extensively.

As I was talking about the specific case of National Forests (and their odd 
"dual boundary" nature), I did not mean to exclude other (e.g. NGO) kinds of 
ownership in the greater realm of mapping.  However, in the distinct case of 
National Forests, the distinction between public and private (for "smaller, 
actually owned" polygon components vs. "larger, potentially own-able without 
additional Congressional legislation" polygon components) remains true.

So while I do not "hit the gold" in all cases, but I think the public-private 
distinction (along with the pesky "Congress has authorized further acquisitions 
out to HERE" outer-outer polygon) accurately captures what we're trying to 
better understand, better map and better render in the case of National 
Forests, I happy accept your "adjustment or correction."

Nicely, I believe we are both correct!

SteveA
___
Talk-us mailing list
Talk-us@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-us

Re: [Talk-us] Trouble with getting Superior National Forest boundary to render on standard map

[Kevin Kenny]

On Tue, Sep 1, 2020 at 3:14 PM stevea  wrote:

> Here I weigh-in with what I believe to be a crucial distinction between
> "cadastral data which are privately owned" and "data which can be
> characterized as cadastral, but which are publicly owned and are often used
> for recreation, hiking and similar human activities."
>

'Private' vs 'public' hits near the mark, but not in the gold.  I was
trying to be precise when I said that the property line determines the
protected status and the public access constraints. A public-access nature
reserve operated by an NGO (such as a private conservancy or land trust -
there are quite a few in my part of the world) deserves the same treatment
as a government-run one.

What we discuss here is the particular (peculiar?) example of national
> forests in the USA, where there are effectively "two legal boundaries, one
> actual ownership, another potential ownership."


There's a nearly parallel situation in New York, where the 'potential
ownership' in the Adirondack and Catskill Parks is, in effect, the entirety
of those parks. In that case, though, the outer boundary is indeed signed,
affects zoning to a tremendous extent, and realtors will make it quite
clear that a property is in (or is not in) the park. (It's parallel to
several national parks in the UK, and I've gotten affirmation from a number
of prominent UK mappers that these two are properly
`boundary=national_park`.)

Within these two parks, there are a great many Wild Forests and Wilderness
Areas and Intensive Use Areas and New York City Watershed Recreation Areas
and a zoo of other things that are owned by one government or another.
They, too, are mapped, since they have protection status different from the
park as a whole, and since they are the public-access portions of the park.
(They account for something like half the land area - and we're talking a
pretty huge swath; the Adirondack Park has about the same land area as the
State of Massachusetts.)  Wilderness and Intensive Use Areas tend to have
fairly compact borders (in topology, not in size!) High Peaks
https://www.openstreetmap.org/relation/6360488 and West Canada Lakes
https://www.openstreetmap.org/relation/6360511 are the largest, and as you
can see, they have few inholdings or transportation corridors.  Wild Forest
areas (a slightly less restrictive classification) are ordinarily a lot
more diffuse, with patchworks of public and private holdings. They include
messes like Saranac Lakes https://www.openstreetmap.org/relation/6362702 and
Wilcox Lake https://www.openstreetmap.org/relation/6360587
.
While the classification of any land being added to the Forest Preserve
goes through a public notice and comment period, I'm sure that someone in
the Adirondack Park Agency has on the drawing board a sketch that says,
'any conservation land that comes into our hands in *this* area will be
added to *that* wild forest', but that's not proclaimed the way it is with
National Forests.

As diffuse as they are, these are the areas that have public access, and
`protect_class=1b` (or whatever the protection class of any given area is).
The cadastre determines the land use and protection status.

We absolutely should agree (here? now?) on which of these two (or both) we
> enter into OSM.  The current situation of data in our map is scattered
> between the two and still confused in the minds of many mappers who do or
> wish to enter these data.  Since we agree they should be entered, let's
> better discuss how we enter them "properly" (by achieving consensus) and
> watch as they render according to our hammered-out-here agreements on how
> this should and will best take place.  We really are getting closer to
> doing this, thanks to excellent discussion here.


With the two great parks of New York, we've mapped both the outer bounds -
which are consistently signed, at least on the highways - and the bounds of
the state-owned conservation land - which are also signed.  With the
National Forests, it's much less clear. Ordinarily the signage does NOT
follow the proclaimed boundary - there are no National Forest signs in the
middle of Reno - but rather are posted at the first actual Forest Service
parcel that a road encounters. The markings for the individual protected
parcels are more subtle, but they're there. Generally, the proclaimed
boundary is NOT visible in the field. (By contrast, there *are*  Adirondack
Park signs on streets  in Glens Falls/Queensbury, Corinth, Broadalbin,
Mayfield,  even in the villages)

I don't mind mapping the proclaimed areas of National Forests, but it's
hard to come up with an appropriate tag since the proclamation has so
little actual effect. The actual owned areas are definitely significant and
I do *not* want to give them up. My belief is that the conservation
easements - the intermediate category - would be nothing but clutter if
rendered on a general-purpose ma

Re: [Talk-us] Trouble with getting Superior National Forest boundary to render on standard map

[stevea]

Here I weigh-in with what I believe to be a crucial distinction between 
"cadastral data which are privately owned" and "data which can be characterized 
as cadastral, but which are publicly owned and are often used for recreation, 
hiking and similar human activities."

Joseph, many others in OSM, I and wide consensus agree that the former (private 
cadastral data, especially down to the level of individual parcels) generally 
do not belong in OSM.  I believe we also agree there are widely-acknowledged 
exceptions to this, such as when polygons tagged landuse=* denote where a farm 
is distinct from a forested area, or where residential vs. commercial vs. 
industrial areas clearly follow property lines up to an edge of "difference," 
especially as they better characterize what we might call "zoning" (of larger 
areas like "neighborhoods" or "downtown's shopping district" or "the industrial 
zone where auto parts are manufactured by numerous industrial companies on 
numerous parcels") instead of individual parcels.  If I am incorrect in any of 
my assumptions, I welcome adjustment or correction.

However, with PUBLIC "cadastral data" which define national parks, large areas 
used for human recreation (such as state parks, county parks, national forests 
and similar public lands), I don't think there is any argument whatsoever that 
OSM wishes to map these.  Yet what Joseph characterizes as "cadastral data" 
precisely define these.  Please, let's dispense with this apparent (but not 
actual) contradiction:  public lands belong in OSM denoted as such, and an 
acknowledged best method to do this is to map their boundary as the data where 
they are "owned by the public."

What we discuss here is the particular (peculiar?) example of national forests 
in the USA, where there are effectively "two legal boundaries, one actual 
ownership, another potential ownership."  We absolutely should agree (here? 
now?) on which of these two (or both) we enter into OSM.  The current situation 
of data in our map is scattered between the two and still confused in the minds 
of many mappers who do or wish to enter these data.  Since we agree they should 
be entered, let's better discuss how we enter them "properly" (by achieving 
consensus) and watch as they render according to our hammered-out-here 
agreements on how this should and will best take place.  We really are getting 
closer to doing this, thanks to excellent discussion here.

SteveA
___
Talk-us mailing list
Talk-us@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-us

Re: [Talk-us] Trouble with getting Superior National Forest boundary to render on standard map

[stevea]

Kevin Kenny  wrote:
> They're both 'legal' boundaries. 
(and more).

Thank you, Kevin.  Finally, this is written in a manner that allows me to 
understand it and I do now.  Whew!

THEN, there is how OSM might ultimately remedy this (by specifying — good 
example wiki diagrams can go miles here — mapping the "simple outer" with an 
"outer" role?) and how Carto (and its authors) remedy this as it renders.  
These remain to be seen.  It's messy, but we do get closer talking about it 
here.  It appears there are some forests which denote "legislative outer" with 
"outer" role and other forests which denote an outer role of land which is 
ACTUALLY federally owned (a smaller area, contained wholly inside of the first 
kind, the could-be-national-forest-without-more-legislation kind).

OSM must specify correct / preferred tagging if we keep both kinds of 
multipolygons (MPs) in our data (I prefer the latter, as the tags in the 
polygon "do apply").  We may also coin a new flavor of MP (it would still BE a 
MP, but perhaps with special tagging, special rendering, or both) for such 
national forests in the USA to better characterize the "dual nature" of this 
odd "sort of" ownership:  an "outer-outer" of "legislative possibility of 
ownership."  But maybe that's not required:  a wiki page describing this and 
the tagging required on one or two MPs could do it, I think.

In my mind, now that these are quite distinct, it seems a straightforward 
solution is two MPs, maybe linked somehow (one a super-relation containing the 
other?).  The first MP might be the (larger) "legislatively-defined outer-role 
possibly-owned 'limit without additional legislation.'"   The second MP might 
be the (smaller) "actually owned, tagged outer-role, plus punched-out 
inner-role inholdings."  Those quoted descriptions can be sharpened up, but I 
hope the idea is clear.

Then, maybe some logic is built into Carto (maybe not, it may not be 
necessary).  Then, we document this well in wiki (explaining as Kevin did, as I 
understand now clear-as-crystal, I believe others will, too).  Then, we discuss 
whether there might be a harmonization of data across the country.  Then (as 
usual, the final act, please pass the popcorn), we watch our hard work render.  
And applaud.

With Kevin and Joseph talking, this feels like it can get solved!

Thanks for putting on thinking caps and typing words carefully,
SteveA
___
Talk-us mailing list
Talk-us@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-us

Re: [Talk-us] Trouble with getting Superior National Forest boundary to render on standard map

[Joseph Eisenberg]

But the Forest Service itself is showing the outer boundary on it's
websites, as I've mentioned above. On the higher resolution web map, there
is only a faint difference in lighter green / darker green color to show
which land within the official boundary is privately or federally owned,
and this distinction is not even mentioned in the map legend:

https://www.fs.usda.gov/detailfull/klamath/maps-pubs/?cid=fseprd533703&width=full


And my experience is that only the outermost boundary has official signs
saying "entering Klamath National Forest". If you drive into a checkerboard
area of private/public land, there are no Forest Service signs at the
limits of private land.

- Joseph Eisenberg

On Mon, Aug 31, 2020 at 4:36 PM Kevin Kenny  wrote:

> On Mon, Aug 31, 2020 at 7:11 PM Joseph Eisenberg <
> joseph.eisenb...@gmail.com> wrote:
>
>> I believe there might be an issue with these complex multipolygons which
>> is preventing osm2pgsql from handling them. Perhaps it is because nodes are
>> shared between two outer rings?
>>
>> However, I also want to note that it is not clear to me that the new
>> mapping is correct.
>>
>> The new outer boundaries for the Superior National Forest are very
>> complex and only cover a small portion of the land within the National
>> Forest outer boundary:
>>
>> https://www.openstreetmap.org/relation/11558095
>>
>> Compare the official National Forest web map:
>> https://usfs.maps.arcgis.com/apps/webappviewer/index.html?id=03a17ac9df1a4cd0bcc872ac996e7231
>> - this matches the older, simpler boundary that was in OpenStreetMap
>> previously. Also see this map on the Forest website:
>> https://www.fs.usda.gov/Internet/FSE_MEDIA/stelprdb5130373.pdf
>>
>> It appears that the new, complex relation is attempting to map what land
>> is owned by the Federal government, rather than mapping the legal boundary
>> of the National Forest. Is that correct?
>>
>> I believe this is a misinterpretation of the meaning of
>> boundary=protected_area.
>>
>
> They're both 'legal' boundaries.
>
> The simple outer boundary of a National Forest is 'the area in which the
> Forest Service is authorized to purchase land without a new Act of Congress
> expanding the forest.'  It's not signed in the field and has very little
> effect upon the actual land management. It's generally all that the
> enabling act of Congress specifies; the rest is done by having the law
> authorize the Executive Branch to determine the status of parcels within
> the legislated boundary.
>
> The outer boundary also generally excludes all 'inholdings' - private
> holdings that are enclosed by the national forest.
>
> It gives a more pleasant rendering at low zoom levels while still giving a
> sense of where the National Forest is, but does not reflect the situation
> in the field.
>
> The 'patchwork quilt' area is the area actually owned by the Federal
> Government and administered by the Forest Service. It's normally what will
> be posted in the field, and it's the area that actually enjoys the
> protection.
>
> For many Federally-administered land areas, there's also a third category:
> land on which the Federal government owns a conservation easement
> (essentially, the right to develop the land) but the land ownership (the
> right to exclude others) is private. There are huge pieces of wildlife
> refuges where Uncle Sam owns the hunting and development rights, but some
> farmer or forester owns and works the land.
>
> Most people in the general public would recognize only the most
> restrictive definition in the field, since that is what's signed. A duck
> hunter would look at an official map to see which of the private parcels
> comprising a wildlife refuge are open to the public for hunting in season.
> Very few people except the real estate lawyers care about the outermost
> boundary, except to give something that can yield a readable rendering on
> small-scale maps.
>
> I'm all for making the boundary follow the legal designation that has the
> greatest effect and is visibly signed.
> --
> 73 de ke9tv/2, Kevin
>
___
Talk-us mailing list
Talk-us@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-us

Re: [Talk-us] Trouble with getting Superior National Forest boundary to render on standard map

[Kevin Kenny]

On Mon, Aug 31, 2020 at 7:11 PM Joseph Eisenberg 
wrote:

> I believe there might be an issue with these complex multipolygons which
> is preventing osm2pgsql from handling them. Perhaps it is because nodes are
> shared between two outer rings?
>
> However, I also want to note that it is not clear to me that the new
> mapping is correct.
>
> The new outer boundaries for the Superior National Forest are very complex
> and only cover a small portion of the land within the National Forest outer
> boundary:
>
> https://www.openstreetmap.org/relation/11558095
>
> Compare the official National Forest web map:
> https://usfs.maps.arcgis.com/apps/webappviewer/index.html?id=03a17ac9df1a4cd0bcc872ac996e7231
> - this matches the older, simpler boundary that was in OpenStreetMap
> previously. Also see this map on the Forest website:
> https://www.fs.usda.gov/Internet/FSE_MEDIA/stelprdb5130373.pdf
>
> It appears that the new, complex relation is attempting to map what land
> is owned by the Federal government, rather than mapping the legal boundary
> of the National Forest. Is that correct?
>
> I believe this is a misinterpretation of the meaning of
> boundary=protected_area.
>

They're both 'legal' boundaries.

The simple outer boundary of a National Forest is 'the area in which the
Forest Service is authorized to purchase land without a new Act of Congress
expanding the forest.'  It's not signed in the field and has very little
effect upon the actual land management. It's generally all that the
enabling act of Congress specifies; the rest is done by having the law
authorize the Executive Branch to determine the status of parcels within
the legislated boundary.

The outer boundary also generally excludes all 'inholdings' - private
holdings that are enclosed by the national forest.

It gives a more pleasant rendering at low zoom levels while still giving a
sense of where the National Forest is, but does not reflect the situation
in the field.

The 'patchwork quilt' area is the area actually owned by the Federal
Government and administered by the Forest Service. It's normally what will
be posted in the field, and it's the area that actually enjoys the
protection.

For many Federally-administered land areas, there's also a third category:
land on which the Federal government owns a conservation easement
(essentially, the right to develop the land) but the land ownership (the
right to exclude others) is private. There are huge pieces of wildlife
refuges where Uncle Sam owns the hunting and development rights, but some
farmer or forester owns and works the land.

Most people in the general public would recognize only the most restrictive
definition in the field, since that is what's signed. A duck hunter would
look at an official map to see which of the private parcels comprising a
wildlife refuge are open to the public for hunting in season. Very few
people except the real estate lawyers care about the outermost boundary,
except to give something that can yield a readable rendering on small-scale
maps.

I'm all for making the boundary follow the legal designation that has the
greatest effect and is visibly signed.
-- 
73 de ke9tv/2, Kevin
___
Talk-us mailing list
Talk-us@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-us

Re: [Talk-us] Trouble with getting Superior National Forest boundary to render on standard map

[Joseph Eisenberg]

I believe there might be an issue with these complex multipolygons which is
preventing osm2pgsql from handling them. Perhaps it is because nodes are
shared between two outer rings?

However, I also want to note that it is not clear to me that the new
mapping is correct.

The new outer boundaries for the Superior National Forest are very complex
and only cover a small portion of the land within the National Forest outer
boundary:

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

Compare the official National Forest web map:
https://usfs.maps.arcgis.com/apps/webappviewer/index.html?id=03a17ac9df1a4cd0bcc872ac996e7231
- this matches the older, simpler boundary that was in OpenStreetMap
previously. Also see this map on the Forest website:
https://www.fs.usda.gov/Internet/FSE_MEDIA/stelprdb5130373.pdf

It appears that the new, complex relation is attempting to map what land is
owned by the Federal government, rather than mapping the legal boundary of
the National Forest. Is that correct?

I believe this is a misinterpretation of the meaning of
boundary=protected_area.

See images at
https://github.com/gravitystorm/openstreetmap-carto/issues/4198#issuecomment-684084296
for another example with the Manistee National Forest, which used to be
mapped in a much simpler fashion and now has been re-made as many smaller
parcels.

- Joseph Eisenberg

On Sun, Aug 30, 2020 at 4:22 PM Clifford Snow 
wrote:

> Paul,
> I don't have a definitive answer for you, but rendering usually takes a
> while for large areas. I would expect it to render when zoomed in but
> wasn't able to see any rendering on a couple of spot checks. I did notice
> that around islands either the forest or the island, are shifted. I would
> recommend cleaning those up.
>
> Clifford
>
> On Sun, Aug 30, 2020 at 1:19 PM Paul White  wrote:
>
>> Hello,
>>
>> I recently added the (super complicated) Superior National Forest
>> boundary to OSM, because I noticed it was missing. However, it refuses to
>> render on the standard map, even though I ran it through JOSM's validator
>> with no problems. (link to relation)
>>  I
>> don't think it's due to the amount of members, because the Tongass National
>> Forest I added recently, with over 10,000 members, renders fine. And I know
>> it's not due to the tags on the relation; they are standard to other
>> national forests.
>>
>> If someone could look into it and see what's causing it to break, that
>> would be great.
>>
>> pj
>>
>>
>> ___
>> Talk-us mailing list
>> Talk-us@openstreetmap.org
>> https://lists.openstreetmap.org/listinfo/talk-us
>>
>
>
> --
> @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 mailing list
Talk-us@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-us

Re: [Talk-us] Trouble with getting Superior National Forest boundary to render on standard map

[Clifford Snow]

Paul,
I don't have a definitive answer for you, but rendering usually takes a
while for large areas. I would expect it to render when zoomed in but
wasn't able to see any rendering on a couple of spot checks. I did notice
that around islands either the forest or the island, are shifted. I would
recommend cleaning those up.

Clifford

On Sun, Aug 30, 2020 at 1:19 PM Paul White  wrote:

> Hello,
>
> I recently added the (super complicated) Superior National Forest boundary
> to OSM, because I noticed it was missing. However, it refuses to render on
> the standard map, even though I ran it through JOSM's validator with no
> problems. (link to relation)
>  I
> don't think it's due to the amount of members, because the Tongass National
> Forest I added recently, with over 10,000 members, renders fine. And I know
> it's not due to the tags on the relation; they are standard to other
> national forests.
>
> If someone could look into it and see what's causing it to break, that
> would be great.
>
> pj
>
>
> ___
> Talk-us mailing list
> Talk-us@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk-us
>


-- 
@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] Trouble with getting Superior National Forest boundary to render on standard map

[Paul White]

Hello,

I recently added the (super complicated) Superior National Forest boundary
to OSM, because I noticed it was missing. However, it refuses to render on
the standard map, even though I ran it through JOSM's validator with no
problems. (link to relation)
 I
don't think it's due to the amount of members, because the Tongass National
Forest I added recently, with over 10,000 members, renders fine. And I know
it's not due to the tags on the relation; they are standard to other
national forests.

If someone could look into it and see what's causing it to break, that
would be great.

pj
___
Talk-us mailing list
Talk-us@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-us