misplacedmichiganders

So, couldn't you use the uique name to generate it and then just rename it in the email message as you send it? It seems like the website is using ASP.NET and I believe that the Attachments classes of the .NET stuff have this ability - to read from a specific file/path for the attachment and send it with a different "name" in the email message.

I have to say that I am surprised only 200 people used the google earth plugin routinely. I guess I didn't use it every day but it was definately quick and easy to use. It will be missed, but I will try and use the built-in maps more now. As you said, they are a lot better. One suggestion for the maps page. Is there any way you can make the scrollwheel zoom in/out when the mouse is over the map? It makes it a lot easier to move and and zoom in/out on the map. It works on maps.google.com. On another random note, I have a request for pocket queries. I know that you're not going to change the limit on them and I respect that but here's a thought. When I go on vacation or travel for work, I tend to not really have an idea of where I'm going to go. For example, we went down to the Tampa area for spring break. A couple years ago we went there and 2 queries sufficed to cover a majority of the areas that we would be going over vacation. I was very surprised to see the number of caches that have been added in the last couple of areas. To cover the tampa/st. pete area took me about 8 queries to get setup. The problem I have is that I tend to have bad or no internet connectivity so I like to have my PQs in GSAK and on my PDA. Makes life easy to go "hey, I'm near a cache" and have the info and be able to get it. So, here's my suggestion. Setup pre-generated PQs that can be subscribed to. Perhaps by county or zip code or something like that. It shouldn't be too much of a load to generate them daily or weekly and then you'd be able to let them download on-demand from the website and also queue them up to be emailed out. If you had that, I'd probably never setup my own pocket query again and just use that. I know that even in my home area (indianapolis) there's a ridiculous number of caches around and it takes a lot of queries to keep me covered for all the places I go routinely.

So, just to throw my 2cents into the mix. I really think there is a misunderstanding of how people are using the pocket queries that want to have a slightly higher mix. First, my details. I live near Indianapolis. I have 7 queries setup to get all the caches within just 50 miles of my house. Not really that unrealistic of a difference for me to go caching with on a spur of the moment. Those caches are broken up, as suggested by others here into date ranges. I did it, but it was a pain. I get updates on the caches close to my house once a week so they are up to date. I then use GSAK to put them into a single database and export the file back out to my PDA. If I'm going caching, I grab the area near where I'm going and dump the nearby caches onto the GPS. My point for wanting a higher limit isn't to download 500,000 caches/week. It's about the ease-of use. I really liked the idea someone else put in of making it a # caches/week downloaded limit instead of "max 5 queries/day of 500 caches each". You're right, 17,500 caches can be downloaded every week. I don't want that many. I just would like an easier way to get the caches within 50 miles of my house. So, from my perspective, let's stop arguing about upping the max caches/query or queries/day and push towards a max # caches/week limit or something like that. The other reason for this type of thing is the example of me going on vacation in a few months. I'm going to, aparently, a fairly cache dense area in tennessee. I will have zero internet connection while there. I'm going with others so can't "plan" my entire week ahead of time. I know we're going to try and go hiking a couple days and that will take me to areas possibly 50-60 miles from my condo. Unfortunately, I can't hit that kind of range. I can only get about 20 miles from the condo before hitting the limit. I'd GLADLY disable my normal queries and again would just like the ability to get about 2000 caches in one query to save me hours of setting up the Pocket Queries to get that data.