zakn
It costs $5 for the packing service, but it's worth it to avoid the burden of shopping. No more tedious math on which is the better deal. No getting lost trying to find avocado oil. And no lines. I wish I had done this years ago.
I was playing with the MapBox SDK roughly a year ago and I remember having a lot of trouble at the time panning and zooming. This was on a Droid X. So gave up on it at the time, even though I thought the desktop experience was so great.
Anyway, I just tested again, and whatever I was seeing before is not there. I'll give MapBox another shot.
Thanks for the feedback too. I want to support finding nearby hikes in two ways:
1. If you go to the maps page, it should zoom you into your location and show you hikes nearby. That part works, but I also wish it zoomed out when no hikes are within your current viewport.
2. Also (and this part isn't done), I wish there was a way to filter the Discover images by location.
Feel free to add any of your local trails or update the Narrows.
AirBnB is a great example of categories done right. I'll look into that.
Someone mentioned affiliate links in a bibliography section. I could see that working because it's not intrusive, but you'd have to be careful not letting your sources be dictated by what's available on Amazon. I like donations because it keeps the financial goals of the site inline with creating the best experience.
I could see sponsorship links working, maybe on the homepage, or maybe in a separate /sponsors page. I'm not completely sure, it's a tricky problem.
Do you have other suggestions?
When I add support for searching by location (because this seems to be a popular request), then I think it should zoom you into the location, enough so that you could see all of Seattle. I think this can be done with google's jsapi / google maps but I'm going to have to investigate.
I've added an issue - https://github.com/zaknelson/hike.io/issues/24
Multi-trail circuits are not really supported at the moment, but I like the idea. You could hack your way around it currently by creating a "master hike", call it Annapurna Circuit, and then link to the other sub-trails from the master.
I've created issues for both of the things you've mentioned - https://github.com/zaknelson/hike.io/issues
In terms of monetization, all I know at this point is that I want it to be freely available without ads. Beyond that, I'm flexible. A supporter badge could work. I was also thinking it would be cool if there was a way to monetize the pictures. For example, if you could order prints, a portion of the revenue would go to original photographer and hike.io.
That is annoying that the map doesn't remember where you were. Seems like the best way to handle that is to store your last location in localstore.
The reason I've been writing driving directions in a wall of text is because in a lot of cases, google doesn't map all of the forest roads required to get to the trailhead. There are some hikes, like http://hike.io/hikes/mount-rose, which do and in that case I include the link in the Directions header. I thought it might be nice to also include the step by step directions in case you don't have an internet connection, but you're right, it feels extraneous.
And, I'm going to have to investigate OSM, you're the second suggest that.
At this point, I'd say just add it, since I'd rather have more data. If it becomes a popular resource, I suppose the site will need a clearer definition of what constitutes a hike.
1. I know exactly which hike I'm looking for. I type it in, and there it is (I know that currently that is almost never true, but let's assume there is a good number of hikes on there already).
2. I want to find hikes near me - rather than type it in, I go to the Maps tab. It should automatically zoom me into my location, to display hikes near me.
3. I want to explore new hikes, not necessarily close to me. That's where the Discover tab is useful.
Watching the logs and reading the comments here, I'm finding that it's very natural to search for a location as well. I'm adding it to my TODO.
I'm using Mailgun to do the mail stuff: https://github.com/zaknelson/hike.io/blob/master/server/util...
A number of people now have mentioned that the first page is not working, so that's something I'm going to reevaluate. I need more info there beyond a daunting search box. At the moment, you can type in the name of a hike and it will show up, e.g. try "The Narrows". The site assumes hikes are named. If you're searching for a location, then you need to go to the maps. I should probably support searching for a location via the search box, e.g. if you search for colorado it will show you all the hikes in colorado, or zoom you into colorado on the map.
Maps. Currently the way to get to the maps is from the lat / lng link in the info box on the side. This will take you to a full screen map with a dot for that location. From here, I'd like to add support for GPX routes, but that is not implemented. It's interesting that you're keen on having maps as the focus because I find that maps aren't that useful for me when researching a hike, I just want the highlights - distance, elevation gain, elevation max, and then I want to see pictures of what the hike has to offer.
Thanks for the encouragement, I'm taking a lot from these comments and will have plenty to work on.
Thanks for the hikr.org link, I haven't come across that one before. And very cool trip tracker of your hikes.
Putting some more info on the homepage is a good idea, whether that ends up being the Discover page... I'm going to mull on it for a bit. Thanks for taking the time to comment.
And good point about The Narrows. I should have that info on there.
I haven't seeded production with it yet because I was a bit unsure on whether that was ok to do. Maybe I should send them an email...
-GPX support is top of my list of TODOs.
-I like the USGS topo / OSM idea. I'll have to do some investigation to see how it compares with Google Maps.
- I agree that a bibliography is a must. This is also something I would have gotten for free with MediaWiki. The reason I didn't build on top of that was, basically because I wanted to have complete control over the end result. Writing the code was the fun part for me. That being said, I wouldn't completely write it off.
- And I did write one scraper already for wta.org, but was unsure about whether that was ok to do or not...