View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0000573 | GeoSetter | Image Data | public | 2010-06-03 14:47 | 2010-07-16 01:40 |
| Reporter | lifelion | Assigned To | Friedemann | ||
| Priority | normal | Severity | major | Reproducibility | always |
| Status | resolved | Resolution | fixed | ||
| Product Version | 3.3.48 Release | ||||
| Target Version | Fixed in Version | 3.3.54 beta | |||
| Summary | 0000573: NMEA GPRMC parsing mismatch | ||||
| Description | Hi, GeoSetter rocks! Thank you. I am exporting GPS logs from a Globalsat GH-625M. With a sentence like: $GPRMC,184826,A,4524.1164,N,1152.8414,E,1.62,,140809,,*38 Latitude is correctly parsed by GeoSetter as: 4524.1164,N which is the same 4524.11640,N The longitude is incorrectly parsed as: 1152.08414,E where is should be parsed as 1152.84140,E Maybe a spec would mention that a correct NMEA sentence must have exactly 5 digits after the period but the fact that only latitudes are correctly parsed seems to indicate a bug the GeoSetter parsing of longitudes. | ||||
| Additional Information | Log file incorrectly parsed: $GPRMC,184826,A,4524.1164,N,1152.8414,E,1.62,,140809,,*38 $GPRMC,184900,A,4524.11592,N,1152.81842,E,1.62,,140809,,*3F $GPRMC,184905,A,4524.11472,N,1152.8141,E,2.16,,140809,,*0E $GPRMC,184909,A,4524.11448,N,1152.81182,E,1.62,,140809,,*35 $GPRMC,184913,A,4524.11358,N,1152.80768,E,1.62,,140809,,*3B $GPRMC,184917,A,4524.11292,N,1152.8036,E,2.16,,140809,,*04 $GPRMC,184921,A,4524.11382,N,1152.80132,E,1.08,,140809,,*38 $GPRMC,184928,A,4524.1143,N,1152.80042,E,0.54,,140809,,*01 $GPRMC,184934,A,4524.1143,N,1152.79952,E,0.00,,140809,,*03 $GPRMC,184938,A,4524.1158,N,1152.7997,E,0.54,,140809,,*34 $GPRMC,184945,A,4524.11712,N,1152.79772,E,0.54,,140809,,*3B $GPRMC,184949,A,4524.11892,N,1152.79982,E,0.54,,140809,,*31 $GPRMC,184953,A,4524.12042,N,1152.80108,E,0.54,,140809,,*30 $GPRMC,185000,A,4524.1206,N,1152.79928,E,1.08,,140809,,*0A Log file correctly parsed: $GPRMC,184826,A,4524.11640,N,1152.84140,E,1.62,,140809,,*38 $GPRMC,184900,A,4524.11592,N,1152.81842,E,1.62,,140809,,*3F $GPRMC,184905,A,4524.11472,N,1152.81410,E,2.16,,140809,,*3E $GPRMC,184909,A,4524.11448,N,1152.81182,E,1.62,,140809,,*35 $GPRMC,184913,A,4524.11358,N,1152.80768,E,1.62,,140809,,*3B $GPRMC,184917,A,4524.11292,N,1152.80360,E,2.16,,140809,,*34 $GPRMC,184921,A,4524.11382,N,1152.80132,E,1.08,,140809,,*38 $GPRMC,184928,A,4524.11430,N,1152.80042,E,0.54,,140809,,*31 $GPRMC,184934,A,4524.11430,N,1152.79952,E,0.00,,140809,,*33 $GPRMC,184938,A,4524.11580,N,1152.79970,E,0.54,,140809,,*34 $GPRMC,184945,A,4524.11712,N,1152.79772,E,0.54,,140809,,*3B $GPRMC,184949,A,4524.11892,N,1152.79982,E,0.54,,140809,,*31 $GPRMC,184953,A,4524.12042,N,1152.80108,E,0.54,,140809,,*30 $GPRMC,185000,A,4524.12060,N,1152.79928,E,1.08,,140809,,*3A | ||||
| Tags | No tags attached. | ||||
|
|
I really don't remember why I have done it like this. Especially for the longitude, I've built in a special handling regarding the number of digits. Depending on the average digits count of longitude values in a track file, a 0 will be included if a longitude value have less digits than this average value :-/ I'm pretty sure that this was because of another user who had problems with his track file (in 2007), but I can't find any mails regarding this anymore. So I removed it now. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2010-06-03 14:47 | lifelion | New Issue | |
| 2010-06-05 19:19 | Friedemann | Status | new => assigned |
| 2010-06-05 19:19 | Friedemann | Assigned To | => Friedemann |
| 2010-07-16 01:40 | Friedemann | Note Added: 0001160 | |
| 2010-07-16 01:40 | Friedemann | Status | assigned => resolved |
| 2010-07-16 01:40 | Friedemann | Fixed in Version | => 3.4.51 beta |
| 2010-07-16 01:40 | Friedemann | Resolution | open => fixed |
