| QUOTE (lignumaqua @ June 23, 2013 04:12 am) |
| the Help file for GcApi() makes it very clear that you are on your own with the parsing. GcApi is provided as a way to get raw API data. |
Correct!
| QUOTE (Hynr) |
| What hurdles did you see when you implemented the GCrefresh and GCgetcaches commands that led you to go the much slower route via the filesystem (producing gpx files and then reading them with Load), rather than moving the data directly from the GCapi table to the GSAK database? |
I would have thought this was quite obvious, but I will explain.
Take a look at the Load GPX dialog. All the options you see there (especially things like updating counties, states, elevation) didn't happen overnight - not to mention the detailed summary of before/after changes. It seemed logical to me that users would still want all these options and functionality when loading the data via the api. All that functionality is tightly interwoven into loading a GPX file. To give you the same functionality by bypassing the GPX file load and updating the database directly would mean having to reinvent the wheel and duplicate all that work. Not only would that have been extremely time consuming, it just creates a whole new area for bugs to creep in (the GPX load is already a tried and tested method of getting bulk information into the database)