Yeah, that was the idea -- provide a high quality database of outdoors activities to the end users and then charge the providers / venues a fee for some extended information etc. But in order to even approach the providers / venues I had to have some kind of traction from the end users, which I failed to achieve.

>One thing that doesn't seem quite right though. >Shouldn't location, not activity, be the first bit of information requested from the user?

At the beginning I wasn't sure how to pull off the location filter nicely (should I use HTML5 geolocation, Gmaps geolocation, simple dropdown etc.) and just went without it but I have received this same piece of feedback more than once so I might go and add that, just for kicks.