Amendments are in CS#153608009 and include removing the street name, adding operator details, and aligning to aerial imagery.

Amendments are in CS#153607928 and include changing the road to a private driveway and adding connected branching private driveways.

The road here is on municipal property, is signed, but is not actively maintained by the City of Chilliwack.

Small typo in my changeset comment: bypass -> overpass

Just a heads up, Suicide Jimmy is now tagged.

Hello Woodpeck,

I have no on-the-ground source for marking permissive, just local knowledge that access has been permissive. It may be the case that the owner is ok with locals having permissive access but others not. Or they have changed their mind completely. In either case, it would make sense to change the access to private. I see you have already made that change. Thank you!

A Strava account is necessary for the the first two web browser plugins but the TMS proxy url (nakarte.me) does not require an account.

Hello Scott,

I see you're using the OSM Public GPS Traces. You might be interested in also using the Strava Heatmap. The Strava Heatmap provides a stronger & more accurate data, fresher data (important for trail re-routes), and coverage of more areas.

Here is an example of the iD editor with the Strava Heatmap as a custom background in an area you recently edited. From this we can see that the Strava Heatmap would have helped greatly in aligning the trails.

https://imgur.com/a/AoKnPRt

I have detailed a easy few ways to get the data into the iD or JOSM editor below.

Chrome/Firefox plugin (iD or JOSM):

https://github.com/zekefarwell/josm-strava-heatmap

Chrome plugin (iD):

https://chromewebstore.google.com/detail/id-strava-heatmap/eglbcifjafncknmpmnelckombmgddlco

TMS Proxy URL (iD or JOSM):

tms[3,16]:https://proxy.nakarte.me/https/heatmap-external-b.strava.com/tiles-auth/all/red/{zoom}/{x}/{y}.png?px=256

Cheers, eerib

Thank you for catching this! No reason, just an error when I was new to using JOSM and importing geometry. I thought I had gotten them all previously but I guess not. I've removed the tags in CS#146997873. If you find anymore, don't hesitate to remove them as well.

Thank you!

Hello JordanOperations,

Welcome to OpenStreetMap and thank you for taking time out of your day to contribute!

I'm guessing from your username and edits that you are an employee of the City of Burnaby. If that is the case, it would be best practice to add that affiliation to your profile page.

I see that you're doing a number of unsanctioned trail deletions. Best practice is to not delete the trails but rather add correct tags to provide context. This helps prevent other mappers from simply accidently adding back the trails without any context and provides that context to downstream users of the OSM database.

If a trail is unsanctioned, use

- informal=yes

If a trail is forbidden to access by all user types, use

- access = no

If a trail has been fully decommissioned (not just a fence or a small amount of debris at the trail entrance) such that there is no path remaining, use

- removed:highway=path

You can read up more about the best practices and see more helpful information on this wiki page.

osm.wiki/United_States/Trail_Access_Project

Thank you, eerib

This change was as a result of a private message from user Arminal that asked about visibility of the trail/launch for "community and safety reasons".

The changes made include:

- Marking the trail as informal=yes as it is an unofficial trail.

- Moving the free flying tags and launch name from the viewpoint node to the grassland landuse area.

I believe these changes are consistent with OSM policies and will result in visibility changes in the most popular outdoor applications (AllTrails and Gaia).

Sorry, this was my error back in one of my first edits as a new mapper. Thank you for catching it and fixing it!

There was a new official 'no horses past this point' sign just before a relatively new bridge.

My recollection (I no longer have my photos from this survey) was that the bridge may support horse loads but that it was code deficient.

In my experience, BC Parks maps, and the GE map, are out-of-date and are error ridden.

Hello Black Tusk,

I saw some disagreement with the roundabout in this area. I've since done a survey of the area using semi-professional equipment and verified my work with government lidar and aggregate GPS data. This roundabout, and many other features in Snug Cove, should now be accurate to within about 1 ft.

It may look like the roundabout, and other features, are incorrect when comparing with Bing Maps Aerial and the OpenStreetMap traces but both of those sources have significant issues and shouldn't be used without further on-site verification.

Cheers & happy mapping, eerib

P.S. if you have an Android device you may be interested in the StreetComplete OSM mapping app.

I also used the Strava Heatmap for help with the path at the rec site.

I'll have to admit that I haven't visited the park recently so it's good you caught that the in-person signage hasn't been updated.

This is quite the confusing case as they did unveil a new entrance sign at the renaming ceremony and they've also updated their digital assets (park website, brochure materials, google listing) but I guess they had a delay in updating the in-person signage.

I've been meaning to detail survey the park so I'll look into speeding that up.

As for the revert, it would have been better to manually change the name back to Colony Farm but then have the new name under alt_name with an included note or fixme given the fact that the digital renaming has occurred and the in-person renaming is seemingly under operation.

Same JOSM bug as before. Changeset comment was supposed to be "P2 - Detail Cascade Peninsula campsite"

Changeset comment was supposed to be "Detail around Hick's Lake area" but some bug with JOSM didn't include the rest.

Hello Shinsplints,

This cabin was well publicized on several mediums (Internet forums, Facebook, Instagram, TikTok, YouTube, etc) and within various niche topics (hiking, mountain biking, trail running, peak bagging, foraging, orienteering, abandoned explorations, etc) before the features were documented on OpenStreetMap so it's hard to determine if and what role OSM played.

My current personal policy for adding "secret" or "sensitive" features such as this cabin is to only add those that are either well publicly publicized and/or well visited. This cabin fit that description and therefore I added it to OSM. I continually discuss this policy with others and am open to constructive changes that revolve around quantitative metrics.

Currently, I have left off all other cabins on the North Shore and nearly all cabins in the Sea-2-Sky region. Looking at recent data suggests that those cabins see significantly less traffic than this one did and therefore do not fit my own personal policy. However, if another user was to add the cabins then I would not remove them as it would go against OSM's ground truth policy.

I should note that there have been more than a dozen cabins on the North Shore destroyed over the years. Often it's because of lightening or accidental fires. None of those cabins were documented on OpenStreetMap.

As a final note I should stress that OSM has a ground truth policy whereby the world is mapped as it exists rather than as one wants it to be displayed. This is different than other platforms you are likely familiar with like TrailForks, which allow significant and frequently arbitrary curation of what is displayed.

I hope this helps provide some background.

Cheers, eerib

Just a heads up, you cannot use TrailForks data to align trails on OpenStreetMap as the TrailForks data is their own proprietary commercial data and hasn't been licensed for use in OpenStreetMap.

Instead, you can use the Strava Heatmap by following this tutorial. This will allow you to get even more accurate pathing than what TrailForks provides.

https://erickdeoliveiraleal.medium.com/tutorial-strava-openstreetmap-josm-or-id-2e2003f4aea3