Congratulations!! You did such a great job on the documentary as well. I am registered for the 2024 Bear 100 this year. If all goes well, I’ll be the 2nd youngest at the age of 17 to finish. Hopefully we have clear weather like we did for this bear. I did paced my mom 42 miles on the 2023 Bear and the colors were beautiful!!! I plan on making a documentary like this. I’m curious what program you used to edit the video. Anyways, congratulations again and I hope to see you at the 2024 Bear 100!!!
Thanks Adam. It would be absolutely amazing if you could finish the bear at 17 years old! I'll be pulling for you! As far as editing the video, I'm a Linux user so I used a tool called KDenLive. It's a bit raw compared to modern video editing tools on Mac and Windows, but it gets the job done. Can't wait to watch your story.
@@WilsonJoeythanks for responding. I’ll look into that software. I’m familiar with IMovie, but I’m exploring other options for making videos because some other softwares have more features. Are you registered for this year’s Bear 100?
@@Ultramarathon_Wolf I'm on the wait-list, but still undecided if I will do it again this year. Either way I'll be at the race either pacing or racing, so I'll see you out there.
Holly, it took about 8 hours round trip on the trail. It's exactly a marathon distance with 4500 feet of ascent if you cut over to Anderson pass from Gunsight pass.
Joey, here's an update for you: I tweeted your video at Fatmap on Twitter the other day, and today they liked the tweet and responded "Thanks so much for sharing MacLean, I’ve passed this information onto the team!". Thanks for this video, hopefully it will help make people safer.
Great. Thank you. I also sent the video in via FATMAP's feedback email. There are some really nice things about FATMAP and it's getting better as they refine it. Hopefully they can tweak a couple things on the color bins and shading to solve this issue on their platform.
Hey Joey! Thanks for the feedback first of all. As someone has pointed out: you're comparing wrong tools - FATMAP has Avalanche terrain tool, which has more similar narrow range and fixed colors. FATMAP's Gradient tools is a very generic tool that is supposed to be used for much wider range of applications. Some of these applications can not be solved with the tool that you're showing in Caltopo. For example: I might be biking and I don't want to climb slopes steeper than 10 degrees; or I might be doing base-jumping and in that case I really care about the top range of the Gradient. That's why FATMAP's Gradient maps full 0-90 degree range. If you want more specific range you need to check the Avalanche tool. Having said that anyone who thinks "yellow = safe" is putting themselves in danger as these tools are very simplistic as far as avalanche risk goes and you need to take much more things into account (vegetation, composition of snow, the slopes above you, etc). I would love to see better and more realtime tools built for the avalanche estimation. Well... some day ;)
Yes! This is exactly what I was going to say. The gradient layer is a catch-all. It is for all sports. The avalanche layer is specifically targeting slope ranges that can be useful to someone assessing the risk. I like the buckets CalTopo has better (27-29, 30-21, etc) which could be an easy win for FATMAP to change. However, the current colors and ranges on the avalanche layer on FATMAP target zones of gradient which categorically become useful given certain risk levels. What I don't agree with is @MacLean's tweet about it being dangerous. Any data visualization tool needs a frame of reference for it to be useful. FATMAP is a tool - it should never (like every other tool) be used as an absolute for risk assessment; it is there to help you make your decision. Nice summary though - always good to hear feedback about tools people use and how they use them. I am very sorry to hear about the losses of life that occurred. Always puts risk back into perspective fo rme
Paulius, I am aware of the avalanche overlay in FATMAP. I still think that the way it's shaded needs to be updated. Having a "pale" color at 35 is not intuitive for people. That slope should be bright red, as it's in the bullseye of avalanche terrain.
With DEM shading in CalTopo, it's easy to add custom slope shading tailored to any activity. For example, based on an avalanche forecast, you could highlight all slopes above 9000' with a NW aspect and steepness above 30°. Or, as you say, only shade zones steeper than 50° if you're interested in base jumping.
@@paulgeimer138 That's awesome. I didn't realize you can do custom shading layers. I just checked it out. Now if CalTopo could just get a better user interface...
New to FatMap, but there is an avalanche-specific terrain layer that ignores all slopes below 25° to help highlight dangerous terrain without the distractions of low-angle slope shading. You could definitely argue that the avalanche layer's color scheme could be improved, since it shows 45°+ in the darkest red, but it is still an improvement over the Gradient terrain layer for this application.
And as a comment here, most avalanche slope angle layers group everything over 45º together because the risk of human-triggered avalanches drastically decreases from here upwards as slopes tend to slide naturally
Paul, yes, I agree. The avalanche layer filtering lower than 25 is great, but the choice of colors for highlighted regions is misleading in my opinion. Pale colors at 35 degrees gives the wrong impression.
Great summary of the software tools Joey. Fatmap definitely needs to change their color gradient scale. To me, Fatmap's advantage over other mapping software is its complexity, but that's also it's downfall; it tries to do too much, but doesn't do it well enough for me to trust it.
It is also important to know the source and resolution of the DEM (digital elevation model) data used to generate the slope shading. LiDAR data is generally the best and can be generated to penetrate the foliage ground cover to give you a true terrain model.
Thank you for showcasing the beauty of this course, set to some lovely music choices. I know this will be a brutally tough race, but I hope to complete it in 2020.
You're welcome Lisa. Best of luck out there this year. Also, let's not forget to credit Nuge's beauty as well, especially when he had his shirt off at the Lambs Canyon aid station. 😲
Hello my friend, What a perfect job! I'm doing an RTI project. What firmeware did you put on the CC2531 to make the mesh network and access the data over USB. Or did you use another device to create the Zigbee network? Did you use python? Or what code to process the RSSI data? Which operating system? Windows or Linux? Do you have an email address? I'm studying at the Federal University of Espirito Santo - Brazil. If you can help me, I would appreciate it.
Hello my friend, I'm doing an RTI project. What firmeware did you put on the CC2531 to make the mesh network and access the data over USB. Or did you use another device to create the Zigbee network? Did you use python? Or what code to process the RSSI data? Which operating system? Windows or Linux? Do you have an email address? I'm studying at the Federal University of Espirito Santo - Brazil.
Hello Friend. I'm finding it very difficult to test a simple communication between 2 CC2531 USB Dongle from Texas Instruments. At first my notebook recognizes the CC2531 through Cebal controlled devices, not through a COM port. By chance. How did you do the tests for your computer to recognize the peripheral? How did you manage to communicate the device with IDLE Python? I am trying to use it in Window 7. 62bits
At first I was shocked but from 2.24 I began to think !!!!!BOAH !!!!!! Nsa I expected more from you. Even my computer can locate my phone better. Excluding 50 cameras placed around this
