New posts

Maintenance of unauthorized/unsanctioned/illegal/whatever trails

May 27, 2024, 11:27 a.m.
Posts: 487
Joined: March 14, 2017

all the dirtjumpers sift their dirt and it becomes concrete. A rake helps getting rid of rocks as well when you dump out the gold. Syncro is right about the drainage.

Ninja Cougar was built from the dirt from the Redbull DJ gig years ago.  Holds up mint.  Just needs to settle and get compacted.


 Last edited by: LoamtoHome on May 27, 2024, 11:29 a.m., edited 1 time in total.
May 27, 2024, 12:56 p.m.
Posts: 196
Joined: Sept. 11, 2008

Posted by: SixZeroSixOne

@canadaka: Trevor: if you're reading this, I suggest you allow reports to be submitted in-the-field even for hidden trails. At least you'll know which trail orgs admin that polygon so can route the report to them to figure out what to do with the info

If it's done in-the-field, the user is standing right on top of the trail so whether it's hidden is irrelevant!

I wouldn't want to allow lookup of hidden trails. However a regular user can submit reports about hidden trails through their ridelog. If a user rides a hidden Trail and we verify through GPS that they rode it they can submit updated conditions and reports for that trail via their ride log and an email sent. It doesn't reveal the location of the trail but if the GPS match we can assume they already know about the trail. Only the owner of the ride log can see this other users the hidden trails won't be listed and the ride log map is hidden.

May 27, 2024, 2:17 p.m.
Posts: 1421
Joined: May 4, 2006

Posted by: canadaka

Posted by: SixZeroSixOne

@canadaka: Trevor: if you're reading this, I suggest you allow reports to be submitted in-the-field even for hidden trails. At least you'll know which trail orgs admin that polygon so can route the report to them to figure out what to do with the info

If it's done in-the-field, the user is standing right on top of the trail so whether it's hidden is irrelevant!

I wouldn't want to allow lookup of hidden trails. However a regular user can submit reports about hidden trails through their ridelog. If a user rides a hidden Trail and we verify through GPS that they rode it they can submit updated conditions and reports for that trail via their ride log and an email sent. It doesn't reveal the location of the trail but if the GPS match we can assume they already know about the trail. Only the owner of the ride log can see this other users the hidden trails won't be listed and the ride log map is hidden.

Hmmm, that seems overly complex and precludes people not riding (eg I usually find problems when out walking my dog) and/or don't use TF ridelog.

My suggestion didn't involve exposing any hidden trails to users. Instead, it's simply a method to say at these geo-coordinates there's this problem. I presume you have some polygon mapping of which can resolve a geo-coordinate to a trail admin. Route report to them and they can decide what action, if any, to take. 

I'm not suggesting such reports need to be visible to anyone else (or even to the original user after logging) though maybe the area admin can pass on a "thank you" message to the user.

If no area admin, just chuck the report into the recycling bin ;-)

May 27, 2024, 5:11 p.m.
Posts: 143
Joined: March 13, 2017

Posted by: Kever

I always thought the smallish rocks helped hold the gold together. I've seen "clean" gold turn to peanut butter in high traffic areas.

I don't use a sifter, so I always end up with some aggregate. I will hand sift when spreading the gold to get rid of the bigger rocks, sticks, pinecones, and any roots. Again, I am not doing this in high traffic areas, so my method will be different than say John Deere, or Expresso. 

If you leave some small rock in, you don't have the peanut butter dirt issue at the start, but once packed, the clean gold will last longer (again, for high traffic areas). The peanut butter issue is when it is fresh work, you could see it happening a lot on the Fromme Climb Route as Peter was working this winter, but once it gets enough traffic it packs solid, unless there is water coming from the bedrock below (this did happen to him in a couple of spots). 

I will use rock and gravel as a base in holes and low points, then layer gold over top, sort of like a paving base, I think it helps with allowing water to filter through.

May 27, 2024, 5:29 p.m.
Posts: 143
Joined: March 13, 2017

Posted by: canadaka

Posted by: SixZeroSixOne

@canadaka: Trevor: if you're reading this, I suggest you allow reports to be submitted in-the-field even for hidden trails. At least you'll know which trail orgs admin that polygon so can route the report to them to figure out what to do with the info

If it's done in-the-field, the user is standing right on top of the trail so whether it's hidden is irrelevant!

I wouldn't want to allow lookup of hidden trails. However a regular user can submit reports about hidden trails through their ridelog. If a user rides a hidden Trail and we verify through GPS that they rode it they can submit updated conditions and reports for that trail via their ride log and an email sent. It doesn't reveal the location of the trail but if the GPS match we can assume they already know about the trail. Only the owner of the ride log can see this other users the hidden trails won't be listed and the ride log map is hidden.

