Bug #105863 for Geo-Gpx: Support fractional times

Tue Jul 14 13:41:17 2015 SACAVILIA [...] cpan.org - Ticket created

Subject:

Support fractional times

Writing tracks currently truncates timestamps to 1-second resolution. This means that track data captured at >1Hz will be recorded with some timing data lost. Real-world requirements for this are probably rare (I only noticed it while testing a seldom-useful configuration of a development tool for a specific niche application) but it would be nice to support it correctly just for completeness. I'm not sure what other tools do in similar cases. It looks like the gpxlogger tool from gpsd will just write 3 decimal places after the seconds value (which is ISO standard). Are there any reader applications that can't deal with such values?

Wed Jul 15 17:04:11 2015 SREZIC [...] cpan.org - Correspondence added

On 2015-07-14 13:41:17, SACAVILIA wrote: Show quoted text

> Writing tracks currently truncates timestamps to 1-second resolution. > This means that track data captured at >1Hz will be recorded with some > timing data lost. > > Real-world requirements for this are probably rare (I only noticed it > while testing a seldom-useful configuration of a development tool for > a specific niche application) but it would be nice to support it > correctly just for completeness. > > I'm not sure what other tools do in similar cases. It looks like the > gpxlogger tool from gpsd will just write 3 decimal places after the > seconds value (which is ISO standard). Are there any reader > applications that can't deal with such values?

Nokia's Sports Tracker Symbian app writes two digits after the decimal dot. Below is a sample trackpoint. The sampling frequency is 1Hz though. <trkpt lat="52.508293" lon="13.453038"> <ele>84.0</ele> <speed>0.90</speed> <course>4.7</course> <desc>Speed 3.2 km/h Distance 0.01 km</desc> <time>2009-01-10T18:47:53.57</time> <name>8</name> </trkpt> Regards, Slaven

Wed Jul 15 17:04:11 2015 The RT System itself - Status changed from 'new' to 'open'