jon Posted March 16, 2012 Posted March 16, 2012 I'm too excited about this not to start posting some teasers. COUNT( * ) name lat lng elevation 249 Mount Rainier 46.85277778 -121.76027780 14416 88 Mount Adams 46.20250000 -121.49055560 12287 9 Little Tahoma Peak 46.84944444 -121.71222220 11014 39 Glacier Peak 48.11111111 -121.11388890 10433 148 Mount Baker 48.77722222 -121.81333330 10420 12 Bonanza Peak 48.23777778 -120.86611110 9347 172 Mount Stuart 47.47500000 -120.90305560 9209 32 Buckner Mountain 48.49500000 -120.99777780 9091 6 Mount Fernow 48.16194444 -120.80805560 9078 112 Mount Shuksan 48.83083333 -121.60305560 9058 3 Seven Fingered Jack 48.15055556 -120.81388890 9022 26 Mount Maude 48.13722222 -120.80388890 9016 25 Goode Mountain 48.48277778 -120.91083330 8989 12 Mount Spickard 48.96944444 -121.24027780 8970 20 Mount Logan 48.53666667 -120.95194440 8937 18 Black Peak 48.52333333 -120.81555560 8920 4 Gardner Mountain 48.50722222 -120.48805560 8911 60 Eldorado Peak 48.53750000 -121.13416670 8861 9 Dome Peak 48.30166667 -121.03166670 8852 3 Lincoln Peak 48.76805556 -121.85944440 8842 14 Mount Redoubt 48.95805556 -121.30166670 8822 117 Dragontail Peak 47.47861111 -120.83333330 8809 Quote
Water Posted March 16, 2012 Posted March 16, 2012 can you elaborate---maybe im missing something--these some TR totals or someone's tick list for summits? Quote
jon Posted March 16, 2012 Author Posted March 16, 2012 these some TR totals? Yup. I've taken the USGS peak data, dumped in a db, and am figuring out the best way to query the TR data to index it. Quote
jon Posted March 20, 2012 Author Posted March 20, 2012 (edited) Scotch induced coding. Getting close to something useable. Edited March 20, 2012 by jon Quote
SeanO Posted March 20, 2012 Posted March 20, 2012 Rad. Google maps API + some ingenuity? Does the Gmap API provide elevation? Quote
jon Posted March 20, 2012 Author Posted March 20, 2012 The elevation is coming from the USGS data. The crux in all of this is how to get the USGS peak names to match up with the TR names, which can have abbreviations, misspellings, a chained TR, or crazy name (Ivan!) etc. What I'm basically doing right now is filtering the USGS peak names subtracting out "mountain, mount, peak" and then doing a full text search with that truncated name against the TR table, saving it as a one to many relationship since one TR can have many peaks. The whole point of this is that we have 7000 TRs and individually indexing them all would take forever, so this is the start, and then manually digging through the rest to provide a location. I still need to add Oregon and BC data. From there I need to come up with an elegant way of people flagging TRs that have the wrong peak associated with them, as well as don't have a location yet. Quote
chubler Posted March 20, 2012 Posted March 20, 2012 This will be an excellent research tool. It will mean less time spent at work filtering through TRs for beta and more time working. Probably not such a great thing after all. Looking forward to it! Quote
ivan Posted March 20, 2012 Posted March 20, 2012 The elevation is coming from the USGS data. The crux in all of this is how to get the USGS peak names to match up with the TR names, which can have abbreviations, misspellings, a chained TR, or crazy name (Ivan!) etc. the worst crime a man can commit is being ordinary Quote
jon Posted March 20, 2012 Author Posted March 20, 2012 The elevation is coming from the USGS data. The crux in all of this is how to get the USGS peak names to match up with the TR names, which can have abbreviations, misspellings, a chained TR, or crazy name (Ivan!) etc. the worst crime a man can commit is being ordinary True true. You can be out of the ordinary and make a spreadsheet with all your TR locations for me to import. Quote
JasonG Posted March 20, 2012 Posted March 20, 2012 So going forward folks will be able to put a pin on the map for a TR, sort of like you can do with Picasa? That will be cool to get the old TRs on the map also... Quote
jon Posted March 20, 2012 Author Posted March 20, 2012 The map above is with the old TRs and it's a fully functional mockup. Getting all the TRs into the map is going to take some time. To elaborate on what I said above, part of the problem is that in the USGS data there is a Short Peak and a West Mountain etc, and when I strip those I'm searching with Short or West, which obviously will hit a lot of TRs. The idea I'm working with right now is that when someone posts a TR they are given the option of adding the location/s name (with autosuggest from our database), which ties into our peak/location table. I say location because it could be a crag as well. If the location doesn't exist they will have the option of adding it to the system. I'd be interested in hearing about how people would like to be able to search TRs. One idea that came to mind is to be able to search a month range. Quote
ivan Posted March 20, 2012 Posted March 20, 2012 You can be out of the ordinary and make a spreadsheet with all your TR locations for me to import. what's a "spreadsheet?" saw that "watson" computer feller on jeopardy last year - i suspect he could figure out all my tr locations - you can rent him, right? a map that you can just click on for tr's is of course a capital idea, btw. Quote
jon Posted March 20, 2012 Author Posted March 20, 2012 I've got Oregon, Cali, and Alaska peak data now. Still working on data for BC. And the most TR award goes to..... COUNT( * ) name 279 Mount Hood 249 Mount Rainier 172 Mount Stuart Quote
ivan Posted March 20, 2012 Posted March 20, 2012 that's only cuz everybody calls the true leader Das Tooth or Der Toofwand or any of a million more charming appellations Quote
jon Posted March 20, 2012 Author Posted March 20, 2012 Actually there only to be a total of about 70 Toof TRs from what I can tell. What I actually find so cool is there are some pretty obscure TRs that I think most people would not know existed unless they say them displayed on a map. Quote
JayB Posted March 21, 2012 Posted March 21, 2012 The elevation is coming from the USGS data. The crux in all of this is how to get the USGS peak names to match up with the TR names, which can have abbreviations, misspellings, a chained TR, or crazy name (Ivan!) etc. What I'm basically doing right now is filtering the USGS peak names subtracting out "mountain, mount, peak" and then doing a full text search with that truncated name against the TR table, saving it as a one to many relationship since one TR can have many peaks. The whole point of this is that we have 7000 TRs and individually indexing them all would take forever, so this is the start, and then manually digging through the rest to provide a location. I still need to add Oregon and BC data. From there I need to come up with an elegant way of people flagging TRs that have the wrong peak associated with them, as well as don't have a location yet. Is there any way to allow users to associate a TR with a particular peak when they can see that it hasn't been indexed because of a mis-spelling, etc? Seems like crowdsourcing could be helpful if it's technically feasible... Quote
curtveld Posted March 21, 2012 Posted March 21, 2012 Excellent! This feature is going to save me alot of digging! COUNT( * ) name 279 Mount Hood 249 Mount Rainier 172 Mount Stuart ..clearly you aren't including the "What's the best approach/descent...?" threads Quote
ivan Posted March 21, 2012 Posted March 21, 2012 Seems like crowdsourcing could be helpful if it's technically feasible... once it's in place, pretty easy for them who's done tr's to go back and make certain it's all kosher, assuming it don't involve advanced calculus 'r nothing Quote
jon Posted March 21, 2012 Author Posted March 21, 2012 Is there any way to allow users to associate a TR with a particular peak when they can see that it hasn't been indexed because of a mis-spelling, etc? Seems like crowdsourcing could be helpful if it's technically feasible... Eventually there will be that ability, both to add TRs to the index and report those that are misplaced. Again, the biggest issue I have discovered is that there are a number of peaks named "short, west, north" that when striped of "peak, mt., etc" hit a bunch of TRs. I think the solution to this is to limit the number of peaks that I use from the USGS data, say only those above 7k ft. Quote
jon Posted March 21, 2012 Author Posted March 21, 2012 once it's in place, pretty easy for them who's done tr's to go back and make certain it's all kosher, assuming it don't involve advanced calculus 'r nothing We have some plans for that, notify people of broken image links that need fixing, adding some more appropriate metadata like route and rating that we can index as well. Quote
BootsandPants Posted March 21, 2012 Posted March 21, 2012 I'd be interested in hearing about how people would like to be able to search TRs. One idea that came to mind is to be able to search a month range. Month range/time of year would be very helpful. Thanks for all the work you're doing. It looks awesome and I'm excited to see the final implementation! Quote
jon Posted March 21, 2012 Author Posted March 21, 2012 Month range/time of year would be very helpful. Thanks for all the work you're doing. It looks awesome and I'm excited to see the final implementation! What I plan on doing is having check boxes for each month, with select all clear all option. Choosing a range between Nov and Feb with two sliders would be confusing. Quote
eldiente Posted March 21, 2012 Posted March 21, 2012 This is RAD. 100% support this, thanks for doing the work. Quick question. Would you allow users to go back and fix their TRs with proper peak names and locations? I for one would gladly fix my TR locations if this would help with the mapping. Thoughts? Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.