MD: US 40 Point Request

[Markkos1992]

I probably should have requested the Rolling Rd (RolRd) point back in April when I mentioned adding it to MD 26.  I traveled US 40 here from Rolling Rd to Cooks Ln (CooLn) to help me clarify that I truly clinched MD 122.

Secondarily, I am surprised not to see a point for the Patapsco Valley State Park.

[Duke87]

I probably should have requested the Rolling Rd (RolRd) point back in April when I mentioned adding it to MD 26.  I traveled US 40 here from Rolling Rd to Cooks Ln (CooLn) to help me clarify that I truly clinched MD 122.

Will add. Really should have been some point in that vicinity anyway for shaping so hey, double bird kill.

Secondarily, I am surprised not to see a point for the Patapsco Valley State Park.

I'm not surprised, considering there is no formal guidance that state park entrances should be included as points. But there is some sense to doing so and it's easy enough to add while I'm editing US 40 anyway so in it goes.

[Markkos1992]

Thanks for adding the point quickly so I do not have to wait to make my list file correct.

Secondarily, I am surprised not to see a point for the Patapsco Valley State Park.

I'm not surprised, considering there is no formal guidance that state park entrances should be included as points. But there is some sense to doing so and it's easy enough to add while I'm editing US 40 anyway so in it goes.

Otherwise I just wanted to quote the manual for national and state park entrances.

http://travelmapping.net/devel/manual/includepts.php

Other major highways that serve regional (not only local) travelers:
Road (not driveway/parking lot) to a national or state-level park, major airport, or popular tourist attraction.

[Duke87]

Somehow I read right past that. Okay, well, so I did the codifiedly right thing!

[Markkos1992]

Somehow I read right past that. Okay, well, so I did the codifiedly right thing!

I thought I had not even posted that yet as I was looking at the Labeling Waypoints page. I was thinking of possibly proposing to move where the park labels are mentioned, but I cannot fully justify it to myself yet to put in the ongoing manual thread.

[froggie]

My past modus operandi is that I will ignore state park points unless specifically requested or it meets a shaping point criteria.  The manual is contradictory in this sense given that many (most?) state parks are "minor tourist attractions, or destinations not regularly used by regional traveler".

[oscar]

My past modus operandi is that I will ignore state park points unless specifically requested or it meets a shaping point criteria.  The manual is contradictory in this sense given that many (most?) state parks are "minor tourist attractions, or destinations not regularly used by regional traveler".

I'm at the other end of the spectrum, really partial to including state/provincial/territorial park points (much more selective about county or other local parks). But in some places, like along the California coast, there are so many parks that I don't try to include them all.

[yakra]

My past modus operandi is that I will ignore state park points unless specifically requested or it meets a shaping point criteria.

Same here. Alberta especially comes to mind. Tourist attractions and signed facilities got waypoints as needed for shaping or to break up VISIBLE_DISTANCE segments. I may have violated the "(not driveway/parking lot)" guideline in the process, but, darnit... shaping! Visible distance!

I'm at the other end of the spectrum, really partial to including state/provincial/territorial park points (much more selective about county or other local parks).

I've been slowly maintaining a file for my parents' travels, and noticed they've been heavy on the state/provincial and national parks. Parks more distant from plotted routes can involve entering/leaving at county or other local roads not included as waypoints.