31BMSG

The position readout of the GPSr seems to have more internal "buffering" than the compass pointer and will make corrections without you having to move, once I'm outside of the vehicle I switch the display page and navigate with only the position fields. If GZ is at N30 40.400 W95 50.500 and your position is N30 40.350 W95 50.450 you know you need to head NW a fair distance. Once you get close to GZ the position will still slowly correct but it will be a matter of .001 minutes instead of 90 degree random compass swings, dead reckoning .001 minute is a snap.

1. You're using an unauthorized app that violates a company's terms of use. 2. You admit to using this unauthorized app on the website of the same company you are using the app to hack. What could go wrong?

This macro may be what you are looking for, https://gsak.net/board/index.php?showtopic=21973&st=0&#entry218187 Read the history of this macro by following the links and see if it's something you can use. At the bottom of the page is a link for questions, suggestions, etc., the author of the macro is quite active on the forum and will be able to guide you in the right direction in case this macro isn't quite what you are looking for.

This, and please average the waypoint at least once.

Around six or eight months ago I added (STOLEN) to the title of several of my trackables mainly to track them in my trackables database and the frog has remained silent. I didn't mention any names but it's pretty obvious once you read the logs.

This makes more sense to me.

Hans is correct, I was going from two year old memory that apparently failed me. I only run one PQ once a week to maintain a large DB and that results in less than 100 caches a week.

Remember if you run the PQ through the website you are limited to 6000 caches per 24 hours, using GSAK you can grab 22000 in the same time period by switching between old and new API. Instead of making three queries (for example) of 990 caches combine three rows of the splitter display and set your maximum cache return to be slightly above the total of the combined rows, three rows of 990 set the maximum to around 3000. As far as I know you can call 16000 caches in one query but I limit a query to around 3000 caches, this takes right at 15 minutes to download to a database on my machine.

I was just adding my 2 cents to the question arisoft just answered above, for my uses I see no reason to change anything.

As far as I know none of my GPS receivers will display an emoji but I'm not concerned. As The Leprechauns pointed out above, GSAK displays these as question marks and I filter, delete, and ignore all caches with question marks before they go on a GPSr. If this thread is about changing the GPX schema or GPS firmware to allow viewing an emoji on a GPSr I vote NO, why spent time and resources reinventing the wheel in order to see something cute that has nothing to do with navigating to a cache?

When you say you 'set up a waypoint', can you tell me exactly what process you are using to create the waypoint?  If the OP is using Basecamp they might want to look here, I stumbled across this yesterday while searching for something else.

Contact GS and let them know I'll gladly give you my spot?

.

The help file is correct, just make sure each code is different, the code is what the database indexes on. Now after reading the last post by Mineral2 I realize you're using GZZ, I'll back out and let the experts take over. This morning was only the second time I've used GSAK to send to GPS, I normally just export a GPX file and drag it to the GPSr, one file for caches and one for waypoints.

I agree with Atlas on a separate database for your personal waypoints and that would be my first step. The name for your personal WP in the code column is not a valid geocache code and you have it mixed in with valid codes, it may be confusing the GPSr. I know it's not a 66 but I just tried this test on an Oregon 750, I sent a single waypoint named WP22 to the GPSr and it showed up as a waypoint. I renamed the code to GCWP22 and after being sent showed up as a geocache, so the name in the code column makes a difference.

You might see if these free maps will meet your needs, USA OSM auto. I have been using their topo maps and they are better than Garmin maps in my opinion.

Read the documentation for the Garmin, does the sample file show the only filter parameters you can specify or can you add to them? I would hate to see you brick a new GPSr because it wouldn't digest a XML file it wasn't intended to use. The ID for available in winter is 15 and 54 for abandoned structure but attributes have to be in their own section, for example: <Groundspeak:attributes> <Groundspeak:attribute id="7" inc="1">Takes less than an hour</Groundspeak:attribute> <Groundspeak:attribute id="13" inc="1">Available at all times</Groundspeak:attribute> <Groundspeak:attribute id="25" inc="0">Parking available</Groundspeak:attribute> <Groundspeak:attribute id="27" inc="1">Drinking water nearby</Groundspeak:attribute> </Groundspeak:attributes>

For me the whole site appears broken at the moment, right in the middle of working a puzzle at that.

This has been going on for some time but it doesn't appear there is much concern in fixing it.

Well duh, I guess I was looking at the wrong page, thanks!

I checked an hour after the original post and my profile showed what is pictured above with my statistics turned off. Now that appears to be working fine but I seem to have lost the check box to display/hide statistics, Firefox here as well.

In order to use an app as it's normally used the cache has to be listed on Geocaching.com, and in order for it to be listed it has to be available to the entire caching community. At my previous location I assisted in a Boy Scout geocaching program where caches were placed for the program but were still available for other cachers.

I don't know this individual personally but it may be worth inquiring about this,

I don't think you are understanding the concern correctly. Some of the posts above were made by individuals that have put countless hours of their own time into giving functionality to caching that the website will never be able to provide, they have also been debugging the new API for GS free of charge. It's been know for quite a while that CSS and javascript were going away and GS told these developers they would have time to modify and test their developments on the staging servers before this change was made, then pulled the rug out from underneath them.

Thank you, I added your response to the message as well. I've used Google to translate into English before and I had to read it a few times to make any sense. I was afraid it would have the same results translating English to another language.