That find/replace trick will only work if you are in a timezone that is 7 hours after Zulu (UTC). It will not work in any other timezone because the number will not be "-7:00".
As I pointed out in post #58, the "-7:00" may be different for other users, depending on which time zone they are in. But that shouldn't matter, should it????
Simply delete all occurrences the string:
"<time>Invalid DateTime-XX:XX</time>" (ignore quotes)
where XX:XX represents the user's offset from UTC, whatever it might be.
Just because I happen to be in a time zone that is -7h Zulu doesn't render the concept of the workaround invalid for users in other time zones.......does it?
All the user has to do is open an example gpx file in Notepad that they have exported from S&T, find an instance of the offending string, copy it to the clipboard, then do a search/replace of that string with a nul string. The numeric value of the offset to Zulu is irrelevant to the concept of the procedure.
I keep a copy of the string that applies to my time zone in a text file for handy reference. When I'm going to "fix" a gpx file, I simply copy the string to the clipboard, open the gpx file, do the replace, and I'm done. It's a nuisance and an extra step, but it works.