View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0001392 | GeoSetter | Image Data | public | 2017-04-20 14:54 | 2020-04-22 00:27 |
| Reporter | Pascal | Assigned To | Friedemann | ||
| Priority | normal | Severity | feature | Reproducibility | always |
| Status | assigned | Resolution | open | ||
| Platform | OS | Windows | OS Version | 10 | |
| Product Version | 3.4.16 beta | ||||
| Target Version | Fixed in Version | ||||
| Summary | 0001392: Track log Nikon D5300 is not a valid GPS file | ||||
| Description | I use the track log dialog, to add the gps coordinates to a set of photos I made on a trip in the countryside. After selecting one of my track log files of my Nikon D5300, the result is: "The file [name.log] is not a valid track file". | ||||
| Additional Information | The file structure is (in notepad): @NikonD5300/ver1.01/wgs84 $GPGGA,065512.00,5220.3867,N,00447.7561,E,1,,,0.3,M,,,,*1A $GPRMC,065512.00,A,5220.3867,N,00447.7561,E,1.5,,100916,,,A*73 $GPGGA,065543.00,5220.3826,N,00447.7490,E,1,,,7.3,M,,,,*13 $GPRMC,065543.00,A,5220.3826,N,00447.7490,E,0.0,,100916,,,A*79 $GPGGA,065614.00,5220.3819,N,00447.7413,E,1,,,15.3,M,,,,*26 $GPRMC,065614.00,A,5220.3819,N,00447.7413,E,0.0,,100916,,,A*7F $GPGGA,065644.00,5220.3820,N,00447.7398,E,1,,,18.3,M,,,,*20 $GPRMC,065644.00,A,5220.3820,N,00447.7398,E,0.0,,100916,,,A*74 $GPGGA,065714.00,5220.3830,N,00447.7428,E,1,,,17.3,M,,,,*26 $GPRMC,065714.00,A,5220.3830,N,00447.7428,E,0.2,,100916,,,A*7F $GPGGA,065744.00,5220.3838,N,00447.7483,E,1,,,14.3,M,,,,*29 $GPRMC,065744.00,A,5220.3838,N,00447.7483,E,0.0,,100916,,,A*71 | ||||
| Tags | No tags attached. | ||||
|
|
N1609100.LOG (144,930 bytes) |
|
|
It seams, that the problem is the first line of the track. If I change this line with the first line of my tracks, then your track is working. This is the first line of my NMEA files: @Sonygps/ver1.0/wgs-84 |
|
|
I have track logs from an Olympus camera with the same issue not being recognized as a valid gps file. The work around is to change the .log extension to .nmea After changing the extension geosetter recognized, plotted the point accurately and easily applied coordinates when processed. This process is manageable for a couple of tracks, however for multiple track I use xcopy to create readable files. This can be done in via command prompt or by creating a batch file within the folder. Here is a sample of coordinates listed within the .log file which are basically nmea format. If they are plugged into any mapping app the location should be the Grand Isle. @Olympus/-0500/-0500 $GPGGA,152152.1,3657.6993,N,08608.0408,W,1,,,232.9,M,,M,,*7D $GPRMC,152152.1,A,3657.6993,N,08608.0408,W,,,071219,,*14 $GPGGA,152221.0,3657.7033,N,08608.0574,W,1,,,220.8,M,,M,,*71 $GPRMC,152221.0,A,3657.7033,N,08608.0574,W,,,071219,,*1A $GPGGA,152251.0,3657.7139,N,08608.0779,W,1,,,211.0,M,,M,,*78 $GPRMC,152251.0,A,3657.7139,N,08608.0779,W,,,071219,,*19 $GPGGA,152321.0,3657.7114,N,08608.0973,W,1,,,227.0,M,,M,,*70 $GPRMC,152321.0,A,3657.7114,N,08608.0973,W,,,071219,,*14 |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2017-04-20 14:54 | Pascal | New Issue | |
| 2017-04-20 14:54 | Pascal | File Added: N1609100.LOG | |
| 2017-04-23 15:00 | heiko | Note Added: 0002463 | |
| 2017-05-16 22:50 | Friedemann | Status | new => assigned |
| 2017-05-16 22:50 | Friedemann | Assigned To | => Friedemann |
| 2020-04-22 00:27 | homer4775 | Note Added: 0003809 |
