Trailforks.com Bug Reports

PB Forum :: Trailforks Feedback
Trailforks.com Bug Reports
Author Message
Posted: May 11, 2021 at 15:21 Quote
it would be nice if Norwegian letters were supported in uploader.

with ŠI get å instead if the it's in the title. so I have to manually add the description with correct letters.

Posted: May 11, 2021 at 17:53 Quote
I have 3 phones available to me 2 of them are showing this red polygon on Dagmar North, "closed for winter" the 3rd phone does not show the polygon.

Similar issue with the SCMBC - ORO Trail Network, 1 phone has pink polygons around the trails, the other 2 do not show them.

Canadmos wrote:
canadaka wrote:
Canadmos wrote:
A polygon on the region linked below seems to be sticking around on the mobile app, but is not visible on the web version.

So I guess two questions:

1. how to fix this view on the mobile app?
2. is there a way to see a list of polygons that have been added to a region? I can't find a menu, other than unpublished, which this particular one is not in.

I also see no mention of the creation/removal of the polygon in the admin audit log, which is odd?

https://www.trailforks.com/region/dagmar-north-trails/

This is what it looks like in the app:

There is a link at the bottom of a regions overview page. Maybe try editing the polygon, so it changes the "changed" timestamp and syncs the change.

But I think this was a bug we recently found, polygon deletes were not being synced to the app, only edits. This was fixed in the last version of the app 1.53


Ok cool, I'll make note of that link.

The link is missing on that region, but I can still view the page. Problem is, the polygon isn't on it...its just missing and I can't find the polygon ID # anywhere...

https://www.trailforks.com/region/dagmar-north-trails/polygons

The app version on my phone is 1.53.

Posted: May 12, 2021 at 8:59 Quote
I was looking at trail overview stats for West Virginia and discovered what I think is a mistake. It shows the highest trailhead as 9878 feet; however, the highest point in West Virginia is Spruce Knob at 4863 feet so this is impossible.
https://www.trailforks.com/region/west-virginia/

Posted: May 12, 2021 at 9:07 Quote
There's more states with the same problem as above. Arizona has the highest trailhead at over 27,000 feet (27,910). That would be awesome if it were true!
Recommend scrubbing the database for these errors to improve reporting accuracy.

Posted: May 12, 2021 at 9:16 Quote
How is "Climb" calculated in the stats of a Ride Log? There is about a 50% difference to the upside on Trailforks vs. my computer and Strava. Example: Trailforks Climb = 2337ft. Strava Elevation= 1578ft.

Mod Plus
Posted: May 12, 2021 at 11:48 Quote
NeoKlaatu wrote:
How is "Climb" calculated in the stats of a Ride Log? There is about a 50% difference to the upside on Trailforks vs. my computer and Strava. Example: Trailforks Climb = 2337ft. Strava Elevation= 1578ft.

Please read this https://www.trailforks.com/help/view/90/




Regarding the Polygon issue. I'm pretty sure it is fixed, for future Polygons that are deleted. But for ones prior to app 1.53 the polygon will be stuck there, unless the user deletes and re-downloads the state or re-installs the app. If the Polygon was just unpublished, it could be fixed by re-publishing, then un-publishing again. But hard to deal with if it's been deleted.





BenLow2019 wrote:
I was looking at trail overview stats for West Virginia and discovered what I think is a mistake. It shows the highest trailhead as 9878 feet; however, the highest point in West Virginia is Spruce Knob at 4863 feet so this is impossible.
https://www.trailforks.com/region/west-virginia/

I added a sort filter for max altitude, to find problem trails.

https://www.trailforks.com/region/west-virginia/trails/?sort=s.alt_max&order=desc&difficulty=2,3,4,5,6,1,7,12&activitytype=-1

Fixed a few trails, re-generated their elevation and stats.

This was one of the problem trails https://www.trailforks.com/trails/connecter-39680/

Posted: May 12, 2021 at 13:32 Quote
canadaka wrote:




Regarding the Polygon issue. I'm pretty sure it is fixed, for future Polygons that are deleted. But for ones prior to app 1.53 the polygon will be stuck there, unless the user deletes and re-downloads the state or re-installs the app. If the Polygon was just unpublished, it could be fixed by re-publishing, then un-publishing again. But hard to deal with if it's been deleted.


