TheAprilFools
-
Posts
323 -
Joined
-
Last visited
Posts posted by TheAprilFools
-
-
I noticed a minor issue with the all finds query the other day.
If I have five normal PQ's scheduled on a given day, I can run the all finds query, either before or after the other PQ's run and it works, no problem.
But if I have already run four PQ's, then the all finds query, the system will not let me schedule a fifth PQ for that day. Not a big issue but a little inconsistent.
-
Here is a stupid aside... Why do you need so many caches, up to date all the time? Are you likely to be traveling 100 miles, to actually need all those caches? Or is it just a 'I like to have a big database' thing. If you don't regularly travel within that 100 mile radius, why do you need all the most up to date cache information all the time?
Can we please stop with such comments. The only ppl who NEED cache data is Jeremy and the staff of Groundspeak because they make there livings using it. For the rest of us caching is our hobby, we don't need it but like having it. If it makes someone happy having the data for the caches in there home territory why not.
-
What I would rather see is rather than the whole state, how about everything within 100 miles of your home coordinates. With possibly the following restrictions.
1) You run only such query per week.
2) It must be centered on your home coordinators.
3) Your home coordinates must not have been modified in the last 7 days.
Right now I set up 14 PQ's to get all the caches within 60 miles of my home.
-
They could restrict these PQs to your home state only.
How about us border dwellers...
Assuming such as system were implemented (I am not going to hold my breath), run it for your home state, change your home coordinates to across the boarder, then run it again.
-
Make it one rectangle and divide by placement date. It's the same for if you want a large radius. If it includes more than 500 caches you create more PQs and divide by date.
Anyway, I was trying to present something that was simple and intuitive.
Understood, right now to map out an area that requires multiple PQ's the only efficient way of doing it is multiple queries with the same center point and radius divided by placement dates. Its a technique I use a lot (right now I have 14 PQ's setup that way to map out my home area, and that's only a 60 mile radius). With circles there is no other way because to do otherwise would have lots overlap or gaps. But just look at the number of times it comes up in this forum, its not a very intuitive idea.
But if we could setup rectangular areas where the edges are precisely defined it would be a very useful and more intuitive way to cover an area. When I have planned out my caching road trips, being able to map out my route using this sort of technique would have been much easier.
Now if you could define two coordinates and then specify that they are either the corners of a rectangle or the ends of a line where its to map out a specified distance either side, that would be very useful.
-
When editing, click the box with the label 'My profile details are written in HTML format'.
-
If all the caches in your area are going missing knowing who is on the watch list is not going to help. With instant e-mail notification and PQ's a cache thief has all the information they need without ever bookmarking or even visiting the cache page.
Now if there is a local cacher who just has a something against you, having an idea you might be on to them could persuade them to stop, but for someone who is truely outside the community there is not much you can do.
-
I think a wap link would be useful for some users. But on my phone, it can receive emails but I can't follow the links, even to the wap site. Having the waypoint code would at least allow me to look it up.
-
Thinking outside the box here (read: not had my coffee yet); continue to use the same paradigm of specifying the center of the search area, but add an option of the allowing the search to be rectangular instead of circular. This option alone would give you a square, however. When the user selects the option of the rectangular search the radius dialog changes to two dialogs; "Distance North and South" and "Distance East and West."
Sort the caches by offset from center either by longitude or latitude. This will still give you a truncated shape like the radius but in the chosen shape of the rectangle. It doesn't really matter which way the shape is truncated as long as it is known--the user can adjust the other dimension to get the desired results.
The advantage of doing it this way is you're still thinking in the same terms of center of search area and distance out. The dialogs will be very similar and intuitive. You can still specify a center by postal code or waypoint name.
The concern I would have is if I was trying to set up two queries with rectangular regions next to each other, I would like them to butt up against each other but not overlap. With a center coordinate and then a distance it would be difficult to calculate what the exact distance would be. Having a center point and boundary where things would be contained would be powerful and for those smart enough to be able to use this forum would not be a challenge, but I worry about those users who are not as savvy.
If the query generator really needed a center point to operate it could always calculate the center of the defined rectangle.
-
I think my suggestion was very intuitive. Just add these fields to the PQ form:
[ ] do not include caches North of ______
[ ] do not include caches South of ______
[ ] do not include caches East of ______
[ ] do not include caches West of ______
Personally I find the 'do not include caches...' a bit backwards, I would rather see:
[ ] only include caches North of ______
[ ] only include caches South of ______
[ ] only include caches East of ______
[ ] only include caches West of ______
Maybe something like:
-
How about something like this:
-
However, some people, whom I shall call puritans, believe that logging a find on the same GC number more than once is a mortal sin. They will not only not log the cache a second time but will not look kindly on those that do. They will not think much of the cache owner who updated a cache for some reason and invited people to revisit and log a second find. Such a cache owner is in league with Satan.
To say that someone has logged the same cache twice has committed a mortal sin and is in league with Satan grossly understates the seriousness of this offence.
(Sorry I could not resist)
-
Yes. It's a big project to make everything work with local dates. Admittedly it has been a low priority but we did anticipate the change so we added it as an option on the account page.
I ran into a problem recently where the time a GPX file was generated was stored in the file as GMT and since I was trying to use it on a system that is working on PDT (GMT - 7) and the gpx file was generated late in the evening it appeared as if it was generated in the future. Just wondering if fixing that would be on the to do list.
-
Choose placed within the last 7 days. What you are probably seeing is so many caches being updated that you don't end up seeing the new ones.
I used to use a query like this but ran into problems when our very dedicated and hard working local approvers fall behind and caches take longer than a week to get approved.
-
My regularly scheduled queries still have not run.
They finally ran at 3:10pm today, thanks.
-
My regularly scheduled queries still have not run.
-
I assumed that since the OP was asking for a GPX file to load into his palm that he was going to use cachemate and GSAK, since most cachers use those program to access the data on the palm.
-
My last query ran at 4/15/2006 5:46:19 AM, my sunday queries did not run.
-
The 16 caches all seem to be within an approximate 75 Km radius. Get a set of coordinates for roughly the centre and create a pocket query based on that. Set the query for the maximum 500 to make sure your 16 are all included.
Now you have your .gpx file which you can filter down to your 16 in GSAK, EasyGPS, or Mapsource to name a few. If you are set-up for paperless caching then you can take it from there.
Cheers, Olar
That would not work for me, it would take me at least 11 PQ's to map out a 75km (47 mile) Radius from my home.
Best you could do is from the search listing, open each cache page and click the download GPX button, a bit more tedious but it will work.
-
My Regular PQ's ran last week at 2AM, its almost 9am and they still have not run.
-
If you use GSAK to manage your PQs, it will keep adding logs as they come in. I have many Past Logs for some caches that have been in my database for a year.
Even if you use this method (which I do by the way) its possible that you will miss some of the logs. I have PQ's setup to run once a week for all the caches within a certain distance from my home, if a cache gets more than 5 logs per a week, I will miss some of them.
-
I tried to download a page full cache data in the form of a LOC data and after pressing "Check All" then "Download Waypoints" I get the following screen
Server Error in '/' Application.
--------------------------------------------------------------------------------
Column 'PublisherId' does not belong to table Table.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.ArgumentException: Column 'PublisherId' does not belong to table Table.
Source Error:
An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.
Stack Trace:
[ArgumentException: Column 'PublisherId' does not belong to table Table.]
System.Data.DataRow.get_Item(String columnName) +121
Groundspeak.Web.CustomWpt.Geocache.ReturnLocFile(DataSet dsCacheData, Boolean ShowSubscriberCaches, Int64 NumResults, Boolean IncludeUnapproved, Boolean IncludeArchived) +419
Groundspeak.Web.CustomWpt.Geocache.ReturnLocFileToHttpContext(String strWptCollection, Int32 DataSource, Boolean ShowSubscriberCaches, Int64 NumResults, Boolean IncludeUnapproved) +122
Geocaching.UI.geocaching_nearest.ReturnLocFile(String strWptCollection) +247
Geocaching.UI.geocaching_nearest.Page_UserLoggedIn(Object sender, EventArgs e) +170
Geocaching.UI.WebformBase.IsLoggedIn() +1097
Geocaching.UI.geocaching_nearest.Page_Load(Object sender, EventArgs e) +255
System.Web.UI.Control.OnLoad(EventArgs e) +67
System.Web.UI.Control.LoadRecursive() +35
System.Web.UI.Page.ProcessRequestMain() +772
-
It would be nice if you could filter on any note type, by yourself or by others.
-
I do a search new post when I enter. At the top of the page there is a mark all post as read. It seems to work from that page for me.
True, but its still an extra step we did not have to do before.
And the way the 'Quote' button confuses me, I keep hitting the one on the response before the one I want to quote, but thats just something I will have to get used to.
Nano Caches
in Website
Posted
Nano's are so small, there practically virtuals.