Clyde, Thanks so much for your comments. This is indeed very helpful to me. Please note that I do not know how you coded GSAK so it cannot possibly be obvious to me. I have no way to know that you interwove all those aspects within the Load rather than handling though post-load-processing. I do not know the details of what you encountered in the years of fine-tuning this. I am aware of the "Resync" command to do post-load-processing. I take it from your comments that this command should not be viewed as a complete handling of all the issues that you handle during a gpx Load.
Mike, I am not using the GCapi function as a replacement for the GCrefresh or GCgetgeocaches function. So it is not an option for what I am doing.
Clyde, I sent you a private message last week (June 14) about a matter that I am not discussing here as a matter of respect for you. That is what I am working on. My question here is broader than that particular issue because it involves the use of the GCAPI() function to move full geocache data into a database.
I see the path forward for me as two possible trajectories: take data from the GCapi() function and:
Either
1. take the xml data (<a:xxxx> tags) and convert that into gpx which the Load command will accept (reinventing methodology that is already embedded in GSAK),
or
2. iterate through the GCapi SQLite table, transfer the data, field by field, item by item, into the main database table, RESYNC,... and (cross fingers, pray,...) etc.
If someone has coded either of these in a macro, then I would love to see that code.
Mike, I am not using the GCapi function as a replacement for the GCrefresh or GCgetgeocaches function. So it is not an option for what I am doing.
Clyde, I sent you a private message last week (June 14) about a matter that I am not discussing here as a matter of respect for you. That is what I am working on. My question here is broader than that particular issue because it involves the use of the GCAPI() function to move full geocache data into a database.
I see the path forward for me as two possible trajectories: take data from the GCapi() function and:
Either
1. take the xml data (<a:xxxx> tags) and convert that into gpx which the Load command will accept (reinventing methodology that is already embedded in GSAK),
or
2. iterate through the GCapi SQLite table, transfer the data, field by field, item by item, into the main database table, RESYNC,... and (cross fingers, pray,...) etc.
If someone has coded either of these in a macro, then I would love to see that code.