Bug 323043 - Can you add timestamp field to the GeoDataCoordinates
Summary: Can you add timestamp field to the GeoDataCoordinates
Status: CLOSED INTENTIONAL
Alias: None
Product: marble
Classification: Applications
Component: general (show other bugs)
Version: 1.5 (KDE 4.10)
Platform: unspecified Unspecified
: NOR wishlist
Target Milestone: ---
Assignee: marble-bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-07-31 13:40 UTC by Pavel
Modified: 2013-09-12 14:37 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
This patch adds field m_tm (timestamp) to the GeoDataCoordinates (2.71 KB, patch)
2013-07-31 13:40 UTC, Pavel
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Pavel 2013-07-31 13:40:18 UTC
Created attachment 81480 [details]
This patch adds field m_tm (timestamp) to the GeoDataCoordinates

It would be nice to have parameter like timestamp in GeoDataCoordinates and methods like setTimestamp(), getTimestamp
Comment 1 Thibaut Gridel 2013-08-03 17:12:40 UTC
It would be interesting indeed to have time information in the coordinates.
Unfortunately we try and follow the  KML specs for the geodata classes and time does not belong there.
You can look for timestamp and timespan in the reference available here:
https://developers.google.com/kml/documentation/kmlreference
Comment 2 Bernhard Beschow 2013-09-07 12:31:44 UTC
You can also subclass GeoDataCoordinates in your own project to add the timestamp methods. Adding it in Marble wouldn't have a gread deal of benefit because Marble doesn't use timestamps internally anyway.
Comment 3 Pavel 2013-09-12 14:37:35 UTC
Thanks, I found another solution.