Sign in to follow this  
Followers 0

C:Geo Tips & Tricks & questions

23 posts in this topic

Posted (edited) · Report post

How do I make the arrow point and the map read in the actual direction I am traveling instead of the default setting of opposite?

Edited by Baytown Bert

Share this post


Link to post
Share on other sites

Posted · Report post

I believe the map is set to always have up be north and the arrow rotates to reflect direction of travel.  The version of Google Maps that it uses does not have the option (to my knowledge) of locking up as direction of travel.  Only thing I could recommend would be to find a different mapping program and access it under the radar option.  Just a thought.

 

Eagle

Share this post


Link to post
Share on other sites

Posted · Report post

You can't really.

However if you launch the compass you can set to use the internal compass rather than relying on sats and movement.

Alternatively... There is Locus. I actually bought the program and think it's pretty darn awesome. It's like the GSAK of mapping programs.

It's a little complex to use but pretty much does everything.. Geocaching included. It supports offline vector maps.. GSAK databases.. etc.

... like I said though.. it takes some time to learn.

Share this post


Link to post
Share on other sites

Posted · Report post

On the subject of C:geo - I am getting coordinates that are slightly different from the Geocaching web pages. Not a lot different: something like XX XX.125 XXX XX.225 vs XX XX.136 XXX XX.216. This is the kind of thing I keep seeing. I don't much trust C:geo anymore. This throws you off just enough that finding the cache is really hard. I don't have any idea if I might have altered something or what. Does anyone else see this sort of thing? The coordinates are so close that I don't think I have a different format.

Share this post


Link to post
Share on other sites

Posted · Report post

Make sure that C:Geo is getting signed into GC.com correctly.  If you are not signed in GC.com will build in a little bit of error to prevent muggles from being able to find the cache.  

 

Eagle

Baytown Bert likes this

Share this post


Link to post
Share on other sites

Posted · Report post

I have a question about pocket queries and c:geo. I have figured out that I can set up a pocket query on geocaching.com, and then go into c:geo and view it. This does not appear to be "running" the pocket query, as it still says the query has never been run. I don't want it to email me the file, so I didn't check off any days for the query to run when I set it up. Will the list in c:geo update if new caches are added that meet the criteria, even if the query is never run? Am I explaining my question well? I find this a bit confusing.

Share this post


Link to post
Share on other sites

Posted · Report post

On the subject of C:geo - I am getting coordinates that are slightly different from the Geocaching web pages. Not a lot different: something like XX XX.125 XXX XX.225 vs XX XX.136 XXX XX.216. This is the kind of thing I keep seeing. I don't much trust C:geo anymore. This throws you off just enough that finding the cache is really hard. I don't have any idea if I might have altered something or what. Does anyone else see this sort of thing? The coordinates are so close that I don't think I have a different format.

 

You might also check to see if your setting is for WGS84 and not something else.

Share this post


Link to post
Share on other sites

Posted · Report post

I use a different phone and app, so I cannot speculate. There are a bunch of C:Geo folks on the board and one of em should be along shortly...It'll take a little getting used to, but it will be well worth learning your apps capabilities. Here's where an event really helps answer a lot of questions since y'all can whip em out and play with 'em. 

Share this post


Link to post
Share on other sites

Posted · Report post

This may be naive on my part, but why run a PQ on your Smartphone?

Share this post


Link to post
Share on other sites

Posted · Report post

I have a vague idea that pocket queries do something fancy with a filetype I don't know how to use, probably involving an actual GPSr, which I don't have. :P So I'm just using it as an easy way to do searches a little more involved than c:geo normally does.

 

As far as I can figure, c:geo only lets you use one filter at a time for your search results. There's not a(n obvious) way to search for "the 20 closest caches that are traditional, EarthCache, letterbox, or multi-cache; I haven't found, don't own, and are enabled; are no more than 2.5/3 d/t; don't have attributes involving access fees, climbing, swimming, falling rocks, dangerous areas, hunting, abandoned mines, long hikes, people's front yards, or UV lights; and don't specifically say they're not recommended for kids." But I can save a pocket query that does exactly that, and then open it on my phone whenever the kids and I are out and about and wanting to find a geocache. :) 

 

