11.06.2009, 09:19
(This post was last modified: 11.06.2009, 09:19 by routeconverter.)
Hi Robert,
it's actually very easy for me to modify the Columbus V900 Format - if it wouldn't render it useless. There are devices and software that use exactly that format.
Of course I could try to define a generic .csv format, but how would that look like? Something like this:
INDEX,DATE,TIME,LATITUDE,LONGITUDE,HEIGHT,SPEED,COMMENT,
1,210409,061051,47.797120,13.049595,524.33,33.44,Somewhere above the sea,
2,210409,061051,47.897120,13.059595,525.33,34.34,For GER/FRA/DK/NW/SW umlauts like äöüß,
Date + Time in GMT
Date in ddmmyy, Time in hhmmss
Latitude, Longitude in WGS84
Height in Meter above sealevel
Speed in Km/h
Whole file is UTF-8 encoded
Spaces ignored
Something like that?
Alternatively: How about splitting the NSWE into separate columns in Excel, doing the subtraction and then joining them again?
it's actually very easy for me to modify the Columbus V900 Format - if it wouldn't render it useless. There are devices and software that use exactly that format.
Of course I could try to define a generic .csv format, but how would that look like? Something like this:
INDEX,DATE,TIME,LATITUDE,LONGITUDE,HEIGHT,SPEED,COMMENT,
1,210409,061051,47.797120,13.049595,524.33,33.44,Somewhere above the sea,
2,210409,061051,47.897120,13.059595,525.33,34.34,For GER/FRA/DK/NW/SW umlauts like äöüß,
Date + Time in GMT
Date in ddmmyy, Time in hhmmss
Latitude, Longitude in WGS84
Height in Meter above sealevel
Speed in Km/h
Whole file is UTF-8 encoded
Spaces ignored
Something like that?
Alternatively: How about splitting the NSWE into separate columns in Excel, doing the subtraction and then joining them again?
--
Christian
Christian