Yes, of course you're at a disadvantage, I'd say a serious one! Just as
I am with this 1% of the project because I'm not a VBA programmer, so
you are with the previous 99% because you don't know GPSU.

But we're now way OT! If you want to discuss GPSU there's a Google group
forum at https://groups.io/g/gpsu/ but it's been pretty quiet for the
last few years and traffic dropped off even more sharply when it moved
to Google after Yahoo dropped its groups.

Well you are certainly correct speaking about your project, but GPSU's help
file is pretty straight forward about explaining how it works and how to use
it, ..speaking from an application developer's point of view. (VBA isn't the
only language I develop in; - all of my Excel-based apps have equivalent
stand-alone Windows EXEs for those who don't/won't use MS Office. These are
currently being revised to implement a newer spreadsheet control that fully
supports working with the latest Excel file formats.)

Also, I'm very familiar with data logging in more general (broader) usage so
the GPX file you posted (4846 lines) is a rather small file by comparison to
many I've seen and worked with before. That said, your final (nicely done) xlsm
has that same walk as its 1st entry; - the Trkpts field value is only 925; how
was that arrived at from the 4846-line data log with 4828 trkpt lines? (Your
ActualMiles field value is 7.9; the GPX value is 8.3; - I assume you turned the
recorder on before actually starting the walk!)

The context of my offer to you is to populate WalkIndex.xlsm directly from the
source file instead of from Clipboard; - that data source file is what I need
to work with because it contains data not in the GPX file. (I was just curious
about the output format from GPSU's CSV file; - disappointed that's not what
you posted!)


My design intent is as follows:

Use a pre-configured source data template file for listing new walk data;
This will be a proper text file dbase template; - 1st line has the
datafields from Target pre-inserted, as a delimited list. (I normally use
the Pipe character but this is your choice as to which character)
- gives you the option to include multiple walks in a file

Use your final Target sheet as its template (xlsm) for adding new walk data
and displaying historical records;

Enable you to choose the file[s] to import via a file dialog for each session
you add more walk data;
- adds new data to the next empty row

A backup (dbase) file will be maintained in case your xlsm gets broken or
damaged such that it won't open; - you'll be able to recover your data into
a new workbook with 1 mouse click.

(This is a typical feature with other data logger analysis projects I've
done)

Would you like it to not pre-load existing walk data when it opens?
(Typically, users are only working with new data being added, and have
existing data display only on demand? Typically, my users like to be
able to view historical data using filters such as 'Place to Place',
'Date to Date', and the like.)

(My experience with data logging systems is mostly in the trucking
industry for analizing road trips; - place-to-place mileage, elapsed-time,
fuel-consumed, rest-stops, and whatever else the client wants. Data
sources are the logger system output file, trip manifest, and trip record.
Normal usage is direct input from the source paperwork and data logger
file is read to setup the record rows for each place-to-place)

Optionally, enable you to view your maps and other images via InsertPicture
on a separate sheet via existing links to image files (for viewing only);

All features run from menu controls on a custom Ribbon tab that appear when
the workbook opens, disappears when it closes;

As is the case with all my clients, this project will remain your proprietary
property. (Don't worry, there's no fee for this!)

If you decide to proceed, I suggest we continue with this offline as it
ventures way too far OT to continue here. (You'll need to post an email
address!)

--
Garry

Free usenet access at http://www.eternal-september.org
Classic VB Users Regroup!
comp.lang.basic.visual.misc
microsoft.public.vb.general.discussion