Import PQ Name in DB by Beaglebrigade - 2013-08-31

Thank you Kai Team for adding the poll to the feature request. My view is that it should only be considered if there is a clear "I would use it" sentiment within the community.

hynr, I always appreciate another perspective on what I'm looking for in this feature. From my narrow view, I'm only interested in the "last" PQ that updated the cache record in GSAK. I strive to avoid PQ's that overlap, but that is an ongoing challenge. I rarely use the API to directly refresh caches so I had not thought of that when forming my request. For the PQ download, each one has a unique GPX file, as do GPX files for individual caches.

If I were to rephrase my feature request to make it more generic in nature:

1) "Could you add a new column to the standard database structure called 'LastGPXFile' ".

2) "Could the Import GPX feature be enhanced to write the name of the GPX file to the above field when the cache record is updated."

Thus, if a cache record is added or updated via the API, the column 'LastGPXFile' is either null or still populated with the name of the last GPX file - in my proposal a PQ generated GPX file - used to add/update the record. This may or may not be acceptable to other users so I recognize I might be skating on thin ice so to speak.

BB