This changeset has been fully reverted by CS# 155039060. Reason: Vandalism

changeset/155039060

This changeset has been fully reverted by CS#155039060. Reason: Vandalism

changeset/155039060

Thank you for the fast action on this.

Good catch on the site update! This one had slipped my radar. Thank you.

Looks like their was an error with regards to ownership of the lands and a recent legal survey corrected that. As a result, RSTBC retired the Recreation Reserve and repealed the backcountry camping designation. Common issue with RSTBC as many of their sites were developed without legal survey.

Hello Glassman,

Information regarding this site was obtained through local knowledge and inference from signage and barriers in the area, and not by access to the Archeological Branch's restricted access database.

Further, the site and other archeological details in this area are mentioned in the following two publicly accessible documents:

- Garden Bay Provincial Park Management Plan (1992)

https://nrs.objectstore.gov.bc.ca/kuwyyf/garden_bay_marine_pa_mp_19921120_de77caa0ec.pdf

- A New Style of Glass Bead from Garden Bay, British Columbia (DOI:10.13140/RG.2.2.23531.03360)

https://www.researchgate.net/publication/313887703_A_New_Style_of_Glass_Bead_from_Garden_Bay_British_Columbia

I can understand that having the archeological sites in the database can result in desecration of the sites.

On the flip side, I can also see users having a greater respect of the area due to a greater understanding of the historical significance of the area.

There is also a concern that the secrecy in archeological sites is resulting in secrecy in land use and management decisions.

I could not find a formal policy about archeological sites on the OpenStreetMap wiki, other than a short informal discouraging sentence. Perhaps changing the "name=DjSa-3" to "ref:borden=DjSa-3" and removing the "historic=archaeological_site" tag would help. The combination of these two changes should preserve the data within the database but remove the sites from consumer renderers. I will leave it with the DWG to determine what steps should be taken.

Thank you, eerib

Hello Razzle4,

Welcome to OpenStreetMap! Thank you for this edit, it looks great!

You may be interested in this Chrome/Firefox extension which makes it easy to add the Strava Heatmap as a background for the editor. This can make it very easy to add and align mountain bike trails.

https://github.com/zekefarwell/josm-strava-heatmap?tab=readme-ov-file

Thank you again!

Cheers, eerib

Also cleaned up areas near private property but referencing Land Title's ParcelMap to properly tag areas.

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.