... the user friendly GPS tool


Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Bug report: missing <time> field
#1
Version: RouteConverterWindowsBundle 3.0
Scenario: when trying to save as a .gpx, there is missing <time> in <trkpt *>, that is troublesome in other use cases, for example in Google Earth.
Details:
in source data
Code:
<trkpt lat="23.752783" lon="120.618601">
<ele>173.2</ele>
<time>2024-03-27T00:00:00Z</time>
</trkpt>kpt>

in the output that RouteConverter generated
Code:
            <trkpt lat="23.752783" lon="120.618601">
                <ele>173.2</ele>
                <name>Position 567</name>
            </trkpt>
The <time> field is missing, I guess it's because the daytime part is 00:00:00Z.
Reply
#2
(29.04.2024, 21:30)Innertia Wrote: The <time> field is missing, I guess it's because the daytime part is 00:00:00Z.

If there is no time, then RouteConverter doesn't write <time>

Are you sure that data you want to write to GPX contains timestamps?
--
Christian
Reply
#3
(30.04.2024, 15:58)routeconverter Wrote:
(29.04.2024, 21:30)Innertia Wrote: The <time> field is missing, I guess it's because the daytime part is 00:00:00Z.

If there is no time, then RouteConverter doesn't write <time>

Are you sure that data you want to write to GPX contains timestamps?

I probably should have listed more data... in my track case, the nodes before and after are like
Code:
<trkpt lat="23.752819" lon="120.618586">
<ele>174.7</ele>
<time>2024-03-26T23:59:33.000Z</time>
</trkpt>
<trkpt lat="23.752805" lon="120.618601">
<ele>174.1</ele>
<time>2024-03-26T23:59:52.000Z</time>
</trkpt>
<trkpt lat="23.752783" lon="120.618601">
<ele>173.2</ele>
<time>2024-03-27T00:00:00.000Z</time>
</trkpt>
<trkpt lat="23.752766" lon="120.61861">
<ele>174.7</ele>
<time>2024-03-27T00:00:16.000Z</time>
</trkpt>
<trkpt lat="23.752785" lon="120.618601">
<ele>173.1</ele>
<time>2024-03-27T00:00:35.000Z</time>
</trkpt>

in the output that RouteConverter generated
Code:
            <trkpt lat="23.752819" lon="120.618586">
                <ele>174.7</ele>
                <time>2024-03-26T23:59:33.000Z</time>
                <name>Position 565</name>
            </trkpt>
            <trkpt lat="23.752805" lon="120.618601">
                <ele>174.1</ele>
                <time>2024-03-26T23:59:52.000Z</time>
                <name>Position 566</name>
            </trkpt>
            <trkpt lat="23.752783" lon="120.618601">
                <ele>173.2</ele>
                <name>Position 567</name>
            </trkpt>
            <trkpt lat="23.752766" lon="120.61861">
                <ele>174.7</ele>
                <time>2024-03-27T00:00:16.000Z</time>
                <name>Position 568</name>
            </trkpt>
            <trkpt lat="23.752785" lon="120.618601">
                <ele>173.1</ele>
                <time>2024-03-27T00:00:35.000Z</time>
                <name>Position 569</name>
            </trkpt>

Position 567 should have a <time>2024-03-27T00:00:00.000Z</time>, which is missing.
Reply
#4
After all these years I find it heard to believe there's a problem in the source code, but you never now. Please send me the complete original and generated files which you have cited above, so I can have a look and debug.
--
Christian
Reply
#5
(05.05.2024, 10:17)routeconverter Wrote: After all these years I find it heard to believe there's a problem in the source code, but you never now. Please send me the complete original and generated files which you have cited above, so I can have a look and debug.

My bad, I over-simplified my problem again, it actually happened on a .kmz => .gpx conversion, and I just checked that there is no bug when input is a .gpx.

Now I'm not sure whether the source is RouteConverter or Google Earth Pro (which I used to create .kmz) since I don't have the skill to check .kmz.  Let me know if it's Google Earth Pro to blame lol


Attached Files
.zip   BugReport.zip (Size: 253.24 KB / Downloads: 104)
Reply
#6
(05.05.2024, 11:34)Innertia Wrote: My bad, I over-simplified my problem again, it actually happened on a .kmz => .gpx conversion, and I just checked that there is no bug when input is a .gpx.

Now I'm confused: when I load the .kmz file in your ZIP and store it as GPX 1.1 it still contains timestamps. Nothing lost. And the RouteConverter's conversion.gpx contains lots of <time> elements, too.

(05.05.2024, 11:34)Innertia Wrote: Now I'm not sure whether the source is RouteConverter or Google Earth Pro (which I used to create .kmz) since I don't have the skill to check .kmz. 

.kmz is actually a ZIP with a doc.kml inside

Just change the extension to .zip and extract the doc.kml to read it
--
Christian
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)