I'm just not sure if it's doing a new search every time I open it in c:geo, or if it's pulling saved results that it got the last time the pq was run.

Share this post


Link to post
Share on other sites

Posted · Report post

My guess is it's the latter.  With Geosphere, I have to run a pq, then save it to dropbox and import it into the app.  If I go back to the app a week later and pull it in again, it's just getting the same data as last time.  I'd need to go back to GC.com and rerun the pq (and resave it to dropbox) to get new results.  If I had a pq set to run every day, I could use the GC.com app to pull it in by touching the Pocket Queries target from the main screen -- THAT would get new results everytime the pq ran (in this case, daily).

Share this post


Link to post
Share on other sites

Posted · Report post

This may be naive on my part, but why run a PQ on your Smartphone?

C:geo will run the PQ from GC.Com and allow you to store the results locally on your phone (assuming someone is using a phone to cache with). I almost never use that function as I can see caches live with C:Geo and dont need to load them on the phone. I guess it could be handy if you are going out of a service area and know you will drop the signal.

 

Hummmmm.

Share this post


Link to post
Share on other sites

Posted · Report post

This isn't saving anything locally to my phone. I'm not saving or importing any files, and it's not available offline. It's also not "running" the pq -- all of my queries still say that they have never been run, even though I've pulled them up on c:geo multiple times each. I think it's more like when you click on the magnifying glass next to a pq on the website and it shows you a preview. The only advantage that I'm getting over just looking at the "Nearby" button is that it's a very specific search.

Share this post


Link to post
Share on other sites

Posted · Report post

When you see the list of caches on the pq screen then hit menu and choose save locally. It will then store the displayed results to your phone. Btw it will only display 20 results, you must hit the more button to get them all.

You are just about as well off to download a gpx file to the phone and import it to cgeo.

Share this post


Link to post
Share on other sites

Posted · Report post

But what would be the advantage of saving it locally? Then it's old information.

Share this post


Link to post
Share on other sites

Posted (edited) · Report post

My only thought would be in case you were out in the sticks with no cell service (cant ever have enough backups). I only use cgeo to see more logs than I have loaded on my GPS if I am having a hard time finding a cache as I don't use my phone to cache with.

 

I only use PQ's to add new caches to my GSAK database when they are published.

Edited by ClanStan

Share this post


Link to post
Share on other sites

Posted · Report post

Slightly off-topic for a minute...sorry...

 

My guess is it's the latter.  With Geosphere, I have to run a pq, then save it to dropbox and import it into the app.  If I go back to the app a week later and pull it in again, it's just getting the same data as last time.  I'd need to go back to GC.com and rerun the pq (and resave it to dropbox) to get new results.  If I had a pq set to run every day, I could use the GC.com app to pull it in by touching the Pocket Queries target from the main screen -- THAT would get new results everytime the pq ran (in this case, daily).

HC~

 

We need to play around with this stuff next time we're together. Geosphere now has both the ability to scoop in real-time, and also to grab PQ's ready for download directly now. It's pretty convenient. Go into the user profile area and you'll see Pocket Queries, when selected it'll hit your downloadable PQ's and even distinguishes the old from the fresh, then asks which group to store them. There are some other goodies in there too...ie, trackables, etc. Anytime you want to you can also "update" any filter of caches in real-time to pull status changes and newer logs, etc. The only thing it cannot do is pull "newly published" caches outside of a small area fast. It's actually easier to hop on phone browser in a pinch and...well...queue up a Pocket Query, wait a couple minutes, then grab it from within the app.

 

Sorry about the branch...but I wanted to mention this handy change for those who were unaware. We really do need to have a phone caching workshop don't we?

GASTX and Jhawk! like this

Share this post


Link to post
Share on other sites

Posted · Report post

Slightly off-topic for a minute...sorry...

 

My guess is it's the latter.  With Geosphere, I have to run a pq, then save it to dropbox and import it into the app.  If I go back to the app a week later and pull it in again, it's just getting the same data as last time.  I'd need to go back to GC.com and rerun the pq (and resave it to dropbox) to get new results.  If I had a pq set to run every day, I could use the GC.com app to pull it in by touching the Pocket Queries target from the main screen -- THAT would get new results everytime the pq ran (in this case, daily).

 

