New Pocket Query Generator

[+Clan-Wallace]

I can see that 'Groundspeak Customers' have been requesting an update to the old GPX format, still in existence today, way back in 2011. It looked like progress was being made in 2014, with more Customer frustration appearing in 2016. This post now makes that six years with no action taken as far as I know on matching the API to the Pocket Query generation tool. 

The new Advanced Search tool is a good example of improved use of the API.

The pocket query tool could offer many more filter options and generate a new GPX format that contains many additional and useful items of data that is currently accessible through the API.

Surely this also makes economical sense? How many Customers download the current GPX format and then have to use other applications, like GSAK, Android and IOS apps, which place further load on the Groundspeak servers, in order to download missing information they need to enhance their geocaching experience in the field and back home? 

Can a member of Groundspeak re-assure us that we are being listened to and action is being taken to fulfil these missing features that would make it better for everyone, including Groundspeak?

Thank you.

Edited September 29, 2017 by Clan-Wallace

[+Viajero Perdido]

+1

If Groundspeak were to put an effort into user-friendliness, making things less confusing, this would be a great place to start.  I just operate an app that's complicated enough without Groundspeak adding their own quirks.

(Usability #2 might be, un-confuse the concept of "Premium".)

[+Starkacher]

Whole-heartedly Agree.   More filter options should include optional Latitude and Longitude limitations (None, Only lower limit, Only upper limit, Lower and upper limit)    This can square off 1-4 edges of the "circle" and potentially make it a square.     This could actually lesson the burden on the geocaching,com servers as people could run fewer pocket queries to cover an area. That is because they would not have to waste returning duplicate caches within overlapping circles.   I have not thought through what happens for people on the zero (or 90?/180) longitude or longitude lines.  That may need an OR option for the limits?      A similar enhancement would be a distance range.     Instead just <= a particular distance, add >= a particular distance (subject to overall individual PQ cache count limitations), or at least add a between X and Y distances.   That way you could create Rings around earlier PQs in order to fully cover a desired area (again without having to have wasted/inefficient overlapping circles).       

Edited October 1, 2017 by Starkacher

[+Kai Team]

I'd be happy if the PQ's were just updated to include all of the information returned by the API - e.g. corrected coordinates, with an indicator, original coordinates, favorite points....  It would reduce the demand on the Groundspeak servers, since users would not have to update caches with the API to get missing information after loading PQ's.  Enhanced PQ generation search criteria would be the icing on the cake, but first we need the cake (complete cache information in the PQ's).

[+Clan-Wallace]

That is now 13 THIRTEEN years since Ground speak was first informed that the GPX generator does not include additional information that is available in the API, (leading to their users having to place additional burden on GS Servers in order to get this missing, required data) and no representative of Ground speak has had the decency to respond to this ongoing issue in all those years.

What is the point of these forums if your customers are not listened to and acknowledged?

Edited July 27, 2023 by Clan-Wallace

[+HHL]

On 10/1/2017 at 4:50 PM, Starkacher said:

That is because they would not have to waste returning duplicate caches within overlapping circles.

No one has to deal with overlapping circles when using ONE bigger circle and split the PQs by date.

See this: http://markwell.us/pq.htm#tips

[+the3gmen]

The frustrating thing about building pocket queries for me is finding the dates to split the PQs by.  It is just tedious.

If I can go to Project-GC, who is a partner with Groundspeak, put in the area I want, and have it give me a list of the split dates, why can't there be a way to automatically generate the pocket queries for me?

[+Frisby24]

I’m currently developing an API to generatively create NFTs and digital souvenirs based on real-world geocaching data. The ultimate vision would likely involve partnering with Groundspeak to access more complete data — right now, I’m working with GPX files, but there are some limitations.

For example, I’d love to access details like:

• Whether I awarded a cache a Favorite point
• The total number of Favorites a cache has
• Favorite percentage and premium-only status

My generative art scripting is still in its early stages — a bit crude — and the lack of full data adds a fun but frustrating puzzle. I don’t currently use tools like GSAK or Project-GC (though I’m looking into them), since I’ve been building out my own pipeline.

Right now, I:

• Download a GPX of all my finds
• Parse it by date and log ID
• Cross-reference a second GPX of my Favorite list (exported by copying the list and downloading that)

From there, I generate NFTs based on unique geocaching attributes — logs, placements, even the cache environments. It’s a bit of a backend labyrinth, but it works.

That said, I understand Groundspeak probably limits certain data in GPX exports intentionally — maybe to steer creators toward more formal API partnerships rather than wild-west-style scraping by folks like me and my grubby little hands 😅

 

Anyway, if anyone has advice or experience navigating these data constraints — or wants to brainstorm around partnerships — I’d love to hear your thoughts. I’ve also started a poll discussion to gauge interest in this concept from the broader community. It hasn’t been approved yet, but hopefully it’ll go live soon...

Generative Art NFTs for Geocachers? Create, Mint, and Track Your Own!