tag:blogger.com,1999:blog-1540679498135170060.post4825761326267765972..comments2023-05-19T00:28:08.389-07:00Comments on Sierra Mapper: ...And we're live!Adamhttp://www.blogger.com/profile/01684839473166329021noreply@blogger.comBlogger3125tag:blogger.com,1999:blog-1540679498135170060.post-85763213391837557342014-09-27T12:41:42.359-07:002014-09-27T12:41:42.359-07:00Bill,
Thanks, as always, for the feedback!
In re...Bill,<br /><br />Thanks, as always, for the feedback!<br /><br />In regard to the unnamed junctions--I've tried to judiciously label the meaningful local mins and maxes. If a node is labelled, it will appear on the profile. So if I've missed some, it's a simple fix--let me know which ones (if you right click on one of those unnamed ones that you'd like to appear on the elevation profile, it will tell you the node id--something like "k019", for example.) Let me know any of those offending nodes, and review them.<br /><br />In re: to spurious elevation change, yes, I agree, it is still a problem. Two sources dominate: error in the route location, and accumulated error from oversampling. I'm working on signal processing to help minimize error from the second source. It it's current incarnation, that signal processing reduces the elevation change on the Agnew Meadows to Edliza Lake trail from +1,938 ft / -962 ft to +1,581 ft / -585 ft--this seems closer to your experience. I hope to roll this out soon, and owe a blog post to it for more explanation.<br /><br />The same signal processing also decreased the elevation changes in the Barney Lake, Duck Pass, JMT section. I also hiked that trail last month, and I do recall a bit of downhill near Barney Lake. But it was small (probably < 100 ft). In any case, again, with the current incarnation of the signal processing scheme, the amount of descent I calculate going up to Duck Pass is only 118 ft, and the amount of ascent on the way down to the JMT is only 45 ft. Errors on the order of tens of feet per mile seem quite good, to me!<br /><br />Thanks for the UI suggestions. Yes, I have to look at how to better handle the "back" button. I'd like a "back" button that would take you back to where you left off, and a "start over" button that would function how the "back" button functions currently.<br /><br />The "undo last" is a little clunky. It was the easiest--but not best--implementation I could come up with. Your suggestion is more elegant and versatile (and probably intuitive).<br /><br />As you can probably tell from the lack of blog posts and updates, I haven't had much time to work on this lately. I'll probably have more time this winter, especially if we have another bad snow year. <br /><br />Adamhttps://www.blogger.com/profile/01684839473166329021noreply@blogger.comtag:blogger.com,1999:blog-1540679498135170060.post-86912723427344950602014-09-25T15:32:31.891-07:002014-09-25T15:32:31.891-07:00Hi, Adam. I finally got a chance to use Sierra Ma...Hi, Adam. I finally got a chance to use Sierra Mapper for real: went up to Mammoth and took a trip over Duck Pass Trail. I printed topo maps from caltopo, but also printed the profile from Sierra Mapper as it provided a really nice summary of the key points along the trail with the mileage and elevation profile between each point.<br /><br />I noticed in a couple places (maybe not that trail) that there were some useful "unnamed junctions" that coincided with high/low points along the route, elevation wise, etc. Cool. That was a feature I really wanted (and mentioned on BPL). Those don't seem to appear on the elevation profile, unfortunately.<br /><br />I'm still running into cases where the elevation gain/loss seems really off on trails that are ostensibly uphill/downhill all the way. For ecample, I'm thinking about going to Ediza Lk out of Agnew Meadows. Sierra Mapper says this is +2K' and -1K'. That's hard for me to believe since there is only one short bit of "downhill" on this route (dropping ~300').<br /><br />I looked at a couple of sections of the route I just hiked (Barney Lk to Duck Pass, Duck Pass down to the JMT). Each of those indicated about a 200' incline in the opposite direction (i.e., downhill going up to the pass, uphill descending from the pass). I know firsthand that that is a total exaggeration. I'm not sure there is *any( downhill heading up to Duck Pass!<br /><br />A couple more minor UI complaints:<br /><br />1. when I say Calculate Route, then hit Back, it forgets the zoom level I was at. This is a pain; maybe store that in a cookie or put it in the URL?<br />2. The "Undo last" seems a bit wonky. Maybe just put a little "x" next to the list of points so one can selectively remove them?<br /><br />Bill LawAnonymousnoreply@blogger.comtag:blogger.com,1999:blog-1540679498135170060.post-39079841384978545882014-07-22T07:14:17.785-07:002014-07-22T07:14:17.785-07:00Adam, great tool thanks for creating and sharing t...Adam, great tool thanks for creating and sharing this!<br />here are a couple ideas I had that would add to its usefulness:<br />1. add in the locations of bear boxes, and (if possible) some sort of indication of where bearcans are required and where they are not. <br />2. add a feature that would let you map out a multi-day trip from start to finish, and then split it up into any number of segments of equal mileage and/or elevation gain. i.e if you want to do a 5 day trip from A to B, it would divide it into 5 roughly equal segments for you to help you decide where to camp each night. <br /><br />Thanks! <br />AllenAnonymousnoreply@blogger.com