Thats a bummer... This polygon is bright red and covering an entire riding area saying its closed, which has now changed.

Is there any way to find the polygon ID and revert the changes - so we can try to publish/unpublish it to trigger a change?

Frown

Can confirm that deleting the top region and downloading again does 'fix' it.

Posted: May 12, 2021 at 13:35 Quote
Arizona shows two trails with wildly inaccurate elevation. Recommend correcting data.
Mormon Mountain https://www.trailforks.com/trails/mormon-mountain/
Airport Conn https://www.trailforks.com/trails/airport-conn/

Posted: May 12, 2021 at 13:47 Quote
Nevada shows trail statistic error - reporting highest trailhead significantly above the state's highest point. I searched the trails for the offender, but the Max Alt filter didn't reveal the culprit.
https://www.trailforks.com/region/nevada/

Posted: May 12, 2021 at 13:58 Quote
South Dakota shows trail statistic error - reporting highest trailhead significantly above the state's highest point. I searched the trails for the offender, but the Max Alt filter didn't reveal the culprit.
https://www.trailforks.com/region/south-dakota/

Posted: May 12, 2021 at 14:10 Quote
Vermont shows trail statistic error - reporting highest trailhead significantly above the state's highest point. I searched the trails for the offender, Max Alt filter showed an excessively high trail, but not as high as what was shown on the state's statistics page. I followed that trail and low-and-behold it was the culprit. Max altitude doesn't show erroneous on the trail overview. Very strange.
https://www.trailforks.com/region/vermont/
https://www.trailforks.com/trails/hardy-s-hill/

Posted: May 12, 2021 at 14:16 Quote
BenLow2019 wrote:
South Dakota shows trail statistic error - reporting highest trailhead significantly above the state's highest point. I searched the trails for the offender, but the Max Alt filter didn't reveal the culprit.

Replying to my own post - I found the bad trail data in South Dakota here: https://www.trailforks.com/trails/homestake-trail/

Posted: May 12, 2021 at 14:27 Quote
BenLow2019 wrote:
Nevada shows trail statistic error - reporting highest trailhead significantly above the state's highest point. I searched the trails for the offender, but the Max Alt filter didn't reveal the culprit.
Replying to my own post. Searching the highest trails in the Max Alt filter revealed multiple trails with elevations that exceed the highest point in the state. You won't see the error until you look at the trail on it's own link.
https://www.trailforks.com/trails/badger-pass-climb/
https://www.trailforks.com/trails/hurl-backdoor/
https://www.trailforks.com/trails/rock-garden-15851/
https://www.trailforks.com/trails/little-jimmy/
https://www.trailforks.com/trails/three-amigos-15843/
https://www.trailforks.com/trails/bone-shaker/
https://www.trailforks.com/trails/ridge-15842/
https://www.trailforks.com/trails/little-jimmy-switchbacks/

Posted: May 13, 2021 at 18:09 Quote
Trails that are "planned" and do not exist yet are required for badges.
An example is the "Completionist" badge for Reston VA (https://www.trailforks.com/badges/view/33899/) - it requires that the "Hillside Trail" is ridden and this trail is marked as planned. See trail info here: https://www.trailforks.com/trails/hillside-trail/
Not sure why a trail that does not exist in reality is allowed to show up in Trailforks at all - even if it is planned to be created someday, maybe...
This seems like a bug.

Posted: May 13, 2021 at 19:27 Quote
oldman32 wrote:
Trails that are "planned" and do not exist yet are required for badges.
An example is the "Completionist" badge for Reston VA (https://www.trailforks.com/badges/view/33899/) - it requires that the "Hillside Trail" is ridden and this trail is marked as planned. See trail info here: https://www.trailforks.com/trails/hillside-trail/
Not sure why a trail that does not exist in reality is allowed to show up in Trailforks at all - even if it is planned to be created someday, maybe...
This seems like a bug.

The local admins should be able to edit that badge and remove the trail..


 
Copyright © 2000 - 2021. Pinkbike.com. All rights reserved.
dv42 0.010195
Mobile Version of Website