EpicSki › The Barking Bear Forums › On the Snow (Skiing Forums) › General Skiing Discussion › Trail and Run Lengths for Ski Program
New Posts  All Forums:Forum Nav:

Trail and Run Lengths for Ski Program

post #1 of 14
Thread Starter 
I have an independent study for a Technology class right now, and I have to come up with some kind of technological study to do. My idea was to write a program that you would be able to input the ski trail/run that you skied and the ammount of time that it took you and that would output you're average speed throughout the run. The actual program would be very simple all you would do is select the resort and the trail(s) that you skied, then enter you're time in and it would output your speed. The only problem I have yet to figure out is how/where to get the data on the length of individual trails. I was wondering if anyone here has any trail length data or know somewhere I could find this data so I could build a database for the program. I have never skied out west  so I have no idea really as to what there are as to mountains out west so if anyone has data on trail length and a request for a mountain will they please post it here or PM me with it. Same goes for the East as well, as at the moment the mountains I ski in the East are my primary objective for the program.
post #2 of 14
Thread Starter 
I just had an idea and thought I'd get an opinion. If I us mapmyride.com--which is a site for mapping out running and biking routes if you're not familiar with the website--I can trace the trail and it will output the data in miles which I can then convert to miles. I just tried this for Black Diamond trail named Waumback at Bretton Woods, NH. I got 3006.9 feet. Anyone familiar with the mountain (or can tell by looking at the trail map) thnk this is an accurate measurement, or do you think the changes in elevation would effect that measurement?
post #3 of 14

Of course the elevation change has an effect.  You can bound the difference -- the largest possible distance would be to go straight over and then straight down (so distance = delta x + delta z), while the shortest would be the diagonal (so distance = sqrt((delta x)^2 + (delta z)^2).
If these two bounds agree within acceptable error, go with some ad hoc answer, such as the average of the two bounds.

 

post #4 of 14
Thread Starter 
 The thing is the program tells me my elevation change (that particular run was about 600 feet) so should I interpret that as taking elevation into effect, because simply finding the distance from your equation wouldn't take curves in the trail into effect would it?
post #5 of 14
 If you look through the forms someone actually made a website that if I remember correctly had average change in elevation of ski runs as well as length of each run. Might save you some time.
post #6 of 14
Thread Starter 
 Any general idea of where I would find it (ie what sub-forum or tag)?
post #7 of 14
Quote:
Originally Posted by lonewolf210 View Post

 If you look through the forms someone actually made a website that if I remember correctly had average change in elevation of ski runs as well as length of each run. Might save you some time.

That would be me.

Tylrwnzl, a pretty vague PM sent, please reply with any questions!
post #8 of 14
Thread Starter 
I'm debating whether or not to include begginer runs, if anyone here thinks they would use this program, do you think I should include some of the longer green runs, or just the blues and blacks?
post #9 of 14
Quote:
Originally Posted by tylrwnzl View Post

I'm debating whether or not to include begginer runs, if anyone here thinks they would use this program, do you think I should include some of the longer green runs, or just the blues and blacks?

I don't know.  My take is that anybody who's serious about measuring their speed skis with a gps in tracking/logging mode which has no need for an external database of ski run lengths.  Sorry, but I don't see how your program fits in with this scenario.
post #10 of 14
Thread Starter 
Quote:
Originally Posted by Walt View Post




I don't know.  My take is that anybody who's serious about measuring their speed skis with a gps in tracking/logging mode which has no need for an external database of ski run lengths.  Sorry, but I don't see how your program fits in with this scenario.

 


True, I didn't think about that. However this is more for an approximation type thing that is easy to do, not for guys training for races that are trying to get exact figures with an expensive GPS unit. Sorry I should have clarified that initially.
post #11 of 14
Trail lengths can be found on most resort websites, either on their trail map, or on their conditions page.
post #12 of 14
Thread Starter 
I'm yet to find the length of individual trails on any websites, can you show me where you found them?
post #13 of 14
Quote:
Originally Posted by freeski919 View Post

Trail lengths can be found on most resort websites, either on their trail map, or on their conditions page.


Really?   I've seen it a couple of times, but I wouldn't use the word "most".

Anyway, the trail length isn't very useful for computing speed unless you're straightlining it.  I usually make turns.  Most people do.
post #14 of 14
Thread Starter 
Quote:
Originally Posted by Walt View Post





Really?   I've seen it a couple of times, but I wouldn't use the word "most".

Anyway, the trail length isn't very useful for computing speed unless you're straightlining it.  I usually make turns.  Most people do.
 
True, I'm more of a straightliner myself with alot of quick turns; I'll have to add in some variables that people will set saying how often they turn. This is getting way more complex than I had anticipated.
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: General Skiing Discussion
EpicSki › The Barking Bear Forums › On the Snow (Skiing Forums) › General Skiing Discussion › Trail and Run Lengths for Ski Program