Sorry about the branch...but I wanted to mention this handy change for those who were unaware. We really do need to have a phone caching workshop don't we?

And a GSAK one as well

Share this post


Link to post
Share on other sites

Posted · Report post

My only thought would be in case you were out in the sticks with no cell service (cant ever have enough backups). I only use cgeo to see more logs than I have loaded on my GPS if I am having a hard time finding a cache as I don't use my phone to cache with.

 

I only use PQ's to add new caches to my GSAK database when they are published.

 

Get T-Mobile as your service provider and you will totally understand. /sigh

Share this post


Link to post
Share on other sites

Posted · Report post

Slightly off-topic for a minute...sorry...

 

My guess is it's the latter.  With Geosphere, I have to run a pq, then save it to dropbox and import it into the app.  If I go back to the app a week later and pull it in again, it's just getting the same data as last time.  I'd need to go back to GC.com and rerun the pq (and resave it to dropbox) to get new results.  If I had a pq set to run every day, I could use the GC.com app to pull it in by touching the Pocket Queries target from the main screen -- THAT would get new results everytime the pq ran (in this case, daily).

HC~

 

We need to play around with this stuff next time we're together. Geosphere now has both the ability to scoop in real-time, and also to grab PQ's ready for download directly now. It's pretty convenient. Go into the user profile area and you'll see Pocket Queries, when selected it'll hit your downloadable PQ's and even distinguishes the old from the fresh, then asks which group to store them. There are some other goodies in there too...ie, trackables, etc. Anytime you want to you can also "update" any filter of caches in real-time to pull status changes and newer logs, etc. The only thing it cannot do is pull "newly published" caches outside of a small area fast. It's actually easier to hop on phone browser in a pinch and...well...queue up a Pocket Query, wait a couple minutes, then grab it from within the app.

 

Sorry about the branch...but I wanted to mention this handy change for those who were unaware. We really do need to have a phone caching workshop don't we?

 

Yes, please! 

Share this post


Link to post
Share on other sites

Posted · Report post

Thanks, Kenny.  As you can probably tell, I don't use Geosphere a lot.  I tried using it at the Block Party last summer and it wouldn't connect to the GC.com server and it frustrated me to the point of giving up on it.  Turns out, it was a GC.com issue, not the app.

 

A phone workshop would be nice!

Share this post


Link to post
Share on other sites

Posted · Report post

Kenny beat me to it, but anytime you pull in a GPX or a PQ, Geosphere will use it as a list of caches and then pull real time info on them.

I've written a GSAK macro that imports all my PQs and does database maintenance and then exports fresh GPX files to Dropbox every morning. All I do is import into Geosphere and I'm good to go.

And now we are branching into phone caching and are off the c:geo topic.

Share this post


Link to post
Share on other sites

Posted · Report post

I have a vague idea that pocket queries do something fancy with a filetype I don't know how to use, probably involving an actual GPSr, which I don't have. :P So I'm just using it as an easy way to do searches a little more involved than c:geo normally does.

As far as I can figure, c:geo only lets you use one filter at a time for your search results. There's not a(n obvious) way to search for "the 20 closest caches that are traditional, EarthCache, letterbox, or multi-cache; I haven't found, don't own, and are enabled; are no more than 2.5/3 d/t; don't have attributes involving access fees, climbing, swimming, falling rocks, dangerous areas, hunting, abandoned mines, long hikes, people's front yards, or UV lights; and don't specifically say they're not recommended for kids." But I can save a pocket query that does exactly that, and then open it on my phone whenever the kids and I are out and about and wanting to find a geocache. :)

I'm just not sure if it's doing a new search every time I open it in c:geo, or if it's pulling saved results that it got the last time the pq was run.

I would like to chime in here and say that in Geosphere you can run most of these filters too! It's one of the reasons I didn't switch to android when I was seriously considering it. Those filters are way handy. The only thing it's missing is filtering on attributes (which you list a lot of!)

But since GC limits the number of PQs you can run, I don't run PQs based on those types of filters. I will filter atts in GSAK if needed (mainly for challenges)

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now
Sign in to follow this  
Followers 0