Changeset When Comment
186840012

Dear Shinsplints,

I would encourage you to submit the relevant information to the OpenStreetMap Data Working Group for their review and assessment. You can contact the Data Working Group by email at data@openstreetmap.org.

When submitting your information, I recommend providing as much relevant and specific information as possible, including the original photo files and any other supporting evidence that may assist the DWG in evaluating the matter. This will ensure the DWG has all information needed to determine what the appropriate actions, if any, need to be taken. Please be aware that the DWG are volunteers so please be patient while you wait for a response.

In particular, it may be difficult to independently determine whether AI has been used to alter the photographs given that you and another user associated with your group have previously utilized AI to alter photos.

changeset/176023407
changeset/177863316

Kind regards,
eerib

187008986

Discussion available in

changeset/99669345

186670335

Dear Frederik Ramm,

Thank you for catching this right away.

I did notice in the block message to the user you mentioned that the trails have been flagged for independent review. I will point out that most of these trails are documented on local websites, YouTube, or have Strava segments that showcase recent activity.

Orleans:

https://thetrail.net/trailHTML/staticHTML/mtSeymour/orleans.html

https://www.youtube.com/watch?v=G_6OeDDvM0U

Iceland/Icelandia:

https://thetrail.net/trailHTML/staticHTML/mtSeymour/iceland.html

Jankaritaville:

https://thetrail.net/trailHTML/staticHTML/mtSeymour/jankaritaville.html

CCAA:

https://www.strava.com/segments/41112128

Neuralyzer:

https://www.strava.com/segments/37842132

Hope this helps! Cheers, eerib

186893875

Here is my changeset that adds access values for sanctioned (but not managed by the District of North Vancouver) and unsanctioned trails that are within Grouse Mountain Resorts property in the Fromme area.

changeset/186955933

If you notice any issues, please do let me know. I will do another review of this in the coming days.

Cheers, eerib

186893875

Dear NathanRib and Fizzie-DWG,

Thank you for catching this Fizzie-DWG.

The reason your edit was reverted NathanRib is because it became clear you were deleting valid trail tags such as description, informal, mtb:scale:imba, sac_scale, trail_visibility in a destructive fashion.

You were also adding access=private and bicycle=no with the changeset comment that the trails are within Grouse Mountain Resorts private property. However, a portion of the trails are not on Grouse Mountain Resorts private property and instead are on the District of North Vancouver's park property. You also added access=private to "Bill's Trail" which is implicitly known to be open to the public, is trail blazed, and has signage posted by North Shore Rescue.

I have created a rough diagram of Grose Mountain Resorts property (in yellow) with the trails you've edited in red.

https://imgur.com/a/AdVYkuS

I do think your edits raise an important question: What should access values be for sanctioned (not managed by the District of North Vancouver) and unsanctioned trails within Grouse Mountain Resorts private property? For sanctioned trails, like Bill's Trail, a permissive value for foot access and a private value for all other modes seems reasonable. For unsanctioned trails a blanket private value seems reasonable. I will go ahead make these changes for the Fromme area shortly and link to my changeset when done.

Kind regards, eerib

186954426

Full explanation and discussion is available in

changeset/186840012

186840012

Dear Shinsplints,

A fundamental core tenant of OpenStreetMap is trust. Unfortunately, the trail builder of this trail (user RNWhis), your group, and yourself have broken that trust.

To recap, user RNWhis lied about the trail's construction status, the trail's difficulty, the trail signage, and about trail deactivations. RNWhis never took responsibility for the lies and never apologized.

changeset/182626615

Then, user RNWhis or someone from your group, submitted a legally dubious DMCA takedown request to the OpenStreetMap Foundation. When that didn't work, an account was created to impersonate the OpenStreetMap Foundation in an attempt to remove the trail.

changeset/184408627

Then two weeks ago, two new accounts were created by your group that falsely presented themselves as visitors from the UK that were unrelated to your group. The blatantly concocted story and specific language used made it obvious that these were sockpuppet accounts related to your group.

