| Summary: | digikam gpssync no altitude | ||
|---|---|---|---|
| Product: | [Applications] digikam | Reporter: | Philippe ROUBACH <philippe.roubach> |
| Component: | Geolocation-Correlator | Assignee: | Digikam Developers <digikam-bugs-null> |
| Status: | RESOLVED NOT A BUG | ||
| Severity: | normal | CC: | caulier.gilles, mike |
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | unspecified | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | 1.3.0 | |
| Sentry Crash Report: | |||
| Attachments: |
GPS_20100404_084801.log the nmea file logged with my gps photo tracker
GPS_20100404_084801.gpx after converting with gebabbel |
||
|
Description
Philippe ROUBACH
2010-04-11 18:21:14 UTC
Hi Philippe, sorry, I can not reproduce this problem. Where exactly is the altitude reported as 0? If you want to, you can send me the GPX file and one photo where the altitude is not saved (mike AT mghansen DOT de, if you do not want to post it here). Michael Created attachment 42693 [details]
GPS_20100404_084801.log the nmea file logged with my gps photo tracker
altitude is 0 as result after correlator did their work
then
i apply correlator results
then
altitude 0 is in the metadata of the photo file
Created attachment 42694 [details]
GPS_20100404_084801.gpx after converting with gebabbel
Hi Philippe, thanks for posting the files. I can not see any altitude information in them. The NMEA file contains only GPRMC statements, which do not carry altitude information: $GPRMC,091631.000,A,4439.5600,N,00110.5346,W,0.04,41.89,040410,,,D*49 Compare it with the documentation here: http://www.gpsinformation.org/dale/nmea.htm#RMC So, of course there is no altitude in the GPX files, either. Maybe you have accidentally changed something in your GPS tracker? Please reopen if you can reproduce this bug with another GPX file which has altitude information. You can check it by opening the file with a text editor like kate, there should be <ele ...> tags in it, like here: <trkpt lat="14.00" lon="7.00"> <ele>14.7</ele> <time>2009-07-26T14:00:00Z</time> <fix>2d</fix> <sat>3</sat> <sym>Dot</sym> </trkpt> Michael ok i understand
yes i record minimum data but i can record richer ones but i am not a nmea technician.
what is the name (as GPRMC) of the statements containing altitude ?
in the doc of the Amod AGL3080 there is this :
LED Status Output Format Minimum Minimum
Records Operation Hours
Mode 1 Memory Full Led GGA/GSA/RMC/VTG->1 260,000 72 hours
ON sec
GSV -> 5 sec
Mode 2 Memory Full Led Only RMC->1 sec 1,040,000 288 hours
Flash
Mode 3 GPS Led ON GGA/GSA/RMC/VTG->5 260,000 360 hours
sec
Mode 4 GPS Led Flash Only RMC->5 sec 1,040,000 1440 hours
Mode 5 Battery Low Led ON GGA/GSA/RMC/VTG->10 260,000 720 hours
sec
Mode 6 Battery Low Led Only RMC->10 sec 1,040,000 2880 hours
Flash
i learn everyday :)
I set mine to record RMC and GGA. GGA contains both altitude information as well as the number of satellites and the precision of the position: http://www.gpsinformation.org/dale/nmea.htm#GGA I intend to extend the GPSSync in the next major version to look at the precision of the measurement, and mark the images which are not measured precisely (for example, when you just came out of a building) so that you can manually move those images to the right position. I am glad that we found the problem ;-) Michael thanks i will setup my amod |