View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0002464 | GeoSetter | User Interface | public | 2023-01-27 13:55 | 2023-01-29 20:00 |
Reporter | WilfriedB | Assigned To | Friedemann | ||
Priority | low | Severity | trivial | Reproducibility | always |
Status | resolved | Resolution | fixed | ||
Platform | ThinkPad | OS | Windows 10 | OS Version | 22H2 Build 19045 |
Product Version | |||||
Target Version | Fixed in Version | 4.0.37 beta | |||
Summary | 0002464: Export to GPX-Track file ... not compatible to other application | ||||
Description | When using the menu option File->Export to GPX-Track file ... the resulting GPX 1.0 file cannot be read by at least one other application (RouteConverter), because the xmlns attribute is missing in the second line of GeoSetter's version. The first two lines of the GPX file produced by GeoSetter are: <?xml version="1.0" encoding="UTF-8"?> <gpx version="1.0" creator="GeoSetter - https://www.geosetter.de"> It can be read by RouteConverter (and probably other applications) by changing to: <?xml version="1.0" encoding="UTF-8"?> <gpx xmlns="http://www.topografix.com/GPX/1/0" version="1.0" creator="GeoSetter - https://www.geosetter.de"> -- Having said the above, I am wondering wether this functions should be better called "Export way points to GPX-file", since this is what it does: The coordinates of selected images (and only those) are exported as points to a track file. As far as I could see, GPX track files in the same folder are ignored for this function. Also it might more sense to create a way point list rather than tracks. However, I'm not sure how much this function in GeoSetter is used. So far, I never needed it- | ||||
Tags | No tags attached. | ||||
|
For my part, as my camera detects GPS coordinates, I found it interesting to create a track where I went using the functionality of GeoSetter. On the other hand, it would be good to modify the header of the file generated by GeoSetter as suggested by WilfriedB |
|
Comments I submitted in 2461: If in the file generated by GeoSetter, I modify the header, the file is readable by "RouteConverterWindows". On the other hand, if in GeoSetter, I transform certain points into "WayPoint", only these points are read in "RouteConverterWindows" |
|
Please see my comments under https://www.geosetter.de/mantis/view.php?id=2461#c4476 |
|
The same applies if a track which was initially correct, is changed (e.g. adding a way point) inside GeoSetter, saved and overwritten. The GPX file can be fixed as described and after that, I did not notice any difference besied the new way point. |
|
@WilfriedB You are absolutely right with your statement. Only waypoints are written to the GPX file. I have tried it. However, only the program RouteConverter seems to have a problem here. I have tested several other GPX programs (GPXSee, GPX Editor, GPS Track Editor), all open the file and show the waypoints. And also in Google Earth this file can be opened and displayed. However, RouteConverter seems to be basically very sensitive to file variations. I have also had problems with various CSV files with the RouteConverter. |
|
I changed the GPX header as suggested by @WilfriedB, thank you!!! :-) |
Date Modified | Username | Field | Change |
---|---|---|---|
2023-01-27 13:55 | WilfriedB | New Issue | |
2023-01-27 16:05 | xyzzy | Note Added: 0004463 | |
2023-01-27 21:33 | xyzzy | Note Added: 0004466 | |
2023-01-28 09:23 | WilfriedB | Note Added: 0004477 | |
2023-01-28 09:36 | WilfriedB | File Added: GeoSetter Save changed Track.jpg | |
2023-01-28 09:36 | WilfriedB | Note Added: 0004478 | |
2023-01-28 11:48 | roscoe | Note Added: 0004479 | |
2023-01-29 19:49 | Friedemann | Assigned To | => Friedemann |
2023-01-29 19:49 | Friedemann | Status | new => assigned |
2023-01-29 20:00 | Friedemann | Note Added: 0004488 | |
2023-01-29 20:00 | Friedemann | Note Edited: 0004488 | View Revisions |
2023-01-29 20:00 | Friedemann | Status | assigned => resolved |
2023-01-29 20:00 | Friedemann | Resolution | open => fixed |
2023-01-29 20:00 | Friedemann | Fixed in Version | => 4.0.37 beta |