@6061: when you say route a report to a "trail org admin" what do you mean, are you talking about sending these to the NSMBA, SORCA, etc...? 

I would think that would put these trails in jeopardy, as if the association "officially" knows of them, they would have to do something about them. Also, the builders don't necessarily want to be known either, so that would not really be a good contact point anyways.

May 27, 2024, 5:48 p.m.
Posts: 3642
Joined: Nov. 23, 2002

Posted by: TonyJ

I will use rock and gravel as a base in holes and low points, then layer gold over top, sort of like a paving base, I think it helps with allowing water to filter through.

That's a good way to go. I'll rake up all the rocks that tend to collect at the bottom of chutes and use that as bedding so I don't need to hand collect a a few buckets of rocks and won't need as much gold dirt on top. Once packed down and with proper grading the water tends to just sheet off tho, so the filtering isn't as critical unless you're trying to go overtop  an area where the water is percolating up or coming out of the hillside from a drainage basin. The key in preventing water damage is not allowing it to collect on the trail, whether that's pooling or little rivulets building up over long straight sections from not having any grade or camber changes. 

This is why I've come to think that the most critical aspect of trail building is allowing for rider behaviour when designing a trail. Rider behaviour is the hardest thing to control and it requires some thought to accommodate for that.

May 27, 2024, 5:58 p.m.
Posts: 1421
Joined: May 4, 2006

Posted by: TonyJ

Posted by: canadaka

Posted by: SixZeroSixOne

@canadaka: Trevor: if you're reading this, I suggest you allow reports to be submitted in-the-field even for hidden trails. At least you'll know which trail orgs admin that polygon so can route the report to them to figure out what to do with the info

If it's done in-the-field, the user is standing right on top of the trail so whether it's hidden is irrelevant!

I wouldn't want to allow lookup of hidden trails. However a regular user can submit reports about hidden trails through their ridelog. If a user rides a hidden Trail and we verify through GPS that they rode it they can submit updated conditions and reports for that trail via their ride log and an email sent. It doesn't reveal the location of the trail but if the GPS match we can assume they already know about the trail. Only the owner of the ride log can see this other users the hidden trails won't be listed and the ride log map is hidden.

@6061: when you say route a report to a "trail org admin" what do you mean, are you talking about sending these to the NSMBA, SORCA, etc...? 

I would think that would put these trails in jeopardy, as if the association "officially" knows of them, they would have to do something about them. Also, the builders don't necessarily want to be known either, so that would not really be a good contact point anyways.

The Sheriff of Seymour, obviously! ;-)

You raise a good point. I don't know the process behind TF which determines which trails are or are not displayed on the TF topo later or where they even scrape their GPX files or similar from. 

But presumably whoever makes that decision that the trail shouldn't be shown is the most logical starting point for this. 

Anyway, it's just a suggestion for TF to take it or leave it. I'm only trying to be helpful to whoever built and maintains the trail...

May 29, 2024, 9:52 p.m.
Posts: 143
Joined: March 13, 2017

Posted by: SixZeroSixOne

Posted by: TonyJ

Posted by: canadaka

Posted by: SixZeroSixOne

@canadaka: Trevor: if you're reading this, I suggest you allow reports to be submitted in-the-field even for hidden trails. At least you'll know which trail orgs admin that polygon so can route the report to them to figure out what to do with the info

If it's done in-the-field, the user is standing right on top of the trail so whether it's hidden is irrelevant!

I wouldn't want to allow lookup of hidden trails. However a regular user can submit reports about hidden trails through their ridelog. If a user rides a hidden Trail and we verify through GPS that they rode it they can submit updated conditions and reports for that trail via their ride log and an email sent. It doesn't reveal the location of the trail but if the GPS match we can assume they already know about the trail. Only the owner of the ride log can see this other users the hidden trails won't be listed and the ride log map is hidden.

@6061: when you say route a report to a "trail org admin" what do you mean, are you talking about sending these to the NSMBA, SORCA, etc...? 

I would think that would put these trails in jeopardy, as if the association "officially" knows of them, they would have to do something about them. Also, the builders don't necessarily want to be known either, so that would not really be a good contact point anyways.

The Sheriff of Seymour, obviously! ;-)

You raise a good point. I don't know the process behind TF which determines which trails are or are not displayed on the TF topo later or where they even scrape their GPX files or similar from. 

But presumably whoever makes that decision that the trail shouldn't be shown is the most logical starting point for this. 

Anyway, it's just a suggestion for TF to take it or leave it. I'm only trying to be helpful to whoever built and maintains the trail...

Understood, thanks.

Jan. 4, 2025, 10:09 a.m.
Posts: 2
Joined: Nov. 26, 2008

Regarding TF hiden trails. If it's hiden on TF there is a very good chance it's new-ish and therefore being maintained.

Forum jump: