Author Topic: Trackpoint date changes in network  (Read 5762 times)

BobBailey

  • Full Member
  • ***
  • Posts: 62
    • View Profile
Trackpoint date changes in network
« on: November 19, 2007, 01:33:51 PM »
I went for a ride on Sunday. (Yeah, I know, congratulations.) Same route up and back down. Created some trackpoints on eTrex Legend and imported to PC.

I modified the elevations with DEM data and saved the file:
http://ebizmax.com/biking....ion.gpx
The trackpoints still have valid, accurate dates at this point.

I used the above file and created a network:
http://ebizmax.com/biking/gambrill/sourcenotes/GambrillNetwork.gpx
Dates on the trackpoints are now mixed some seem ok and others are clearly bogus, like 1977. I have seen this before but don't recall specifics, seems like the dates were 1900 which makes some sense given the history of date coding by MS.

Is this expected? Why?

tia... Bob

Krein

  • Global Moderator
  • Sr. Member
  • *****
  • Posts: 1203
  • TopoFusion Author
    • View Profile
    • http://www.topofusion.com/diary
Trackpoint date changes in network
« Reply #1 on: November 19, 2007, 10:17:13 PM »
Hey - any day with a ride is a good day, so congrats are in order!

Actually, you'll find that when you save a network out, time data is not saved (that GPX file you posted does not have time stamps). This is because, largely, when you merge tracks in this way, time data doesn't make much sense.

I did make some effort to intelligently merge tracks with the network code, and the remnants of that effort may be what you are seeing (before saving / reloading).  It *should* be possible to, say, grab the average travel time across each link in the network.  But right now it's best to just ignore it, as the program does once you save the network out.

BobBailey

  • Full Member
  • ***
  • Posts: 62
    • View Profile
Trackpoint date changes in network
« Reply #2 on: November 20, 2007, 08:44:37 AM »
You are indeed correct, no time data is associated with the saved track. I must have been looking at it before saving.

You are also correct in that it doesn't make sense to have the timestamp in the network especially the one I sent you, an up and back.

...Bob