note/5407120
changeset/186033363

Specifically for you, you have lied multiple times and have never taken responsibility when caught and have never apologized.

You utilized AI to create altered photographs of a Metro Vancouver Regional District (MVRD) signpost that you and your partner had vandalized because you disagreed with the name MVRD selected for the trail when they upgraded and sanctioned the trail.

changeset/176023407

You lied about a trail suffering severe water damage and being impassible despite activity data across multiple applications that showed users were still using and continue to use the trail to this day.

changeset/180561671

You have also created a sockpuppet account (PatGT). The original name of this account was "PatGroundTruther", which is a term ("ground truth") that your specific group has been fixated on. The account also utilized the Strava Heatmap iD editor plugin on it's first edit. These two coincidences made it obvious that the account was unlikely to be a legitimate new user. The account has since gone on to only edit trails that are specifically connected to you and your partner.

On that sockpuppet account you deleted a trail saying it doesn't exist and then switched your rationale multiple times when caught.

changeset/185369911

On that sockpuppet account you have also falsely claimed the existence of a new trail, that for some reason you neglect to map. No new trail exists in this area but you and your partner have setup a trail camera and potentially booby trapped the area.

changeset/183803084

You, or your group, have also been creating Strava accounts and uploading fake activities with the express goal of tricking Strava users. I am also aware your group was planning to add fake trails to OpenStreetmap by using the artificially developed heatmap data as your ground truth rationale.

You have continued to make unconstructive comments on social media platforms about OpenStreetMap, myself, and the Data Working Group.

Finally, when you marked the Balthazar trail as decommissioned, you decided to remove the trail name, description, and difficulty ratings which is unnecessary when marking a trail as decommissioned and suggests you're not making a constructive edit but instead trying to hide as much information about the trail as possible.

With all of this taken into account, I have determined that on the balance of probabilities that the trail is unlikely to have been decommissioned and as a result have reverted your edits. To determine whether this trail has truly been decommissioned it will require an evaluation from an established OpenStreetMap user who is unrelated to your group.

If you disagree then you're welcome to submit a complaint to the Data Working Group. Please reference this changeset discussion when making the complaint. Please remember that the Data Working Group are volunteers and to be patient while they review.

Kind regards, eerib

186953356

Changeset discussion available in

changeset/186660481

changeset/183141069

186660481

Dear noblewarrior,

I have reverted your changeset as I identified it as a mass deletion of trails against OpenStreetMap policy. You also previously mass deleted trails in this area, and you were provided a short explanation of OpenStreetMap policy and a link to the specific wiki page that expands on that explanation.

changeset/183141069

osm.wiki/Why_can%27t_I_delete_this_trail%3F

My understanding of this situation is that several user groups have developed trails on Fine Peace's land including rock climbers, slackliners, hikers, dirtbikers, and trials motorcyclists. Some of these trails are sanctioned by Fine Peace, including trails in the Furry Creek Beach recreation area and the Oliver's Landing area, and Fine Peace has received funding from the regional government to maintain these trails with public access. There is also other trails in the Minaty Bay area, which were open for permissive use depending on whether there was active filming in the former gravel pit area. And people utilize old logging roads to access sanctioned hikes like the Beth Lake Trail. For other trails, I am unaware whether Fine Peace is aware of them as there is an absence of official signage and policy.

Given you're primarily targeting dirtbike trails it appears that you may be associated with the Furry Creek Motorcycle Club, a club that has built the dirtbike trails on Fine Peace lands and enacted informal signage attributing the trails to their club. I haven't been able to find any information about this club or whether they have permission to utilize Fine Peace lands. Given that some trails illegally cross the Canadian National Railway Squamish Subdivision and other trails cause in-stream disturbances it is doubtful that permission has been granted. It would be helpful if you provided more information about these trails and specifically whether they're sanctioned by Fine Peace and what the permission provided is, if any.

Kind regards, eerib

186593082

Discussion in

changeset/186424970

186530417

Discussion in

