radek on Pinkbike

radek pinkbikeaudience's article

Mar 8, 2019 at 17:09

Mar 8, 2019

Pinkbike Announces Acquisition of Road Cycling Site CyclingTips

Finally after 14 years of waiting I can rock my spandex . https://www.pinkbike.com/photo/16942594/

Added 1 photo to radek1

Mar 8, 2019 at 17:07

Mar 8, 2019

3 comments – Add comment

Added 1 photo to Mobile

Mar 5, 2019 at 16:48

Mar 5, 2019

1 comment – Add comment

Added 1 photo to radek1

Mar 1, 2019 at 12:52

Mar 1, 2019

1 comment – Add comment

Added 1 photo to Trailforks

Feb 18, 2019 at 8:13

Feb 18, 2019

0 comments – Add comment

radek radek's article

Feb 18, 2019 at 8:03

Feb 18, 2019

Trailforks Introduces Trail Grade Visualization

You can somewhat do this currently. An option when creating a trail is to draw in the point. The more points you put in the more accurate the grade will be. Additionally as you are adding a trail you can see the topo. Example: https://www.pinkbike.com/photo/16876938/ Also there is a "planned" option when adding a trail. A planned trail is only visible to those that have admins to an area, which should be associations and builders in a region. Once you add a trail, you simply sync the region and the planned trail along with grade info will be available on the app ( if you have admin ) . You also can see what the grade is at any point in the trail by sliding your finger on the elevation chart. Example: https://www.pinkbike.com/photo/16876980/

Added 2 photos to Trailforks

Feb 18, 2019 at 8:00

Feb 18, 2019

radek radek's article

Feb 17, 2019 at 7:31

Feb 17, 2019

Trailforks Introduces Trail Grade Visualization

We will be adding this in the next update.

radek radek's article

Feb 16, 2019 at 12:07

Feb 16, 2019

Trailforks Introduces Trail Grade Visualization

The larger elevation on the trail is still there. This was always below all the trail data so you have to scrill down on the trail page.

radek radek's article

Feb 16, 2019 at 10:37

Feb 16, 2019

Trailforks Introduces Trail Grade Visualization

@xyrion: We don't do anything nefarious and only build features and use data that is required for the app features. But, I do want to understand your point of view so here is a couple of questions. The tracker app test you pointed to just scans the app for the existence of a code library. Say in the case of fb. Yes there is a lib that will be used to do the fb login, but only when you actually decide to use that feature. If you never do a fb login, there is never any kind of call made to fb. How do you envision us making it work for someone like yourself, but yet still have the ability to provide a feature for those who choose to use fb login?