changeset/186424970

186424970

Hello PatGT,

Thank you for pointing out the errors on the wiki. It appears that the community never approved the specific language used on the wiki page and that edits have been made without community consensus.

I have created a discussion topic on the OpenStreetMap Community Forum to document the errors and seek community consensus for proposed fixes.

https://community.openstreetmap.org/t/proposed-improvements-to-mtbimba-documentation/145838

Thank you again, eerib

186464815

Discussion in

changeset/186424970

186426589

The only way I know is to use the reverter plugin in JOSM, then select the specific features and use upload selection.

Not sure if this is the best way to do it but it's the way I've had success with.

186426589

Thank you for re-adding the camp!

Looks like the deletions were done by user Mason Aldridge (a kid editing for Pokemon Go) in changeset #136366420 about 3 years ago.

way/1134165369/history

Unfortunately, I never caught the deletions otherwise I would have done a partial revert.

Thank you again, eerib

186424970

For additional context, these edits are consistent with recent changesets by the user EricJMilannn12 (changesets 185118783 and 185306892), which similarly removed mtb:scale:imba values and added access=no tags to trails of a nearby trail network, specifically affecting trails associated with this group of individuals.

The relevant changesets are:

changeset/185118783

changeset/185306892

186426903

Discussion in

changeset/186424970

186424970

Hello PatGT,

The recent edits to the Neuralyzer trail and nearby trails have been reverted because they were identified as vandalism.

Neuralyzer is an unsanctioned trail that was purpose-built for mountain biking. As such, removing the mtb:scale:imba value is not appropriate. Your edits also removed references to the trail's intended use and difficulty rating from the description, and added a no access value despite there being no official signage or other authoritative basis to support that change.

In OpenStreetMap, a trail's difficulty rating is descriptive only. It does not imply that a trail is authorized, recommended, or appropriate for use; it simply records the trail's technical difficulty according to the relevant rating system.

I am aware that Strava recently updated its maps to display mtb:scale:imba and access tags, and that some members of your group have expressed concerns about this change. However, attempting to remove or alter valid trail attributes in OpenStreetMap, particularly while using a deceitful changeset comment, is not an appropriate way to address those concerns.

Additionally, this account is being used as a sockpuppet of the user Shinsplints. Please use your primary account for future contributions in accordance with OpenStreetMap's community expectations.

Kind regards, eerib

99669345

Dear NFZANMNIM,

I noticed in this changeset you added way ID 909236592, which represents the Clinton Indian Reserve 2 and 2A. These Indian Reserves were expropriated by BC Hydro in the 1970's and no longer exist.

way/909236592

It appears that the dataset you've used to add Indian Reserve boundaries here in British Columbia is out of date by decades and is shifted or distorted.

I also noticed that several Indian reserves were added as inner boundary relations to municipal government, regional government, and electoral area boundaries. In British Columbia, these reserves are generally located within those administrative boundaries rather than forming holes in them.

Would you please take a look over your edits and correct any boundaries or relations that may have been affected by these issues? The following authoritative datasets available through the Government of British Columbia's Data Catalogue will help.

https://catalogue.data.gov.bc.ca/dataset/indian-reserves-administrative-boundaries

https://catalogue.data.gov.bc.ca/dataset/e3c3c580-996a-4668-8bc5-6aa7c7dc4932

https://catalogue.data.gov.bc.ca/dataset/d1aff64e-dbfe-45a6-af97-582b7f6418b9

https://catalogue.data.gov.bc.ca/dataset/81940c47-a534-47e0-94d0-947c96a59de4

Thank you for your contributions, and I hope these resources are helpful.

Kind regards, eerib

186086902

Hello salalsalad,

The best practice for unsanctioned trails is to not delete them but instead to mark them as informal=yes and to add any legal access restrictions such as bicycle=no, foot=discouraged, etc. etc. The rationale for this best practice is available in the following wiki page.

osm.wiki/Why_can%27t_I_delete_this_trail%3F

Thank you, eerib