View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
2109 [GeoSetter] Image Data major always 2020-11-12 21:25 2020-11-13 14:31
Reporter: jng Platform:  
Assigned To: OS: Windows 10  
Priority: high OS Version:  
Status: new Product Version: 3.5  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Thumbnail contents are orientated wrong
Description: Thumbnail from Samsung Galaxy 7 are orientated correctly but content in the thumbnail are oriented wrong.
See 2020-11-12 21_18_19-GeoSetter.jpg
Selecting multiple pictures and "Edit data..." (Ctrl-E) open dialog where content are rotated correct
See 2020-11-12 21_19_07-Edit Data.jpg
Other programs such as acdsee and photofiltre do not have problem
Tags: Thumbnail orientation
Steps To Reproduce:
Additional Information:
Attached Files: 2020-11-12 21_19_07-Edit Data.jpg (67,778 bytes) 2020-11-12 21:25
https://geosetter.de/mantis/file_download.php?file_id=836&type=bug
2020-11-12 21_18_19-GeoSetter.jpg (59,032 bytes) 2020-11-12 21:25
https://geosetter.de/mantis/file_download.php?file_id=837&type=bug
9701122.jpg (4,916,104 bytes) 2020-11-12 21:25
https://geosetter.de/mantis/file_download.php?file_id=838&type=bug
2020-11-13 14_29_50-file_download.php (617×567).jpg (44,840 bytes) 2020-11-13 14:31
https://geosetter.de/mantis/file_download.php?file_id=839&type=bug
Notes
(0003840)
jng   
2020-11-13 14:31   
One more info - the preview below thumbnails also correct


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
2108 [GeoSetter] User Interface minor always 2020-10-30 13:43 2020-11-04 16:47
Reporter: AlexPiLion Platform: Product ver 3.5.3  
Assigned To: OS: Windows 7  
Priority: low OS Version: 64bit  
Status: new Product Version: 3.5.1  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Corrupted data warning on every RAW .CR2 coming from EOS M6 Camera.
Description: The software under exif info report a false alert : Warning "Possibily Corrupted CanonCustom2 data"
Tags:
Steps To Reproduce: open the program, click on any .CR2 file shot with EOS M6
Additional Information: I am not able to upload here since size is about 31.7 Mb and it exceeds the limit, you can download a sample image at https://1drv.ms/u/s!AqXe7j8OFQini-gFoz0IF6grAzwW5Q?e=mJruwE
Attached Files: Cattura2.PNG (348,729 bytes) 2020-10-30 13:43
https://geosetter.de/mantis/file_download.php?file_id=835&type=bug
Notes
(0003838)
heiko   
2020-11-04 16:32   
GeoSetter is using ExifTool for writing exif data and the warning is from ExifTool. I think you have better chances in the ExifTool forum (www.exiftool.org)
(0003839)
heiko   
2020-11-04 16:47   
I've just opened the image with ExifTool.exe. ExifTool reports the following:
[minor] Missing 2 entries in CanonCustom2 group 4 directory

As I said before, ask this in the ExifTool forum.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
2107 [GeoSetter] Image Data block always 2020-10-30 13:17 2020-10-30 13:17
Reporter: AlexPiLion Platform:  
Assigned To: OS:  
Priority: normal OS Version:  
Status: new Product Version: 3.5.1  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Ver 3.5.3 get error "for development use" on clicking Map tab
Description: The map is no more visible, this is likely an issue due to google API restriction which is no more free, maybe it could be replaced with OpenStreetMap API
Tags:
Steps To Reproduce: Open the program, wait for exif tool inizialization, select any image and click on Map tab.
Additional Information:
Attached Files: Cattura.PNG (334,847 bytes) 2020-10-30 13:17
https://geosetter.de/mantis/file_download.php?file_id=834&type=bug
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
2106 [GeoSetter] Image Data feature always 2020-10-11 10:48 2020-10-28 11:41
Reporter: Eric Platform:  
Assigned To: OS:  
Priority: normal OS Version:  
Status: new Product Version: 3.5.1  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: DCRawlib and support of newer camera RAW files. Libraw?
Description: Current Geosetter 3.5.3 is shipped with the dcrawlib.dll from 2016: it's actually the ImageEn dcraw plugin 9.17
Image preview from many (most?) camera more recent than that are not properly displayed (greenish) because the dcrawlib is too old.
Last version of dcraw is from 2018 but I don't find any lib version of it yet.
Thus, for instance, my Panasonic G80/G81 RW2 files are not displayed properly - greeenish, and so also from the older G6, even if both should be supported by dcraw from 2018.
Issue already reported here in 2014: https://geosetter.de/mantis/view.php?id=1140

Question 1: would it be possible to get latest dcraw version?
Question 2: longer term: how much effort would it be to use libraw instead of dcraw?
https://www.libraw.org/about seems indeed to be a better alternative to the stalled dcraw project, at is aims to generate a library.
Tags:
Steps To Reproduce:
Additional Information:
Attached Files:
Notes
(0003837)
Jacobliam1   
2020-10-28 11:41   
Taking assignment help for your homework from allassignmenthelp.com is completely legit and in fact also very resourceful. https://www.allassignmenthelp.com/programming-language-assignment-help.html


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
2092 [GeoSetter] User Interface feature N/A 2020-05-06 04:35 2020-09-15 22:28
Reporter: pistesil0 Platform:  
Assigned To: OS:  
Priority: normal OS Version:  
Status: new Product Version: 3.5.1  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Add sort tool
Description: Could you please add a tool that reorgnize a given folder (and its sub folders) using a user defined structure?
The tree folder structure would use EXIF properties (date, location, title,...) in order to name its folders, it would be very alike to the rename tool.
Txs in advance
Tags:
Steps To Reproduce:
Additional Information:
Attached Files:
Notes
(0003836)
heiko   
2020-09-15 22:28   
as far as I know you can do this with ExifTool.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
2099 [GeoSetter] Image Data trivial random 2020-08-03 08:39 2020-09-15 22:26
Reporter: ACon1289 Platform:  
Assigned To: OS:  
Priority: immediate OS Version:  
Status: new Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Error with geotagging the images
Description: Some images gets geotagged with the same location. It is not geotagging correctly. It is missing out on the geotags randomly. Every time the GPS files gets synced differently with the images.
Tags:
Steps To Reproduce:
Additional Information:
Attached Files: Erro.PNG (3,662 bytes) 2020-08-03 08:39
https://geosetter.de/mantis/file_download.php?file_id=832&type=bug
image.png (175,149 bytes) 2020-08-03 08:39
https://geosetter.de/mantis/file_download.php?file_id=833&type=bug
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
2101 [GeoSetter] User Interface major always 2020-08-30 15:09 2020-09-15 22:15
Reporter: Lindi Platform:  
Assigned To: OS:  
Priority: normal OS Version:  
Status: new Product Version: 3.5.1  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Error in reading GPX data
Description: My tracker records the GPXdata with waypoints for pauses and trackdata for the tracks.
geosetter can't read the norm conform GPX data.
An example where i skipped a lot of WPTs and trks for better reading:
<?xml version="1.0" encoding="UTF-8"?>
<gpx xmlns="http://www.topografix.com/GPX/1/1" version="1.1" creator="http://gpxframework.com">
    <metadata>
        <name>270720_11:15:52.gz</name>
        <bounds minlat="64.141342" minlon="-21.951132" maxlat="64.153488" maxlon="-21.912024">
        </bounds>
        <extensions>
            <gpxdata:nt>10747</gpxdata:nt>
            <gpxdata:at>27311</gpxdata:at>
        </extensions>
    </metadata>
    <wpt lat="64.144096" lon="-21.917263">
        <ele>0.000000</ele>
        <time>2020-07-27T11:16:11Z</time>
        <cmt>00:04:15</cmt>
        <type>pause</type>
        <extensions>
            <gpxdata:nt>25</gpxdata:nt>
        </extensions>
    </wpt>
    <trk>
        <trkseg>
            <trkpt lat="64.144287" lon="-21.916977">
                <ele>25.763964</ele>
                <time>2020-07-27T11:16:08Z</time>
            </trkpt>

            <trkpt lat="64.145760" lon="-21.925636">
                <ele>13.942226</ele>
                <time>2020-07-27T18:41:06Z</time>
            </trkpt>
            <trkpt lat="64.145866" lon="-21.925543">
                <ele>13.759905</ele>
                <time>2020-07-27T18:49:08Z</time>
            </trkpt>
            <trkpt lat="64.145859" lon="-21.925539">
                <ele>13.683279</ele>
                <time>2020-07-27T18:49:09Z</time>
            </trkpt>
            <trkpt lat="64.145859" lon="-21.925541">
                <ele>13.683279</ele>
                <time>2020-07-27T18:49:10Z</time>
            </trkpt>
        </trkseg>
    </trk>
</gpx>
Tags: GPS trace
Steps To Reproduce: open tracks (ctrl+T)

Error Message:
270720.gpx - Ohne Namen 1 (0Punkte)
Reference to undeclared namespace prfix: 'gpxdata'.

Linie: 8 <gpxdat:nt)10747</gpxdata:nt>
Additional Information:
Attached Files:
Notes
(0003835)
heiko   
2020-09-15 22:13   
if I delete the data between
<extensions>
..
</extensions>
then the GPX file works. I don't know how often you have delete this data. In your example it was 2x.
Perhaps you can convert your file with GPSBabel


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
2093 [GeoSetter] Image Data major always 2020-05-12 05:12 2020-09-14 20:00
Reporter: exifeverywhere Platform:  
Assigned To: OS:  
Priority: high OS Version:  
Status: new Product Version: 3.5  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Getting message 'not found'
Description: Hello,

All of a sudden, i started seeing this message: https://www.screencast.com/t/RxjYjwzuX40

The tool was fine till yesterday.

Please advise.

Thanks!
Tags: Google API, not found
Steps To Reproduce:
Additional Information:
Attached Files: Meldung1.jpg (20,391 bytes) 2020-05-22 12:00
https://geosetter.de/mantis/file_download.php?file_id=828&type=bug
Meldung.jpg (10,746 bytes) 2020-05-22 12:00
https://geosetter.de/mantis/file_download.php?file_id=829&type=bug
Notes
(0003811)
bselbmann   
2020-05-16 02:03   
I have exact the same problem
(0003814)
roscoe   
2020-05-22 12:00   
Habe das gleiche Problem mit unterschiedlichen Meldungen, siehe Bilder
(0003817)
wanneslier   
2020-05-25 22:58   
Same problem since today May 25th
Also cannot update exiftool - says to check internet connection, which is perfectly sound.
(0003818)
wanneslier   
2020-05-25 23:35   
I just noticed I got a message from "smartscreen" (microsoft check on installation) that it cannot be reached.
Maybe there is a connection?
(0003820)
johanvranken   
2020-06-01 12:21   
Sometimes it works, sometimes it doesn't. I fear it has to do with a maximum number of calls to geonames.org as that seems to be the website used to find locations.
(0003821)
antipaxos   
2020-06-02 17:28   
same here: just intalled (and actullay worked like a charm for 2 hours) then, all of a sudden it just started to stop finding any location
(0003822)
heiko   
2020-06-02 21:35   
as far as I know Friedemann has ristricted the ammount of search queries. Google charges money for these searches. To limit Google's bills, Friedemann has limited the number of searches in GeoSetter.
(0003824)
Slammer   
2020-06-15 11:50   
I have the same problem.
Have changed the mapfile from
http://www.geosetter.de/map_google.html
to
http://map.geosetter.de/v3/map_google.html
But with no effect.
BTW: Which one would be correct? Map display works with both :)
Thank you and kind regards
(0003825)
Kiko Benitez   
2020-07-21 23:14   
The same problem after reinstalling Windows 10 Pro Insider Preview.
(0003829)
martinzima   
2020-09-03 01:02   
Hi guys, I have been having this issue for several months -- is a shame, as otherwise I really love the app!
Is there any ETA of when this might be fixed?

Diagnostic info:
- Ran app as Administrator -- ? no effect
- changed map file http://www.geosetter.de/map_google.html <--> http://map.geosetter.de/v3/map_google.html -- ? no effect
- Added app to firewall allowed list -- ? no effect
- Registered for own Geonames login (so queries now pass through own account) -- ? no effect
- Changed internet settings IE proxy OFF <--> ON -- ? no effect
(0003833)
heiko   
2020-09-13 17:25   
@martinzima: these are not GeoNames queries, these are Google queries and Google charges money for these serches.
(0003834)
zava   
2020-09-14 20:00   
Hmm... several new issues... hardly any fix or improvements in the past some years... no new versions...
Sounds GS is a fading project?
Shame, because it is simply THE BEST tool in it's category: simply NO comparable tool (to my knowledge).
But these issues are eroding it's usability...
Resisting, but until when?


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
2104 [GeoSetter] User Interface block always 2020-09-06 22:39 2020-09-06 22:39
Reporter: zava Platform:  
Assigned To: OS:  
Priority: urgent OS Version:  
Status: new Product Version: 3.5.1  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Crashes ALWAYS as soon as a different folder is selected
Description: Hello,
this affects both V3.5,3 (build 2195) and V3.4.82 BETA (Build 2184)
Program starts OK. When you try to select a different folder, program ALWAYS crashes after a couple seconds.
It seems that
- crash happens opening a "lower level" folder (doesn't crash opening a higher level folder)
- crash happens if selected folder contains images

Opening an empty folder does not crash program.

No warning or error messages displayed.

Both versions have worked fine for years of flawless service, up until last usage a few weeks ago.
A major Windows 10 upgrade happened in between...
(Windows 10 Home, Ver. 2004, build 19041.450)
Tried restarting PC, reinstalling GS, still crashes.
Unfortunately this makes program fully unusable!

How can I fix/investigate?
Thank you!
Tags:
Steps To Reproduce: Select a lower level folder containing images.
Additional Information:
Attached Files:
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
2045 [GeoSetter] Image Data feature sometimes 2019-05-23 10:04 2020-09-04 16:57
Reporter: WuppiGER Platform:  
Assigned To: OS:  
Priority: normal OS Version:  
Status: new Product Version: 3.5  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: GPR-Support (GoPro RAW)
Description: GPR wird von Exiftool unterstützt (r/w; ist eine DNG-Variante). Lightroom genauso. Geosetter unterstützt hier nur das schreiben von Sidecard-Dateien. Das führt dann leider zu Problemen mit LR.

Feature-Request:
* GPR-Einbindung in Geosetter
* Möglichkeit des schreibens in die Originaldatei (wie bei CR2, JPG)
Tags:
Steps To Reproduce: LR wertet die embedded Daten höher als die im XMP. Folge: ich setze mit LR das Land -> LR schreibt in das GPR. Für die Details möchte ich nun Geosetter nehmen. Ich schreiben die Örtlichkeit rein, lösche die Beschreibung (bei GoProbilder hat man immer den Dateinamen in der Beschreibung) etc. Wenn ich in Geosetter jetzt auf Aktualisieren drücke => Mission erfolgreich.

In LR lade ich die Bilder neu ein. Folge: das XMP wird ignoriert.

Wenn ich jetzt Exiftool-GUI öffne und das GPR von seinen Metadaten befreie und nur noch ein vollständiges XMP habe -> wird alles in LR übernommen. Dann schreibe ich in LR die Metadaten und könnte theoretisch die GPRs löschen (leider nur Theoretisch; die Zeitzonen-Einstellung liest LR leider nicht aus den XMPs - somit auch kein Übertrag ins GPR möglich; Workaround: händisch ins GPR schreiben via LR...)

Additional Information:
Attached Files:
Notes
(0003831)
WuppiGER   
2020-09-04 16:57   
GPR ist quasi ein umbenanntes DNG. Wenn ich meine GPRs in DNG umbenenne, kann Geosetter Problem damit arbeiten (also auch direkt beschreiben, ohne .xmp!). Mal so als Workaround. Für GeoSetter könnte das heißen das zu DNG einfach GPR hinzugefügt werden könnte


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
2096 [GeoSetter] User Interface crash random 2020-06-03 15:43 2020-09-03 17:31
Reporter: Erik Bachmann Platform:  
Assigned To: OS: Windows  
Priority: high OS Version: 10  
Status: new Product Version: 3.5.1  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Crashes reguarly while saving data for multiple images [v.3.5.3 (2195)]
Description: Crashes
Starting up with "Collection mode Activated" to continue - and crashes againg
Tags:
Steps To Reproduce:
Additional Information:
Attached Files:
Notes
(0003827)
Malcolm_Ferguson   
2020-08-31 15:41   
Any chance you have RAW files with JPEG sidecars? I have to set Geosetter to filter by viewing by either "not RAW" or "RAW only". It looks like there is a race condition when it tries to write the same XMP for both files.
(0003830)
Erik Bachmann   
2020-09-03 17:31   
Nope! Plain simple JPG's without sidecar

BUT taking a closer look at the bug report:

exception message : Datei "C:\bin\GeoSetter\queue\20200903-170429868.que" kann nicht erstellt werden. Processen kan ikke få adgang til filen, da den bruges af en anden proces.
(The process cannot access the file because it is used by another process.=

And that "other process" appeared to be: Dropbox!

Lesson: Don't EVER close a temp que file and allow others to lock you out of your own files!


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
2103 [GeoSetter] User Interface major always 2020-09-03 15:44 2020-09-03 15:44
Reporter: georoom Platform:  
Assigned To: OS:  
Priority: high OS Version:  
Status: new Product Version: 3.5  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Karte wird nicht mehr angezeigt: ERROR: Der Vorgang konnte aufgrund des folgenden Fehlers nicht fortgesetzt werden: 80020101
Description: Keine Kartenansicht mehr möglich, direkt nach Verzeichnis mit Bildern, die GEO-Infos enthalten wird obiges Fehlerprotokoll angezeigt.
Version 3.5.3 Build 2195

Beispiel-DNG kann leider nicht hochgeladen werden, da > 10 MB
Tags: DNG, exif, Google API, gps, RAW
Steps To Reproduce: Verzeichnis mit Bildern, die Geo-Koordinaten enthalten, anzeigen.
Additional Information: Windows 10 Pro 64 Bit
Version 2004
Build 19041.450

03.09.2020 15:28:08 ERROR: Der Vorgang konnte aufgrund des folgenden Fehlers nicht fortgesetzt werden: 80020101
  showFocusMarker(49.4131888889, 8.7137777778, 94, true, 49.4135451015, 8.7133572456, 49.4133976619, 8.7131665109, 49.4136269687, 8.7136253940, true);
03.09.2020 15:28:16 ERROR: Der Vorgang konnte aufgrund des folgenden Fehlers nicht fortgesetzt werden: 80020101
  showFocusMarker(49.4131888889, 8.7137777778, 94, true, 49.4135451015, 8.7133572456, 49.4133976619, 8.7131665109, 49.4136269687, 8.7136253940, true);
03.09.2020 15:28:54 ERROR: Der Vorgang konnte aufgrund des folgenden Fehlers nicht fortgesetzt werden: 80020101
  showFocusMarker(49.4131888889, 8.7137777778, 94, true, 49.4135451015, 8.7133572456, 49.4133976619, 8.7131665109, 49.4136269687, 8.7136253940, true);
03.09.2020 15:28:57 ERROR: Der Vorgang konnte aufgrund des folgenden Fehlers nicht fortgesetzt werden: 80020101
  showFocusMarker(49.4131888889, 8.7137777778, 94, true, 49.4135451015, 8.7133572456, 49.4133976619, 8.7131665109, 49.4136269687, 8.7136253940, true);
03.09.2020 15:29:05 ERROR: Der Vorgang konnte aufgrund des folgenden Fehlers nicht fortgesetzt werden: 80020101
  showFocusMarker(49.4131888889, 8.7137777778, 94, true, 49.4135451015, 8.7133572456, 49.4133976619, 8.7131665109, 49.4136269687, 8.7136253940, true);
Attached Files:
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
2094 [GeoSetter] User Interface minor always 2020-05-25 10:15 2020-08-31 15:45
Reporter: watsonm Platform:  
Assigned To: OS:  
Priority: normal OS Version:  
Status: new Product Version: 3.5  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: For UK images, state/province displayed as England rathan the county (somerset, dorset etc.)
Description: Hi,
I am using version 3.5.3 in the UK and have issues with the results of the
get image from web.

The state/Province is marked as England rather than Somerset (the county).
I cannot find anywhere to set where it can pick up the county.

I thought this used to work OK in a previous release so wonder if I have
corrupted a setting.

Thanks for any help
Tags: County, Province, State, UK
Steps To Reproduce: set a place in UK for any image and get location.
Additional Information:
Attached Files:
Notes
(0003828)
Malcolm_Ferguson   
2020-08-31 15:45   
It's never worked for me :( Now I've got my own system because of this where I put the county or unitary authority (e.g. City of Bristol or London) in the State/Province (and in these examples, just "Bristol" or the London Borough in the city field.) I developed this system long before Lightroom added its map module, so now I can't get along with that either (plus the whole 3 letter vs. 2 letter country code thing).

The other annoyance is the frequent reversal of city and sublocation.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
2070 [GeoSetter] User Interface minor N/A 2019-12-07 06:43 2020-08-31 14:27
Reporter: StarGeek Platform:  
Assigned To: OS:  
Priority: normal OS Version:  
Status: new Product Version: 3.5.1  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Exiftool web address change
Description: I'm assuming you use the "ver.txt" file at http://owl.phy.queensu.ca/~phil/exiftool/ver.txt to check for updates to exiftool. Exiftool has now moved to exiftool.org and the "ver.txt" file is located https://exiftool.org/ver.txt

Phil will be retiring soon and the queensu.ca address will no longer work around April 2020.
Tags:
Steps To Reproduce:
Additional Information:
Attached Files: Immagine.png (27,593 bytes) 2020-05-21 21:03
https://geosetter.de/mantis/file_download.php?file_id=827&type=bug
Notes
(0003792)
DannyOsh   
2020-02-17 01:06   
I assume this is why Geosetter will no longer update Exif tool?
(0003801)
othmarmarti   
2020-04-10 12:36   
I can confirm that the lookup of new exiftool versions does not work because the website changed name. Is there a config file where I could update the name of the server. What works is to click on the exiftool website link. This is automatically forwarded to the correct site. And there you can manually download the new version and copy it into the folder specified in the update dialog.

Great Program! But the world keeps on moving.....
(0003802)
othmarmarti   
2020-04-10 12:36   
Short update: applies to 3.5.3
(0003812)
bselbmann   
2020-05-16 02:22   
is it possible to patch the new path myself or is the link hard coded?
(0003813)
Davide   
2020-05-21 21:03   
I have this problem
(0003815)
roscoe   
2020-05-22 12:03   
Same Problem with 3.5.3
(0003826)
othmarmarti   
2020-08-31 14:27   
I was browsing through the geosetter exe file. I found three plases where the old wrong address is hardcoded in version 3.5.3

https://owl.phy.queensu.ca/~phil/exiftool/rss.xml
Location: 6361408 Decimal
new equivalent string:
https://exiftool.org/rss.xml

http://www.sno.phy.queensu.ca/~phil/exiftool/
Location: 11072990 Decimal
new equivalent string:
https://exiftool.org/

http://www.sno.phy.queensu.ca/~phil/exiftool/
Location: 11178182 Decimal
new equivalent string:
https://exiftool.org/

It would be really nice if you could publish an updated 3.5.3 wit just these three strings replaced.

Thank you very much

Othmar Marti


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
2100 [GeoSetter] Image Data trivial have not tried 2020-08-29 15:07 2020-08-29 15:10
Reporter: Rani Platform:  
Assigned To: OS:  
Priority: normal OS Version:  
Status: new Product Version: 3.5.1  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Couple of questions
Description: Hi.

Just started using your great software. I'm geotagging my photos for website SEO purposes and would like to ask a couple of questions, please

1- In the GPS timestamp it's showing "30-Dec-99, 10:00:00 AM". What is that and can I get it to copy that timestamp from "photo taken"?
2- I have a lot of photos that I'd like to geotag, is it possible to make lots of Favourites and get the software to randomize locations for all photos I need tagged instead of manually tagging one by one?

Look forward to your reply
Thank you
Tags:
Steps To Reproduce:
Additional Information:
Attached Files:
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
2097 [GeoSetter] User Interface feature always 2020-06-09 13:53 2020-06-09 13:53
Reporter: roscoe Platform:  
Assigned To: OS:  
Priority: normal OS Version:  
Status: new Product Version: 3.5.1  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: open png file
Description: Suffering cannot open PNG files. Please add support for this file format.
Thank you
Tags: file formats
Steps To Reproduce:
Additional Information:
Attached Files:
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
2095 [GeoSetter] User Interface block always 2020-05-26 13:30 2020-06-02 21:38
Reporter: johanvranken Platform:  
Assigned To: OS: Windows 10  
Priority: urgent OS Version:  
Status: new Product Version: 3.5.1  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: No answer any more searching for places in maps
Description: See also issue 0002093: Getting message 'not found'

https://developers.google.com/maps/documentation/javascript/browsersupport?hl=en
Notice: Support for Internet Explorer 10 will end between November 2019 and May 2020 depending on the release channel or version number you use.

I think the API Geosetter is using, is not supported any more by google maps javascript.
I will try to go back to a previous version of the API but as I am not literate in javascript or google chrome, I don't know if I will be able to do so ...

Tags:
Steps To Reproduce: In the Search field under the map type any well known place (eg Berlin)
Answer is 'Berlin' not found
Additional Information:
Attached Files:
Notes
(0003819)
johanvranken   
2020-06-01 12:20   
Sometimes it works, sometimes it doesn't. I fear it has to do with a maximum number of calls to geonames.org as that seems to be the website used to find locations.
(0003823)
heiko   
2020-06-02 21:38   
as far as I know Friedemann has ristricted the ammount of search queries. Google charges money for these searches. To limit Google's bills, Friedemann has limited the number of searches in GeoSetter.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
2090 [GeoSetter] User Interface block always 2020-05-04 12:01 2020-05-23 16:26
Reporter: Laffer Platform:  
Assigned To: OS:  
Priority: immediate OS Version:  
Status: new Product Version: 3.5.1  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: 3.5.3 Google Map not displaying
Description: Die URL http://map.geosetter.de/v3/map_google.html zeigt keine Karte.

Fehlermeldung in GeoSetter

Die Karte wurde nicht gefunden unter:

http://map.geosetter.de/v3/map_google.html

Bitte geben Sie in den Einstellungen den korrekten Pfad zur Kartendatei an...

Dieses Problem kann auch folgende Ursachen haben:

•Der Microsoft Internet Explorer ist nicht korrekt installiert
•Die Sicherheitseinstellungen des Microsoft Internet Explorers verhindern die Ausführung aktiver Skriptinhalte
•Proxy Server (bitte dies auch in den Programmeinstellungen von GeoSetter berücksichtigen)
•Eine Firewall blockiert den Zugriff von GeoSetter
Tags:
Steps To Reproduce: Die URL http://map.geosetter.de/v3/map_google.html zeigt keine Karte.

Fehlermeldung in GeoSetter

Die Karte wurde nicht gefunden unter:

http://map.geosetter.de/v3/map_google.html

Bitte geben Sie in den Einstellungen den korrekten Pfad zur Kartendatei an...

Dieses Problem kann auch folgende Ursachen haben:

•Der Microsoft Internet Explorer ist nicht korrekt installiert
•Die Sicherheitseinstellungen des Microsoft Internet Explorers verhindern die Ausführung aktiver Skriptinhalte
•Proxy Server (bitte dies auch in den Programmeinstellungen von GeoSetter berücksichtigen)
•Eine Firewall blockiert den Zugriff von GeoSetter
Additional Information:
Attached Files:
Notes
(0003810)
Laffer   
2020-05-04 12:04   
Problem hat sich erledigt. Jetzt geht es wieder. Kann nicht nachvollzogen werden...
(0003816)
c196948   
2020-05-23 16:26   
Bei mir tritt genau dasselbe Problem auf.
Die W10-Meldung
    "Der Administrator hat festgelegt, dass diese Netzwerkverbindung von Windows-Sicherheit blockiert wird",
ist nicht hilfreich, weil ich nicht weiss, welche W10-Einstellung die Blockierung verursacht.
Eine Internet-Suche hat auch nichts passendes ergeben.
Im IE 11 wird die Seite auf http://map.geosetter.de/v3/map_google.html umgeleitet und es kommt die Meldung
    "HTTP 403 Verboten: Die Website hat die Anzeige dieser Webseite abgelehnt".
Ich verwende W10 1909.
Hat jemand einen Tipp?


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
2091 [GeoSetter] User Interface block always 2020-05-04 17:40 2020-05-04 17:40
Reporter: MadGrin Platform: Windows 10  
Assigned To: OS:  
Priority: urgent OS Version:  
Status: new Product Version: 3.5.1  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: By opening the MAP tab the program freezes
Description: As soon as you click on the MAP tab, the program freezes.
I have tried with different map files like http://map.geosetter.de/v3/map_google.html but without success
Tags:
Steps To Reproduce:
Additional Information:
Attached Files:
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
2089 [GeoSetter] Image Data major always 2020-04-29 10:41 2020-04-29 10:41
Reporter: matteo.manfredini Platform:  
Assigned To: OS: Windows 7  
Priority: high OS Version: Service pack 7  
Status: new Product Version: 3.5  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Map can't be found
Description: Today I had a problem with GeoSetter, it doesn't download the map to which to connect the photo.
In attached the issue message.
 
I checked the solutions that you give, but I couldn't solve the problem.

Are there any communication problems with your server?
Are there other firewall rules to put beyond allowing to connect to "http://geosetter.de" ?
Tags:
Steps To Reproduce:
Additional Information: geosetter version: 3.5.3. Build 2195
Attached Files: 11.png (42,110 bytes) 2020-04-29 10:41
https://geosetter.de/mantis/file_download.php?file_id=826&type=bug
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
2088 [GeoSetter] User Interface feature always 2020-04-22 00:57 2020-04-22 00:57
Reporter: homer4775 Platform: PC  
Assigned To: OS: Windows  
Priority: normal OS Version: 10  
Status: new Product Version: 3.5.1  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Olympus .log file support
Description: Geosetter cannot read olympus location files in their original format. Please consider adding an Olympus (.log) file extension to the dropdown selection for tracks. My current work around is to change the file extension to .nmea. Geosetter reads the file perfectly after the extension change.
Tags: file formats
Steps To Reproduce: Basically change the file extension to *.nmea and geosetter reads the track perfectly!
Additional Information: Geosetter v3.5.3 build 2195. This is a similar request as issue 0001392
Attached Files: 19120701.LOG (502 bytes) 2020-04-22 00:57
https://geosetter.de/mantis/file_download.php?file_id=825&type=bug
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
1392 [GeoSetter] Image Data feature always 2017-04-20 14:54 2020-04-22 00:27
Reporter: Pascal Platform:  
Assigned To: Friedemann OS: Windows  
Priority: normal OS Version: 10  
Status: assigned Product Version: 3.4.16 beta  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: 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".
Tags:
Steps To Reproduce:
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
Attached Files: N1609100.LOG (144,930 bytes) 2017-04-20 14:54
https://geosetter.de/mantis/file_download.php?file_id=466&type=bug
Notes
(0002463)
heiko   
2017-04-23 15:00   
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
(0003809)
homer4775   
2020-04-22 00:27   
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


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
2087 [GeoSetter] User Interface minor always 2020-04-09 06:32 2020-04-21 07:55
Reporter: Malcolm_Ferguson Platform:  
Assigned To: OS:  
Priority: normal OS Version:  
Status: new Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Error getting timezone info
Description: I get an error when trying to retrieve timezone information from the web for coordinates in Tomsk.
Tags:
Steps To Reproduce: 1) Select an image with coordinates such as:
56°28'58.3882" N 84°57'13.7064" E
Lat: 56.48288561 / Long: 84.95380732

2) Hit Ctrl+E to edit data and select the date tab

3) In the "Timezone" box, hit the "Get From Web" button

=> See the error
Additional Information: I have to manually choose the "(UTC +07:00) Asia / Novosibirsk" timezone, although this is just an approximation that is currently the same.
Attached Files: Tomsk timezone error.png (317,717 bytes) 2020-04-09 06:32
https://geosetter.de/mantis/file_download.php?file_id=822&type=bug
Tomsk Timezone Error-2.png (275,254 bytes) 2020-04-19 15:57
https://geosetter.de/mantis/file_download.php?file_id=823&type=bug
europe (176,194 bytes) 2020-04-20 22:33
https://geosetter.de/mantis/file_download.php?file_id=824&type=bug
Notes
(0003800)
heiko   
2020-04-09 20:23   
is this a permanent problem? I've just tried it and all works without problems.
(0003803)
heiko   
2020-04-16 23:44   
does the problem still exists? or can I close this issue?
(0003806)
Malcolm_Ferguson   
2020-04-19 15:57   
Yes, it's still a problem. I'm attaching another screenshot after reproducing it a moment ago.
(0003807)
heiko   
2020-04-20 22:33   
with the coordinates of your image I can reproduce this error. With the following api call

http://api.geonames.org/timezone?lat=56.485325&lng=84.945053&username=geosetter&style=full

you get the following timezone data from geonames:

<geonames>
<timezone tzversion="tzdata2019c">
<countryCode>RU</countryCode>
<countryName>Russia</countryName>
<lat>56.485325</lat>
<lng>84.945053</lng>
<timezoneId>Asia/Tomsk</timezoneId>
<dstOffset>7.0</dstOffset>
<gmtOffset>7.0</gmtOffset>
<rawOffset>7.0</rawOffset>
<time>2020-04-21 03:15</time>
<sunrise>2020-04-21 05:59</sunrise>
<sunset>2020-04-21 20:39</sunset>
</timezone>
</geonames>

There you see that the timezoneId is "Asia/Tomsk" and this entry is not available in the timezone database which is used from GeoSetter. If I downlaod the latest version of this database and copy it in the GeoSetter directory all works fine for me, but I don't know if this actual database will work without problems.

If you want to try this goto the directory "%ProgramFiles(x86)%\GeoSetter\tzdata" and make a backup of the file "europe". Then copy the file "europe" from the attachment into this directory. But as I said, I don't know if there will be any other problems if you do this.

@Friedemann: Perhaps you should update the tzdata database in the next release
(0003808)
Malcolm_Ferguson   
2020-04-21 07:55   
There's some fascinating history in that file :) This appears to resolve this issue for me and I will attempt to use the file going forward. Given the frequency of timezone data updates my Garmin watch recieves, it might indeed be a good idea to update this data in Geosetter.

Thanks for help resolving this.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
2076 [GeoSetter] Image Data major always 2020-01-19 23:18 2020-04-17 16:02
Reporter: ceroni Platform: Microsoft  
Assigned To: OS: Windows  
Priority: high OS Version: 10 pro  
Status: new Product Version: 3.5.1  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Cannot display DNG from Samsung Galaxy S9
Description: See attached image showing a JPG (left) and a DNG (right) from the same device.
Tags:
Steps To Reproduce:
Additional Information:
System Description
Attached Files: 190535.jpg (15,448 bytes) 2020-01-19 23:18
https://geosetter.de/mantis/file_download.php?file_id=812&type=bug
192910.jpg (20,180 bytes) 2020-01-19 23:37
https://geosetter.de/mantis/file_download.php?file_id=813&type=bug
Notes
(0003779)
ceroni   
2020-01-19 23:37   
Additional information: an original DNG straight from the device (left) is perfectly viewable after conversion using Adobe DNG converter 12.1 (right).
(0003805)
ceroni   
2020-04-17 16:02   
Workaround:
I'm using Adobe DNG converter to get much smaller and compatible files that Geosetter can handle without a glitch.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
2079 [GeoSetter] Image Data major always 2020-02-16 21:20 2020-04-16 23:46
Reporter: tohis Platform:  
Assigned To: OS:  
Priority: normal OS Version:  
Status: new Product Version: 3.5.1  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Can't save files having umlaut characters in name
Description: I built a new PC with UK-English Windows 10, and installed Geosetter 3.5.3 (portable) into it. When I try to geotag and save any image which has non-English characters in its name (Å, Ä, Ö for example), I get "Warning: Error opening file" and "Error: File not found" and the image will not be saved. See the attached image.

In thumbnails window the file names with umlauts are shown correctly, but in the error report these are shown as a tilted square with ? inside. Also, in some places the degree symbol ° (Alt-248) is shown as ? as well.

I have set the Windows locale to Finland, and the chcp command in cmd.exe shows the code page is 850 like expected.

I found the IPTC setting and tried ISO-8859-1 and UTF-8 instead of default ANSI, but this seems not to have effect on this issue.

For years I used Windows 7 and an older Geosetter 3.3.48 without this issue. I tried that old version again, but it's having the same issue in Windows 10. I also tried the newest Geosetter in a virtual Windows 7 in VirtualBox, and the issue was not present there.

So it may as well be a Windows 10 issue, however I haven't seen this kind of problem in any of my other programs (and some of them are very old).

There is a workaround by geotagging the images before renaming them with any non-English characters.
Tags:
Steps To Reproduce: Have two image files named test_AO.jpg and test_ÄÖ.jpg, and (optionally) a GPS data file containing the location for them. Select the images in Geosetter and press Ctrl-G to attach location data (or enter it manually), and then try to save the images. test_AO.jpg will be saved, but test_ÄÖ.jpg produces the error and will not be saved.
Additional Information:
Attached Files: geosetter_problem.png (159,107 bytes) 2020-02-16 21:20
https://geosetter.de/mantis/file_download.php?file_id=818&type=bug
IPTC-Character-Coding.png (33,534 bytes) 2020-02-18 23:02
https://geosetter.de/mantis/file_download.php?file_id=820&type=bug
Notes
(0003797)
heiko   
2020-02-18 23:02   
I'm also using Win10 and have no problems to save files which have umlauts in the filename. You can see my settings for the "IPTC Character Coding" in the attached screenshot.
(0003804)
heiko   
2020-04-16 23:46   
does this work for you? can I close this issue?


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
2086 [GeoSetter] Image Data major sometimes 2020-04-01 23:46 2020-04-03 22:11
Reporter: EnronHubbard Platform:  
Assigned To: OS: Windows  
Priority: high OS Version: 10  
Status: new Product Version: 3.5.1  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: viewing another program causes loss of data, resort
Description: Viewing a file in the image or GPX folder that GeoSetter is using in another program causes GeoSetter to refresh the image thumbnails. In the process any unsaved changes are lost, and the thumbnails are sorted in an unpredictable way, mostly by name but with a few random photos at the end (mine were originally sorted by Taken Date). Sort by Taken Date remains selected in the menu even though it is not displaying properly. This is occurring in version is 3.5.3 (not available to select in drop-down). For me the other programs in question are XnView (photo editor) and g7towin (GPX file manager).
Tags:
Steps To Reproduce: It is triggered from g7towin upon first opening a gpx file after opening the program (any file, not necessarily one used for syncing by GeoSetter), but not opening subsequent ones. I haven't figured out precisely what triggers it from XnView; it was full-screen and I found the files re-set when I went back to GeoSetter. Simply opening and editing files doesn't do it though.
Additional Information:
Attached Files:
Notes
(0003799)
EnronHubbard   
2020-04-03 22:11   
Starting Google Earth also triggers this.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
2085 [GeoSetter] User Interface crash always 2020-03-20 10:43 2020-03-20 10:44
Reporter: jmtfjm Platform: windows 10  
Assigned To: OS: 64 bits  
Priority: normal OS Version: latest  
Status: new Product Version: 3.5  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Crash when try to load directory with a large gpx file
Description: Loading a gpx file containing above 20,000 wayponints the software crashes reporting not enough memory
Product 3.5.3
Tags:
Steps To Reproduce:
Additional Information:
Attached Files: image.png (1,469 bytes) 2020-03-20 10:43
https://geosetter.de/mantis/file_download.php?file_id=821&type=bug
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
2084 [GeoSetter] Image Data minor have not tried 2020-03-13 08:24 2020-03-13 08:24
Reporter: jmoliver Platform:  
Assigned To: OS:  
Priority: normal OS Version:  
Status: new Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Support Google-supported IPTC licensing fields
Description: Google recently announced support for certain XMP IPTC fields for licensing information. Already Geosetter supports some.

Here is an article which best explains it: https://searchengineland.com/google-adds-new-image-license-metadata-for-licensable-image-label-329522

Here are the Google IPTC fields:
https://developers.google.com/search/docs/data-types/image-license-metadata#iptc-photo-metadata
Tags:
Steps To Reproduce:
Additional Information:
Attached Files:
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
2083 [GeoSetter] User Interface tweak always 2020-02-22 23:42 2020-02-22 23:42
Reporter: Suedlicht Platform:  
Assigned To: OS:  
Priority: normal OS Version:  
Status: new Product Version: 3.5.1  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Would like to zoom in more with OSM
Description: When switching between google maps and OSM, google maps allows to zoom in 2 more steps (in most towns, at least). This is a pity since google maps does not work properly at this time. Also, when I use OSM on the website https://www.openstreetmap.org, I can zoom in a bit more than in Geosetter. Work would be easier if we could have a bigger map also in OSM.
Thank you so much for your work, dear Friedemann, I know your good work since good old Exifer. I wish you all the best.
Tags: OSM, zoom
Steps To Reproduce:
Additional Information:
Attached Files:
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
2080 [GeoSetter] User Interface major always 2020-02-17 10:09 2020-02-20 15:23
Reporter: js111 Platform: Windows  
Assigned To: OS:  
Priority: normal OS Version: 10  
Status: new Product Version: 3.5.1  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Map not working with my own Google Maps API key
Description: The map does not load at all.
In the map log I get the error message : ERROR: OLE-Fehler 80020101
I've only just got my own Google Maps API key and I think I did everything as explained in the documentation to adjust the settings and map document. But it doesn't work for me.
I've updated Geosetter to 3.5.3 but that makes no difference.
My Internet Explorer is version 11
Any advice would be appreciated. This is a major showstopper for me.
By the way, my map document looks a bit different than that shown in the documentation. There is a script block before the meta tags. See attached file. I modified the map document using Coffeecup HTML editor.
Tags:
Steps To Reproduce: restart the app.
Additional Information:
Attached Files: map_with_my_api_key2.html (54,440 bytes) 2020-02-17 10:09
https://geosetter.de/mantis/file_download.php?file_id=819&type=bug
Notes
(0003795)
WilfriedB   
2020-02-17 12:20   
Geosetter only works with Internet Explorer Version 10 as explained here: https://geosetter.de/2018/05/10/geosetter-and-internet-explorer-de/
(0003798)
js111   
2020-02-20 15:23   
Thanks for your reply.
However, Geosetter has worked fine for me until two months ago, even without my own Google Maps API key. I haven't changed anything in my Internet Explorer version since then.
This would suggest that the problem may be with the configuration of my own Google Maps API key.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
1970 [GeoSetter] User Interface minor always 2018-09-07 20:50 2020-02-18 08:15
Reporter: othmarmarti Platform:  
Assigned To: Friedemann OS:  
Priority: normal OS Version:  
Status: assigned Product Version: 3.5  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Google claims that maps do not work
Description: On startup google issues a warning: maps not working properly. See geosetter1.png
Closing the alert and using openstreetmap everything seems to work properly.
Switching to google maps (any version) gives "for developmental purpses only" (see geosetter2.png)

Windows 10 build 1803 with all the updates
Tags:
Steps To Reproduce: Just start the program
Additional Information:
Attached Files: geosetter2.png (2,149,491 bytes) 2018-09-07 20:50
https://geosetter.de/mantis/file_download.php?file_id=722&type=bug
Geosetter1.png (1,323,106 bytes) 2018-09-07 20:50
https://geosetter.de/mantis/file_download.php?file_id=723&type=bug
HowTo-GeoSetter API.pdf (135,215 bytes) 2018-11-29 18:03
https://geosetter.de/mantis/file_download.php?file_id=739&type=bug
Geosetter.jpg (91,991 bytes) 2018-12-08 18:56
https://geosetter.de/mantis/file_download.php?file_id=747&type=bug
Geosetter Fehler Google-Karte.pdf (297,908 bytes) 2018-12-20 01:50
https://geosetter.de/mantis/file_download.php?file_id=753&type=bug
2018-12-24_074013.jpg (368,038 bytes) 2018-12-24 15:44
https://geosetter.de/mantis/file_download.php?file_id=754&type=bug
google api.PNG (39,256 bytes) 2018-12-31 23:58
https://geosetter.de/mantis/file_download.php?file_id=755&type=bug
geosetter-osm.png (553,815 bytes) 2019-04-11 21:24
https://geosetter.de/mantis/file_download.php?file_id=773&type=bug
geosetter.htm (59,431 bytes) 2019-04-11 21:24
https://geosetter.de/mantis/file_download.php?file_id=774&type=bug
HowTo-GeoSetter Google API.zip (120,120 bytes) 2020-02-07 18:10
https://geosetter.de/mantis/file_download.php?file_id=816&type=bug
grafik.png (26,586 bytes) 2020-02-14 18:47
https://geosetter.de/mantis/file_download.php?file_id=817&type=bug
Notes
(0003534)
Friedemann   
2018-09-07 21:01   
(Last edited: 2018-09-07 21:05)
Yes, that's a big problem! Unfortunately I received an invoice on Monday from Google for the map usage in August over about 250 Euro. Today I had a phone call with Google and I hoped they will maybe increase my free map load limit. But they won't. That's why I limited the daily map loads today from 25.000 to 1.000, which then will cost "only" About 80 Euros. I will write a blog entry on my web page in the next days. The only solution will be for the future, that every user have to register his own Google key. I will provide the map files then for download and the users can save them wherever they want and they have to fill in their private Google key. That's the only solution I see at the moment. Another solution will be to get something like a sponsering by someone ;-) For me myself it's by far too expensive to pay 250 or 300 Euro each months… I'm totally sorry About it!!!! :-(

(0003535)
Friedemann   
2018-09-07 21:06   
Additional info: Google changed their pricing model for Google Maps about 2 months ago. That's why it costs now and didn't for years...
(0003536)
Erik Krause   
2018-09-09 17:20   
Perhaps OSM and Bing could be an alternative. OSM could be enhanced a bit allowing to use the bicycle layer (which adds height lines and shaded terrain). Bing is used as a background layer by OSM editors. In fact those editors allow for a lot more imagery resources, like DigitalGlobe or Esri aerial images.
(0003537)
Friedemann   
2018-09-10 14:08   
> Perhaps OSM and Bing could be an alternative.

No, unfortunately not. OSM and Bing are offering Maps, but not a JavaSript API to handle these Maps, as Google do with their Google Maps JavaSript API. The only alternative I see is OpenLayers. But then I have to set up a map server for my own. And all the stuff for handling the map has to be recoded from scratch...
(0003539)
Erik Krause   
2018-09-10 20:51   
I guess you know already, but just in case:
http://geoawesomeness.com/google-maps-api-alternatives-best-cheap-affordable/
(0003545)
zava   
2018-09-20 22:40   
Fyi...
OSM is quite often better and more detaild than Google (especially in the remote areas where I am concerned, Google is often just a blank green swath, while OSM seems to report many more secondary paths).
The only reason why I am most often using a Google background is just that for some reason OSM background severely limits the max zoom leevel vs. Google (and this is, for my purpose, a major difference).
If the same zoom level could be displayed, I would most often use OSM as a background.

A kind of alternative solution (even better for some purposes) would be to be able to use georeferenced images as a background.
Although this does require some extra work and competence, it does allow a higer level of personalization.
I am using GS for a sistematic survey of WWI installation and I have a full coverage of historical maps from the military archives which I have digitized and referenced.

Needless to say, the Google maps would be a far more general solution for most users...

What about asking users to pay a small fee for using GS?
Depending on the user base, I suppose a small fee may be enough to cover a 300€ monthly fee to Google...

On the other hand, it would be a shame if GS would be doomed by Google's price policyt or by the lack of a suitable alternative...
Just ideas...

Hope a solutions does emerge after so much great work!
(0003546)
zava   
2018-09-21 11:07   
By the way, I would not dismiss this issue as "minor"...
The lack of a background map heavily impacts the program's effectiveness...
(0003547)
rau1   
2018-10-02 18:56   
I suggest to consider adding a subscription model for Geosetter to cover the costs. If every user pays a few €/year you should be able to cover the costs and subscribing users would see full Google maps again. I'd be happy to join this group. I love Geosetter since many years. I looked at a few alternative applications, but Geosetter is simply the best in terms of versatility and Map/route visualization.
(0003549)
DenisPac   
2018-10-08 18:50   
I would find more "fair" that each user uses his own API key to connect to Google Maps.
In such case each user would pay - or not - based on his own usage.
This will also allow a broader use of Geosetter, since there will be nothing to pay for a basic usage (as of today).
Thank you anyway for this great tool!
(0003550)
zava   
2018-10-08 19:11   
@DenisPac: I agree it would be more fair under several respects, yet we all know that each unfamiliar click required on the users will half the users' number!
How many will be willing to learn what an API is and how to get such key?
Paying a small fee is easy anf familiar, anybody can do it and also has the additional "fairness" that the whole program we like gets some reward, not just Google API...
Of course the choice is up to the developer, but it seems that the issue of having no map below our images is not being considered very important...while instead I think in the long term will undermine the users base.
Keep up this great work!
(0003551)
aacomm   
2018-10-09 16:57   
@zava e @DenisPac: sono d'accordo con tutte e due. Mi piacerebbe, se @Friedemann è d'accordo, di avere due possibilità: Geosetter completo di mappe pagando un corrispettivo e un Geosetter con l'uso di una propria chiave APi (che per un uso personale è praticamente gratuita). Nulla toglie che il progetto deve continuare e che è doveroso donare magari solo il costo di una birra o un caffè.
(0003557)
JoopvB   
2018-10-25 16:31   
How can I get my own API key from Google and apply it to GeoSetter to solve this problem. To bad to see a great program (and the developer :) to be the victim of changed pricing!
(0003571)
gessel   
2018-11-22 00:20   
My vote would be providing affordance for end-user Google Maps API keys and to preferentially use such a key, if available. Frequent users would likely jump through the hoops and would thus significantly lower the load on program key.
(0003572)
zava   
2018-11-22 11:21   
In fact, not much seems to be going on about this issue.
So it is not clear what is the case: is the issue considered non significant? (which I disagree, because having images georeferenced on... no map does seem to make GS somehow pointless); or is GS a dead/frozen project? (a big shame, given how good the program is!)
It may be a problem of financial support, but I am confident that users would be happy to participate a support policy if one was proposed.
Yet the long lasting silence over this issue does not seem promising...

I hope such great project is not dead!
(0003574)
gsommer   
2018-11-27 17:09   
I tried to download http://map.geosetter.de/v3/map_google.html and change the API-Key to my own, as suggested. But this workaround does not work, or I am missing something important. Could anybody give me a hint, how to do this correctly. Or do I need additional files?
(0003577)
Erik Krause   
2018-11-27 17:52   
gsommer, where did you get the suggestion to use a modified map_google.html? And how would you point geosetter to it?
(0003578)
Erik Krause   
2018-11-27 18:11   
Ok, I found it out: You need the source code of http://map.geosetter.de/v3/map_google.html Copy it in a new file and place it on your computer. Change the api key in the googlapis call (with a plain text editor of course). In geosetter go to File->Settings->Map->Map Address and Layers and under Map File insert the URL of the file like in a browser: f.e. file:///D:/my/path/to/map_google.html - with your particular drive letter and path of course.
(0003579)
RolfW   
2018-11-27 23:51   
To make Markers visible again add the following tag to the local map_google.html file after <meta> tags:
<base href="http://map.geosetter.de/v3/">

Nice solution Erik Krause. Everything works as aspected with personal API-Key and clear map.
(0003580)
gsommer   
2018-11-28 12:33   
Erik Krause, this is exactly, what I did, but the file is not accepted by GeoSetter. If I display the original online URL in the browser, I get a blank page. If I do the same with the changed local file, I get a display of HTML code. So something works completely different after editing the downloaded file. Maybe adding <base href="http://map.geosetter.de/v3/"> will make it work. I will try it, but doubt it.

I used Visual Studio Code to change the Key. I can try another editor maybe. Ah yes and the saved file has a different name. This could also be the problem (I will check it in the evening).
(0003581)
WilfriedB   
2018-11-28 14:11   
Also many thanks to Erik and Rolf!
In the beginning, I had some problems since GeoSetter wouln't recognize the modified file. Not sure, what exactly the problem was (saved in Firefox. extension .htm instead of .html, path names with embedded spaces ...?) After displayed the source code in a browser, select all, copy and paste into an empty text editor, changing the key adding a line according to Rolf's suggesting, saving in the root with extension .html and works fine now!
(0003582)
gsommer   
2018-11-29 00:04   
Thank you all for the tips. It works for me too now.
(0003583)
zava   
2018-11-29 13:27   
I understand that the solution of obtaining a private API key and then directing GS to use it for displaying maps seems viable and effective.
So now it would be very appreciated if some more skilled user could post a dummy-proof instruction as to how to do this, possibly a simple, step by step guide to
- how to obtain an API key
- how to direct GS to use it

Since no "native" solution seems to be available, I guess this would be a great contribution!
Thank you in advance!
(0003584)
JoopvB   
2018-11-29 14:36   
Yes please!!
(0003585)
WilfriedB   
2018-11-29 14:54   
See https://developers.google.com/maps/documentation/javascript/get-api-key for how to get an API key. You need to register and provide a credit card number(!). However, are certain number of accesses per month is free. Google claims, the number is high enough, so "normal" users would never pay - we will see ...
Not sure, what you have to configure in your Google configuration, to get it to work with GeoSetter. I requested the key several months ago, to get another application (RouteConverter) to work. The process was not straight forward and there was some discussion in the forum for RouteConverter.
(0003586)
zava   
2018-11-29 17:35   
Thank you WilfriedB, this seems to be the first half of the solution (getting the API key).
Reading the current, updated pricing conditions, though, it appears that since July 2018 there's no "free quota": users used to be entitled to get 25.000 map loads per day for free; now all map loads are charged (0,007USD/load up to 100.000 loads/day).
So now ALL loads are charges, and using the previously free quantity (25.000 loads) would now cost above 150USD...).
Also, it is not clear exactly what a "map load" is and how many map loads a normal use of GS will generate...

Finally, a "how to" guide would now be required in order to describe what to do in order to get GS to work with the API key.
If anybody cares to make it available, thank you in advance!
(0003587)
RolfW   
2018-11-29 18:03   
To make the configuration steps more clear, I wrote a little HowTo. Use it at your own risk ;-)
(0003588)
zava   
2018-11-29 18:52   
Thank you RolfW!
Very neat, it worked straight away!
Now I just need be very careful with Google invoicing the map loads, it is surely not clear how much that may cost.
At least, I now have a proper map loaded again!
(0003589)
WilfriedB   
2018-11-29 19:15   
Zava, after logging into your Google account, you can open the "Pricing Calculator" https://mapsplatformtransition.withgoogle.com/calculator. Her you can see the prices for usage of the API and your current balance ("Estimated monthly cost Includes recurring $200 credit" in my case)
(0003590)
WilfriedB   
2018-11-29 19:19   
The "Google Cloud Console" provides you with actual usage: https://console.cloud.google.com/google/maps-apis/overview
(0003593)
DenisPac   
2018-12-02 18:56   
Thanks to @Erik Krause and @RolfW!!
Base on their tips I could make GeoSetter work again. Great!!
(0003594)
rau1   
2018-12-03 20:21   
Special Thanks to RolfW - I followed your HowTo Guide in it works great again!
(0003603)
Mapr   
2018-12-07 23:23   
Although the tips to get the map to show up again works, there still is a problem, a big one. The search box is no longer usable. When you search for a location or address, you'll get: "what you searched for .. was not found"

Does anyone have a fix for that?
(0003605)
Erik Krause   
2018-12-08 16:50   
According to http://www.geosetter.de/mantis/view.php?id=1992 you need to activate the geocoding api for your key. Will test on monday...
(0003606)
u564533   
2018-12-08 17:22   
I did the steps of the RolfW's HowTo, but I see a grey area with a sentance "Hoppla! Ein Fehler ist aufgetreten. Google Maps wurde auf dieser Seite nicht richtig geladen. Technische Details dazu entnimmst du der JavaScript-Konsole."
(0003607)
Mapr   
2018-12-08 18:16   
@Erik Krause Thank you for your reply. Yes, my api key is already activated, but the search feature doesn't work.
(0003608)
WilfriedB   
2018-12-08 18:23   
@Mapr: I never experienced any problems with the search, neither before Google changed its policies nor when the map showed "only for development" nor now using my own API key. I'm not sure whether the Google API is indeed used for the search or rather GeoNames instead. Please verify under Settings -> Internet -> GeoNames. The "Adddress of GeoNames Free Webservises" should be http://api.geonames.org .
(0003609)
Mapr   
2018-12-08 18:56   
Just to be clear to anyone reading or replying. The google search that I say is no longer working, is the map search box in geosetter itself.

I've attached a screen shot of the area I am speaking of .
(0003610)
WilfriedB   
2018-12-08 19:00   
@Mapr: This is exactly the search, I meant. But we don't know, if this really uses Google or GeoNames instead. Therefroe I suggested to verify the settings for GeoNames.
(0003611)
RolfW   
2018-12-08 19:11   
@Mapr: For the search feature to work properly, you need to add to add Geocoding API to your API Project. Go to API-Dashboard, open Library, search for Geocoding API and add it to your project.
(0003616)
geewee   
2018-12-19 20:54   
@U564533: same problem here.

After program start the map is shown for a short moment, then the error message "Hoppla..." appears. Also, there is no traffic shown in the API-Dashboard.

Apart from creating an API key, does one have to explicitly activate any specific API (other than Geocoding)? If not, what else can be the cause for the error?
(0003617)
WilfriedB   
2018-12-19 21:11   
@geewee: You also need to activate certain APIs on you Google account. Here is a description in German language https://www.routeconverter.com/faqs/google-api-keys/de . Not sure whether GeoSetter needs all four APIs described on that page, though, but it works fine for me RouteConverter as well as for GeoSetter.
(0003618)
geewee   
2018-12-19 21:34   
OK, I have activated two more APIs and now it works: Maps Static and Maps JavaScript.
(0003619)
u564533   
2018-12-20 01:50   
Works here too, had to active the 2 APIs. For German users I attached a howto. Friedemann should publish it to the homepage
(0003620)
Mapr   
2018-12-21 18:13   
@RolfW Thank you, it looks like all I had to do was to enable the Geocoding API. Everything works now. Thank you, and thank you all who helped me with this!
(0003621)
dydxdx   
2018-12-24 15:44   
Christmas present (from whom)??....I have no personal Google API key/Acc't and the Google maps works this morning.
Merry Christmas!
(0003622)
WilfriedB   
2018-12-24 15:49   
Before I implemented my own personal API key I noticed the same daily: When you start GeoSetter in the morning (but not too early) it would work fine. I assume, in that case Friedeman's account is charged for that, so I decided to use my own key instead to be fair.
(0003623)
dcb_oz   
2018-12-31 23:58   
@rolfw - thanks for the instructions

I have maps working but cannot get anything to search. Both that Javascript API and Static API are enabled. No luck. Search returns "location not found".

Some clarification also on the current pricing as of Jan 1, 2019. There is a $200 credit applied each month which covers approx 28,000 calls. So while it's not "Free" it is for a lot of calls.
(0003624)
RolfW   
2019-01-01 01:26   
@dcb-oz
As I mentioned in 0003611 you need to add Geocoding API to your API project.
http://www.geosetter.de/mantis/view.php?id=1970#c3611
Happy new year!
(0003625)
dcb_oz   
2019-01-01 01:54   
Thanks @rolfw Missed that. Working now.
(0003626)
othmarmarti   
2019-01-01 20:16   
Thanks to all for the help setting up the google API. I have one question left: What do I select at "API-Restrictions"? I am not sure, what to do. I appreciate any cmments!
(0003627)
Erik Krause   
2019-01-01 20:24   
If you use the page on your local computer where there won't be any chance your api key gets exposed to the broad public you don't need any restrictions.
(0003677)
ceroni   
2019-01-26 13:43   
Is there a way to disable Google maps altogether and use OpenStreet maps only?
I’m asking this because I’ve noticed that loading Google maps has been intermittent: it doesn’t load most of the time (as expected) but eventually loads on some (sunny?) days.
Another thing I’ve notice is when Google maps doesn’t load the UI interface is very slow. I haven’t done extensive tests but am quite sure there is a correlation.
(0003679)
Erik Krause   
2019-01-26 18:05   
Currently not (as far as I'm aware of). Even OSM is loaded via google maps API. Google maps works as long as the use count is below a certain threshold. The only option ATM is to register with google maps API and use this as written above.
(0003680)
WilfriedB   
2019-01-26 18:18   
During the last two or three weeks I also experience extremely long response times when I start GeoSetter. I use a personal API since November 2018 and in the beginning I had even the impression, it was faster than using Friedewald's key.
(0003681)
dydxdx   
2019-01-26 23:43   
It would be nice if the publisher would update software to enable easy API Key entry.
(0003688)
Studia   
2019-01-29 06:43   
I would be more than happy to pay a reasonable annual fee for this software to ensure full access to the map.

Is that a possibility?
(0003698)
Erik Krause   
2019-02-24 14:46   
Earlier in this discussion Friedemann wrote there is no javascript API for OpenStreetMap. This is not entirely true. I recently stumbled across the open source leaflet.js API, which can use a lot of different tile providers. See http://leaflet-extras.github.io/leaflet-providers/preview/ for examples. Of course this API also offers markers, popups, polygons and various other layers. openstreetmap.org itself uses leaflet.js. May be it is possible to rewrite the complete map_google.html to use leaflet instead. API reference: https://leafletjs.com/reference-1.4.0.html
(0003703)
pbb   
2019-04-11 21:24   
Just a quick heads up to people wanting to use OpenStreetMap (the map layer, not the API) in GeoSetter: it is perfectly possible to add those layers if you are self-hosting the map. It involves adding new layer definitions inside the showMap3 function. I've attached my modified HTML map file.
(0003724)
OsmImage   
2019-06-04 12:33   
@pbb Tried the geosetter.htm you provided but unfortunately it doesn't work. Could you please describe the procedure to ensure the functionality? By the way I use in a personal project for adding the GPS location to m2ts-files the leaflet-API and I avoid the use of Google maps jsAPI.
(0003725)
pbb   
2019-06-10 00:24   
@OsmImage, did you point GeoSetter to the file? File > Settings > Map > Map Address and Layers > Map File.

Also, it might be that the HTML file only works from a webserver, not as a local file.
(0003726)
pbb   
2019-06-10 00:24   
@OsmImage, did you point GeoSetter to the file? File > Settings > Map > Map Address and Layers > Map File.

Also, it might be that the HTML file only works from a webserver, not as a local file.
(0003727)
OsmImage   
2019-06-10 12:30   
@pbb, thanks for your reply and yes, I did the settings inside Geosetter and furthermore I added in your geosetter.htm, as written above by RolfW, the <base href="http://map.geosetter.de/v3/"> to include all the scripts and icons Geosetter applies. Doesn't function.

Why it should not work as a local file? If there are all the refs included then it should.
(0003767)
Paul   
2019-12-12 15:53   
Hello, everybody,
I have my own API-Key and integrated it as described here. So I edited the map_google.html and entered my key.
That all works now so far.
My only problem are the image markers in the map, they are no longer visible. What else have I done wrong?
Can one of you help me?

Thank you very much
Paul
(0003783)
zava   
2020-02-07 17:45   
Hmm... I had applied the fix and had worked but now I get the "developmento only" warning again.
I checked the "how to " guide I had then used, but Acrobat cannot open it anymore, saying it's damaged!?
Has the issue changed? Was the guide removed?
Anybody knows better?
Thank you!
(0003784)
WilfriedB   
2020-02-07 18:10   
@zava, do you mean this PDF?
(0003786)
wim_van   
2020-02-14 09:37   
Sorry, but I already tried every thing I could find here, but stll, I can't use search.
1) When using file:// ...... the changed maps_google.html does not work.
2) I put the map_google.html on my site and there it works ...
But, Which API are really needed for use with geosetter ? Eveybody is talking that a key is needed (I have one for my proper usage, but I can't use the search-option for a locality and that I need)
Direction.api is for as far I can see no more free in use
Geocoding.api is free, and is activated in my proper key.

When I enter a place to search for, I got errors in a javascript ?

Any help is welcome.
Thanks
(0003787)
WilfriedB   
2020-02-14 10:17   
@wim_van: It is not enough to enter a valid key, instead you also need to enable your Google account for one or more APIs (which is not so straight forward). Before using my own key for GeoSetter, I did so for Routeconverter following the instructions out lined here : https://forum.routeconverter.com/thread-2501.html?highlight=Google+APi .
(0003788)
wim_van   
2020-02-14 18:02   
Strange ?
I did enable my google account. I too have some developments where I use maps from google, it is from there that I own a key.
When I look to Routeconverter, somewhere I found out that next API's are required. I looked to the API I already enabled for my key.
Maps Java Script API: is enabled and is free of charge
Directions API: is not enabled. It costs minimal 5 Euro/month to use it
Geocoding API: is enabled and is free of charge
Maps Elevation API: is not enabled. it costs minimal 5 Euro/month to use it

I have also other API's enabled.
If direction and maps elevation is really needed, I'll pass. 120 Euro /year just to make a search possible ...
My API-key permits to use googlemaps .... So, I just lack the search. It is by trying to use the search I got the javascript-error
Geosetter by the way is a marvel
(0003789)
WilfriedB   
2020-02-14 18:47   
"costs minimal 5 Euro/month" is quite correct. There is a certain number of requests free each months. I don't remember the details now, but that was part of the discussion in the RouteConverter forum. In any case, so far I did not pay anything.
(0003790)
WilfriedB   
2020-02-14 18:48   
Ooops should have been: "costs minimal 5 Euro/month" is NOT quite correct.
(0003791)
wim_van   
2020-02-16 16:22   
OK, I'll give it a try. Thanks.
Just did not found any response why I have to call for the modified maps_google.html on my site and that I can't run it from a local folder on my desktop as mentioned in the documentation.
(0003793)
wim_van   
2020-02-17 08:50   
I changed the modules for the key. At first view all is working nicely, but...
When I request to search for a town, I always get the result '<townname> is not found'
Can there be somewhere a rpoblem with http and https ? I found some urls containing http (not secured connection) ?

Wim
(0003794)
WilfriedB   
2020-02-17 11:45   
@wim_van: This problem has been discussed further up in this thread ( https://www.geosetter.de/mantis/view.php?id=1970#c3611) and the suggestion was: "For the search feature to work properly, you need to add to add Geocoding API to your API Project. Go to API-Dashboard, open Library, search for Geocoding API and add it to your project."
(0003796)
wim_van   
2020-02-18 08:15   
@WilfriedB
Thanks fo the time you invest. But, Geocoding Api is since several years a module in my project, so in my colleciton of enabled API.
All mentioned API's here on the forum are enabled (Only Direction API and Elevations API were diabled and are now enabled too).
But, I have a stupied work arround. In maps.google.com I do the search, copy the coordinates and put these in Geosetter. When done, geosetter shows me the wanted place and I can continue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
1217 [GeoSetter] Image Data feature always 2014-09-06 01:11 2020-02-12 17:03
Reporter: aush Platform:  
Assigned To: Friedemann OS:  
Priority: normal OS Version:  
Status: assigned Product Version: 3.4.51 beta  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: allow "Link to Originals" to local files in "Export to Google Earth"
Description: in "Export to Google Earth" feature, now it's only possible to add links to full-size photos if they are first uploaded to web. Why not allow also links to local original files? (to open local files from GE, user should enable "Allow access to local files" in GE options, but it's not a big deal)
As a workaround, now I change links in the generated kml from web to local path - with regular expressions it's not difficult but still takes some time...
Tags:
Steps To Reproduce:
Additional Information:
Attached Files:
Notes
(0003785)
Jacky67300   
2020-02-12 17:02   
Hello.
is there any news about this ?
I wish I can get in the KMZ-file the links to the several photos I just displayes in GeoSetter.
So that I can click on the icon in Google Earth and it opens the photo with picture viewer.
Regards JS


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
2078 [GeoSetter] Image Data major always 2020-02-09 16:52 2020-02-09 16:52
Reporter: willhux Platform:  
Assigned To: OS:  
Priority: high OS Version:  
Status: new Product Version: 3.5.1  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Does not load the images into a map, popup with "map not loading correctly"; freezes
Description: I am using to place pictures into Earth Pro at work. was working perfectly until this week.
Tags:
Steps To Reproduce: select pictures and load into Geosetter
click FILE
click Export to Google Earth

loads the selected pictures but will not display on Earth.
Additional Information:
Attached Files:
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
2073 [GeoSetter] Image Data minor always 2019-12-26 17:42 2020-01-30 12:23
Reporter: orensbruli Platform:  
Assigned To: OS:  
Priority: normal OS Version:  
Status: new Product Version: 3.5.1  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: 3.5.3 Dng lose the Color Label set on Lightroom setting location and timezone on Geosetter
Description: Hello,

I usually set color labels on Lightroom on my process to select my files.
After saving metadata to file on lightroom, closing and setting the location on Geosetter, I read de metadata from file in lightroom and I see that the DNG files have lost the color label. This doesn't happen with the Nikon NEF files. Only with the DNGs (in this case, these are pano files generated by Lightroom).

I hope someone can reproduce this and we can find a fix.

Best regards.



Tags: color label, geosetter, lightroom
Steps To Reproduce: - Set a color label on Lightroom to a DNG file.
- Save metadata to file.
- Close Lightroom.
- Open dir on Geosetter.
- Change the location (I'm also changing the timezone).
- Save on Geosetter.
- Close GeoSetter.
- Open Lightroom.
- Read the changes in metadata from files.
- Check that the color label of the DNGs has disappeared.
Additional Information:
Attached Files:
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
2077 [GeoSetter] User Interface major always 2020-01-23 10:28 2020-01-27 08:27
Reporter: bobsun Platform:  
Assigned To: OS: Windows 10  
Priority: high OS Version:  
Status: new Product Version: 3.5.1  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Can't view trackpoints
Description: When I open a track file and press the "show list of trackpoints" button, nothing happens.
Tags:
Steps To Reproduce: Consistent over long period of time. No change with upload of 3.5.3
Additional Information:
Attached Files: trackpointsMissing.jpg (270,325 bytes) 2020-01-23 10:28
https://geosetter.de/mantis/file_download.php?file_id=814&type=bug
Notes
(0003780)
bobsun   
2020-01-23 20:30   
never mind

Found the problem
(0003781)
WilfriedB   
2020-01-27 08:27   
@bobsun, it might be helpful for others, if you explain, what exactly your problem was.
In any case from my own experience, I noticed that you don't see track files you added to the folder AFTER starting Geosetter. In such a case, you need to do a File -> Refresh (F5) before the View -> Tracks (Ctrl+T). However, be aware that you loos all changes you made since starting Geosetter unless you save them (Ctrl+S).


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
2074 [GeoSetter] User Interface major have not tried 2019-12-30 00:12 2020-01-06 22:30
Reporter: nhosko Platform:  
Assigned To: OS:  
Priority: high OS Version:  
Status: new Product Version: 3.5.1  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Javascript Link to Google Maps has an old http link which is not working anymore - change to https required
Description: On http://map.geosetter.de/v3/map_google.html, line 11 is pointing to "http://maps.googleapis.com/maps/api/..." which returns a ERR_CONNECTION_RESET error.

From Internet Explorer's console:
HTML1300: Navigation wurde ausgeführt.
map_google.html
HTML1423: Falsch formatierte Startmarkierung. Attribute sollten durch Leerzeichen getrennt werden.
map_google.html (11,117)
SCRIPT5009: "google" ist undefiniert
map_google.html (19,3)

From Chrome's Console:
map_google.html:11 GET http://maps.googleapis.com/maps/api/js?v=3.14&key=AIzaSyDpMI6jmlJbH5d_YIH40FIDrYnpZhaiHYY&libraries=geometry net::ERR_CONNECTION_RESET
map_google.html:20 Uncaught ReferenceError: google is not defined
    at map_google.html:20

If in Chrome, I go to "https://maps.googleapis.com/maps/api/...", the file can be downloaded correctly from google.

Maybe Google changed recently and allows only https connections to its API?
Can you please update the http://map.geosetter.de/v3/map_google.html code or provide an alternative link?
Tags:
Steps To Reproduce: Open GeoSetter normally, then an error that certificate is wrong will appear. No maps will be shown.
Additional Information:
Attached Files:
Notes
(0003777)
Erik Krause   
2020-01-06 22:30   
No problems here, can not reproduce. However, until version 4 is ready you should use you own local map_google.html file with your own maps api key anyway. See http://www.geosetter.de/mantis/view.php?id=1970


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
2075 [GeoSetter] User Interface major sometimes 2020-01-01 14:39 2020-01-01 14:39
Reporter: fonebone Platform: PC  
Assigned To: OS: Windows  
Priority: normal OS Version: 10.0.18362  
Status: new Product Version: 3.5.1  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: xmp file write issue
Description: When I save a batch of modified photos that are a mix of raw (Sony .ARW) and jpeg file with the same base name, e.g. "DSC08394.arw" and "DSC08394.jpg" then I normally get a number of errors like "Error: Temporary file already exists: V:/ftp/a7Riv/DSC08394.xmp_exiftool_tmp".

I guess that this happens due to 2 exiftools running at the same time for the arw and the jpg file that want to write the same xmp file "DSC08394.xmp" where for the jpg there should actually be no xmp needed as it actually should embed the data.
Tags:
Steps To Reproduce: - take a larger set of photo pairs (DSCxxxxx,arw and DSCxxxxx,jpg)
- modify their data
- save
Additional Information:
Attached Files:
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
290 [GeoSetter] User Interface feature N/A 2008-04-21 11:47 2019-12-27 14:53
Reporter: mmm Platform:  
Assigned To: Friedemann OS:  
Priority: normal OS Version:  
Status: assigned Product Version: 2.4.3 release  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Frage: Besteht die Moeglichkeit auch Karten lokal zu halten?
Description: Ich wuerde gerne auch unterwegs (z.B. abends im Hotel) meine Fotos bearbeiten OHNE Internet-Zugang.
Besteht die Moeglichkeit eine Karte fuer GeoSetter auch lokal auf mein Notebook zu laden und dann auf diese zuzugreifen?

(Vielleicht ist die Frage dumm, aber ich habe in der Vergangenheit mit Exifer gearbeitet und da gab es kein GPS-Koordinaten-Update. Habe bisher wenig mit Karten gearbeitet, ausser uebers Internet mit Google Maps. Aber den Wunsch bzgl. lokaler Karte OHNE Internet hatte ich da auch schon, nur nicht weiterverfolgt.)
Tags:
Steps To Reproduce:
Additional Information:
Attached Files:
Notes
(0000606)
Friedemann   
2008-04-21 20:00   
Mit Google Maps geht das leider nicht. Eine Alternative wäre freies Kartenmaterial (z.B. http://www.openstreetmap.org). Aber da müsste dann ein lokaler Kartenserver installiert werden. Außerdem müsste ich alle Funktionalitäten welche Google Maps über seine API anbietet dann selbst programmieren - denke ich. Kein Problem, würde ich gerne machen. Wenn hier jemand einen Tipp hat, wie man z.B. das unter http://www.openstreetmap.org angebotene Kartenmaterial lokal einbinden kann, dann möge er sich bitte melden!
(0003051)
GeoUser   
2017-09-08 00:25   
Hallo! Die Einbindung der Möglichkeiten die OSM bietet wäre eine wahre Bereicherung. Wenn Du die Möglichkeiten rund um OSM abchecken möchtest, dann besuche uns doch mal im Forum unter https://forum.openstreetmap.org/viewforum.php?id=14 (users: Germany). Dort sind immer freundliche und auskunftsfreudige, hilfsbereite Mapper welche gerne helfen. Offline-Kartenmaterial lässt sich ganz sicher erzeugen, das geht ja auch für Garmin, Android-Apps usw. Darüber hinaus ist http://nominatim.openstreetmap.org/search.php vielleicht eine Option für das Reverse-Geocoding, bei all den Daten die OSM hat. Schau doch mal rein ins Forum!
(0003775)
Helma   
2019-12-27 14:53   
Hallo Friedemann,
wird dieses Projekt, dieser Feature-Wunsch, noch weiter verfolgt?
Der Hinweis von GeoUser zeigt ja zumindest auf, wie man hier evtl. weiterkommen kann.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
2072 [GeoSetter] User Interface major have not tried 2019-12-19 02:42 2019-12-19 02:44
Reporter: JackDaynes Platform:  
Assigned To: OS:  
Priority: immediate OS Version:  
Status: new Product Version: 3.5  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: A month ago I asked for help and was assigned "0002068". Since then crickets!
Description: see issue 0002068 PLEASE!
Tags:
Steps To Reproduce: see issue 0002068 PLEASE!
Additional Information: see issue 0002068 PLEASE!
Attached Files:
Notes
(0003774)
JackDaynes   
2019-12-19 02:44   
I installed the latest version of Java, but that didn't help.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
2063 [GeoSetter] Image Data major always 2019-11-05 08:59 2019-12-15 21:35
Reporter: lowjoel Platform:  
Assigned To: OS:  
Priority: normal OS Version:  
Status: new Product Version: 3.5  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Support for Canon CR3
Description: Hello there, the newer Canon cameras (EOS R, EOS RP, EOS 90D, EOS M6 mkii) use the new CR3 format, which Exiftool supports, but Geosetter does not recognise.
Tags:
Steps To Reproduce: If you need sample CR3 files, you can get them from dpreview: https://www.dpreview.com/reviews/canon-eos-90d-review/9
Additional Information:
Attached Files:
Notes
(0003773)
rau1   
2019-12-15 21:35   
I have the same request please (Canon G7x Mk iii)


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
2071 [GeoSetter] Image Data tweak always 2019-12-11 13:52 2019-12-13 22:06
Reporter: U.heker Platform:  
Assigned To: OS:  
Priority: normal OS Version:  
Status: new Product Version: 3.5  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Gps daten von Photoshop dateien
Description: Frage: wie bringe ich Geosetter dazu gps Daten NICHT in eine xml datei zu schreiben.
Weitere Angaben benötigt ?
 off Topic :
Eine google maps API sucht nicht zeigt aber daten an ?
Tags:
Steps To Reproduce:
Additional Information:
Attached Files:
Notes
(0003772)
heiko   
2019-12-13 22:06   
"Datei | Einstellungen" Reiter "Datei-Optionen". Hier dann den entsprechenden Dateityp auswählen und "Daten in XMP-Sidecars speichern" abwählen.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
1778 [GeoSetter] User Interface major always 2017-10-14 18:55 2019-12-13 14:12
Reporter: justone Platform: all  
Assigned To: Friedemann OS: all  
Priority: urgent OS Version: all  
Status: assigned Product Version: 3.4.51 beta  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Speichern nicht möglich wegen Encoding
Description: 80 files getaggt .... ort, zeiten und so weiter alles noch ROT
auf SAVE geklickt ....
Meldung das er die mit dem encoding nicht speichern kann.
Keine Abfrage zur Auswahl des Encoding wie in der release version.
Das Ende vom Lied .. alle gemachten änderungen weg.
1h Arbeit für die Tonne.
Tags:
Steps To Reproduce:
Additional Information:
Attached Files: IMG_9989.jpg (1,893,926 bytes) 2019-12-13 13:59
https://geosetter.de/mantis/file_download.php?file_id=811&type=bug
Notes
(0003171)
Friedemann   
2017-10-14 18:56   
Tut mir leid, aber eine Stunde arbeiten ohne zu speichern, das ist ja auch sehr leichtsinnig...
(0003172)
Friedemann   
2017-10-14 19:18   
Ich wüsste aber sehr gerne, was da wohl die Ursache war bzw. wie ich das vielleicht nachstellen kann...
(0003173)
justone   
2017-10-14 19:35   
kein Problem .. ist halt ne Beta ... damit muss man rechnen.

Das lustige daran ist .. ich habe für jpg in den Einstellungen
"IPTC-Daten als unicode speichern" und
"Bei bereits existierenden IPTC Daten Zeichensatz übernehmen"
angehakt.
Vielleicht ist das mit dem Übernehmen nicht so clever gewesen.
Denn die Dateien haben natürlich schon IPTC Informatioen vom Scanservice de die Negative eingescannt hat.
(0003174)
justone   
2017-10-14 19:48   
Ich würde mal sagen die Fotos hatten IPTC mit lokalem Zeichensatz also ohne unicode, und ich habe Tunesien getaggt samt Ort.
In der heutigen Release version kommt dann eine Abfrage das er die nicht speichern kann.
Egal ob man abbricht oder OK sagt was ja dann nicht geht, geht das Speichern fenster wieder zu und die modifizierten Dateien behalten in ROT die Änderungen.
In der Alpha sind dann die Änderungen direkt verschwunden, das war etwas blöd.
Vielleicht hängt es auch mit dem Verschieben UP/DOWN zusammen das er dabei irgendwie durcheinander gekommen ist, keine Ahnung.

Ich würde den Fehler in der Save Routine vermuten.
Sprich IF Änderung = True and Saved = False .. Änderungen in jedem Fall behalten bis jemand Hardcore das Programm trotzdem beendet.
Oder was generell viel viel besser wäre: Wenn Zeichen vorhanden sind die unicode erzwingen, dann kann man sich die Abfrage nach unicode generell schenken, denn entweder müsste ich dann ja alle Daten mit Sonderzeichen ändern oder aber trotz allem unicode verwenden. Letzteren ist wohl heute Standard.
(0003770)
drose   
2019-12-13 13:59   
Habe den Fehler "Warning: FileName encoding not specified - D:/FileStore/Bilder/Urlaube/2018_Südafrika/Andere Reisenden/IMG_9989.jpg" aus dem Aufruf
"C:\Users\nnn\AppData\Roaming\GeoSetter\tools\exiftool.exe -@ "C:\Users\nnn\AppData\Local\Temp\et0057D96D.arg" -common_args "D:\FileStore\Bilder\Urlaube\2018_Südafrika\Andere Reisenden\IMG_9989.jpg""

Laut diesen Thread "https://exiftool.org/forum/index.php?topic=9753.0" sollte der Aufruf von EXIFTool um "-charset filename=latin" ergänzt werden.
D.h. das müsste in common.args aufgenommen werden ?

Ich lade mal ein Demo-Bild hoch.
(0003771)
drose   
2019-12-13 14:12   
Habe mal das Kommando unter den Einstellungen/EXIFTool Nacheinander in die beiden Boxen "Zusätzliche ExifTool-Kommandos ..." eingefügt und nun ein andere Fehlermeldung:

Error: Error reading StripOffsets data in IFD3 - D:/FileStore/Bilder/Urlaube/2018_Südafrika/Andere Reisenden/IMG_9989.jpg
Warning: FileName encoding not specified - D:/FileStore/Bilder/Urlaube/2018_Südafrika/Andere Reisenden/IMG_9989.jpg

Ohne den Eintrag "-charset filename=latin" bekomme ich diese Meldungen :
Warning: FileName encoding not specified - D:/FileStore/Bilder/Urlaube/2018_Südafrika/Andere Reisenden/IMG_9989.jpg
Error: Error reading StripOffsets data in IFD3 - D:/FileStore/Bilder/Urlaube/2018_Südafrika/Andere Reisenden/IMG_9989.jpg
Warning: FileName encoding not specified - D:/FileStore/Bilder/Urlaube/2018_Südafrika/Andere Reisenden/IMG_9989.jpg


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
1264 [GeoSetter] Image Data minor always 2015-06-10 12:58 2019-12-13 13:55
Reporter: muellerj Platform: Windows  
Assigned To: Friedemann OS: Windows  
Priority: normal OS Version: 7  
Status: assigned Product Version: 3.4.16 beta  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: ExifTool warning "encoding not specified" on saving attributes to jpg
Description: On saving changes to jpg-files "FileName encoding not specified" - warnings are displayed in case path name to file contains special characters (Umlaute).
Reason: changed behavior of ExifTool v9.81 ff. -charset filename=CHARSET has to be used when using special characters in directory name.
Tags:
Steps To Reproduce: Save changes to jpg file with special characters (Umlaute) in path
Additional Information: see http://u88.n24.queensu.ca/exiftool/forum/index.php?topic=6259.0
Geosetter version is 3.4.16 (last non-beta).
Attached Files:
Notes
(0002342)
Flominator   
2016-08-13 16:59   
Same here when tagging pictures from Allgäu :)
(0003769)
drose   
2019-12-13 13:55   
Ich habe Bilder von einem Kollegen bekommen.
beim speichern der Änderungen wird der Fehler
    "C:\Users\nnnn\AppData\Roaming\GeoSetter\tools\exiftool.exe -@ "C:\Users\nnnn\AppData\Local\Temp\et0057D96D.arg" -common_args "D:\FileStore\Bilder\Urlaube\2018_Südafrika\Andere Reisenden\IMG_9989.jpg""
ausgegeben. Die Dateinamen enthalten keine Umlaute, sind aber im Charset nicht kompatibel !?!? => vieleicht unter UNIX erzeugt ?

Unter https://exiftool.org/forum/index.php?topic=9753.0 wurde diskutiert, das der exif-Tool-aufruf um z.B. "-charset filename=latin" ergänzt werden sollte.

Kann ich das Konfigurativ in Geosetter in den EXIF-Aufruf einfügen ?


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
2069 [GeoSetter] User Interface major always 2019-12-02 21:30 2019-12-02 21:30
Reporter: elie.mccarthy Platform:  
Assigned To: OS: Windows 10  
Priority: normal OS Version:  
Status: new Product Version: 3.5.1  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Version 3.5.3! - unable to synchronise with selected images containing image coordinates already
Description: The option for selected images containing image coordinates already is blanked out so I am unable to select it in the menu.
Tags:
Steps To Reproduce: Click GPS data files from the edit menu
Additional Information:
Attached Files: Capture.JPG (129,508 bytes) 2019-12-02 21:30
https://geosetter.de/mantis/file_download.php?file_id=810&type=bug
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
2067 [GeoSetter] User Interface feature always 2019-11-22 14:25 2019-11-22 14:25
Reporter: fstchr Platform: PC  
Assigned To: OS: Windows  
Priority: normal OS Version: 10  
Status: new Product Version: 3.5  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: How copy original file name in metadata
Description: Hi,
before renaming my jpg files with geosetter, I want to store the initial filename (from the digital camera) in a metadata.
I haven't found such a function. Is there a solution or fonctionnality that I haven't seen ?
Thanks for help
Tags:
Steps To Reproduce:
Additional Information:
Attached Files:
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
2065 [GeoSetter] User Interface major sometimes 2019-11-19 21:40 2019-11-21 20:26
Reporter: brunocodebox Platform:  
Assigned To: heiko OS:  
Priority: normal OS Version:  
Status: resolved Product Version: 3.5.1  
Product Build: Resolution: no change required  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Incorrect codepage encoding for Czech characters
Description: While editing the data for a set of images/pictures taken in the Czech Republic, I use the "Get from Web" button to fill in the Country, State/Province, City and Sublocation automatically. The names are found with correct Czech character spelling. However when selecting "Save Changes" I cannot find an option to select UTF-8 as the Codepage and GeoSetter uses (incorrectly) Latin 1.

My system runs on Windows 10 with US English by default. It seems that GeoSetter will then use Latin 1 (ANSI) (CP 1252) by default and accepts (strangely) certain Czech characters and consequently when trying to save the city name (or province) with Czech characters in the database (phpMyAdmin and pdo with utf8_general_ci for city column) I get the exception error "incorrect string value: '\x9Aovice." The city name for this example is Holešovice.

It seems that GeoSetter doesn't always give the possibility to change the Codepage. When it does, selecting UTF-8 (CP 65001) for Czech characters corrects the error and prevents exception errors in the database.

I cannot find anywhere in the settings where to set UTF-8 as the default character set.
Is there a way or work around to set Unicode UTF-8 as the default Codepage in GeoSetter regardless of the Codepage used on my system?

Thank you in advance.

p.s. the version of GeoSetter is 3.5.3 (Build 2195)
Tags:
Steps To Reproduce: Select any image, edit the data and select a city or province or sub location to a name with one or more Czech characters.
Save the changes. GeoSetter doesn't always detect the conversion error and does not give the possibility to change the Codepage other than the system Codepage.
Additional Information:
Attached Files: City and Sublocation with Czech characters.png (13,149 bytes) 2019-11-19 21:40
https://geosetter.de/mantis/file_download.php?file_id=808&type=bug
Notes
(0003765)
heiko   
2019-11-20 00:39   
Have you tried to set the character coding to "Osteuropa (ANSI)" or "UTF-8"? You can find this setting under "File | IPTC Character Coding | Osteuropa (ANSI)" or "File | IPTC Character Coding | UTF-8"
(0003766)
brunocodebox   
2019-11-20 18:58   
Hi Heiko,
Thank you for your suggestion, and for the solution actually !!!
It never occurred to me to look under File " IPTC, and it looks so obvious now that you mentioned it,. And that is exactly what I was looking for.
I chose UTF-8 and now everything works. I can save all the images with Czech city names in the database without exception errors, Any other Czech characters can be saved also and show correctly in the database records. This is brilliant !!
Thank you for your quick response Heiko, I really appreciate it. Thank you so much again!!!


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
2066 [GeoSetter] Image Data minor always 2019-11-20 06:34 2019-11-20 06:34
Reporter: brunocodebox Platform:  
Assigned To: OS:  
Priority: normal OS Version:  
Status: new Product Version: 3.5.1  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Name entered in the image source/description Artist field not written in EXIF IFDO Artist tag
Description: When editing image data fields in Source/Description, the Caption writer, Credit, Copyright, Headline, Caption, etc .are all written in their respective IPTC tags.

But the Arttist field is missed. It is not written / not appearing in the EXIF IFDO Artist tag.
Tags:
Steps To Reproduce:
Additional Information:
Attached Files:
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
2062 [GeoSetter] Image Data feature always 2019-10-26 15:03 2019-11-14 09:23
Reporter: atlantissimo Platform:  
Assigned To: OS: Windows  
Priority: high OS Version: 10  
Status: new Product Version: 3.5.1  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Google Maps Zeitachse kompatibel machen
Description: Ich habe versucht, aus meiner Google Zeitachse, die automatisch mithilfe eines Android Smartphones erstellt werden kann,
eine KML-Datei zu exportieren, was so auch erstmal funktioniert.
Nun wird mir beim Versuch Bilder mit der Trackdatei zu verbinden folgender Fehler angezeigt:

Sie haben keine Trackdatei ausgewählt oder die gewählte Trackdatei enthält keine Koordinaten mit Datums- und Zeitinformationen.

Dies gilt es also zu beheben, sodass nachträglich von Google heruntergeladene Zeitachsen so verknüpft werden können
Tags:
Steps To Reproduce:
Additional Information: Nach kurzem nachlesen bin ich darauf gestoßen, dass Google wohl die Zeitpunkte der Wegpunkte etwas komisch angibt, ich habe jedoch keine Ahnung davon deshalb hier der Link:

https://support.google.com/maps/forum/AAAALwUX44A5jzQmxJwftA/?hl=de&gpf=%23!msg%2Fmaps-de%2F5jzQmxJwftA%2FW-Iovmq1AgAJ&msgid=W-Iovmq1AgAJ
Attached Files:
Notes
(0003757)
Jaff   
2019-11-06 02:06   
Images and trackdata match the same day?
Do you have any data for that day?

Convert KML file to GPX using GPSBabel (waypoints/routes/tracks). Check the track on Geosetter.
Post KML file so we can check if you don't manage to get to a result.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
2054 [GeoSetter] User Interface minor have not tried 2019-08-15 21:06 2019-11-14 09:22
Reporter: WilfriedB Platform:  
Assigned To: OS:  
Priority: normal OS Version:  
Status: new Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: [Action Required] Google Maps Platform Internet Explorer 10 support end
Description: Just received this from Google:
"As Microsoft’s support for IE10 will cease in January 2020, the use of Embed API and Javascript API from IE10 will gradually be degraded:
    From Javascript API version 3.38 (release date August 2019): For IE10 users, a dismissible warning message will be displayed at the top of maps stating: "You are using a browser that is not supported by the Google Maps Javascript API. Consider changing your browser."
    From Javascript API version 3.39 (release date November 2019): Map Loads from IE10 will not be possible. Javascript API support for IE10 will be entirely discontinued in May 2020 when version 3.38 will be retired.
    For Embed API, a dismissible warning message (same as above) will be displayed at the top of maps for IE10 users from August 2019. After November 2019, the Embed API will no longer be available with IE10"
Does it mean GeoSetter will quit working by the end of the year?
Tags:
Steps To Reproduce:
Additional Information:
Attached Files:
Notes
(0003736)
heiko   
2019-08-16 20:52   
what's with IE 11? I don't get any messages using IE 11
(0003737)
WilfriedB   
2019-08-18 15:29   
I also have IE 11 installed and the message from Google doesn't mention IE 11. However, it says "Your projects listed below which may have associated client IDs have had more than 5% IE10 usage in the past month:" and the project referred is the one I requested the API key for GeoSetter. So, I don't know, if GeoSetter uses IE 10 under the covers, even though, I have IE 11 installed ...?
(0003758)
Cameron   
2019-11-06 04:01   
I cannot see any ms-windows versions that are able to run IE-10 that cannot by upgraded to IE-11.
Certainly my win-7 is already running IE-11.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
2064 [GeoSetter] User Interface major random 2019-11-06 20:01 2019-11-14 09:21
Reporter: chrisbati Platform: PC  
Assigned To: OS: Windows  
Priority: high OS Version: Windows 10(1809)  
Status: new Product Version: 3.5.1  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Geosetter auto close
Description: Hi,

randomly, Geosetter stop running and close itself.
No crash, no error message, just no more geosetter running.

I have 3.5.3 version with last Exif tool version 11.75

No special action, I'm browsing photo to geotag and suddenly, it closed itself and I loose all my work.
I have never found a special action to reproduce the problem each time.

Thanks for help

Chrisbati
Tags:
Steps To Reproduce: No special action, I'm browsing photo to geotag and suddenly, it closed itself and I loose all my work.
I have never found a special action to reproduce the problem each time.
Additional Information: Also happened with previous geottag versions
Attached Files:
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
2058 [GeoSetter] Image Data text have not tried 2019-10-20 17:48 2019-11-14 09:20
Reporter: Kieron Platform:  
Assigned To: OS:  
Priority: normal OS Version:  
Status: new Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: GPS Coordinates
Description: Dag,
have a simple question, if there is not a GPS coordinate on the metada of the foto, how can i find the Location??
Thanks a lot
Kieron
Tags:
Steps To Reproduce:
Additional Information:
Attached Files: GeoSetter Search 2019-10-21 144357.jpg (72,926 bytes) 2019-10-21 14:46
https://geosetter.de/mantis/file_download.php?file_id=805&type=bug
grafik.png (33,905 bytes) 2019-10-21 21:59
https://geosetter.de/mantis/file_download.php?file_id=806&type=bug
Screen Shot 042.PNG (1,096,916 bytes) 2019-10-23 18:45
https://geosetter.de/mantis/file_download.php?file_id=807&type=bug
Notes
(0003742)
heiko   
2019-10-20 21:16   
(Last edited: 2019-10-20 21:19)
you can use the map to find to location. You can then assign the coordinates to the Image and save this data.

just take a look into the helpfile: "GeoSetter Workflows | Assigning Geo Data | Assigning Geo Data Manually"

(0003743)
WilfriedB   
2019-10-21 14:46   
If you don't see the "Search" field below the map, click the pencil and the "Favorite", "Search" and "Coordinates" fields will appear. Under "Search" you can a street address.
(0003744)
Kieron   
2019-10-21 21:04   
The question was if there are NO coordinates on the metadata from the foto!! is it possible to find the location??? So you see i have NO coordinates
(0003745)
WilfriedB   
2019-10-21 21:59   
@Kieron this is what I understood:
The metadata of your photo does not contain any coordinates, but if you do know the name of the place (country, state, city), you can enter the address into the search field and click the button search. If the place can be found, a read marker will be placed on the map. Then you can drag the marker to a more exact position, if necessary, select one or more pictures and click the red marker with green arrow to left to assign the position to the image(s). Editing the image now, you will see the coordinates now.
Is this what you meant or did I misunderstand?
(0003748)
Kieron   
2019-10-23 18:45   
Hello WilfriedB
Thanks i think i understand what you are trying to say, i Have the country and the town Engeland, Brighton, but thats it !! how can i find the place where that
foto is taken, IT's in a shop!! If you right click , you can see al the data, is that enough to find the exact place? Or Coordinates??
Thanks for your help,much much appriciated..
(0003749)
WilfriedB   
2019-10-23 19:13   
@Kieron, you said the metadata of your photo doesn't have any coordinates. If you don't remember, where you made it, then you don't have any possibility.
(0003752)
Kieron   
2019-10-23 21:55   
WilfriedB,
Okay thanks for al the help ! don't have to search anymore !
Thanks Again
Kieron
(0003756)
Jaff   
2019-11-06 01:13   
Try, if is possible, to make an average of previous and next foto locations (only if the time period between them is not too long, you might get the right location).
(0003759)
Kieron   
2019-11-11 19:00   
i have one or two foto's , and they are not taken by me, send to me by mail, but i know what you mean, thanks anyway!


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
1846 [GeoSetter] User Interface feature always 2018-02-03 08:11 2019-11-05 09:00
Reporter: lowjoel Platform:  
Assigned To: Friedemann OS:  
Priority: normal OS Version:  
Status: assigned Product Version: 3.4.14 Release  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Support for high-dpi displays
Description: Hello there! Thank you for this excellent tool.

I would like to ask about potential support for high-resolution displays. On such monitors, GeoSetter's interface is blur because of scaling by the OS. Would it be possible to implement DPI-awareness for the tool?

It may be a massive undertaking so if it requires time I fully understand. If I could be of help (I did Win32 programming for a few years before) do let me know.
Tags:
Steps To Reproduce:
Additional Information:
Attached Files: GeoSetter.png (428,710 bytes) 2018-02-03 08:11
https://geosetter.de/mantis/file_download.php?file_id=683&type=bug
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
2061 [GeoSetter] User Interface major always 2019-10-25 21:03 2019-11-02 18:03
Reporter: eph Platform:  
Assigned To: OS:  
Priority: high OS Version:  
Status: new Product Version: 3.5.1  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Fehlermeldung statt Karte
Description: Seit Anfang Oktober erscheint bei mir im Kartenfenster nur die Meldung

Die Karte wurde nicht gefunden unter:
http://map.geosetter.de/v3/map_google.html
Bitte geben Sie in den Einstellungen den korrekten Pfad zur Kartendatei an...

Auch die Installation von 3.5.2 hat daran nichts geändert.
Tags: map
Steps To Reproduce: Direkt nach dem Programmstart.
Additional Information:
Attached Files:
Notes
(0003753)
WilfriedB   
2019-10-26 10:41   
Laut Friedemann Schmidt müsste das inzwischen behoben sein. Siehe hier: https://geosetter.de/2018/05/10/new-website-new-geosetter-de/#comment-2184
(0003754)
eph   
2019-10-26 16:38   
Die dort genannte Webseite wird bei mir auch angezeigt, es erscheint aber keine Karte.
Ich habe zum Test alles deinstalliert, das User-Verzeichnis gelöscht und neu installiert, keine Verbesserung. Dafür muss ich den Geosetter jetzt mehrfach neu starten, weil er meist erst mit einer Fehlermeldung abstürzt.
(0003755)
eph   
2019-11-02 18:03   
Mit der neuen Version 3.5.3 bleiben die Abstürze wenigstens aus.
Aber die Karte wird immer noch nicht angezeigt! Ich habe das Programm nochmal komplett deinstalliert, das Benutzervereichnis gelöscht und alles wieder installiert. Immer noch nichts. Wird irgendwo im System noch was hinterlegt, was ich beim Deinstallieren nicht erwischt habe? Oder warum startet die Karte nicht ?


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
2059 [GeoSetter] User Interface block sometimes 2019-10-22 20:36 2019-10-23 19:17
Reporter: bobsun Platform: PC  
Assigned To: OS: Win 10  
Priority: high OS Version:  
Status: new Product Version: 3.4.50 beta  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: hourly limit exceeded??
Description: I opened Geosetter for the first time in several weeks and received a message " Your hourly limit of 1000 credits has been exceeded...."
Tags:
Steps To Reproduce: Reopened Geosetter twice
Additional Information:
Attached Files:
Notes
(0003751)
WilfriedB   
2019-10-23 19:17   
@bonsun, please see the discussion under http://www.geosetter.de/mantis/view.php?id=1970


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
2060 [GeoSetter] User Interface minor always 2019-10-22 20:41 2019-10-23 19:15
Reporter: othmarmarti Platform:  
Assigned To: OS:  
Priority: normal OS Version:  
Status: new Product Version: 3.5.1  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: geonames.org now has problems with Umlauts
Description: When geotagging a place in Baden-Württemberg, the "ü" appears as ?
The same is for cities, e.g. Bad Dürnheim
This worked in the previous version 3.5.
Tags:
Steps To Reproduce: Select a place in Baden-Württemberg and7or a city with an umlaut and place the red marker there.
Assign the position to an image.
The geonames.org data has the ?

Logging directly to geonames.org baden-Württemberg is displayed correctly.
Additional Information: Thanks for any help
Attached Files:
Notes
(0003746)
othmarmarti   
2019-10-22 20:46   
I just observed that the old version 3.4.53 has the same issue.
(0003747)
othmarmarti   
2019-10-22 22:11   
I did some more tests:

- when uninstalling geosetter and reinstalling the 3.4.53 beta, the issue with geonames and Umlauts is gone
- when selecting in win 10 regions: Deutschland and ticking "beta: use utf 8 for foreign " some of the ° symbols in Geosetter are correct, some not (unintellegible letters) It seems that there were some strings were forgotten

A good program!
(0003750)
WilfriedB   
2019-10-23 19:15   
I noticed the same today with 3.5.1. The problem did not exist in 3.5 or earlier.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
2057 [GeoSetter] User Interface minor always 2019-09-28 17:02 2019-09-28 17:02
Reporter: Malcolm_Ferguson Platform:  
Assigned To: OS:  
Priority: normal OS Version:  
Status: new Product Version: 3.5  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Show translations in OpenStreetMap
Description: As a western European with no Chinese language skills, looking a maps of China is pretty damn difficult if they're not translated from Chinese. It seems that Geosetter shows the default tiles that we can also see OSM's main website (https://www.openstreetmap.org/), which is a known limitation of their web site. https://www.openstreetmap.de/karte.html# however shows translations (unfortunately for me German's not very strong, but it's easier to work with than Chinese!), and so you can see what is possible with OSM. I have to use OSM by the way because Google street maps have a shift applied to them, putting photos up to ~500m away in the wrong location.
Tags:
Steps To Reproduce: Switch to OSM map
Zoom in to Shanghai
Additional Information:
Attached Files: Geosetter view.png (371,561 bytes) 2019-09-28 17:02
https://geosetter.de/mantis/file_download.php?file_id=803&type=bug
openstreetmap.de view.png (318,645 bytes) 2019-09-28 17:02
https://geosetter.de/mantis/file_download.php?file_id=804&type=bug
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
2056 [GeoSetter] Image Data minor always 2019-08-26 15:52 2019-09-09 21:05
Reporter: joergens_mi Platform:  
Assigned To: OS:  
Priority: normal OS Version:  
Status: new Product Version: 3.4.51 beta  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: problemr mit KML Dateien meiner Kamera
Description: Meine Kamera Pentax K1 schreibt einen GPS-Log als .kml Datei, dieser wird auch als Track in geosetter angezeigt. (geos_001.png)
Bei dem Versuch den Track mit den Bildern zu synchronisieren über bearbeiten "Synchronisierung mit GPS-Daten"
kommt immer die untere Fehlermeldung. (geos_002.png). Eine verkürzte Form einer kml Datei ist beigefügt (demo verkürzt_001_0812.KML)

Die Frage ist warum das so, bzw. was ist an der kml Datei falsch, dass ich nicht damit synchronisiert werden kann.
Ein Beispiel für eine synchronisierbare kml Datei würde mir auch helfen, meine Dateien bei Bedarf umzuformatieren

Es wäre für mich interessant, da ich eine zweite Kamera haben ohne GPS und ich auf dieses Weise über die Uhrzeit die Positionen zuweisen könnte
Tags:
Steps To Reproduce:
Additional Information:
Attached Files: geos_002.png (270,901 bytes) 2019-08-26 15:52
https://geosetter.de/mantis/file_download.php?file_id=800&type=bug
geos_001.png (3,212,511 bytes) 2019-08-26 15:52
https://geosetter.de/mantis/file_download.php?file_id=801&type=bug
demo verkürzt_001_0812.KML (9,201 bytes) 2019-08-26 15:52
https://geosetter.de/mantis/file_download.php?file_id=802&type=bug
Notes
(0003741)
heiko   
2019-09-09 21:05   
Nachdem ich das KML Format nicht wirklich kenne, habe ich die Datei mit GPSBabel in GPX konvertiert.

Hier ist zu sehen, dass das File 16 Wegpunkte enthält. Der Name der Wegpunkte ist die Uhrzeit. Im Feld <cmt> und <desc> (ich nehme an Kommentar und Beschreibung) ist das Datum und die Uhrzeit hinterlegt.

Der GPS Track enthält 41 Punkte mit Koordinaten, allerdings fehlt hier das Datum und die Uhrzeit komplett. Und genau hier wäre es wichtig, dass Datum und Uhrzeit vorhanden ist. Das ist auch im KML File ersichtlich; hier werden im Track nur Koordinaten aufgeführt.

Wie man hier allerdings ein vernünftiges File hinkriegt kann ich leider nicht sagen.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
2055 [GeoSetter] Image Data feature sometimes 2019-08-24 11:25 2019-08-28 11:24
Reporter: hwcw Platform:  
Assigned To: OS:  
Priority: low OS Version:  
Status: new Product Version: 3.5  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Spalten und Anzeigeinfoe einstellen
Description: Aus mir nicht erklärbaren Gründen ist

- das Digitalisierunsdatum/-uhrzeit manchmal um Sekunden oder Minuten später als das Erstellungsdatum / -uhrzeit. (Kameras Sony Rx100, Apple iPhone 8).
- sortieren mein Bildbetrachtungsprogramme (Fotos, Adobe Elements) nach Digitalisierunsdatum/-Uhrzeit. Wenn Bilder beider Kameras in eine Kartei zusammengeführt werden, ist die Reihenfolge nicht richtig

Ich bin mir bewusst, dass dieses nicht durch Geosetter oder EXIF verursacht wird, es könnte mir allerdings helfen, wenn das Digitalisierunsdatum/-Uhrzeit angezeigt und änderbar wäre.
Tags:
Steps To Reproduce:
Additional Information:
Attached Files:
Notes
(0003738)
WilfriedB   
2019-08-27 19:02   
Dass es da einen großen Unterschied zwischen Digitalisierungs- und Erstellungsdatum gibt und dass einige Programme ersteres nutzen, ist mir noch nicht aufgefallen, wohl aber dass die Uhr in meiner Sony A77 M2 (im Gegensatz zur A55 und A68) in wenigen Tagen eine Differenz zur (automatisch gesetzten) Zeit im Smartphone zeigt. Ich behelfe mir dadurch, dass ich zum einen die Zeit in der Kamera häufiger neu einstelle und zum anderen - wenn mehrere Kameras und Smartphone zu synchronisieren sind - als letztes Bild die Uhrzeit auf dem Smartphone fotografiere und dann per GeoSetter Erstellungsdatum / -uhrzeit korrigiere. Das funktioniert dann in meinen Programmen (Daminion, Picasa/Google Photos) gut.
(0003739)
hwcw   
2019-08-28 11:04   
Die Uhrzeit der verschieden Kameras anzugleichen, ist ein guter Hinweis. Danke! Was die Programme betriff werde ich noch weiter experimentieren.
(0003740)
WilfriedB   
2019-08-28 11:24   
Noch ein Tipp:
In der Vergangenheit hatte ich die Zeit vom GPS-Logger abfotografiert, bis ich dann die Android App "GPS Time" fand. Vor allem deshalb, weil sie die Sekunden anzeigt, aber die App zeigt auch die GPS-Zeit an, die durchaus vom Timer des Smartphones abweichen kann. Die Abweichungen waren da bislang zwar nur Bruchteile von Sekunden, könnten durch Hard- oder Softwarefehler aber auch größer werden. Ob es so etwas aber auch für das iPhone gibt, weiß ich nicht.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
2052 [GeoSetter] Image Data block always 2019-07-27 11:29 2019-07-29 22:15
Reporter: JoopvB Platform: Intel  
Assigned To: OS: Windows 10 Pro  
Priority: immediate OS Version: 10.0.18362  
Status: new Product Version: 3.5  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Inserted my own Google API as instructed; works but my markers don't show
Description: I have followed the instructions on https://www.photools.com/community/index.php?topic=8689.0 and the Google map shows up. And when I select a picture with GPS coordinates the map centers on the location of the picture, but no marker is shown. Also I cannot set markers (none of them show up). When I switch to OpenStreetMap my markers don't show either.

Before (or without) my own Google API the OPenStreetMap works fine.
Tags:
Steps To Reproduce:
Additional Information:
System Description
Attached Files: Correct map_google.txt (49,903 bytes) 2019-07-29 22:15
https://geosetter.de/mantis/file_download.php?file_id=799&type=bug
Notes
(0003732)
JoopvB   
2019-07-29 22:15   
I've found the problem! The HTML page was unable to load the images for the markers. I probably did something wrong with step 6: adding the BASE tag. After going through the steps again it is working.

If you open the HTML file in your browser you'll notice a warning in the developer console. The Google Maps version used in the HTML has been retired. I fixed this by removing the v=3.14 query string argument.

Just replace YOUR-KEY-HERE with your API-key in the enclosed file and save as map_google.html and it will work (at least it did for me :)).


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
2051 [GeoSetter] User Interface crash random 2019-07-22 09:12 2019-07-22 15:35
Reporter: Cameron Platform: i7 x64  
Assigned To: OS: MS Windows  
Priority: high OS Version: 7 and 10  
Status: new Product Version: 3.5  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: occasional crash on folder open
Description: This is happening regularly, but not repeatably.
I have a working folder from a recent trip, containing a folder for each day, each containing between 10 and 150 images - all jpegs.
Geosetter will regularly crash as I am switching to a new folder of images - without starting to display the contents.
Tags:
Steps To Reproduce: Get a single folder with about 100 jpegs. Navigate to it and set file list to "report" (actually - I just reproduced with thumbnails).
Map can be set to satellite, or OSM, or map display not present. Crashes in all cases.
repeat {
    Click on the "up one folder" button.
    Double click on the image folder and wait for it to populate.
} until crashed.
Additional Information: Usually it will just crash, but occasionally will generate a bug report. I have saved 3:
* one from my old win 7 system
* one from Win 10 with OSM map selected
* one from Win 10 with Google map satellite selected (I have my own API as of yesterday, but this was happening before that).
One laptop running Win 10 does NOT show the problem.
All 3 test systems are x64, Pro editions.

On the systems that crash v3.5.0, I installed 3.4.51-beta build 2164 and it has not crashed.

The crashing folders can have between zero and all images being geotagged (lat-long only). The presence or not of a track makes no difference.
System Description
Attached Files: geosetter-bugreport-Win7.txt (31,372 bytes) 2019-07-22 09:12
https://geosetter.de/mantis/file_download.php?file_id=796&type=bug
geosetter-bugreport-win10-satellite.txt (29,103 bytes) 2019-07-22 09:12
https://geosetter.de/mantis/file_download.php?file_id=797&type=bug
geosetter-bugreport-win10-OSM.txt (27,195 bytes) 2019-07-22 09:12
https://geosetter.de/mantis/file_download.php?file_id=798&type=bug
Notes
(0003730)
Cameron   
2019-07-22 10:28   
update - I realised that I had copied my win-7 appdata\roaming profile to the win 10 system that crashed, so I did some more experiments.

1. wiped all geosetter details from the win 10 system and reinstalled v3.5.0 from scratch, including the profile and some registry entries.
2. no crashes with a fresh install. So that rules out other software/dlls on the different win 10 systems
3. copied over the old config.ini to the new and it immediately started crashing again.

I will now try to isolate which of the many differences are associated with the crash, because this config file was from a working beta version.
(0003731)
Cameron   
2019-07-22 15:35   
I think I have identified the conditions that trigger the crash, and have been reminded of another, possibly related, bug as well, which I think has been around since the beta versions.
The condition is setting sort-order to "Date Taken".
This is important to me because I usually have photos on the one day taken with multiple cameras. Sorting in date order makes it much easier to fill in missing locations by association with photos taken nearby.

If you are within a folder and click the column header to sort by date taken then it seems to work as expected.
However, if the default sort order is already set to Date Taken then, on entering a folder:
1. geosetter sometimes crashes, or
2. if it does not crash then the images are not sorted properly. Because there is a strong correlation between name and date taken it is not clear how or if they are being sorted at all. Maybe they are just in order in folder.

Also...
* pre-selecting "Coordinates" as sort order results in incorrect sorting, and took a bit longer (perhaps 10 folder visits) to cause it to crash.
* The Win 10 laptop that in the first report did not show the problem crashed very soon after setting the sort order to Date Taken.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
2048 [GeoSetter] User Interface major always 2019-06-03 13:48 2019-06-25 19:27
Reporter: blu28 Platform:  
Assigned To: OS:  
Priority: normal OS Version:  
Status: new Product Version: 3.5  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: After setting API key, getting "For Development purposes only"
Description: I followed the instructions for getting my own Google map API key, and it worked. Everything appeared to be working fine. However, once I exited Geosetter and tried to edit a new image file, I got the dialog about "This page can't load Google Maps correctly." and clicking past that I get the shaded overlay that says "For development purposes only." Looking at the Google Cloud dashboard shows the initial correct requests, but all requests after that point show a "4-3" error. I have the Javascript, static and geolocation API enabled. By the way, the step about enabling those APIs is missing from the English PDF in the other issue thread.
Tags: map
Steps To Reproduce: Get an API key, change the key in the google_map.html file, add the "base" tag and change the map file in the settings. Edit a file, then exit.
Additional Information:
Attached Files:
Notes
(0003723)
blu28   
2019-06-03 13:54   
Sorry, I meant the Geocoding API, not Geolocation.
(0003728)
Erik Krause   
2019-06-25 19:27   
Can not reproduce here. Works for me all the time. Did you check the file is still correctly set in Settings -> Map Address and Layers?


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
2049 [GeoSetter] Image Data major always 2019-06-21 01:01 2019-06-21 01:01
Reporter: Goreb Platform:  
Assigned To: OS:  
Priority: normal OS Version:  
Status: new Product Version: 3.5  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Beim Speichern wird Exception EFCreateError erzeugt: *.que kann nicht erstellt werden
Description: Im Verzeichnis liegen einige hundert Nikon RAW Dateien im NEF Format. Nach dem Schritt "Synchronisierung mit GPS Datendatei" per Strg-G und dem "Auswählen der Ortsdaten" sollen die Änderungen an den NEF Dateien per Strg-S gespeichert werden. Das Speichern startet und läuft einige Zeit bis eine Exception EFCreateError entsteht.

Details:
date/time : 2019-06-20, 22:19:20, 191ms
operating system : Windows 10 x64 build 17763
system language : German
system up time : 6 hours 10 minutes
program up time : 9 minutes
processors : 8x Intel(R) Core(TM) i7 CPU 860 @ 2.80GHz
physical memory : 8981/16382 MB (free/total)
free disk space : (C:) 266,22 GB
display mode : 1680x1050, 32 bit
process id : $2a68
allocated memory : 515,04 MB
largest free block : 518,87 MB
executable : GeoSetter.exe
exec. date/time : 2018-05-10 11:42
version : 3.5.0.2188
callstack crc : $0247e48d, $fa45a428, $16e111ca
settings folder : C:\Users\Heiko\AppData\Roaming\GeoSetter\
ExifTool folder : C:\Users\Heiko\AppData\Roaming\GeoSetter\tools\exiftool.exe
map file : http://www.geosetter.de/map_google.html
map file version : 12
exception number : 1
exception class : EFCreateError
exception message : Datei "C:\Users\Heiko\AppData\Roaming\GeoSetter\queue\20190620-221021180.que" kann nicht erstellt werden. Der Prozess kann nicht auf die Datei zugreifen, da sie von einem anderen Prozess verwendet wird.

main thread ($2af4):
0048648c +0a8 GeoSetter.exe Classes 5114 +5 TFileStream.Create
004863be +02a GeoSetter.exe Classes 5102 +2 TFileStream.Create
004866c7 +01b GeoSetter.exe Classes 5174 +1 TCustomMemoryStream.SaveToFile
00a6acfd +149 GeoSetter.exe ImageDataQueue 318 +18 TImageDataQueue.SaveQueueFile
00a6aaab +07f GeoSetter.exe ImageDataQueue 272 +9 TImageDataQueue.OnItemSavedEvent
00a6a073 +013 GeoSetter.exe ImageDataQueueSaveThread 174 +2 TImageDataQueueSaveThread.ProcessDataSaved
0048cbc1 +101 GeoSetter.exe Classes 9339 +22 CheckSynchronize
005144e8 +6e4 GeoSetter.exe Forms 6670 +144 TApplication.WndProc
0048ea3c +014 GeoSetter.exe Classes 10966 +8 StdWndProc
7727bb3b +00b user32.dll DispatchMessageA
00514c3c +0ac GeoSetter.exe Forms 6872 +13 TApplication.ProcessMessage
00514c83 +00f GeoSetter.exe Forms 6891 +1 TApplication.HandleMessage
00514f1e +0a6 GeoSetter.exe Forms 6975 +16 TApplication.Run
00c0c8dc +04c GeoSetter.exe GeoSetter 160 +4 initialization
75b90417 +017 KERNEL32.DLL BaseThreadInitThunk

Vollständige logs und ini Dateien sind angehängt.
Tags:
Steps To Reproduce: Beim Bearbeiten von einigen hundert Nikon RAW Dateien im NEF Format kann der Fehler mit folgenden Schritten bei jedem Versuch reproduziert werden:
1) Strg-G: "Synchronisierung mit GPS Datendatei" durchführen
2) "Auswählen der Ortsdaten" durchführen
3) Änderungen speichern per Strg-S
--> Exception EFCreateError entsteht nach einigen gespeicherten NEF Dateien:
exception class : EFCreateError
exception message : Datei "C:\Users\Heiko\AppData\Roaming\GeoSetter\queue\20190620-221021180.que" kann nicht erstellt werden. Der Prozess kann nicht auf die Datei zugreifen, da sie von einem anderen Prozess verwendet wird.
Additional Information:
Attached Files: Geosetter-config.ini (67,622 bytes) 2019-06-21 01:01
https://geosetter.de/mantis/file_download.php?file_id=794&type=bug
Geosetter-bugreport.txt (31,970 bytes) 2019-06-21 01:01
https://geosetter.de/mantis/file_download.php?file_id=795&type=bug
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
2038 [GeoSetter] User Interface feature always 2019-05-15 19:44 2019-05-23 21:57
Reporter: tman39 Platform:  
Assigned To: OS: Windows  
Priority: normal OS Version: 10  
Status: new Product Version: 3.5  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: No Crosshairs displayed in Map window
Description: "Cross-Hair" does NOT display when "Map>Show Cross-Hair" is toggled ON either from Map Window or main tool bar.
Tags:
Steps To Reproduce:
Additional Information:
Attached Files:
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
2041 [GeoSetter] Image Data major always 2019-05-18 21:13 2019-05-23 21:51
Reporter: tman39 Platform:  
Assigned To: OS:  
Priority: normal OS Version:  
Status: new Product Version: 3.5  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: GeoSetter fails to create GPX track file without errors.
Description: Using GeoSetter V3.5.0
& Garmin Basecamp V4.7.0
Both are latest up-to-date versions.

Selected 6 pictures with GPS info in GeoSetter and used
GeoSetter->File->'Export to GPX Track File'. No errors shown by GeoSetter.
GeoSetter shows correct track in Map window. Track agrees with manually produced track in BaseCamp. Lat/Long's from selected pictures were used to create a route which was then converted to a track using GPSBabel V1.6.0.

When Basecamp tries to import TrackFile.gpx produced by GeoSetter, Basecamp says "Unknown Error Opening Import file" and fails to import.

Error is repeatable with different sets of pictures/track file.
Tags:
Steps To Reproduce: Exited GeoSetter and then re-invoked GeoSetter.
Selected different pictures from different folder.
Same ERROR result in BaseCamp.
Additional Information:
Attached Files:
Notes
(0003722)
heiko   
2019-05-23 21:51   
this is the second line in a GPX file which is written form GeoSetter:
<gpx version="1.0" creator="GeoSetter - http://www.geosetter.de">

it seems, that this part is missing:
xmlns="http://www.topografix.com/GPX/1/0"

if you add this missing part to the second line RouteConverter can read the GPX file which was created from GeoSetter:
<gpx version="1.0" creator="GeoSetter - http://www.geosetter.de" xmlns="http://www.topografix.com/GPX/1/0">

Ok, this is only a workaround, but I hope it helps


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
2043 [GeoSetter] User Interface block always 2019-05-20 07:27 2019-05-20 07:27
Reporter: radervet Platform:  
Assigned To: OS:  
Priority: normal OS Version:  
Status: new Product Version: 3.5  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Menü beim Rechtsklick
Description: Beim Rechtsklick war in der Beta Version ein Windows Menü vorhanden, wobei man z.B. das Bild bearbeiten, kopieren, ausschneiden etc. konnte.
Ich habe immer das "Bearbeiten" benutzt, damit man evtl. etwas uf dem Bild ändern kann. Nach dem Update ist das Menü weg und kommt nur das Menü vom Geosetter mit wenigen Punkten. Kann man dies irgendwie einstellen?
Tags:
Steps To Reproduce: Rechtsklick auf einem Bild im Geosetter Fenster
Additional Information:
Attached Files: Manü früher.jpg (59,931 bytes) 2019-05-20 07:27
https://geosetter.de/mantis/file_download.php?file_id=792&type=bug
Manü jetzt.jpg (262,510 bytes) 2019-05-20 07:27
https://geosetter.de/mantis/file_download.php?file_id=793&type=bug
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
2040 [GeoSetter] User Interface block always 2019-05-16 16:54 2019-05-16 16:54
Reporter: tdd86 Platform:  
Assigned To: OS:  
Priority: urgent OS Version:  
Status: new Product Version: 3.5  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Crash on Start
Description: Software opens and immediately become unresponsive.
Have attempted uninstall and reinstall issue occurs again
Tags:
Steps To Reproduce:
Additional Information:
Attached Files:
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
2026 [GeoSetter] User Interface major always 2019-02-27 21:49 2019-05-16 14:14
Reporter: karlm Platform:  
Assigned To: heiko OS: Windows 10 Pro  
Priority: normal OS Version:  
Status: resolved Product Version: 3.4.51 beta  
Product Build: Resolution: no change required  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Map is not loaded correctly
Description: The map is loaded, but with an error message: "This page can't load Google Maps correctly. Do you own this web site?"
The map is darkened and has several instances of "For development purposes only" spread on top of it.
Please see attached screen shot.

N.B. I am using version 3.4.82 (Build 2184) - BETA and Windows 10 Pro
Tags:
Steps To Reproduce:
Additional Information:
Attached Files: Map problem.jpg (562,727 bytes) 2019-02-27 21:49
https://geosetter.de/mantis/file_download.php?file_id=772&type=bug
Notes
(0003700)
heiko   
2019-03-01 20:49   
see http://www.geosetter.de/mantis/view.php?id=1970
(0003701)
karlm   
2019-03-02 19:42   
Heiko, thank you for the link!


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
2034 [GeoSetter] User Interface minor sometimes 2019-04-20 00:44 2019-05-12 23:13
Reporter: pbb Platform:  
Assigned To: OS:  
Priority: normal OS Version:  
Status: new Product Version: 3.5  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: "INF" in GPS coordinates
Description: This is a new one! :-) One of my photos got the coordinates S0°0'INF"; W0°0'INF". This is very rare, I am geotagging 100-thousands of photos, and I never noticed this before. It is reproducible, if I close GeoSetter and redo all with the same GPX track and the same photo, I get the INF value again.
Tags:
Steps To Reproduce:
Additional Information:
Attached Files: geosetter-inf.PNG (6,121 bytes) 2019-04-20 00:44
https://geosetter.de/mantis/file_download.php?file_id=777&type=bug
Notes
(0003718)
Erik Krause   
2019-05-12 23:13   
Could you provide the relevant GPX track? I guess INF stands for infinity and probably is the result of a division by zero or alike.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
2036 [GeoSetter] User Interface trivial always 2019-05-06 17:55 2019-05-06 17:55
Reporter: tman39 Platform:  
Assigned To: OS: Windows 10  
Priority: low OS Version:  
Status: new Product Version: 3.5  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Error message on startup
Description: Using Geosetter 3.5.0 (Build 2188)

When I start Geosetter, I get an error msg in the map window =
"This page can't load Google Maps correctly"
even tho Map selection is set to "Open Street Map".

Is this a bug or am I doing something wrong?
Larry J
Tags:
Steps To Reproduce:
Additional Information:
Attached Files:
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
1105 [GeoSetter] User Interface minor always 2014-01-18 12:19 2019-05-03 14:52
Reporter: joergens_mi Platform:  
Assigned To: Friedemann OS:  
Priority: normal OS Version:  
Status: assigned Product Version: 3.4.16 beta  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Probleme beim zuweisen der Richtung
Description: In großen Vergrößerungen ist der Rot-Weiß-Blaue Zuweisungspunkt für die Richtung regelmäßig außerhalb des Bildes, weswegen man um ihn zu erreichen entweder die Zoom-Stufe deutlich ändern oder sich entlang der roten Linien durch panning dorthin hangeln muß.

Kann man nicht dafür sorgen, daß der Anfaßpunkt sich bei Zuweisung zu einem neuen Punkt innerhalb des dargestellten Kartenausschnittes bleibt. Das die Richtung wie bisher beibehalten wird wäre sehr angenehm.

Das beigefügte Bild zeigt links das Problem und rechts die nötige Änderung in der Zoomstufe.

Übrigens ich nutze die 3.4.16 stabil nicht beta (Die stabil ist in der Mantis Liste nicht zu finden)
Tags:
Steps To Reproduce:
Additional Information: Trotz der oben aufgeführten Fehlermeldung. Es ist ein exzellentes Tool, das mir sehr hilft Aufnahmen, Auch Teilaufnahmen an Gebäuden in kurzer Entfernung sehr gut zu verorten und zu verschlagworten. Alle wichtigen Möglichkeiten zum Beschreiben der Bilder sind gegeben.

Manchmal wäre es noch angenehm wenn man aus dem Tool heraus die aktuelle Brennweite (mit und ohne crop-faktor) oder den Blickwinkel (diesen am besten durch zwei Anfasser am Ende des blauen Dreiecks) angeben könnte.

Bei einigen Optiken werden von den Herstellern keine Brennweite eingetragen und bei gestitchten Panoramaphotos stimmen die Winkel oft nicht. Zur Zeit behelfe ich mir da mit händischen Aktionen mit dem exiftool.
Attached Files: mantis_prob.jpg (613,878 bytes) 2014-01-18 12:19
https://geosetter.de/mantis/file_download.php?file_id=360&type=bug
mantis_003.png (380,123 bytes) 2014-04-29 17:21
https://geosetter.de/mantis/file_download.php?file_id=365&type=bug
mantis_004.png (861,574 bytes) 2014-04-29 17:22
https://geosetter.de/mantis/file_download.php?file_id=366&type=bug
mantis_005.png (1,338,156 bytes) 2014-04-29 17:22
https://geosetter.de/mantis/file_download.php?file_id=367&type=bug
mantis_006.png (46,669 bytes) 2014-04-29 17:39
https://geosetter.de/mantis/file_download.php?file_id=368&type=bug
Notes
(0002036)
mmm   
2014-04-29 15:38   
Auch für mich wäre es wünschenswert, wenn der Zuweisungspunkt beim Zoomen innerhalb des Kartenausschnitts bleiben würde. Es ist doch ein größerer zusätzlicher Zeitaufwand, da ich bei fast jedem Foto die Richtung korrigieren muß, da das GPS-Modul den Aufnahmewinkel selten genau richtig liefert.

Manfred
(0002038)
Friedemann   
2014-04-29 16:20   
Hallo,

zu dem "Anfasspunkt" der Aufnahmerichtung: Wenn diser Punkt rot/weiß/blau ist, dann beinhaltet das Foto auch eine Zielkoordinate, welche durch diesen Punkt dargestellt wird. Die wird halt dort dargestellt wo sie sich befindet, evtl. außerhalb des Kartenausschnittes. Enthält das Bild keine Zielkoordinate, sondern nur einen Winkel, dann wird der Punkt nur in lila dargestellt und sollte sich eigentlich auch immer im Kartenausschnitt befinden. Kann sein, dass es da noch etwas hakt. Das schaue ich mir mal an.

Alternativ zum Anfassen an dem Punkt, kann man den Bildwinkel auch durch Verschieben des Bildmarkers selbst verändern. Wenn man den mit der Maus verschiebt, dann kommt eine Nachfrage, ob man das Bild verschieben möchte (nein), oder aber den Blickpunkt hinzufügen bzw. verschieben möchte (ja). Damit ist es vielleicht einfacher.

Ob der Blickpunkt als Koordinate im Bild gespeichert wird oder nicht, das kann man in den Programmeinstellungen angeben ("GPS-Zielkoordinaten speichern"). Bei einem Doppelklick auf das Bild, also im Datenbearbeitungsdialog (Strg+E) sieht man auch, ob da eine Koordinate steht oder nur ein Winkel.
(0002041)
mmm   
2014-04-29 17:17   
Hallo Friedemann,

ich habe das mit dem Verschieben des Bildmarkers sofort getestet. Leider wird dann auch der Aufnahmewinkel auf einen völlig anderen Wert gesetzt.
(Ist die Ursache dieses Problems mit dem Aufnahmewinkel ähnlich dem Problem 001134 ?)

Den Wert "GPS-Zielkoordinaten speichern" in den Programmeinstellungen hatte ich bisher übersehen. Damit erspare ich mir die ExifTool-Kommandos, die ich bisher verwendete. Danke für den Hinweis.

Manfred
(0002042)
joergens_mi   
2014-04-29 17:38   
Danke für die erste Antwort, und ich scheine nicht der einzigste zu sein.

Mein Vorgehen bei Bildern ohne jegliche Koordinaten.

- Suchen der Kameraposition in der Karte (Google, Einstellung satellit)
- Auswählen des Bildes
- Setzen des roten Markers (kkordinate ist eingetragen)
- Setzen des Winkelmarkers (blau mit grünem +) Ergebniss (mantis_003.png)
- Verschieben bis Zielpunkt sichtbar, typischerweise 1 bis 1.5 Kartenausschnittslängen (mantis_004.png) Zielpunkt ist Rot weiss Blau (Richtung und Ziel obwohl von mir nicht gesetzt sind eingetragen) (mantis_006.png)
- Ziehen des rotweisblauen Markers in das selbe Feld wie den Startpunnkt
- positionieren auf den Zielpunkt
- Nächstes Bild
- setzen roter Marker ok
- setzen Blau grüner Marker, wieder außerhalb des Bildes.
- und von vorne

Ursache könnte vielleicht meine gewählte Vergrößerung sein.
Es scheint so zu sein, daß wenn ich die Karten um 3 Minus Klicks verkleinere, daß dann der rot weiss Blau Punkt zumindest in der Karte bleibt. (mantis_005.png)

Vielleicht wäre es hilfreich im Falle der fehlenden Zielkoordinate, den Vektor als default Halb so lang wie die sichtbare Kartengröße ist zu machen.

Danke für die Hilfe und ich hoffe meine Schilderung meiner Arbeitsweise hilft dir weiter. Ich photographiere viele Kirchen und das relativ kleinteilig, so das ich ich viel Koordinaten im Nahbereich habe.

Wenn ich mit der Kamera Pentax K-5 und K-3 und dem zugehörigen GPS-Modul O-GPS1 arbeite, stimmt die Position zwar nicht hundertprozentig - die Ursache ist systematisch und ich kenne sie - die Richtung ist immer perfekt übernommen. Zielkoordinaten trägt die Kamera keine ein und das Problem bleibt bestehen.


Danke für die Unterstützung
(0002043)
Friedemann   
2014-04-29 18:47   
Ich verstehe das Problem noch nicht so ganz bzw. müsste doch der beschriebene Workaround mit dem Verschieben des Markers funktionieren. Hier ein Video welches ich gerade gemacht habe: http://goo.gl/r0Ai47 Ich glaube in der Version 3.4.16 war tatsächlich mal ein Fehler drin, dass der Winkel irgendwie auf 0 gesetzt wurde. Aber in der aktuellen Betaversion sollte das doch passen: http://www.geosetter.de/geosetter_beta.exe
(0002044)
joergens_mi   
2014-04-29 19:07   
Hallo Friedemann,
danke, dank des Videos habe ich den "Workaround" jetzt begriffen. Er funktioniert auch bei maximaler Zoomstellung. Das Problem in der 3.4.16 ist tatsächlich sporadisch vorhanden (interessierte mich aber bisher nicht). Das geschilderte Problem besteht zwar weiter, ist aber dank des Workarounds für mich nicht mehr wichtig.

Womit hast du das Video erstellt, vielleicht kann ich dann bei Gelegenheit das Problem filmen, falls es dich interessiert.

Entschuldigung, das ich nicht die neueste Beta nutze, ich bin etwas konservativ mir ist die stable sicherer.

Da ein Teil etwas off topic ist, kannst du mir es auch über joergens.mic at gmail.com per mail zukommen lassen.


Freundlich Grüße und Danke für die Hilfe (Lösung)

joergens.mic
(0002045)
Friedemann   
2014-04-29 19:25   
Das Video habe ich mit SnagIt gemacht, kann ich sehr empfehlen! Und was das "stabil" angeht: Ich würde mal sagen, dass die "Betaversion" nicht wissentlich unstabiler ist als die offizielle, 3 Jahre alte Version. Die Wahrheit ist auch, dass ich es zeitlich immer nicht hinbekommen habe oder keine Lust hatte, die Betaversion mal zur offiziellen Version zu erheben, mit allem was dazu gehört, also Änderung der Webseite etc. Sicher sind in der Betaversion auch Fehler, aber die sind in der 3.4.16 auch ;-) Da die Sicherheit der Bilddaten eigentlich nicht von GeoSetter abhängt, sondern eher von ExifTool, empfehle ich eigentlich relativ guten Gewissens die Betaversion...
(0002047)
mmm   
2014-04-29 19:43   
Hallo Friedemann,
danke für das Video. Jetzt verstehe auch ich das Verschieben. Durch diese Vorgehensweise ist mein oben beschriebenes Problem gelöst.
Übrigens: ich verwende 3.4.50 BETA, somit auch in dieser Version ok.

Manfred
(0003717)
kevlevrone   
2019-05-03 14:52   
At the moment I'm using the Google Maps JavaScript API for showing and processing the map, it does not depend on the data of the map itself. So offline using is not possible because a connection to the Google server has to be used. https://goo.gl/KyvnZF
I'm thinking about using OpenLayers instead. Then it would be possible to use a local map server (if the user wants to) with any map data the user wants to use. Unfortunately, some things are not so easy to manage with OpenLayers, for example simply dragging and moving markers in the map. Maybe this will be easier with coming OpenLayers 3.
BTW: I'm working hard on a new version of GeoSetter, but I think it will take a few months until it's finished.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
2035 [GeoSetter] User Interface minor always 2019-04-29 22:07 2019-04-30 17:34
Reporter: Ticarlo64 Platform: PC Desktop  
Assigned To: OS: Win7 Premium Family Ed. 64bits  
Priority: normal OS Version: Win7 SP1 -x64  
Status: new Product Version: 3.5  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Content of "Artist" field displays a blank when "XMP Toolkit=XMP Core 4.4.0-exiv2" even when "xmp-tiff:artist" has valid data.
Description: I use GeoSetter 3.5.0 build 2188 as one of 4 different programs to edit the metadata in my photos. I am migrating my photos over to my new Synology NAS DS216J and I am using the Photo Station (supplied by Synology) to manage my photos with the Synology NAS Media Server.

When I was editing the metadata of one of my photo folders, I typically did the following:
1) I used ExifToolGUI application (with ExifTool v11.11) to set (amonst other things) the tag "xmp-tiff:artist = my name" on all pictures. (XMP Toolkit=Image::ExifTool 11.11)
2) When I viewed the same folder in GeoSetter (with Display mode capable to view the field "artist"), I can see my name OK in the artist column and is also OK in the artist field available in the Edit Window.
3) I then use GeoSetter (with latest ExifTool version) to set GPS and Location fields, photo description, ... --> all OK --> artist field is still OK = my Name. (XMP Toolkit=Image::ExifTool 11.33 or latest)
4) Then I use the Synology Photo Station program to define the people in the picture (name and rectangle regions). The XMP Toolkit becomes "XMP Core 4.4.0-exiv2".
5) When I go back in GeoSetter to check if the changes to my metadata are OK --> the column "artist" is now BLANK in BOTH the Display View and the Edit View of the artist field, even when the ExifTool View shows the photo tag xmp-tiff:artist tag = my name.
6) If I reuse ExifToolGUI or GeoSetter to modify anything in the photo metadata, the XMP Toolkit value becomes different than XMP Core 4.4.0-exiv2, and then the artist field reappears as normal with My Name in it.
CONCLUSION: Every single photo that is edited last with Photo Station ( and setting XMP Toolkit = XMP Core 4.4.0-exiv2) have the same problem for displaying the "artist" value.
Tags: XMP
Steps To Reproduce: 1) In a jpg photo, Set the tag xmp-tiff:artist to "ABC" with ExifTool or with GeoSetter. Then take a note of the value of the tag XMP Toolkit.
2) Using GeoSetter, check that the artist column displays normally="ABC"
          a) in Display Report View --> Artist="ABC"
          b) in Edit Mode Window --> Artist="ABC"
          c) in ExifTool Window, the tag xmp-tiff:artist = "ABC"
          d) in ExifTool Window, the tag XMP Toolkit is NOT equal to XMP Core 4.4.0-exiv2
3) Next, use the Synology application Photo Station, modify anything in the photo metadata that is editable within Photo Station --> Photo Station uses the XMP Toolkit = XMP COre 4.4.0-exiv2 to write the modified metadata in the jpg photo file header.
4) Go back to GeoSetter and view the same photo again --> the problem will now be present.
          a) in Display Report View --> Artist=BLANK
          b) in Edit Mode Window --> Artist=BLANK
          c) in ExifTool Window, the tag xmp-tiff:artist = "ABC" (no change to the tag content in the photo header)
          c) in ExifTool Window, the tag XMP Toolkit is now EQUAL to XMP Core 4.4.0-exiv2

Additional Information: Option 1 - If you want to have access to Photo Station, the Synology Web site offers a Demo Server where one can test the SYNOLOGY Desktop Station Manager and other Synology application (such as Photo Station) for free for 30 minutes.
Option 2 - you can use my sample photos + sample metadata files below (with and without the problem XMP Toolkit = XMP Core 4.4.0-exiv2)
Option 3 - you can email me in private and we can setup a collaborative remote session on my PC (with TEAM VIEWER + Skype) so that I can show you the problem in a live session.

Note 1: I used ExifToolGUI metadata export feature to extract all the photo metadata as *.TXT files (before and after every steps of my tests), and I used the "compare with ... " feature of Sublime Text to view the differences in these TXT files. I noticed that when the XMP Toolkit switches from ExifTool::Image 11.38 to XMP Core 4.4.0-exiv2, the tags in the photo header are rearranged (i.e. moved around) significantly. This could be a clue as to the root cause to the problem.
NOTE 2: Even when the photo was last modified by Photo Station (and XMP Toolkit=XMP COre 4.4.0-exiv2), the two ExifTool applications that I use can still read and report the photo metadata correctly (and the artist field is still OK). It is ONLY inside the GeoSetter Display Window (and in the Edit Window) that the artist data retrieved by GeoSetter from the photo metadata is not displayed correctly when the Toolkit= XMP COre 4.4.0-exiv2.
System Description i5-3570 CPU / 16 GB RAM
- ExifToolGUI v5.16.0.0 by Bogdan Hrastnik (with ExifTool by Phil Harvey v11.11)
- GeoSetter v 3.5.0 (build 2188) (current ExifTool by Phil Harvey v11.38)
- Synology NAS DS216j running DSM v 6.2.1-23824 Update 6
- Photo Station (by Synology) v 6.8.11-3489
Attached Files: 3_Both.JPG (44,601 bytes) 2019-04-29 22:17
https://geosetter.de/mantis/file_download.php?file_id=781&type=bug
4_WithProblen_EditMode.JPG (31,757 bytes) 2019-04-29 22:17
https://geosetter.de/mantis/file_download.php?file_id=782&type=bug
5_NoProblem_EditMode.JPG (29,821 bytes) 2019-04-29 22:17
https://geosetter.de/mantis/file_download.php?file_id=783&type=bug
RedToolbox_noProblem.JPG (1,050,884 bytes) 2019-04-29 22:17
https://geosetter.de/mantis/file_download.php?file_id=784&type=bug
RedToolbox_noProblem_T0_DataDefinedInGeoSetter.txt (10,318 bytes) 2019-04-29 22:17
https://geosetter.de/mantis/file_download.php?file_id=785&type=bug
RedToolbox_WithProblem.JPG (1,050,205 bytes) 2019-04-29 22:17
https://geosetter.de/mantis/file_download.php?file_id=786&type=bug
RedToolbox_WithProblem_Compare_XMP_Meta_T0_T1.JPG (143,984 bytes) 2019-04-29 22:17
https://geosetter.de/mantis/file_download.php?file_id=787&type=bug
1_No Problem.JPG (150,614 bytes) 2019-04-30 17:34
https://geosetter.de/mantis/file_download.php?file_id=788&type=bug
2_WithProblem.JPG (162,564 bytes) 2019-04-30 17:34
https://geosetter.de/mantis/file_download.php?file_id=789&type=bug
RedToolbox_WithProblem_T0_DataDefinedInGeoSetter.txt (10,320 bytes) 2019-04-30 17:34
https://geosetter.de/mantis/file_download.php?file_id=790&type=bug
RedToolbox_WithProblem_T1_ModDescrInPhotoStation.txt (10,761 bytes) 2019-04-30 17:34
https://geosetter.de/mantis/file_download.php?file_id=791&type=bug
Notes
(0003716)
Ticarlo64   
2019-04-30 17:34   
Add final files that were not successfully loaded in mylast 2 attempts.
There shoud be a total of 11 files now!


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
2032 [GeoSetter] User Interface major always 2019-04-14 11:06 2019-04-24 23:24
Reporter: Egon1 Platform: PC  
Assigned To: heiko OS: W10  
Priority: urgent OS Version: 1809  
Status: resolved Product Version:  
Product Build: Resolution: no change required  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Fehler beim Abrufen der geografischen Höhe. Fehler beim Prüfen auf Updates.
Description: Fehler beim Abrufen der geografischen Höhe wird folgender Fehler angezeigt:
http://api.geonames.org
Beim Abrufen der Höhendaten ist ein Fehler bzw. Timeout aufgetreten.
Eventuell ist der benutzte Webservice zur Zeit nicht verfügbar.
Versuchen Sie es zu einem späteren Zeitpunkt nochmal... (siehe Anhang 1)

Fehler beim Prüfen auf Updates.
Es wird folgender Fehler angezeigt:
To check for an update failed.
Perhaps your internet connection is not available. (siehe Anhang 2)

Meine Geosetter Version ist 3.4.82 (Build 2184). Die kann aus dem Menü oben nicht ausgewählt werden.
Tags: altitude, exif
Steps To Reproduce: An mehreren Tagen hintereinander getestet.
Additional Information:
Attached Files: Anhang 1.jpg (267,224 bytes) 2019-04-14 11:06
https://geosetter.de/mantis/file_download.php?file_id=775&type=bug
Anhang 2.jpg (37,765 bytes) 2019-04-14 11:06
https://geosetter.de/mantis/file_download.php?file_id=776&type=bug
xml_1.jpg (168,750 bytes) 2019-04-23 11:05
https://geosetter.de/mantis/file_download.php?file_id=778&type=bug
xml_2.jpg (127,479 bytes) 2019-04-23 11:05
https://geosetter.de/mantis/file_download.php?file_id=779&type=bug
xml_3.jpg (140,682 bytes) 2019-04-23 11:05
https://geosetter.de/mantis/file_download.php?file_id=780&type=bug
Notes
(0003705)
heiko   
2019-04-15 19:02   
ist es möglich, dass zu dem Zeitpunkt der Fehlermeldungen die Internetverbindung wirklich nicht vorhanden war?
(0003706)
Egon1   
2019-04-16 08:21   
Hallo,
eben wieder probiert.
Internetverbindung ist vorhanden. (Mail + ping geht)
(0003707)
Egon1   
2019-04-16 08:48   
Hallo,
habe eben GeoSetter 3.5.0 (Build 2188) und ExifTool 11.36 installiert.
Keine Änderung
(0003708)
Egon1   
2019-04-21 18:00   
Hallo,
auf einem 2. PC erhalte ich keine Fehler.
Liegt das vielleicht an der Firewall?
(0003709)
heiko   
2019-04-21 22:41   
das kann natürlich ein Grund sein. Ich würde die Firewall zum Test einfach einmal ausschalten. Wenn das der Grund für das Problem ist, dann kannst du ja eine entsprechende Firewall Regel erstellen.
(0003710)
Egon1   
2019-04-22 19:18   
Hallo
habe ich getestet und hat nichts gebracht.
(0003711)
heiko   
2019-04-22 20:46   
wird bei folgendem Aufruf eine Fehlermeldung oder ein Ergebnis zurück geliefert?
http://api.geonames.org/srtm3XML?lat=47.588956&lng=10.544369&username=geosetter&style=full
(0003712)
Egon1   
2019-04-23 11:05   
Hallo,
mir ist nicht klar, was Aufruf bedeuted.
Beim Doppelklick auf den Link in Ihrer Notiz wird folgendes angezeigt. (xml_1.jpg)
Nach dem Download der xml Datei und Doppelklick darauf wird folgendes angezeigt. (xml_2.jpg)
Im Dateifenster von Geosetter werden nur jpg Dateien angezeigt.
Nachdem ich die angefangende Stunde abgewartet habe, habe ich erneut den Link in Ihrer Notiz "gedoppelklickt". Es wird folgendes angezeigt. (xml_3.jpg)
(0003713)
heiko   
2019-04-23 20:04   
na dann denke ich, dass wir das Problem gefunden haben. Mit dem Link wird eine Höhenabfrage bei GeoNames durchgeführt. Für die Abfrage wird der Benutzername "GeoSetter" verwendet. Diesen Benutzernamen verwendet GeoSetter auch, wenn man keinen eigenen Account bei GeoNames angelegt. Ich war zwar der Meinung, dass GeoSetter eine "vernünftige" Fehlermeldung ausgibt, wenn das stündliche Limit erreicht ist, aber das schein wohl doch nicht der Fall zu sein.

Ich würde an deiner Stelle einen eigenen Account bei GeoNames anlegen (der ist kostenlos). Den Account kann man unter http://www.geonames.org/login erstellen. Wenn der Account angelegt und aktiv ist, dann kann der Accountname in den Optionen im Reiter Internet eingegeben werden.

Ich hoffe, dass dann die Höhenabfrage auch wieder funktioniert.
(0003714)
Egon1   
2019-04-24 07:22   
Hallo,
ich hatte einen Account. (Nutzer Egon1)
Mit diesem Account erhalte ich immer noch Fehler.
Nachdem ich den Namen entfernt habe, funktioniert geosetter wieder (mit Standardname "GeoSetter")
Nun ist mir aufgefallen, das nach der Anmeldung mit "Egon1" "Welcome egon1" angezeigt wird.
Eine Anmeldung mit "egon1" funktioniert auch. Nun habe ich in den Internet Einstellungen "egon1" eingetragen. Und es funktioniert wieder.
(0003715)
heiko   
2019-04-24 23:24   
ich habe noch im Hinterkopf, dass man nach dem Erstellen des GeoNames Accounts diesen auch noch für die Webservices freischalten musste .. aber gut, dass es jetzt funktioniert, das ist die Hauptsache


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
2033 [GeoSetter] User Interface minor always 2019-04-19 11:28 2019-04-19 11:28
Reporter: pbb Platform:  
Assigned To: OS:  
Priority: normal OS Version:  
Status: new Product Version: 3.5  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Subsecond values are trimmed from GPX track
Description: It looks to me like GeoSetter trims the subsecond values from timestamps in GPX tracks. Not rounding off the numbers to the nearest second, but simply removing the subsecond part.
Tags:
Steps To Reproduce: I have a GPX track where to points that follow eachother have the timestamps "...:21:01.714" and "...:21:03.000". I have three photos with timestamps "...:21:01", "...:21:02" and "...:21:03" (no subseconds in the photo timestamps).

Synchronizing these photos with the GPX track, places the first photo on the "...:21:01.714" point of the track, the last photo on the next point, and the middle photo in between. In reality, the middle photo should have been very close to the "...:21:01.714" point of the track.

I can only explain this behaviour by assuming the subsecond part of the GPX timestamps is simply discarded, meaning the "...:21:01.714" point of the track is treated as being "...:21:01".
Additional Information:
Attached Files:
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
1997 [GeoSetter] Image Data feature always 2018-11-03 18:10 2019-04-14 05:42
Reporter: rturnock Platform:  
Assigned To: OS:  
Priority: normal OS Version:  
Status: new Product Version: 3.5  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Unable to access .HEIC files (HEIF)
Description: HEIC files do not appear and cannot be selected since they are a relatively new format. Consequently Geosetter cannot be used with these files.
Tags:
Steps To Reproduce: Open a folder that includes both .JPG and .HEIC files and even without a filter applied only the .JPGs appear.
Additional Information: Perhaps a work around might be possible. If an HEIC file is renamed to be a JPG, edited in Geosetter, and named back can changes be made without affecting the image?
Attached Files:
Notes
(0003604)
Malcolm_Ferguson   
2018-12-08 00:13   
Geosetter relies on ExifTool to read and modify metadata. The current version is 11.21, and it only has the ability to read the metadata from HEIC files, and no way to write it. Keep an eye here though for updates: https://sno.phy.queensu.ca/~phil/exiftool/#supported

There are various free ways to convert these to JPEG without sharing your photos, although invariably this requires an iPhone or Mac. Mac has a command line utility called ‘sips’ that will preserve the metadata during conversion to JPEG. The Image Capture app has a checkbox bottom-left to keep originals or convert them during copy from my iPhone. And the iPhone itself has an option in the settings to automaticallly convert pictures to a compatible format if you’re on Windows. Yes, all of this loses the extra colour space data, loses the bitrate savings and loses some detail, but maybe this isn’t important given that images came from a mobile phone camera (not exactly high quality in the first place)
(0003704)
Malcolm_Ferguson   
2019-04-14 05:42   
ExifTool now supports writing to HEIC files.

Lightroom creates XMP files when saving metadata for HEIC files (i.e. treats them as a read-only RAW).

I have a Mac based workflow with GeoSetter running in a virtual machine. I get GeoSetter to work with my HEICs as follows:
1) Save metadata from Lightroom
2) Use the 'sips' command that comes with macOS to create JPEG sidecars
3) Make metadata settings in GeoSetter, which updates the sidecar
4) Read the metadata back in to Lightroom
5) Delete the JPEGs.

There is another bug in GeoSetter that's a bit annoying: with this setup all files appear duplicated if I show files recursively, so I have to go folder to folder. Maybe it gets confused by JPEGs with XMP sidecars?

This is the script I use to batch convert all the HEICs to JPEGs:

#!/usr/bin/env python

import sys
import os
import fnmatch
import subprocess
from distutils import file_util

if len(sys.argv) != 2:
    print("Specify root directory to parse from")
    sys.exit(1)

root_dir = sys.argv[1]

if False == os.path.isdir(sys.argv[1]):
    print("Directory '" + root_dir + "' doesn't exist")
    sys.exit(1)

print("Scanning '" + root_dir + "' ... ")

pattern = '*.HEIC'
for root, dirs, filenames in os.walk(root_dir):
    for f in fnmatch.filter(filenames, pattern):
        fullpath_RAW = os.path.join(root, f)
        fullpath_JPG = os.path.join(root, os.path.splitext(os.path.basename(fullpath_RAW))[0] + ".jpeg")

        print("Processing " + f + "...")
        print("\tRAW: " + fullpath_RAW)
        print("\tJPG: " + fullpath_JPG)
        subprocess.call(["sips", "--setProperty", "format", "jpeg", "--setProperty", "formatOptions", "30", fullpath_RAW, "--out", fullpath_JPG])

        print("\n")

And when I'm finished, I replace "<<ROOT_FOLDER>>" in this command:
find <<ROOT_FOLDER>> -name "*.jpeg" -print0 | xargs -0 -I {} rm "{}"


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
2031 [GeoSetter] User Interface feature have not tried 2019-04-12 22:19 2019-04-12 22:19
Reporter: pbb Platform: PC  
Assigned To: OS: Windows  
Priority: normal OS Version: 10  
Status: new Product Version: 3.5  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Going from Google Maps to Leaflet
Description: I don't know if this is in any way helpful. But "GPX Editor" is an open source Delphi application that has recently switched from integrating Google Maps to using Leaflet. This might help the author of GeoSetter (which as I understand it is also written in Delphi) if he wants to switch away from Google Maps.

The source code is available at https://sourceforge.net/projects/gpxeditor/files/.
Tags:
Steps To Reproduce:
Additional Information:
Attached Files:
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
2030 [GeoSetter] User Interface feature always 2019-04-11 21:03 2019-04-11 21:03
Reporter: pbb Platform: PC  
Assigned To: OS: Windows  
Priority: normal OS Version: 10  
Status: new Product Version: 3.5  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Request: Support for GPS tracks with (partially) missing timestamps
Description: Currently, the map module has no problem displaying GPS tracks with missing time stamps; the whole track with all points is being displayed.

However, when synchronising images with these tracks, something weird happens. All images surrounding a GPS point without timestamp, are moved to the nearest point with timestamp.

Say I have 100 photos and a GPS track with 10 points defined, these correspond to photo 0, 10, 20, etc. However, point 5 (corresponding to photo 50) does not have a timestamp. When I now synchronise all photos to the track, then photos 0-40 and 60-100 are nicely put on the track by interpolating their timestamp with the GPS track. But photos 41-50 are all put together with photo 40, and 51-59 are all put together with photo 60. If I completely delete point 5 from the GPS track, then photos 41-59 are nicely interpolated between GPS point 4 and 6.

If this could be fixed, then it would really help me geotag large amounts of photos. I could create a timeless GPS track (for example using OpenRouteService), add the timestamps to only a few of the GPS points, and then have all my photos positioned correctly along the GPS track. (Assuming I kept a constant speed...)
Tags: GPS trace
Steps To Reproduce: - Take a large collection of photos.
- Add GPS coordinates to the first, the last, and a few random photos in between.
- Select those photos and create a GPS track (File > Export to GPX Track File).
- Select all photos and synchronise them with the track (Edit > Synchronise with GPS Data Files). Notice how all photos are nicely distributed over the track.
- Open the track in a text editor, and remove the timestamps from some of the points.
- Re-open the GPS track in GeoSetter, and again synchronise all photos with the new track. Notice now how photos are clustered along the last trackpoint before and the first trackpoint after the point that doesn't have a timestamp.
Additional Information:
Attached Files:
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
2029 [GeoSetter] Image Data major have not tried 2019-04-05 17:01 2019-04-05 22:00
Reporter: Schmetzer Platform:  
Assigned To: heiko OS:  
Priority: normal OS Version:  
Status: resolved Product Version: 3.5  
Product Build: Resolution: no change required  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Google Karten Fehlermeldung
Description: Heute Vormittag einwandfreie Kartendarstellung der Google Karten,
am Nachmittag wieder die bekannte Fehlermeldung:
For development purposes only
Tags:
Steps To Reproduce:
Additional Information: Liegt der Fehler an meinem System? Win 10, Edge, IE 11, ....
Ich habe alles aktualisiert
Attached Files:
Notes
(0003702)
heiko   
2019-04-05 21:59   
es liegt nicht am System, sondern an den Bezahlbedingungen von Google. Hier ist es etwas genauer beschrieben: http://www.geosetter.de/mantis/view.php?id=1970


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
2025 [GeoSetter] User Interface minor always 2019-02-22 20:20 2019-02-24 22:52
Reporter: Katermerlin Platform: Fujitsu Celsius W370  
Assigned To: OS: Win10Pro(32)  
Priority: normal OS Version: 1809  
Status: new Product Version: 3.5  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Bei Verwendung des "Hoher-Kontrast" Modus keine Kartenanzeige
Description: Verwendet man den "Hoher Kontrast" -Anzeigemodus, bleibt das Kartenfenster leer.
Tags:
Steps To Reproduce: Hin- u.- Herschalten zwischen normalem Ansichts-Modus und "Hoher Kontrast"-Modus mit ALT+UMSCH+DRUCK
Additional Information: Trat nach Update auf WinVer 1809 auf, hat aber damit nichts zu tun.
Attached Files: Fehler Geosetter.jpg (92,319 bytes) 2019-02-22 20:20
https://geosetter.de/mantis/file_download.php?file_id=771&type=bug
Notes
(0003695)
Erik Krause   
2019-02-23 18:31   
Könnte das auch dieses Problem sein? http://www.geosetter.de/mantis/view.php?id=1970
(0003696)
Katermerlin   
2019-02-23 23:14   
...ich weiß nicht, muß das mal durcharbeiten. Ich glaub aber eher nicht. Das mit der Darstellbarkeit von Google Karten hat eine seltsame Wendung bekommen: Es scheint so zu sein, daß die Meldungen von Google nur an Arbeitstagen kommen. Am Wochenende funktioniert es seltsamerweise und ich kann (heute erst probiert) die Google-Karten ohne Einschränkung sehen...
(0003697)
Erik Krause   
2019-02-24 13:56   
Das ist nicht seltsam. Friedemann hat das Kontingent beschränkt. D.h. das nach einer bestimmten Anzahl Zugriffen die Einschränkung greift. Dauerhafte Abhilfe schafft nur eine eigene Abfrageseite mit eigenem API-Key, wie unter http://www.geosetter.de/mantis/view.php?id=1970 beschrieben. Das ist auch schon aus Gründen der Fairness geboten, weil (wenn ich das richtig verstanden habe) Friedemann sonst trotzdem Kosten entstehen.
(0003699)
Katermerlin   
2019-02-24 22:52   
Jetzt fange ich so langsam an, das zu verstehen das mit dem Kontingent... Mit dem eigenen API-Key muß ich mich mal befassen, das macht Sinn.

Jedoch ist das nicht das Problem daß ich gemeldet habe. Man kann es leicht provozieren, indem man zwischen normalem Ansichts-Modus und "Hoher Kontrast"-Modus mit ALT+UMSCH+DRUCK hin- und herschaltet bei geöffnetem Kartenfenster. Wenn ich OpenStreetMap gewählt habe und ALT+UMSCH+DRUCK mache, verschwindet die Anzeige im Kartenfenster und je nach Einstellungen für den Hohen Kontrast wird ein schwarzer, weißer oder andersfarbiger Hintergrund OHNE Bild gezeigt... Nach nochmaligem ALT+UMSCH+DRUCK ist man wieder in der Normalanzeige und die Karte ist wieder da...
Was etwas seltsam ist, daß links unten im Kartenfenster auch bei Benutzung von OpenStreetMap "Google" angezeigt wird... Warum?


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
2024 [GeoSetter] User Interface tweak always 2019-02-07 20:27 2019-02-07 20:27
Reporter: cpo Platform: Windows  
Assigned To: OS: Windows 10  
Priority: normal OS Version: 1809  
Status: new Product Version: 3.5  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Delete key to delete files when jpg files are selected
Description: I think it would be good to have a warning dialog before files are deleted when pressing the delete key. There could also be a setting to disable the warning in that case. Since in other programs used to modify jpg tags when there is a file list the delete key can be used to remove files from the interface rather than delete files, this can be confusing when moving between different programs.
Tags:
Steps To Reproduce:
Additional Information:
Attached Files:
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
2023 [GeoSetter] Image Data major random 2019-02-04 21:18 2019-02-04 21:18
Reporter: cbd Platform:  
Assigned To: OS: Windows 10  
Priority: normal OS Version: 1803  
Status: new Product Version: 3.5  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Assigns no or null value locations to some images
Description: Geosetter
I am encountering a problem where Geosetter says if can find gps information for all images, but it assigns correct locations to less than half of the files and some of those values are null (0,0).

I am trying to determine
1) if the problem I am encountering is a known error, and
2) if so, is there a known work around.
or maybe 3) user error

(If there is a different forum I should post this in, please point me in the right direction.)

I try to geotag a collection of images (.jpg) with a GPS track (.gpx). In geosetter under “sycrhonize with GPS Data Files”, it reports that it has found GPS data for all 239 images. But when I select yes to sync, it only assigns locations to 75 out of 239 images, and some of those assigned lat/long are null locations (0.0 South, 0.0 West). It assigns locations to the first and last images, and some of the images in the middle. There is no clear pattern of skipped images (ie., it does not select a regular interval of images or only a particular subsection of the flight).

The track is from a sUAS. The images are from a camera attached to the drone. All the camera images were taken within the time frame of the GPS track. The time offset between GPS clock and camera is known and was recorded at the time of data collection (1 sec; or 6:00:01 with the time zone correction).

I followed the general process of importing images, loading the gpx file, and selecting a matching image and point in the GPS track. Screenshots attached to document the full process. The last screenshot (05) shows the missing and incorrect data highlighted.

I have repeated this with the same dataset multiple times. I closed and restarted GeoSetter and rebooted my machine, made not difference. I have worked successfully with other datasets from the same camera and aircraft. There are no identifiable problems with the GPS track or image files.

Using GeoSetter 3.5 with Windows 10 (ver 1803)

Thanks in advance.
Tags:
Steps To Reproduce:

Additional Information:
Attached Files: geosetter-01_process.png (1,240,454 bytes) 2019-02-04 21:18
https://geosetter.de/mantis/file_download.php?file_id=767&type=bug
geosetter-02_process.png (46,444 bytes) 2019-02-04 21:18
https://geosetter.de/mantis/file_download.php?file_id=768&type=bug
geosetter-03_report-fails.png (38,334 bytes) 2019-02-04 21:18
https://geosetter.de/mantis/file_download.php?file_id=769&type=bug
geosetter-05_results-with-errors.png (184,108 bytes) 2019-02-04 21:18
https://geosetter.de/mantis/file_download.php?file_id=770&type=bug
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
2013 [GeoSetter] User Interface minor always 2018-12-26 21:11 2019-02-03 23:07
Reporter: u.b.muc Platform:  
Assigned To: OS: Windows 10 Pro 1803  
Priority: normal OS Version: 17134.472  
Status: new Product Version: 3.5  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: UI very slow
Description: Just installed v3.5 over existing previous non-beta version.
UI is very slow now. Some mouse clicks or key presses end up with one or two seconds of response time.
Examples:
- Starting the app until all of the screen is drawn
- Ctrl-E to open edit window: Several seconds to wait, regardless whether one or multiple images selected
- in the edit window, switching back and forth between images: a second per switch
and so on and so on

In general, seems way more sluggish than before.
Tags:
Steps To Reproduce:
Additional Information:
Attached Files: GEOSetterError.png (230,050 bytes) 2019-01-20 14:59
https://geosetter.de/mantis/file_download.php?file_id=762&type=bug
Notes
(0003652)
ceroni   
2019-01-19 23:12   
What happens if you change the map window from Google to OpenStreetMap?
(0003653)
u.b.muc   
2019-01-20 14:59   
No noticeable difference.
However, interesting side effect: Although map is set to OpenStreeMap, upon startup of the application, it still comes with a Google Maps related error message - see screenshot attached.
(0003654)
galeog   
2019-01-20 23:07   
I have the same problem, both with the latest and the previous version of Geosetter.
No matter what map I set, every minimal resize or drag of the map will result in a several seconds, if not minutes, wait.
The problem started a few days ago on both of my PCs. I am using Windows 10 on both PCs.
The only thing I noticed is that there was a little Windows Update not too long before the problem started.
I say "little update" because it took a very short time to accomplish.
(0003655)
galeog   
2019-01-20 23:26   
P.S. if it can be useful, the Windows update I was talking about is KB4023057 which happened on my PC on January 18 and you can find more info here:

https://support.microsoft.com/it-it/help/4023057/update-to-windows-10-versions-1507-1511-1607-1703-1709-and-1803-for-up

or, in German,

https://support.microsoft.com/de-de/help/4023057/update-to-windows-10-versions-1507-1511-1607-1703-1709-and-1803-for-up
(0003656)
ceroni   
2019-01-22 01:33   
According to Microsoft "This update includes reliability improvements to Windows Update Service components in Windows 10, versions 1507, 1511, 1607, 1703, 1709, and 1803"
I'm too experiencing the same problem but my Windows is 1809 (don't have this KB4023057 installed).
(0003675)
henrylw   
2019-01-26 07:10   
I'm having the same problem. Windows 10 version 1809
(0003678)
ceroni   
2019-01-26 13:44   
Please see my comment in https://www.geosetter.de/mantis/view.php?id=1970#c3677
(0003683)
WilfriedB   
2019-01-28 14:16   
Meanwhile, this problem was reported several times. So far no solution, but a workaround or at least reducing the lack by decreasing the size of the map panel drastically:
 https://www.geosetter.de/mantis/view.php?id=2019#c3662
(0003694)
galeog   
2019-02-03 23:07   
Tonight the problem seems to be solved: Maps load very quickly again!


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
2019 [GeoSetter] User Interface major always 2019-01-17 17:52 2019-02-01 16:48
Reporter: abr01 Platform:  
Assigned To: OS:  
Priority: urgent OS Version:  
Status: new Product Version: 3.5  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Geosetter friert ein, ist nicht mehr nutzbar
Description: Hallo Herr Schmidt,


seit heute funktioniert die Version 3.5 von Geosetter nicht mehr. Das Programm lädt keine Karte mehr, und friert dabei ein. Auch die Bildervorschau links friert mitten beim Aufbau ein.
Vielleicht hat Google erneut etwas geändert, denn bisher kam nur eine Fehlermeldung von Google, die man wegklicken konnte. Geosetter funktionierte trotzdem.

Nun kommt beim Schließen folgende Meldung:

Managing metadata (EXIT/IPTC/XMP) of image files reagiert nicht





Tags:
Steps To Reproduce: Geosetter starten.
Additional Information:
Attached Files:
Notes
(0003639)
heiko   
2019-01-18 16:34   
Funktioniert GeoSetter nach einem Neustart des Rechners wieder? Bei mir läuft die Version 3.5 problemlos.
(0003640)
abr01   
2019-01-18 17:10   
Nein, den Rechner hatte ich mehrfach neugestartet, dasselbe Problem leider.
(0003641)
abr01   
2019-01-18 18:28   
UPDATE: wenn ich Geosetter im Administratormodus starte, komme ich ein Stück weiter. Allerdings wird die Karte nicht vollständig angezeigt, und es ist etwas von "Developer Mode" als Muster
auf der Karte zu sehen. Danach friert es ein. Muß ich eine bestimmte neue Geo-URL angeben? Das hatte sich ja zwischendurch mehrfach geändert.

Liest eigentlich der Entwickler hier mit? Ich hätte doch gerne ein paar mehr Vorschläge, nachdem auch eine Neuinstallation nichts gebracht hatte. Oder wenigstens einen Vorschlag auf
ein alternatives Programm. Es ist für mich wichtig, Geodaten in Bildern zu taggen. Danke schonmal für die Mühe!
(0003642)
heiko   
2019-01-18 20:47   
Wurde vor einer Neuinstallation von GeoSetter das Verzeichnis %AppData%\GeoSetter auch gelöscht?

Eine Alternative um Bilder zu taggen ist z.B. Lightroom.
(0003643)
abr01   
2019-01-18 20:50   
Nein, das hatte ich noch nicht probiert. Ich hab eigentlich auch nicht vor unzusteigen, sondern suche nur etwas zur Überbrückung, bis Geosetter wieder bei mir läuft. Lightroom habe ich hier, aber nur Version 5, wo ich nicht wüsste, ob sie das auch kann.
Danke für den Hinweis!
(0003644)
heiko   
2019-01-18 21:01   
In Version 5 von Lightroom wurde die Karte abgeschalten, also ist das wohl keine Alternative.

Wurde denn an dem Rechner etwas geändert? Scheinbar hat GeoSetter ja schonmal funktioniert. Was für ein Betriebssystem ist denn installiert? Falls Win 10, wurde evtl. das Oktober Update eingespielt (Build 1809), das wurde die Tage von MS auf breiterer Ebene freigegeben.

Die Meldung "Developer Mode" in der Karte hängt übrigens mit den Einstellungen zur Bezahlmethode bei Google, die Friedemann Schmidt hinterlegt hat, zusammen.
(0003645)
abr01   
2019-01-18 21:12   
Nein, programmetechnisch wüsste ich nichts Neues. Aber eins fiel mir neulich shcon einmal auf. Manchmal, wenn ich Strg-G drückte, um alle Bilder in die Karte zu laden, blieb oft das "ok" Fenster ausgegraut. Da musste ich manchmal mehr als ein halbes Dutzend mal das Programm
neustarten, bin die Schaltfläche benutzbar war. Installiert ist Windows 10, Version 1803. Da hat sich also nicht geändert. Das Programm läuft übrigens so lange, bis ich auf den Kartenmode umschalten will, der ja die eigentliche Arbeitsfläche ist. Dann stürzt es ab.

Nur fürs Protokoll, die Karten-URL hier lautet: http://map.geosetter.de/v3/map_google.html

Ist das korrekt so?
(0003646)
abr01   
2019-01-18 21:17   
Was natürlich zwischendurch neu war, das sind wohl kb-Patches von Microsoft. Könnten die das nicht verursacht haben? Wobei ich sowas eigentlich noch nie hatte.
(0003647)
heiko   
2019-01-18 21:35   
(Last edited: 2019-01-18 21:35)
ich habe hier Win 10 Build 1803 mit den aktuellsten Patches von MS, bei mir läuft wie gesagt alles problemlos. Was schon vorgekommen ist, dass bestimmte Bilder zu einem Absturz geführt haben.

(0003648)
abr01   
2019-01-18 21:48   
Also, ich habe schon ältere Sessions getestet, gleiches Ergebnis, zumal ich mit dieser Kamera schon viele Bilder in geosetter bearbeitet habe. Sehr seltsam.
(0003649)
gehav   
2019-01-19 08:45   
Ich habe leider das gleiche (oder zumindest ein sehr ähnliches) Problem wie abr01 - seit ein paar Tagen friert Geosetter immer beim Start ein. Dann erscheint die Karte nach langer Zeit doch, aber Geosetter friert immer ein, wenn man die Karte bedienen möchte (zoomen). Das Programm ist damit leider plötzlich unbenutzbar geworden. Das passiert auf 2 PCs, sowohl in der portablen als auch in der installierten Variante. Es wird wohl an Windows Updates liegen, denn auf einem älteren Notebook mit Win10, das schon 2 Jahre lang keine Updates installiert hat, läuft Geosetter noch problemlos.
(0003650)
abr01   
2019-01-19 14:56   
Danke für die (wahrscheinliche) Bestätigung.
(0003651)
Franklin2K   
2019-01-19 17:41   
Ich habe das gleiche Problem, bis vor ein paar Tagen lief GeoSetter prima (mit eigenem API Key hinterlegt). Seit 3-4 Tagen jedoch hängt das Programm beim Start und vielen Aktionen.
Ich bin auf Windows 18 1809 inkl. aller Updates. Ich vermute auch, dass hier ein Update das Problem, verursacht.
(0003657)
abr01   
2019-01-22 14:30   
Eine Frage mal an die Entwickler, wird eigentlich schon an einer Problemlösung gearbeitet?
(0003658)
Thomas   
2019-01-22 18:57   
Ich hab' seit ein paar Tagen, genau das gleiche Problem, ebenfalls Win10, ebenfalls keine Änderungen am PC außer ggfs. WinUpdates.

Beim Starten von Geosetter kommt, wenn man lange genug wartet, eine Fehlermeldung, dass ein Skript sehr lange läuft. Wenn man dann anklickt, dass man das Skript abbrechen will, "funktioniert" Geosetter, aber ohne Karte (weder Google noch OSM).
Ich kann dann z.B. einen Location-Favoriten auswählen und dessen Daten Bildern zuweisen - halt "blind".
(0003659)
gehav   
2019-01-23 11:03   
@abr01: Geosetter wurde von einem Entwickler als Hobby in seiner Freizeit geschrieben. In den letzten Jahren hat sich kaum mehr was getan und ich fürchte daher, dass eine Lösung lange dauern könnte... Siehe auch: https://www.geosetter.de/2018/05/10/new-website-new-geosetter-de/
(0003660)
EkMaKro   
2019-01-23 12:49   
Seit einigen Tagen habe ich das gleiche Problem.
Geosetter 3,5 Windows 7 x64

Das Problem ist unabhängig vom gewählten Kartentyp.
Der Taskmanager zeigt, dass Geosetter die CPU dann dauerhaft stark beansprucht (allerdings ohne das ersichtlich was passiert).
Seltsamerweise hat heute das Programm ein paar mal zwischendurch wieder etwas schneller reagiert (aber immer noch deutlich verlangsamt), um dann wieder in die "Erstarrung" zu verfallen.
So ist das Programm leider nicht nutzbar !
(0003661)
abr01   
2019-01-23 13:40   
Das ist dann ja ganz schlecht. Was ich nicht verstehen kann, daß es offenbar so gut wie keine ähnlichen Programme gibt, auf die man ausweichen könnte. Wie kann das überhaupt angehen?
(0003662)
gehav   
2019-01-23 14:42   
Ich habe einen Workaround gefunden, der zumindest bei mir momentan funktioniert. Es ist keine schöne und saubere Lösung, aber ich komme damit zurecht. Wie EkMaKro schon richtig geschrieben hat, wird ja die CPU offenbar von der Kartenansicht völlig ausgelastet. Die "Lösung" für mich war also das Fenster der Kartenansicht so weit zu verkleinern, bis meine CPU nicht mehr zu stark ausgelastet war und die Navigation wieder halbwegs flüssig funktioniert hat. Wie gesagt, nicht optimal, aber ich kann mit Geosetter zumindest wieder arbeiten. Anleitung: ich habe die Kartenansicht abgedockt (kleiner Pfeil rechts oben in der Kartenansicht), dann kann man die Karte unabhängig vom restlichen Programm vergrößern oder verkleinern. Ich habe soweit verkleinert, bis alles flüssig funktioniert hat und dann wieder soweit vergrößert, bis es zu Ruckeln begonnen hat. Ich schätze, dass die Kartenansicht momentan nur mehr ca. 800x400 Pixel hat. Hoffe, diese Information kann jemandem helfen!
(0003663)
lamalate   
2019-01-23 17:03   
Même problème depuis la dernière mise à jour d'exiftool aujourd'hui.
(0003664)
lamalate   
2019-01-23 17:07   
J'ai remis la version précédente d'exiftool, soit la 11.25 depuis geosetter/tools.exiftool.bak et cela refonctionne normalement
Ich habe die vorherige Version von exiftool (11.25) von geosetter / tools.exiftool.bak geliefert und es funktioniert wieder
(0003665)
Franklin2K   
2019-01-23 20:46   
Bei mir tritt das Problem mit ExifTool 11.25 und 11.26 auf, ich glaube daher nicht, dass dies die Ursache ist...
(0003669)
abr01   
2019-01-25 20:51   
Gehav, guter Tipp! Auch wenn ich es etwas anders machen musste, da beim Klick auf die Registerkarte "Karte" der Absturz das Abkoppeln verunmöglichte. Ich habe das gesamte Programm daher stark verkleinert, dann geht es halbwegs (es kommen Fehlermeldungen bezüglich der karte selbst, von wegen Entwicklermodus, oder so).

Gibt es denn seitens der Entwickler hier schon Pläne, das soweit zu reparieren?
(0003686)
WilfriedB   
2019-01-28 14:26   
Danke gehav, der Tip scheint zu funktionieren!

Das Problem wurde hier inzwischen schon mehrfach gemeldet. In einem Thread wurde der Verdacht geäußert, es könne mit einem Windows Update (KB4023057?) zusammen hängen. Zeitlich könnte das bei mir auch zutreffen. Das letzte Windows Update war bei mir am 19.1. Seit wann ich die Probleme mit GeoSetter habe, kann ich allerdings nicht ganz genau sagen.
(0003689)
Franklin2K   
2019-01-29 10:10   
Der Tip funktioniert, Danke! Aber schön ist das natürlich nicht. Schade dass Friedeman sich hier nicht melden
(0003690)
Thomas   
2019-01-31 21:28   
... und heute funktioniert plötzlich wieder alles praktisch wie früher (mit OSM) - keine Idee, wieso ...
(0003691)
WilfriedB   
2019-01-31 21:40   
Stimmt! Auch das Google Satelliten Bild öffnete bei mir gerade sofort. Hoffentlich bleibt das so.
(0003692)
Franklin2K   
2019-02-01 16:48   
Tatsache, es klappt alles wieder wie vorher. Jetzt wäre natürlich interessant, was die Ursache des Problems war.
(0003693)
Franklin2K   
2019-02-01 16:48   
Tatsache, es klappt alles wieder wie vorher. Jetzt wäre natürlich interessant, was die Ursache des Problems war.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
2022 [GeoSetter] Image Data minor always 2019-01-29 14:01 2019-01-29 14:01
Reporter: SQuarmby Platform:  
Assigned To: OS:  
Priority: normal OS Version:  
Status: new Product Version: 3.5  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Feature Request: edit Taken Date by using another date information in the file
Description: Sometimes the Taken Date information in an image file is <blank>; for example images downloaded from mobile phones. This is annoying because many picture viewer applications use the Taken Date to sort the images; when this data is not available, other date information is used and this can mean that images appear in the wrong place in the timeline.

The Date tab of the Edit dialog box allows the Taken Date to be set to a fixed date (user defined) or be adjusted forward / backward by a fixed offset (user defined). The feature proposal is to include additional options for setting the Taken Date field.

This would be useful when a user is making a mass update of image files taken from the same device because the issue will be consistent; ie they will have the same missing / available data.

The additional options would be:
- set Taken Date to be equal to Created Date
- set Taken Date to be equal to Modified Date
The function should copy both the date and time information to the Taken Date field.

Note: the Edit tool already allows the Date Created to be set equal to the Taken Date... this proposal is to use the same process in reverse.

Note: an additional option would be to allow the Date Created to be set equal to the Modified Date.
Tags:
Steps To Reproduce: n/a
Additional Information: n/a
Attached Files:
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
2021 [GeoSetter] Image Data minor always 2019-01-24 02:30 2019-01-28 17:58
Reporter: KeB0 Platform:  
Assigned To: OS:  
Priority: normal OS Version:  
Status: new Product Version: 3.5  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Edit Data "Save as Template" Error
Description: If I try to save a template with some basic data, I get the error below. This is happening in 2 of my machines that run Win10 V1803 Runnig, Geosetter 3.5.0 Portable version. I haven't used this feature in a while, so I cannot verify when it was the last time it worked. I do use it when batching large amounts of photos. I don't know where the problem is, but it cannot write the XMP file. This is what is have done so far: I have clean all files in my Temp Folder; I have removed all files in the C:\Users\....\AppData\Roaming\Geosetter; And I have have runned Geosetter as Administrator. There is no XMP written on those directories.

The following error occured while trying to save the template::
Error: Zero-length file name - ''''
-o "C:\Users\KeB0\AppData\ Local\ Temp\ gs_templateQF2983A3.xmp" -orientation= 1 -execute -@ "C:\ Users\KeB0\AppData\ Local\ Temp\ et{)F2983A3.arg"
"C:\Users\KeB0\AppData\ Local\ Temp\ gs_templateQF2983A3.xmp" -execute -orientation= "C:\Users\KeB0\AppData\ Local\ Temp\ gs_templateQF2983A3.xmp'
1 image files created
0 image files updated
1 image files unchanged

Tags: XMP
Steps To Reproduce: Frankly this might only be happening to me.

Select any image, then Edit Data. then add Author or any field, and then click on "Save as Template". There is a short pause and then the error message appears.
Additional Information:
Attached Files: 24-01-2019 3-29-35 PM.png (14,594 bytes) 2019-01-24 08:48
https://geosetter.de/mantis/file_download.php?file_id=763&type=bug
Image 001 [2019-01-10].png (32,119 bytes) 2019-01-25 23:04
https://geosetter.de/mantis/file_download.php?file_id=764&type=bug
Image 001 [2019-01-25].png (24,728 bytes) 2019-01-25 23:07
https://geosetter.de/mantis/file_download.php?file_id=765&type=bug
26-01-2019 10-17-52 AM.png (192,750 bytes) 2019-01-26 03:18
https://geosetter.de/mantis/file_download.php?file_id=766&type=bug
Notes
(0003666)
Studia   
2019-01-24 08:48   
I believe that I am experiencing the same problem.
(0003667)
KeB0   
2019-01-24 21:30   
Yes, that's it Studia. I just did not attached the image. OK, so it not only me! I feel better..in a way!
(0003668)
Studia   
2019-01-25 04:19   
If only there was an explanation forthcoming or a fix?

I have uninstalled and completely eradicated from registry and reinstalled but no change.
(0003670)
KeB0   
2019-01-25 22:18   
Studia, Do you have an older version? I could only find version 3.1.2 and that feature was working fine! Is just too old version. Maybe you a have a previous version to install and try that! It's not that big of an issue, but I would just like to know if it's the application or my machine. I could make my own template, but i'm prone to make too many typing error and is a big pain the neck. Especially when you know that it can be done with a couple of mouse clicks and done! lol
 
The developer said on this web page about the forum, 'As I’m working on GeoSetter in my spare time, please understand that I will not answer immediately."

By the way, this software is fantastic for tagging photos! just the Best!...I got to remember to donate!
(0003671)
KeB0   
2019-01-25 22:57   
Studia, I did a little testing with older versions and it worked and then I notice exiftool was version 9.65 and the "Save as Template" feature was working OK! So, then tried updating exiftool and then I got the error! For now just downgrade Exiftool to version 11.23 and the problem is temporarily fix in till the developers can figure something out. The moment I upgrade to version 11.24 i get the error!

Regards,
(0003672)
KeB0   
2019-01-25 23:04   
Friedman,
Here is where I think the issue might be in the Exiftool 11.24 and above versions. See the highlighted text portion the screen capture bellow

"- Improved warning when trying to read a file with a zero-length name"
(0003673)
KeB0   
2019-01-25 23:07   
Ooops sorry wrong image. Can you please remove it? thanks
(0003674)
Studia   
2019-01-26 03:18   
Thank you very much - you are correct in that the exif tool appears to be the problem.

I have uninstalled again but reinstalled the same version (3.50) but have not updated the exif tool and it does now appear to be working as it should.

Hopefully a bugfix version will issue soon.

Now it just remains to be able to fix the map view.....
(0003687)
KeB0   
2019-01-28 17:58   
Studia,
If you revert the Exiftool to version 11.23 it will work!
The google map issues is a google issues from what I understand. Look here, this might be the answer to your (our) problem. https://www.geosetter.de/mantis/view.php?id=1970


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
2017 [GeoSetter] User Interface major always 2019-01-15 11:10 2019-01-28 14:19
Reporter: trainman Platform:  
Assigned To: OS:  
Priority: normal OS Version:  
Status: new Product Version: 3.5  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Map not working
Description: The map is not working.
I obtained an API key from Google, and followed the steps in another thread to install, but still not working.
Possibly related to the line <base href="http://map.geosetter.de/v3/"> which seems to point to an empty page.
Tags:
Steps To Reproduce:
Additional Information:
Attached Files:
Notes
(0003685)
WilfriedB   
2019-01-28 14:19   
Meanwhile, it seems an additional problem appeared (not necessarily related to the API key) and was reported several times. So far no solution, but a workaround or at least reducing the lack by decreasing the size of the map panel drastically:
 https://www.geosetter.de/mantis/view.php?id=2019#c3662


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
2020 [GeoSetter] User Interface crash always 2019-01-20 10:49 2019-01-28 14:17
Reporter: joergens_mi Platform:  
Assigned To: OS:  
Priority: high OS Version:  
Status: new Product Version: 3.5  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Die Karten laden nicht auch bei Umstellung auf OSM
Description: Aktuelles Windows 10 64 Bit 32 GB Hauptspeicher. Mehrfacher Reboot. Als einzigstes Userprogramm nach dem reboot gestartet

Die Karten laden nicht weder - bzw extremst zögerlich, Pausen im Minutenbereich - in der Version 3.5 und in der Version 3.4.8.2 Build 2184 genauso

3.5 portable installiert mit config.ini
3.4.8.2. "normal" installiert.

Fehlermeldung Probleme mit dem Management der Metadaten.

Ab und zu klappt es dann auch mal
Tags:
Steps To Reproduce:
Additional Information:
Attached Files:
Notes
(0003684)
WilfriedB   
2019-01-28 14:17   
Das Problem wurde hier inzwischen schon mehrfach gemeldet. Keine Lösung, aber eine Abschwächung durch Verkleinerung der Karte wurde hier beschrieben: https://www.geosetter.de/mantis/view.php?id=2019#c3662


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
2018 [GeoSetter] User Interface major N/A 2019-01-16 14:01 2019-01-28 14:08
Reporter: geobiene Platform: Desktop  
Assigned To: OS: Windows  
Priority: high OS Version: 7  
Status: new Product Version: 3.4.16 beta  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Karten laden sehr langsam
Description: Sehr merkwürdiges Verhalten zur Zeit.
Einige Wochen hatte ich Geosetter nun nicht genutzt. Heute wollte ich GPS bei einigen Fotos korrigieren.
Das Laden der Karte dauert, bei allen Karten. Dabei ist Geosetter die Zeit über bei 25% CPU Volllast. Dies beim Wechseln der Karten, beim Zoomen und beim Wischen, oder beim Anklicken einer bereits gesetteten Fotodatei im Explorer-Fenster. Jedesmal 10-60 Sekunden 25% CPU. "GeoSetter (Keine Rückmeldung)".

In den letzten Wochen keine Veränderung am PC, außer Firefox und Thunderbird Updates.
Tags:
Steps To Reproduce:
Additional Information:
Attached Files:
Notes
(0003637)
Franklin2K   
2019-01-16 19:11   
Hi,

ich habe das gleiche Problem, die Ursache liegt vermutlich bei Google und nicht in unseren Systemen.

Franklin
(0003676)
geobiene   
2019-01-26 12:57   
Gibt es schon eine Lösung? Das Problem besteht weiterhin.
(0003682)
WilfriedB   
2019-01-28 14:08   
Das Problem wurde hier inzwischen schon mehrfach gemeldet. Keine Lösung, aber eine Abschwächung durch Verkleinerung der Karte wurde hier beschrieben: https://www.geosetter.de/mantis/view.php?id=2019#c3662


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
1736 [GeoSetter] User Interface block always 2017-09-17 13:40 2019-01-16 20:31
Reporter: lamalate Platform:  
Assigned To: Friedemann OS:  
Priority: normal OS Version:  
Status: assigned Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Format '%s' ungültig oder nicht kompatibel mit Argument
Description: Un message d'erreur apparait 2 fois lors de l'enregistrement des modifications. Voir bugreport. Version 3.4.16 (build 2119)
Beim Speichern von Änderungen erscheint eine Fehlermeldung zweimal. Siehe Bugreport.
Tags:
Steps To Reproduce:
Additional Information:
Attached Files: bugreport.txt (19,414 bytes) 2017-09-17 13:40
https://geosetter.de/mantis/file_download.php?file_id=616&type=bug
bugreport-2.txt (28,737 bytes) 2018-12-14 17:15
https://geosetter.de/mantis/file_download.php?file_id=748&type=bug
bugreport2.txt (28,432 bytes) 2018-12-14 17:15
https://geosetter.de/mantis/file_download.php?file_id=749&type=bug
bugreport-3.txt (22,384 bytes) 2019-01-16 20:31
https://geosetter.de/mantis/file_download.php?file_id=761&type=bug
Notes
(0003053)
lamalate   
2017-09-17 16:32   
Fixed in beta
(0003613)
lamalate   
2018-12-14 17:15   
Version 3.5 - Ce bug recommence .. impossible de sauvegarder les données gps, la photo est bien sauvegardée mais sans inscription des données et le rapport de bug s'ouvre.
(0003638)
gaetoons501   
2019-01-16 20:31   
Exact same problem here, trying to set new coordinates to a large amount of photo, and I get that bug randomly on some of them. That's really annoying.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
2012 [GeoSetter] Image Data feature always 2018-12-24 14:54 2018-12-24 15:07
Reporter: jakub.rusiecki@gmail.com Platform:  
Assigned To: OS:  
Priority: normal OS Version:  
Status: new Product Version: 3.5  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Support Lightroom via extensions (not only ExifTool)
Description: First of all I'd like to say I'm impressed by the Geosetter (I'm new to it).
I'm searching for a tool to workaround Lightroom (LR) policy to force me into subscription (ransomware) just because Google changes API and it blocks my LR from geoencoding images.
PROBLEM:
Trying Geosetter 3.5.0 xmp writing (Exiftool 11.*) proved to negatively impact my pictures (it may be Adobe's "feature", NOT your) - however I figured out that xmp manipulation for LR access is wrong because it is workaround while it should use LR API to set location directly without messing other values that get overwritten when xmp metadata is read-back into LR. Obviously a method that only changes intended data (preferably using official API) is needed.

REQUEST:
I propose extending GeoSetter by: allowing Geosetter to call something else than current exiftool - e.g. any defined programme, local url, API call to geotag (or apply Geosetter-defined fields) to a file by its path in the way it chooses.

I'd then add a power shell (or vbs or lua) script that would apply that geolocation (lat/lon) to particular image using API or direct Litesql - this would affect ONLY location fields and other info will not get deleted by LR.

Possible roadmap:
ver 1:
In settings allow to define external program path and assign name to it on the context menu or menu bar.
When context menu /menu bar button used, call that program with 2 parameters: photo filename_with_path and xml/json serialized metadata package (put there whatever you have at hand so that no further configuration in previous step is needed). It shall return e.g. 0 for Ok, -1 for problems

ver n:
- add better communication (http post)
- add more configurability on UI (context menu ...) or data to be passed
- add more parameters
- add more return codes

Thanks again for great software, Marry Xmas and Happy New Year.


Tags:
Steps To Reproduce:
Additional Information:
Attached Files:
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
1465 [GeoSetter] User Interface major always 2017-05-16 07:55 2018-12-11 23:15
Reporter: hansjoerg Platform: geosetter 3.4.16 und beta  
Assigned To: Friedemann OS: win 10  
Priority: high OS Version:  
Status: confirmed Product Version: 3.4.16 beta  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Karte scheint nicht auf
Description: Hallo

Im Kartenfenster erscheint:
"Hoppla! Ein Fehler ist aufgetreten.
Google Maps wurde auf dieser Seite nicht richtig geladen. Technische Details dazu entnimmst du der JavaScript-Konsole."

Den Hinweis zum Link auf http://www.geosetter.de/map_google.html habe ich gelesen und befolgt.

.. und es wird keine Karte angezeigt. Im Anhang habe ich die Settings und einen screenshoot angefügt. Das Problem kommt auf mehreren Arbeitsstationen windows 7 und windows 10 vor.

LG Hansjörg
Tags:
Steps To Reproduce:
Additional Information:
Attached Files: geosetter_settings.zip (969,593 bytes) 2017-05-16 07:55
https://geosetter.de/mantis/file_download.php?file_id=483&type=bug
Notes
(0002494)
Friedemann   
2017-05-16 09:17   
Ja, die Karte meldet den Fehler:

You have exceeded your daily request quota for this API. We recommend enabling billing to get a higher quota: https://developers.google.com/maps/documentation/javascript/usage

Das ist noch nie passiert. Und in meinem Google-Account sehe ich, dass heute über 100.000 Requests stattgefunden haben. Normalerweise sind es so 10.000 bis 15.000. Kostenlos sind 25.000 Zugriffe pro Tag. Jeweils 1.000 Zugriffe darüber hinaus kosten 50 Cent. Das habe ich natürlich glücklicherweise nicht aktiviert.

Mal schauen, ich hoffe, das war eine einmalige Sache. Ansonsten müsste ich schauen, dass ich den Google-Key wechsele. Oder aber sogar jeden Nutzer dazu verpflichte, sich selbst einen Key anzulegen...

Entschuldigung für die Umstände! :-(
(0002571)
moboter   
2017-05-23 10:59   
Habe heute eine interessante Entdeckung gemacht bei der Installation des Geosetters.
Installiert habe ich die Anwendung als Administrator hat wunderbar funktioniert auch die Karte baute sich auf. Danach als normaler Benutzer angemeldet und Geosetter gestartet danach wurden immer wieder requests an die Karte geschickt ohne dass sie sich aufbaute. Wäre vielleicht eine Erklärung für die hohen zugriffszahlen
(0003612)
u564533   
2018-12-11 23:15   
Ich habe mit Version 3.5.0 den gleichen Fehler, leider finde ich auf der Seite https://www.geosetter.de/mantis/view.php?id=1970 keine Lösung, daher hänge ich mich hier dran.
Ich habe verschiedene Szenarien erfolglos ausprobiert. Datei > Einstellungen > Karte > Kartendatei und Layer > Feld Kartendatei

1. http://www.geosetter.de/map_google.html
Fehler: "Google Maps kann auf dieser Seite nicht richtig geladen werden

2. file:///d:/Users/.../geosetter/map_google.html
nach Anleitung von https://www.geosetter.de/mantis/view.php?id=1970#c3587
Fehler: "Hoppla! Ein Fehler ist aufgetreten. Google Maps wurde auf dieser Seite nicht richtig geladen. Technische Details dazu entnimmst du der JavaScript-Konsole."

Was muss ich tun, damit ich die Karte wieder sehe? Ich habe einen eigenen Google API-Schlüssel.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
2009 [GeoSetter] User Interface minor sometimes 2018-12-05 04:47 2018-12-06 23:27
Reporter: eliz_bot Platform:  
Assigned To: OS:  
Priority: normal OS Version:  
Status: new Product Version: 3.5  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Imagesize is displaying wrong
Description: In one particular folder, the image size in Geosetter is listed as "4032x3024" for both files with the size "4032x3024" and "3024x4032". This makes it impossible for me to rename my images with the resolution in title.
 It appears that Geosetter is deciding to list the largest size first, as an image with the size "1920x3412" is being displayed as "3412x1920".
Please note, this doesn't happen with every single folder of photos I have, it does work sometimes , and I know that the metadata is correct, as Windows explorer tells me the correct image resolution. It is also not due to the camera (iPhone SE) as other photos taken with the same camera do not reproduce this affect.
Is there a setting that I have wrongly ticked in association with these files? I have looked and looked and cant find anything!
Tags:
Steps To Reproduce:
Additional Information:
Attached Files: Geosetter not reading them correct note the top one.PNG (6,144 bytes) 2018-12-05 04:48
https://geosetter.de/mantis/file_download.php?file_id=740&type=bug
Geosetter Reading the file sizes correctly.PNG (4,432 bytes) 2018-12-05 04:48
https://geosetter.de/mantis/file_download.php?file_id=741&type=bug
Windows explorer being able to define the image sizes, note the last one.PNG (10,885 bytes) 2018-12-05 04:48
https://geosetter.de/mantis/file_download.php?file_id=742&type=bug
Capture.PNG (305,511 bytes) 2018-12-06 04:16
https://geosetter.de/mantis/file_download.php?file_id=743&type=bug
Img showing the geosetter reading, the exiftool reading, and the image.JPG (244,006 bytes) 2018-12-06 22:06
https://geosetter.de/mantis/file_download.php?file_id=744&type=bug
Porttrait.JPG (2,547,162 bytes) 2018-12-06 22:31
https://geosetter.de/mantis/file_download.php?file_id=745&type=bug
Landscape.JPG (2,155,928 bytes) 2018-12-06 22:31
https://geosetter.de/mantis/file_download.php?file_id=746&type=bug
Notes
(0003595)
eliz_bot   
2018-12-06 04:16   
- Image of Geosetter reading a portrait photos height and width wrong.
(0003596)
heiko   
2018-12-06 20:52   
can you upload the Image which is shown in Capture.png?

The data which is shown in the screenshot is form ExifTool.
(0003597)
eliz_bot   
2018-12-06 22:06   
Attached is a photo that shows the geosetter reading (4032x3024) the exif reading, and the portrait image. Not that the width and height are wrong - it should be H = 4032 not 3024. Adding files with shorter titles and adding less files in at once also don't solve this.
(0003598)
heiko   
2018-12-06 22:14   
is it possible that you upload the Image itself, not a screenshot of GeoSetter
(0003599)
eliz_bot   
2018-12-06 22:29   
Here is one portrait and one landscape.
(0003600)
heiko   
2018-12-06 23:13   
I've checked the image "Porttrait.JPG" with 4 different programs (GeoSetter, ExifTool, ExifDataView, Jeffrey's Image Metadata Viewer). All programs are saying, that the width of the Image is 4032. So I assume, that this value is stored in the metadata of this file.
Have you edited this Image with any Software?
(0003601)
eliz_bot   
2018-12-06 23:17   
I've only used it through geosetter! Windows explorer is able to determine the correct dimensions (I postulate, that it maybe takes into account the angle of the phone?) If I have to determine the deminsions manually is fine, for this set, I just am worried that this will be a continual thing!
(0003602)
heiko   
2018-12-06 23:27   
I don't know what Windows Explorer reads and interprets, but I'm sure the value is in the exif data like this


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
2006 [GeoSetter] User Interface major always 2018-12-04 11:46 2018-12-06 20:45
Reporter: aressegu Platform: Lenovo Think Pad  
Assigned To: OS: Windows 10 Pro  
Priority: normal OS Version: 1803  
Status: new Product Version: 3.5  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Rechts-Klick auf Ordner im Windows Explorer führt zu Fehler & Abbruch des Geosetter
Description: Zur Bearbeitung von Fotos in einem Datei-Ordner wird per Geosetter per Rechts-Klick gestartet. Es erscheint sofort ein Pop-Up in dem der Fehlerstatus dokumentiert wird. Das beim Startversuch am 3.12.2018 erzeugte Fehlerprotokoll wurde bereits per E-Mail an support@gesosetter.de übermittelt.
Tags:
Steps To Reproduce:
Additional Information: Das beschriebene Fehlverhalten ist nach dem Upgrade von Windows 10 Home auf Windows 10 Pro aufgetreten. Könnte auch ein "Rechte-Problem" bei Zugriff auf das Dateisystem sein (?)
Attached Files:
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
1995 [GeoSetter] User Interface tweak have not tried 2018-11-01 12:38 2018-12-01 18:54
Reporter: geobiene Platform: Desktop  
Assigned To: OS: Windows 7  
Priority: normal OS Version: Ultimate  
Status: new Product Version: 3.4.16 beta  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Gesettete Koordinaren gehen verloren
Description: Hallo,
seit neuestem passiert mir extrem mieses mit Geosetter. Die gesetteten Koordinaten gehen verloren. Scheinbar wenn ich Geosetter verlasse, minimiere, und kurz woanders etwas nachsehe, wie zB im Browser. Aber das kann ich nicht sicher beweisen.

Beim aktuellen jetzigen Vorfall geht mir über 1 Stunde Arbeitszeit verloren. Zuletzt war es ähnlich viel. Davor etwas weniger. Es summiert sich. Alles zurück auf Anfang... Das frustet.

Ich habe keine Ahnung warum »auf einmal« dieser Fehler auftritt. Das ist erst seit ein paar Tagen. Die Version ist die gleiche. Am BS habe ich auch seit Monaten nichts gemacht.

Google Maps (Sat) habe ich in Verdacht. Und zwar so: Manchmal habe ich Glück und Google Maps (Sat) wird nicht gegraut mit Hinweistext "for development purposes only". Dann funktioniert alles einwandfrei. Doch irgendwann scheint Google Maps (Sat) in den gegraut-Modus zu verfallen, ohne dass (bei mir) die Tiles gegraut werden. Dann gehen die bereits gesetteten, aber noch nicht gespeicherten, Koordinaten verloren. Es gehen alle nicht gespeicherten Koordinaten verloren, die bereits gesettet wurden.

Eventuell hängt es damit zusammen, dass ich im Browser Google Maps (Sat) geöffnet habe/hatte, oder Google Earth geöffnet habe/hatte?

Beim letzten Vorfall hatte ich Geosetter neu gestartet und mit dem Neustart war Google Maps (Sat) gegraut.

Soviel als Info.
Natürlich werde ich jetzt vorsichtiger sein und öfters Speichern.
Schön is das nicht.
Tags:
Steps To Reproduce:
Additional Information:
Attached Files:
Notes
(0003564)
geobiene   
2018-11-01 12:41   
Nach "Eintrag absenden" kommt:
Fatal error: Class 'ClientException' not found in /homepages/22/d19292159/htdocs/geosetter/mantis/api/soap/mc_tag_api.php on line 162
(0003565)
geobiene   
2018-11-01 12:43   
Nach Registration kam:

APPLICATION ERROR #1901

Die Bestätigungs-URL ist ungültig oder wurde bereits verwendet. Bitte registrieren Sie sich erneut.
Bitte benutzen Sie die „Zurück“-Taste Ihres Browsers, um auf die vorhergehende Seite zurückzukehren. Dort können Sie den hier angezeigten Eintrag korrigieren oder eine andere Aktion ausführen. Über das Menü können Sie auch direkt zu einer anderen Aktion wechseln.

„Zurück“-Taste Ihres Browsers ist "about:blank".
(0003566)
geobiene   
2018-11-01 12:46   
OK. Also es ist allen Anschein nach das Öffnen von Google Maps Sat im Browser. Damit werden alle nur gesetteten und noch nicht gespeicherten Koordinaten gelöscht. Kann das jemand bestätigen? Ich bin hier jetzt wieder raus.
(0003575)
WilfriedB   
2018-11-27 17:31   
Ich hatte schon vor längerer Zeit (und zwar lange bevor Google die API policies änderte!) ein ähnliches Verhalten beobachtet. Rekonstruieren konnte ich das noch nicht, es scheint aber so zu sein, das GeoSetter irgendwie dazu veranlasst wird, alle Dateien neu einzulesen. Also das gleiche, was auch bei einem Refresh (F5) ablüft, nur mit dem Unterschied, dass es plötzlich, wie aus heiterem Himmel passiert. In dem Fall sind dann auch alle geänderten Daten (nicht nur Koordinaten sondern auch andere Meta-Daten) verloren. Obigen Verdacht "Scheinbar wenn ich Geosetter verlasse, minimiere, und kurz woanders etwas nachsehe ..." kann ich da auch bestätigen, aber, wie schon gesagt, nicht bewusst herbei führen.
Ich es auch schon erlebt, dass das während des zurück schreiben auftritt, dass heißt ein Teil waren korrekt auf dem neuesten Stand, während andere in dem Zustand waren, wie zum Zeit als GeoSetter gestartet wurde.
(0003591)
geobiene   
2018-12-01 14:35   
Neue Erkenntnis: Es liegt am Starten von Google Chrome. Es muss nur Google Chrome gestartet werden und alles ist weg. Das liegt wohl daran, dass Google Chrome beim Starten auf ALLE angeschlossenen Festplatten zugreift und dort irgendetwas abfragt. Keine Ahnung was. Deswegen ist Google Chrome auch in der Kritik. Google Chrome starten und die Festplatten rattern. Wahrscheinlich wird der Verzeichnisbaum jeder Festplatte ausgelesen (und an Google übersandt? Datenkralle.).
(0003592)
WilfriedB   
2018-12-01 18:54   
Es ist bestimmt nicht nur Google Chrome, sondern sicher auch andere Programm, die das verursachen können. Mir ist das heute auch passiert, dass ich etwas anderes gemacht hatte und dabei vergaß, dass der GeoSetter im Hintergrund noch offen war und ich einige Änderungen noch nicht gespeichert. In der Zwischenzeit hatte ich Opera, Word und wohl auch andere Anwendungen benutzt, aber mit Sicherheit kein Chrome.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
1728 [GeoSetter] Image Data text always 2017-09-03 09:28 2018-11-27 17:47
Reporter: rugux Platform:  
Assigned To: Friedemann OS: Win 10  
Priority: normal OS Version: latest  
Status: assigned Product Version: 3.4.51 beta  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: deutsche Umlaute werden zerstört
Description: aktuell in Verwendung: 3.4.53 beta:
Beim Speichern von Bilddateien nach Vornahme von Änderungen in GeoSetter (z.B. Einfügen von Höhendaten) werden alle deutschen Umlaute (ä, ö, ü, Ä, Ö, Ü) in den IPTC-Texten (Headline, Description) durch unleserliche Zeichen erstezt.
Tags:
Steps To Reproduce:
Additional Information:
Attached Files:
Notes
(0003576)
WilfriedB   
2018-11-27 17:47   
Ich habe die Feststellung gemacht, dass das nicht passiert, wenn man Texte mit Umlauten erstmals eingibt, sondern nur wenn diese einmal erfolgreich abgespeichert wurden, die gleiche Dateien irgendwann später wieder mit GesoSetter geöffnet und ein anderer(!) tag geändert und abgespeichert. Das Unangenehme daran ist: Schaut man sich die Texte unmittelbar nach ändern und abspeichern in GeoSetter an, sieht alles richtig aus. Öffnet die aber dann erneut oder auch in einem anderen Programm, dann wurden die Umlaute durch andere Zeichen ersetzt.
Das Ganze betrifft nicht nur Headline und Description, sondern auch Keywords, Supplemental Categories, Location und vielleicht noch andere Tags. Neben den deutschen Umlauten sind davon auch französische accents betroffen (z.B. é erscheint als é).
Als Verwaltungsprogramm nutze ich Daminion und hab mir dort extra eine Reihe von Saved Searches erstellt um tags mit é, ö, è, ä ... etc zu suchen und zu korrigieren.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
2005 [GeoSetter] User Interface minor always 2018-11-25 09:40 2018-11-25 09:40
Reporter: Peter Meinhold Platform: Terra PC, Lap Top  
Assigned To: OS: Windows 8  
Priority: normal OS Version: 8.1  
Status: new Product Version: 3.5  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Geonames
Description: Ich habe wie empfohlen mich bei Geonames registriert und die Zugangsdaten im GeoSetter Programm eingetragen. Die Abfrage funktioniert dann aber nur bedingt, d.h. die Höhenangabe funktioniert nicht und bei "Ort" werden nur Ländercode, Lande und Ort eingefügt. Benutze ich dagegen "http://api.geonames.org" mit Ihrem Passwort werden die Daten komplett eingetragen
Tags:
Steps To Reproduce:
Additional Information: Wie kann das Problem beseitigt werden?
Attached Files:
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
884 [GeoSetter] User Interface feature N/A 2011-09-14 22:07 2018-11-23 00:12
Reporter: heiko Platform:  
Assigned To: Friedemann OS:  
Priority: normal OS Version:  
Status: assigned Product Version: 3.4.21 beta  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Kollektions-Modus
Description: phantastisch wäre es wenn sich der Kollektions-Modus in der Oberfläche von GeoSetter aktivieren läßt, und die Kollektion dann per Drag&Drop aus dem Explorer füllen liese
Tags:
Steps To Reproduce:
Additional Information:
Attached Files:
Notes
(0001672)
heiko   
2011-09-14 23:10   
idealerweise sollte das natürlich sowohl mit Dateien als auch mit Verzeichnissen funktionieren
(0001963)
heiko   
2013-12-01 23:10   
das fände ich immer noch klasse :-)
(0003573)
Kugelblitz78   
2018-11-23 00:12   
Das fände ich auch sehr klasse.
Die Kollektionen könnten auch als TXT Datei (list mit Pfad und Dateiname) exportierbar sein...z.B. zur Weiterverarbeitung mit dem exiftool


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
2001 [GeoSetter] User Interface feature always 2018-11-16 15:49 2018-11-16 21:31
Reporter: Kugelblitz78 Platform:  
Assigned To: OS:  
Priority: high OS Version:  
Status: new Product Version: 3.5  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Liste ohne "vorschau Icon"
Description: Wenn ich extrem viele Fotos (100.000) als Liste mit Verzeichnissen und Unterverzeichnissen von Geosetter anzeigen lasse kommt es häufig zu der Fehlermeldung "Nicht genug Arbeitsspeicher" und das bei 16GB Ram.

Kann man die Liste auch anzeigen ohne die kleinen "Foto" Icons ganz links in der Spalte?

Möchte nur schnell alle Bilder überfliegen um Fehler bei den Metadaten zu sehen. z.B. fehlendes Aufnahmedatum etc.

Tags:
Steps To Reproduce: Gehe in einen Ordner der 100.000 Bilder oder mehr enthält.
Klicke auf Listenansicht und klicke dann auf "Zeige Bilder in Unterverzeichnissen"

Nach einer weile ist der Arbeitsspeicher vollgelaufen.
Additional Information:
Attached Files:
Notes
(0003570)
heiko   
2018-11-16 21:31   
das Icon lässt sich nicht ausblenden und ist sicherlich nicht dran schuld dass der Speicher vollläuft


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
2000 [GeoSetter] User Interface crash always 2018-11-15 18:59 2018-11-16 14:07
Reporter: anders@xoz.dk Platform: Firefox  
Assigned To: OS: Windows 10  
Priority: normal OS Version:  
Status: new Product Version: 3.5  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Error: Division by 0 at startup...
Description: The system worked for some days, but now gives an initialization error. See attached. Map cannot be displayed and map types cannot be selected.

I have tried re-installation, but no change.

Tags:
Steps To Reproduce: Start the program.
Additional Information: I am sitting in Turkey. My own guess is that it is due to geosetter not being able to get to its map link address. I currently have troubles with several other addresses without being able to see any clue to what gets through and what not. Possibly external cause - local name server limited due to sudden government restrictions.
Attached Files: geosetter crash2.jpg (50,645 bytes) 2018-11-15 18:59
https://geosetter.de/mantis/file_download.php?file_id=737&type=bug
geosetter crash.jpg (33,901 bytes) 2018-11-15 18:59
https://geosetter.de/mantis/file_download.php?file_id=738&type=bug
Notes
(0003569)
anders@xoz.dk   
2018-11-16 14:07   
Yes, this was definitely an unexpected abend due to DNS-trouble. With DNS okay it all works well and OSM comes up immediately, even without any "Do you own..."-google pop-up....


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
1999 [GeoSetter] User Interface major always 2018-11-05 09:35 2018-11-15 19:03
Reporter: carsten@riddersholm.dk Platform: Microsoft Signature Edition  
Assigned To: OS: Windows 10  
Priority: normal OS Version: 1803  
Status: new Product Version: 3.5  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Google Maps will not load
Description: See attached screen dump. No problem with OSM
Text: "For development Purposes only"
Do I have to pay for Google Maps API?
Tags:
Steps To Reproduce:
Additional Information:
Attached Files: Google maps.JPG (119,187 bytes) 2018-11-05 09:37
https://geosetter.de/mantis/file_download.php?file_id=736&type=bug
Notes
(0003567)
heiko   
2018-11-05 22:01   
(Last edited: 2018-11-05 22:01)
take a look at http://www.geosetter.de/mantis/view.php?id=1970

(0003568)
anders@xoz.dk   
2018-11-15 19:03   
Google Maps behaves this way against several other programs that include them. Quite identical to what I experienced in my genealogy program and in my former GPS-- photo-localization program....


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
1996 [GeoSetter] User Interface tweak have not tried 2018-11-01 12:39 2018-11-01 12:39
Reporter: geobiene Platform: Desktop  
Assigned To: OS: Windows 7  
Priority: normal OS Version: Ultimate  
Status: new Product Version: 3.4.16 beta  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Gesettete Koordinaren gehen verloren
Description: Hallo,
seit neuestem passiert mir extrem mieses mit Geosetter. Die gesetteten Koordinaten gehen verloren. Scheinbar wenn ich Geosetter verlasse, minimiere, und kurz woanders etwas nachsehe, wie zB im Browser. Aber das kann ich nicht sicher beweisen.

Beim aktuellen jetzigen Vorfall geht mir über 1 Stunde Arbeitszeit verloren. Zuletzt war es ähnlich viel. Davor etwas weniger. Es summiert sich. Alles zurück auf Anfang... Das frustet.

Ich habe keine Ahnung warum »auf einmal« dieser Fehler auftritt. Das ist erst seit ein paar Tagen. Die Version ist die gleiche. Am BS habe ich auch seit Monaten nichts gemacht.

Google Maps (Sat) habe ich in Verdacht. Und zwar so: Manchmal habe ich Glück und Google Maps (Sat) wird nicht gegraut mit Hinweistext "for development purposes only". Dann funktioniert alles einwandfrei. Doch irgendwann scheint Google Maps (Sat) in den gegraut-Modus zu verfallen, ohne dass (bei mir) die Tiles gegraut werden. Dann gehen die bereits gesetteten, aber noch nicht gespeicherten, Koordinaten verloren. Es gehen alle nicht gespeicherten Koordinaten verloren, die bereits gesettet wurden.

Eventuell hängt es damit zusammen, dass ich im Browser Google Maps (Sat) geöffnet habe/hatte, oder Google Earth geöffnet habe/hatte?

Beim letzten Vorfall hatte ich Geosetter neu gestartet und mit dem Neustart war Google Maps (Sat) gegraut.

Soviel als Info.
Natürlich werde ich jetzt vorsichtiger sein und öfters Speichern.
Schön is das nicht.
Tags:
Steps To Reproduce:
Additional Information:
Attached Files:
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
1992 [GeoSetter] Image Data feature N/A 2018-10-29 17:21 2018-10-30 20:27
Reporter: Nasenbaer Platform:  
Assigned To: heiko OS:  
Priority: normal OS Version:  
Status: resolved Product Version: 3.5  
Product Build: Resolution: no change required  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Suchfeld für Orte im Kartenfenster
Description: Bei der Nutzung einer eigenen API wäre es klasse, wenn man auch die places searchbox nutzen könnte. Siehe: https://developers.google.com/maps/documentation/javascript/examples/places-searchbox
Als Laie in Sachen Programmierung ist es mir leider nicht gelungen, die maps.html korrekt anzupassen. Eine entsprechende Vorlage für Nutzer mit eigener API wäre super.
Tags:
Steps To Reproduce:
Additional Information:
Attached Files: Bug1992.png (56,706 bytes) 2018-10-29 22:56
https://geosetter.de/mantis/file_download.php?file_id=734&type=bug
Suche_not_found.png (1,378,186 bytes) 2018-10-30 14:41
https://geosetter.de/mantis/file_download.php?file_id=735&type=bug
Notes
(0003559)
heiko   
2018-10-29 22:56   
dieses Suchfeld gibt es bereits unterhalb der Karte (siehe Screenshot).

Wenn die Frage/Wunsch hiermit erledigt ist, bitte kurz melden, dann mache ich diesen Vorgang zu.
(0003560)
Nasenbaer   
2018-10-30 14:41   
Bei Nutzung des Suchfeldes kommt eine Fehlermeldung. Ich war davon ausgegangen, dass hier nur nach Bildern mit entsprechenden Ortsnamen gesucht wird und nicht nach beliebigen Orten auf der Karte. Was könnte die Ursache für die Fehlermeldung sein?
(0003561)
heiko   
2018-10-30 15:48   
Bei mir wird sowohl München als auch Hamburg bei der Suche gefunden und entsprechend auf der Karte angezeigt.
(0003562)
Nasenbaer   
2018-10-30 18:02   
Ich habe das Problem gelöst und wie in 99% der Fälle liegt es am Anwender. Ich hatte die Geocoding API aktiviert, aber dämlicherweise nicht für meinen Schlüssel freigegeben. Nachdem sich die 403 Fehler in der Konsole gehäuft haben, ist es mir dann auch endlich aufgefallen. Vielen Dank für die schnellen Antworten!
(0003563)
heiko   
2018-10-30 20:27   
Hauptsache es funktioniert jetzt


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
1989 [GeoSetter] Image Data feature N/A 2018-10-18 14:18 2018-10-25 16:43
Reporter: frherbers Platform:  
Assigned To: OS:  
Priority: normal OS Version:  
Status: new Product Version: 3.5  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Retrieve Spot information from GeoNames
Description: GeoSetter allows the retrieval of city data from GeoNames.
It would be great when GeoSetter could also retrieve nearby spots or parks.

GeoNames supports the search of the following feature classes (interesting are L, S and T):
A: country, state, region,...
H: stream, lake, ...
L: parks,area, ...
R: road, railroad
S: spot, building, farm
T: mountain,hill,rock,...
U: undersea
V: forest,heath,...

Doing it automatically could be error prone. So I am more asking for an additional button (search for spot data) within the Edit Data / Location, which brings up some results to choose from or with "Get from Web" to show cities and spots in two lists to choose from.

I noticed that spot data does not contain city information, so first selecting the spot and selecting the city to add the missing city information when wanted.

Hoping of other users to bring in ideas.
Tags:
Steps To Reproduce:
Additional Information:
Attached Files:
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
1990 [GeoSetter] User Interface minor always 2018-10-20 14:39 2018-10-20 23:45
Reporter: petergabor Platform:  
Assigned To: OS:  
Priority: normal OS Version:  
Status: new Product Version: 3.5  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: For develpment purposes only
Description: On the map view there is a text "For development purposes only and the map is very dark.
Tags: map
Steps To Reproduce:
Additional Information:
Attached Files: geosetter screen.jpg (493,300 bytes) 2018-10-20 14:39
https://geosetter.de/mantis/file_download.php?file_id=729&type=bug
Notes
(0003556)
heiko   
2018-10-20 23:45   
see http://www.geosetter.de/mantis/view.php?id=1970


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
1988 [GeoSetter] User Interface trivial have not tried 2018-10-15 19:01 2018-10-15 19:01
Reporter: zava Platform:  
Assigned To: OS:  
Priority: normal OS Version:  
Status: new Product Version: 3.4.51 beta  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: What version to use?
Description: Hello,
I seem to have got a bit lost...
A loooong time ago I received advice to use a BETA version in order to overcome some issue (can't even rememeber what it was).
I have used V3.4.82 (Build 2184) BETA ever since.
I now notice that stable versions have reached 3.5
Which version shoul'd I now use? Go back to stable version and keep mainstream maybe?
Thank you!
Tags:
Steps To Reproduce:
Additional Information:
Attached Files:
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
1987 [GeoSetter] User Interface minor always 2018-10-15 18:57 2018-10-15 18:57
Reporter: zava Platform:  
Assigned To: OS:  
Priority: low OS Version:  
Status: new Product Version: 3.4.51 beta  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Zooming preview image with mouse wheel also scrolls image list
Description: Hello,
this is just a minor issue...
After focusing on a preview image (docked window) and using the mouse wheel to zzom the preview, zoom works fine but in the meanwhile the (unfocused) images list is also scrolled. As a result, after zooming the selected image in the list is not the correct one anymore.
Btw I am using 3.4.82 Beta, whici his not listed in the versions drop down list.
Thank you
Tags:
Steps To Reproduce: Focus on docked window with preview image; roll mouse wheel to zoom.
Additional Information:
Attached Files:
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
1957 [GeoSetter] Image Data feature N/A 2018-07-06 17:28 2018-10-14 07:00
Reporter: jmoliver Platform:  
Assigned To: OS:  
Priority: normal OS Version:  
Status: new Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Allow to edit EXIF 2.3 Weather fields
Description: Exif 2.3 introduces new fields such as:

0x9400 AmbientTemperature
0x9401 Humidity
0x9402 Pressure

It would be interesting that in a similar fashion in which GeoSetter obtains the Altitude and location names using the GPS latitude and longitude coordinates, that it utilize the same coordinates along with the date and time an image was taken to obtain the Ambient Teperature, Humidity and Pressure values.

There are several data sources such as NOAA Global Historical Climatology Network Weather Data and https://openweathermap.org.

Tags:
Steps To Reproduce:
Additional Information:
Attached Files:
Notes
(0003524)
jmoliver   
2018-07-06 19:46   
Weather Underground also provides historical weather and an API: https://www.wunderground.com/weather/api/d/docs
(0003525)
jmoliver   
2018-07-08 16:06   
Capturing the moment and the ambient weather information in photos:
https://jmoliver.wordpress.com/2018/07/07/capturing-the-moment-and-the-ambient-weather-information-in-photos/
(0003555)
jmoliver   
2018-10-14 07:00   
I wrote an experimental app which in a similar fashion as geosetter does with track files it is meant to match weather data using the datetime a photo was taken. The data may be retrieved from a nearby weather station. On my list of improvements it to take into account multiple weather stations labeled by lat/long and use the closest one. The GPX schema extension provides for air temperature values.

https://github.com/josemoliver/WeatherTag


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
1980 [GeoSetter] Image Data major always 2018-09-15 20:21 2018-10-11 17:39
Reporter: DavidStokes Platform:  
Assigned To: OS:  
Priority: high OS Version:  
Status: new Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Question/suggestion on Google maps issue
Description: I apologise that I am not very IT-savvy and don't know how sites like this work, so may not be posting this properly. I reported an issue that the Google map on Geosetter doesn't work any longer. I understand that this is because Google has started charging a fee for the use of Google maps.
Is there some way that I could pay Google direct to be able to use the maps?
Alternatively, could Geosetter charge a monthly subscription to cover the additional costs? I should be happy to pay a subscription in order to be able to carry on using Geosetter.
Tags:
Steps To Reproduce:
Additional Information:
Attached Files: 2018-10-11_113720.jpg (1,637,733 bytes) 2018-10-11 17:38
https://geosetter.de/mantis/file_download.php?file_id=728&type=bug
Notes
(0003552)
Adam   
2018-10-10 19:29   
Hi,
I obtained API key from Google, but have no idea what to do with it.
Can anyone send me instructions how to use it? If possible to my email.
Thank you!
(0003553)
Adam   
2018-10-11 17:38   
Hi Friedman,
Maybe you could write up a little article (instructions) how to get Geosetter to display maps once we get API key of our own, so you don't have to pay Google out of your own pocket.
How much is a fair amount for donation anyways?
Thank you!


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
1986 [GeoSetter] User Interface tweak always 2018-10-08 00:29 2018-10-08 00:29
Reporter: SeeBer Platform: Desktop PC  
Assigned To: OS: Windows  
Priority: low OS Version: 7 64bit  
Status: new Product Version: 3.4.16 beta  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: eigentlich kein beta - sonder Version 3.4.16 release (Buiold 2119) - Problem: Check Update -> Fail
Description: Auf Update Prüfen - Fehlermeldung: Die Überprüfung auf ein Update schlug fehl - überprüfen Sie die Inet-Verbindung (sinngemäß)
Tags:
Steps To Reproduce: Hilfe -> Auf Update Prüfen ...
Additional Information: wirklich nix Schwerwiegendes - ein Hinweis auf der Homepage wäre auch ok (z.B. "Deinstallieren Sie zunächst die alte Version bevor Sie die aktuell installieren")
Attached Files:
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
1982 [GeoSetter] Image Data minor N/A 2018-09-15 23:16 2018-10-02 18:58
Reporter: ml Platform:  
Assigned To: OS:  
Priority: normal OS Version:  
Status: new Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: 64bit Version
Description: Gibt es Plaene, eine 64bit-Version zu erstellen? Ich habe regelmaessig Memory-Probleme mit Crashes, wenn zu viele Bilder in einem Directory sind. Ich kann immer im Process Explorer sehen, dass geosetter dann ueber 2GB gross werden will. Passiert so ab ca. 1500 Bildern im Directory. Und das hab ich haeufig. Verteilen der Bilder auf mehrere Directories macht den Workflow komplizierter, man muss dasselbe mehrfach tun.
Tags:
Steps To Reproduce:
Additional Information:
Attached Files:
Notes
(0003548)
rau1   
2018-10-02 18:58   
Ich möchte mich diesem Wunsch anschließen. Nach einer längeren Urlaubsreise stehe ich oft vor dem selben Problem.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
1981 [GeoSetter] Image Data minor always 2018-09-15 23:10 2018-09-20 20:55
Reporter: ml Platform:  
Assigned To: OS:  
Priority: normal OS Version:  
Status: new Product Version: 3.5  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: reuse exiftool processes
Description: Ein Feature Request: geosetter erszeugt beim Speichern fuer jedes Bild einen neuen exiftool-Prozess. Man kann exiftool aber auch ueber eine Pipe steuern und so den Prozess wiederverwenden. Das muesste das Speichern der Bilder erheblich beschleunigen. Kannst du das evtl. mal untersuchen? Ich frage mich das schon, seit ich geosetter verwende (ca. 10 Jahre).
Tags:
Steps To Reproduce:
Additional Information:
Attached Files:
Notes
(0003544)
Erik Krause   
2018-09-20 20:55   
Wenn ich das richtig verstehe bietet exiftool eine Option auf Befehle zuwarten und die abzuarbeiten, ohne den Prozess zwischenzeitlich zu schließen: https://sno.phy.queensu.ca/~phil/exiftool/#performance


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
1983 [GeoSetter] User Interface feature N/A 2018-09-17 20:45 2018-09-18 20:34
Reporter: pihlo Platform:  
Assigned To: OS:  
Priority: normal OS Version:  
Status: new Product Version: 3.5  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Ortsabfragen mit PLZ
Description: Bei der Abfrage von Ortsdaten fehlt die PLZ
Tags:
Steps To Reproduce: Context Aktion auf Bild(er), Bearbeiten, (alle) online abfragen
Additional Information:
Attached Files:
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
1985 [GeoSetter] User Interface feature N/A 2018-09-17 20:51 2018-09-17 20:51
Reporter: pihlo Platform:  
Assigned To: OS:  
Priority: normal OS Version:  
Status: new Product Version: 3.5  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Geoinformationen in Clipboard kopieren
Description: Es wäre schön wenn bestimmte (auswählbare) Geoinformationen ins Clippboard kopiert werden können.
z.B. - in meinem Fall Lon + Lat in Dezimal

Idee wäre neben jedem der Felder in der "online abfragen" box eine Checkbox - plus ein Button (würde gut unter "alle Ortsinformationen entfernen" passen). Button beschriftet mit "Markierte Felder in Zwischenablage kopieren"

Luxus - Unter den Optionen angabe ob trenner Komma oder Blank sein soll und ob die Werte "delimitiert" werden sollen - also in Hochkommas kommen
Tags:
Steps To Reproduce:
Additional Information:
Attached Files:
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
1729 [GeoSetter] User Interface major sometimes 2017-09-08 00:15 2018-09-15 23:03
Reporter: GeoUser Platform: PC  
Assigned To: Friedemann OS: Windows  
Priority: normal OS Version: 10  
Status: assigned Product Version: 3.4.51 beta  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Geonames liefert fehlerhafte Ortsbezeichnungen
Description: Beim Reverse-Geocoding (z. B. 51,54620000, 7,41060000) werden fehlerhafte Ortsnamen geliefert. Bei den og. Koordinaten z.B. "Nieder Nette" statt "Niedernette". Das ist mir schon öfter aufgefallen, bisher ignoriert. Nun setze ich Stadt + Ort in einigen Bildern als Beschriftung in Bildern ein (wie ein Wasserzeichen).
Tags:
Steps To Reproduce: 51,54620000, 7,41060000
Additional Information: Alle Versionen / in Benutzung 3.4.53 (Build 2170) BETA

Im Vergleich zur GeoNames-Abfrage, liefert OpenStreetMap-Nomatim nicht nur ein korrektes Ergebnis, sondern auch


Eine Straße:
http://nominatim.openstreetmap.org/search.php?q=51.54620000,%207.41060000

Eine genaue Bezeichnung eines Geländes/Gebäudes sofern vorhanden:
http://nominatim.openstreetmap.org/search.php?q=51.57135000%2C7.38345000
http://nominatim.openstreetmap.org/search.php?q=51.57122%2C+7.38022
http://nominatim.openstreetmap.org/search.php?q=51.56603%2C+7.36701
http://nominatim.openstreetmap.org/search.php?q=51.4291%2C+7.4734

http://nominatim.openstreetmap.org/search.php?q=51.49000%2C+6.87245
Und über die place_id sind noch mehr Detaildaten zu erhalten:
http://nominatim.openstreetmap.org/details.php?place_id=120856896

Und sogar Hausnummern:
http://nominatim.openstreetmap.org/search.php?q=51.55067%2C+7.36149


Eine OpenStreetMap-Karte hat GeoSetter ja schon.

Wäre es da nicht zu überlegen ob es möglich ist, primär Nomatim und nur als Fallback GeoNames zu befragen?

Die Nomatim-Antworten / OSM-Daten sind erheblich detailreicher und wären eine wahre Bereicherung für die Beschriftung von Bildern.



Attached Files:
Notes
(0003065)
Erik Krause   
2017-09-30 13:56   
Ich würde das auch begrüßen! Für etliche Alpengipfel liefert GeoNames den Gewann-Namen, der in dem Zusammenhang völlig uninteressant ist. Nomatim macht das besser: http://nominatim.openstreetmap.org/search.php?q=47.326717%2C+10.128402
(0003543)
ml   
2018-09-15 23:03   
Ich kann das nur unterstuetzen. Hab das gerade fuer Schweden erlebt, geonames liefert ziemlichen Unsinn, nominatim hat dagegen absolut korrekte Ergebnisse.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
1979 [GeoSetter] User Interface major always 2018-09-14 22:56 2018-09-15 21:59
Reporter: bobsun Platform:  
Assigned To: OS:  
Priority: normal OS Version:  
Status: new Product Version: 3.5  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Had google map problem with earlier "Beta:" version of Geosetter and downloaded 3.5 It worked yesterday, but Google map problem
Description: Google maps display error message and are darkened
Tags:
Steps To Reproduce: It happens consistently
Additional Information:
Attached Files:
Notes
(0003542)
heiko   
2018-09-15 21:59   
see http://www.geosetter.de/mantis/view.php?id=1970


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
1977 [GeoSetter] Image Data major always 2018-09-14 19:06 2018-09-14 21:40
Reporter: DavidStokes Platform:  
Assigned To: OS: Windows 10  
Priority: normal OS Version:  
Status: new Product Version: 3.5  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Google map problem
Description: When I open Geosetter I see a message saying This page can't load Google Maps correctly. and the map is greyed out. see screenshot.
Is there any way to solve this, please?
Tags:
Steps To Reproduce:
Additional Information:
Attached Files: Capture.JPG (180,952 bytes) 2018-09-14 19:06
https://geosetter.de/mantis/file_download.php?file_id=727&type=bug
Notes
(0003541)
heiko   
2018-09-14 21:40   
see http://www.geosetter.de/mantis/view.php?id=1970


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
1976 [GeoSetter] User Interface crash always 2018-09-13 04:31 2018-09-13 04:31
Reporter: barnowlds Platform:  
Assigned To: OS:  
Priority: high OS Version:  
Status: new Product Version: 3.5  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Crashes upon open
Description: Crashes upon startup of application
Tags:
Steps To Reproduce:
Additional Information:
Attached Files: bugreport.txt (2,869 bytes) 2018-09-13 04:31
https://geosetter.de/mantis/file_download.php?file_id=726&type=bug
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
1967 [GeoSetter] User Interface feature N/A 2018-08-23 21:45 2018-09-11 20:20
Reporter: KirkWM Platform:  
Assigned To: OS:  
Priority: normal OS Version:  
Status: new Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: REQUEST: Combine multiple images to single point for KMZ export
Description: Is it possible to add an option that when exported to Google Earth (kmz), images with the exact same coordinates are combined into one map point with multiple images? Thanks.
Tags:
Steps To Reproduce:
Additional Information:
Attached Files:
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
1972 [GeoSetter] User Interface minor always 2018-09-08 21:24 2018-09-10 21:06
Reporter: beyer6411 Platform:  
Assigned To: OS:  
Priority: normal OS Version:  
Status: new Product Version: 3.5  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Wasserzeichen bei GoogleMaps
Description: Bei der Verwendung der Kartengrundlagen von Google erscheint eine Fehlermeldung (Google Maps kann auf dieser Seite nicht richtig geladen werden. Do you own this website?) , die Kartendarstellung enthält ein Wasserzeichen (s. Anlage). Gibt es eine Möglichkeit wieder zur "gewohnten" Darstellung zu kommen?
Tags:
Steps To Reproduce:
Additional Information:
Attached Files:
Notes
(0003538)
PeterDa   
2018-09-10 16:26   
This is a consequence of the fact that Google now requires users of the Map-API to register and obtain an API-key. This is something that Friedemann would have to do; the end-users can't influence this. The key is free for the first year; after that there is a use-related fee, but only if use exceeds a certain value. The limit seems te be fairly high, so hopefully total use (by all the Geoetter users) will stay below this, but actually only time will tell.
https://developers.google.com/maps/documentation/javascript/error-messages?utm_source=maps_js&utm_medium=degraded&utm_campaign=billing#api-key-and-billing-errors
I hope this has no consequences for this great application!
(0003540)
heiko   
2018-09-10 21:06   
hier ist die Erklärung von Friedemann:
http://www.geosetter.de/mantis/view.php?id=1970


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
1969 [GeoSetter] User Interface feature always 2018-08-31 08:39 2018-08-31 08:39
Reporter: Sparx82 Platform:  
Assigned To: OS:  
Priority: normal OS Version:  
Status: new Product Version: 3.5  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: NMEA import should also allow GNxxx messages
Description: When importing a NMEA file, only the messages with GPxxx are parsed. At least the new uBlox receivers only send GNxxx messages to show that the data is not only coming from GPS but also other positioning systems (GLONASS, Galileo...).

It would be great if the NMEA file import would also allow GNxxx messages (for my self built GPS logger :-).
Tags:
Steps To Reproduce:
Additional Information:
Attached Files:
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
1008 [GeoSetter] Image Data major always 2012-12-31 17:57 2018-08-15 16:53
Reporter: noirist Platform:  
Assigned To: Friedemann OS:  
Priority: normal OS Version:  
Status: assigned Product Version: 3.4.16 beta  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Geosetter hangs when reading ARW files from Sony DSC-RX!
Description: Thank you for your outstanding tool! I'm using geosetter 3.4.16 Build 2119, which uses exiftool 9.09 to read and write image metadata. Geosetter hangs when I open a directory full of ARW image files from the new Sony DSC-RX1. When I try kill geosetter, windows reports an error that "Managing metadata (EXIF/IPTC/XMP) of image files is not responding". If I don't kill geosetter, eventually it loads the directory but it takes a very long time (eg., 30 seconds for a directory with only 2 24MB ARW files, 4 minutes for a directory with 13 24MB ARW files, and an unknown amount of time for a directory with 80 ARW files). When I open a directory full of similarly-sized NEF files, Geosetter loads the directory much more quickly (eg., 49 seconds for 35 21MB NEF files). This is on a Windows 7 64-bit machine with 8GB of RAM.
Tags:
Steps To Reproduce:
Additional Information: At first I thought it was an issue with exiftool, but Phil thinks not.
http://u88.n24.queensu.ca/exiftool/forum/index.php/topic,4668.0.html
Attached Files:
Notes
(0003533)
obetz   
2018-08-15 16:53   
The slow handling makes Geosetter practically unusable for Sony ARW files.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
1956 [GeoSetter] Image Data minor always 2018-07-06 16:24 2018-08-02 15:23
Reporter: faj2323 Platform:  
Assigned To: OS:  
Priority: normal OS Version:  
Status: new Product Version: 3.4.16 beta  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: launching Google Earth causes unsaved changes to be lost
Description: Experienced in 3.4.16 and 3.4.82 beta.
If there are unsaved changes (red items), launching Google Earth causes the changes to be lost.
Tags:
Steps To Reproduce: Edit the metadata of a photo, and press OK. Changes are shown in red.
Launch Google Earth and return to Geosetter - changes disappear.
Additional Information: Workaround is to launch Google Earth before Geosetter, or save changes in Geosetter first.
Attached Files:
Notes
(0003526)
Erik Krause   
2018-07-15 22:00   
Version 3.5 is affected as well.
(0003532)
faj2323   
2018-08-02 15:23   
Confirming the problem persists in Version 3.5. Also, Vuescan causes the same behaviour when it is closed while Geosetter is running.
Further investigations show that when either Google Earth is opened, or Vuescan is closed, Windows Explorer and Desktop icons are refreshed, as is the list of photos in Geosetter - hence the loss of unsaved data.
System is Windows 10 version 1804, and a nVidia graphics card.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
1959 [GeoSetter] User Interface tweak always 2018-07-16 12:09 2018-07-16 22:12
Reporter: darkfiber Platform: Edge - development tool  
Assigned To: OS: WINDOWS  
Priority: low OS Version: 10  
Status: new Product Version: 3.5  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: HTML1423: De begintag heeft niet de juiste vorm. Kenmerken moet van elkaar worden gescheiden door een witruimte. map_google.html
Description: In map_google.html (Zeile 11,position 117) - Vor dem ";" scheint ein Leerzeichen zu fehlen oder das ";" ist überflüssig.
<script
        src="http://maps.googleapis.com/maps/api/js?v=3.14&key=AIzaSyDpMI6jmlJbH5d_YIH40FIDrYnpZhaiHYY&libraries=geometry";></script>
Tags:
Steps To Reproduce:
Additional Information:
Attached Files:
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
1958 [GeoSetter] Image Data major have not tried 2018-07-15 21:48 2018-07-15 21:48
Reporter: Erik Krause Platform:  
Assigned To: OS:  
Priority: urgent OS Version:  
Status: new Product Version: 3.5  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Google maps will change it's pricing policy tomorrow
Description: According to https://cloud.google.com/maps-platform/pricing/ there won't be a really free maps API access any more. What will this mean to geosetter?
Tags:
Steps To Reproduce:
Additional Information:
Attached Files:
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
1140 [GeoSetter] User Interface minor always 2014-05-09 19:10 2018-07-05 13:24
Reporter: capricorn Platform:  
Assigned To: Friedemann OS:  
Priority: normal OS Version:  
Status: feedback Product Version: 3.4.14 Release  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Improper Image Preview of Panasonic DMC-G6 RAW files
Description: When displaying DMC-G6 RAW files in the image preview window it seems that part of the color information is not included. The Image looks extremely pale, especially all red color information seems to be missing. See uploaded file.
Tags:
Steps To Reproduce:
Additional Information: Preview of DMC-G3 RAW files seem to not have this problem.

Problem also exists in latest beta 3.4.50.
Attached Files: Screenshot.jpg (195,264 bytes) 2014-05-09 19:10
https://geosetter.de/mantis/file_download.php?file_id=373&type=bug
Notes
(0002052)
Eric   
2014-05-15 20:00   
Sure you don't have the issue with your G3?
I have the same pale preview with both G3 and G5 Raw files!
(0002057)
capricorn   
2014-05-16 07:12   
For none of my G3 RW2 files I could see the issue. Only G6. I don't have access to any other cam.

In the meantime, I have investigated a bit on my own. I have replaced the dcrawlib.dll used by geosetter with a more recent version I found on the web (revision 1461) with this it looks much better. Still not perfect (might be some WB issue) but for a preview it's ok.

Hope that Geosetter can include this fix as well with the next update.
(0002070)
Eric   
2014-05-16 22:27   
I remember indeed it had something to do with dcraw.
I was still using the "stable" version with dcrawlib 1.4.3.9
I just upgraded to 1.4.5.4 found in CameraRawFiles demo on http://www.imageen.com/demos/index.html.
This fix partially the issue for the G3 and G5, having also WB error, but it might be related to the way dcraw in handling the file. In comparison, FastPictureViewer (and therefore Windows via FPV codec pack) shows a much nicer picture.
Where did you find version 1.4.6.1 ?
(0002075)
Friedemann   
2014-05-17 00:15   
Hi! Can you perhaps send such a RAW file to me (support@geosetter.de)?
(0002080)
capricorn   
2014-05-17 12:26   
@Eric:
I don't know anymore and I can't find the page. I just recall that it took me quite some to find an up-to-date version.
If you don't mind, I can share the file I downloaded via my dropbox:
https://dl.dropboxusercontent.com/u/7619865/dcraw_1461.zip

@Friedemann:
Here are two RAW files taken with DMC-G6:
https://dl.dropboxusercontent.com/u/7619865/P2020739.RW2
https://dl.dropboxusercontent.com/u/7619865/P2030035.RW2
(0003523)
Eric   
2018-07-05 13:23   
The new release 3.5 is using dcrawlib.dll from 2016.

The issue seems to be resolved for the rw2 of my G5 file, but I have now a G80/G81 camera which RW2 are badly shown.

Could you update the dcraw lib in 3.5.x ?


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
1955 [GeoSetter] User Interface feature always 2018-07-05 13:12 2018-07-05 13:12
Reporter: Eric Platform:  
Assigned To: OS:  
Priority: normal OS Version:  
Status: new Product Version: 3.5  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Restore open file in context menu
Description: Just upgraded to 3.5, a very welcome update after 6 years on 3.4.14 !
However, I miss one basic feature: the opportunity to open the file from the context menu in Geosetter: i use it to view a picture in full size, especially because the preview in Geosetter is still problematic with Panasonic RW2 files (see http://www.geosetter.de/mantis/view.php?id=1140 still not resolved, because of outdated version of dcraw lib?)
It is possible to get the 'open' back?
Tags:
Steps To Reproduce:
Additional Information:
Attached Files:
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
982 [GeoSetter] User Interface feature sometimes 2012-09-02 19:18 2018-07-05 13:07
Reporter: Eric Platform:  
Assigned To: Friedemann OS:  
Priority: normal OS Version:  
Status: assigned Product Version: 3.4.16 beta  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Feature request: save all metadata in a local file.
Description: Every once a while, while saving, I got a complete freeze of Geosetter and I must kill the process, thus losing all temp data not yet saved. Losing work is always very frustrating.
They might be many different cause for such an issue.
Therefore, it would be much more convenient to save all metadata to be saved in a file BEFORE saving them on each pictures via exiftool.

On exit, Geosetter should write a bool "properly saved". If a crash or a freeze happen, on next start, Geosetter will read that it was not properly saved and will load the metadata file saved before.

With this quite simple feature, it will again a pleasure to use Geosetter, even if it's crashed.

PS: 3.4.16 is release, not beta
Tags:
Steps To Reproduce:
Additional Information:
Attached Files:
Notes
(0001925)
Eric   
2013-09-15 17:17   
what do you think about this?
(0001957)
Friedemann   
2013-12-01 17:41   
Yes, very good idea!
(0001990)
Friedemann   
2013-12-08 18:41   
The data will be saved now in background. When closing the program without finished the saving processes, next time when opening GeoSetter you will be asked to continue. It's not finished already, the user interface has to be still adjusted, for example the content of new panel for showing the queued files. But it shuld work already...
(0002068)
Eric   
2014-05-16 22:18   
if implemented, should it be marked as resolved?
(0003522)
Eric   
2018-07-05 13:07   
just upgraded to 3.5 and had another crash, allowing me to check these feature: well implemented in the collection mode. The ticket can be closed!


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
1206 [GeoSetter] Image Data minor N/A 2014-07-29 14:05 2018-07-01 03:19
Reporter: jmoliver Platform:  
Assigned To: Friedemann OS:  
Priority: normal OS Version:  
Status: assigned Product Version: 3.4.14 Release  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: [Feature Request] Use Foursquare to obtain Sublocation names
Description: Although Geonames.org has a lot of locations, it would be interesting if the nearby sublocation names could be retrieved from Foursquare as well. User would log in to Foursquare via GeoSetter.

Also, retrieving and displaying places where the user has checked in, would aid in the process of geotagging photos.
Tags:
Steps To Reproduce:
Additional Information:
Attached Files:
Notes
(0002160)
jmoliver   
2014-07-29 14:30   
Interesting. I just discovered one can do something similar! Foursquare exposes location data as kml in https://foursquare.com/feeds/

It would be nice then, if the feed can be added directly to Geosetter. Without having to download it to the PC first.
(0002161)
jmoliver   
2014-07-30 04:43   
The KML export feed contains the geo coordinates, placename, date of checkin as well as the URL of the foursquare location. This may come in use for synchronization.
(0002508)
jmoliver   
2017-05-16 23:04   
This is somewhat related to this issue: http://www.geosetter.de/mantis/view.php?id=1307

Ref: https://jmoliver.wordpress.com/2016/03/18/using-iptc-location-identifiers-to-link-your-photos-to-knowledge-bases/
(0003520)
jmoliver   
2018-07-01 03:19   
I wrote a blog post on how to use Foursquare Check-ins with GeoSetter - more of a hack.

Keeping a log of your visited locations for later adding them to your photo’s metadata
https://jmoliver.wordpress.com/2018/06/30/keeping-a-log-of-your-visited-locations-for-later-adding-them-to-your-photos-metadata/


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
1225 [GeoSetter] Image Data feature have not tried 2014-11-17 16:16 2018-06-27 14:44
Reporter: Yirg Platform: Windows  
Assigned To: Friedemann OS:  
Priority: normal OS Version:  
Status: resolved Product Version: 3.4.14 Release  
Product Build: Resolution: fixed  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Option to disable addition of geo:lat, geo:lon and geotagged
Description: I just discovered GeoSetter and am very impressed. The software seems to do exactly what I want, and that is to add location information based on the GPS info embedded in my Sony A77 files. The only issue I have is that it adds the tags geo:lat, geo:lon and geotagged which seems redundant because the GPS information is already in the files. Moreover, this clutters the image cataloging software I'm using with many needless tags, making manually entered tags harder to access. See attached screenshot. Is there a way to disable the addition of these three keywords? If not, I really hope you see the value and would consider adding it.
Tags:
Steps To Reproduce:
Additional Information:
Attached Files: psp-x7-tags.png (14,126 bytes) 2014-11-17 16:16
https://geosetter.de/mantis/file_download.php?file_id=406&type=bug
error.PNG (24,365 bytes) 2018-06-18 11:30
https://geosetter.de/mantis/file_download.php?file_id=716&type=bug
Flickr Geo Tags.PNG (45,403 bytes) 2018-06-19 07:56
https://geosetter.de/mantis/file_download.php?file_id=717&type=bug
Notes
(0003502)
Kugelblitz78   
2018-06-15 02:30   
Hello,
I have exactly the same issue with geosetter. The Additional Tags makes working with Tags in other programs very messy.

I love to have a feature to bulk remove the "geo:lat=xxxxx", "geo:lon=xxxxx" and "geotagged" Tags from all my Images.
(0003503)
heiko   
2018-06-16 16:26   
you have the posibility to delete these tags with an additional ExifTool command.
(0003504)
Kugelblitz78   
2018-06-17 11:22   
Hello Heiko,
thank you for the Message.
I have no clue how to use ExifTool commands.
What would the command be to delete all "geo:lat=xxxxx", "geo:lon=xxxxx" and "geotagged" Tags from all my Images ?
Danke für deine Hilfe
Schöne Grüße
mARTin
(0003505)
heiko   
2018-06-17 20:54   
Hallo Martin,

ich habe gerade ein paar meiner Bilder angeschaut, und da gibt es nirgends ein "geo:lat=xxxx". Sollte der Tag so heißen, dann öffne die Einstellungen ("Datei | Einstellungen") und wechsle auf den Reiter "ExifTool". Hier aktivierst du dann "Zusätzliche ExifTool-Kommandos nach GeoSetter-Kommandos aktivieren" und trägst folgendes ein:

-geo:lat= -geo:lon= -geotagged=

evtl. muss noch ein -execute vor das Kommando, aber das müsstest du testen.

Grüße
Heiko
(0003506)
heiko   
2018-06-17 20:56   
ach ja .. bitte mit Testbildern probieren bis alles so ist wie es sein soll! Mit den ExifTool Kommandos kann man sich durchaus einiges abschießen! In der Hilfe steht da übrigens auch was dazu ..
(0003507)
Kugelblitz78   
2018-06-18 11:30   
Hallo Heiko,
vielen Dank für Deine Antwort. Hat mich schon mal in die richtige Richtung verwiesen.

So ganz hat es jedoch nicht geklappt. (siehe Screenshot)
Bei der Methode muss ja auch jede Datei erstmal geändert werden damit geosetter diese Speichert und dann die zusätzlichen exiftool-Kommandos auch ausführt.

Denke ich werde es mit dem ExifTool direkt versuchen und habe in dem Support Forum die Frage beschrieben.

http://u88.n24.queensu.ca/exiftool/forum/index.php/topic,9288.0.html
(0003508)
heiko   
2018-06-18 20:26   
stimmt, bei der Methode muss das Bild gespeichert werden, aber für die Zukunft ist das sicher ein gangbarer Weg. Ich verwende diese Kommandos z.B. um das Copyright automatisch in meine Bilder zu schreiben. Ich würde also die bestehenden Bilder direkt mit ExifTool bearbeiten und die zukünftigen mit GeoSetter ..

So wie das im ExifTool Forum aussieht scheint der Aufruf doch ein wenig komplexer zu sein.
(0003510)
Kugelblitz78   
2018-06-18 22:49   
Hallo Heiko

der korrekte exiftool befehl für diese Aufgabe lautet:

exiftool -sep xxx "-subject<${subject@;$_=undef if /^(geo:lat=|geo:lon=|geotagged)/}" "-Keywords<${Keywords@;$_=undef if /^(geo:lat=|geo:lon=|ffffffffffffffff)/}" -r -overwrite_original d:\fotos

Wobei "d:\fotos" natürlich der Pfad zu den Bildern ist.

Hello Yirg,
I know some years have passed but if you still need to solve this issue you can download the exiftool and use the command written above. Just change the Path "d:\fotos" to match your Path to your Images.

Cheers
(0003513)
Yirg   
2018-06-19 00:11   
Hi Kugelblitz78,

I haven't been used GeoSetter since I created this bug, although I would love to if it didn't add these tags. I'm not sure how I feel about using this complex command-line solution. I would much prefer if these tags were not added in the first place than using a solution that could result in unexpected and bad results if I mess up even a single character. I think I'll wait for the option to not include these tags as part of GeoStter itself before I start using this application. I haven't lost hope...
(0003514)
Yirg   
2018-06-19 00:15   
BTW, I'd be happy to donate something (e.g. $20) if it helped get this issue fixed, but I haven't seen any update on this bug from the project maintainer in more than a year...
(0003515)
Kugelblitz78   
2018-06-19 07:56   
Hello Yirg,
in the Current Geosetter Version you have to check a box in the Settings menu if you want these Tags to be added. If you do not want them (like we do) make sure it is unchecked.

The Command line works like charme and it is a one time fix for the "old" Pictures.

Cheers
(0003516)
Kugelblitz78   
2018-06-19 08:45   
exiftool -sep xxx "-subject<${subject@;$_=undef if /^(geo:lat=|geo:lon=|geotagged)/}" "-Keywords<${Keywords@;$_=undef if /^(geo:lat=|geo:lon=|geotagged)/}" -r -overwrite_original d:\path-to-your-pictures
(0003518)
Kugelblitz78   
2018-06-21 17:32   
If you like not to display the errors on screen but log them in a file you can use this command

exiftool -sep xxx "-subject<${subject@;$_=undef if /^(geo:lat=|geo:lon=|geotagged)/}" "-Keywords<${Keywords@;$_=undef if /^(geo:lat=|geo:lon=|geotagged)/}" -r -overwrite_original d:\path-to-your-pictures 2>error_log.txt
(0003519)
Friedemann   
2018-06-27 14:44   
(Last edited: 2018-06-27 14:44)
Kugelblitz78 und Heiko, danke für Euern Support!!! :-) Bin zurück aus dem Urlaub ;-) Ich schließe das jetzt, diese Flickr-Daten gibt's ja in der aktuellen Version nicht mehr...



View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
1488 [GeoSetter] User Interface major always 2017-05-25 18:55 2018-06-27 14:41
Reporter: petergabor Platform: HP ZBook 17 mobile workstation  
Assigned To: Friedemann OS: WIN  
Priority: urgent OS Version: 7 pro 64 bit  
Status: resolved Product Version: 3.4.14 Release  
Product Build: Resolution: fixed  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Map is not visible
Description: No map and tracks are visible in the map section. See the attached screenshot.
Tags:
Steps To Reproduce: Restart the software
Additional Information:
Attached Files: no_map.jpg (240,545 bytes) 2017-05-25 18:55
https://geosetter.de/mantis/file_download.php?file_id=493&type=bug
Notes
(0002572)
petergabor   
2017-05-25 19:04   
Solved. Thanks.
I did not recognize the similar topic but no I found it.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
1953 [GeoSetter] Image Data feature have not tried 2018-06-22 01:15 2018-06-22 01:15
Reporter: jmoliver Platform:  
Assigned To: OS:  
Priority: normal OS Version:  
Status: new Product Version: 3.5  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Support new exif 2.31 time zones features
Description: The new exif 2.31 standard added timezone support for exif dates. This probably should be an option to be enabled or disabled since it may cause problems with other applications which may not yet support it.

0x9010 OffsetTime string ExifIFD (time zone for ModifyDate)
0x9011 OffsetTimeOriginal string ExifIFD (time zone for DateTimeOriginal)
0x9012 OffsetTimeDigitized string ExifIFD (time zone for CreateDate)

source: https://www.sno.phy.queensu.ca/~phil/exiftool/TagNames/EXIF.html
reference spec: http://www.cipa.jp/std/documents/e/DC-008-Translation-2016-E.pdf
Tags:
Steps To Reproduce:
Additional Information:
Attached Files:
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
1948 [GeoSetter] User Interface feature N/A 2018-05-21 17:00 2018-05-21 17:00
Reporter: jmoliver Platform:  
Assigned To: OS:  
Priority: normal OS Version:  
Status: new Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Feature Request: Add landmark recognition capability using Google Vision API
Description: The Google Vision API provides the capability of recognizing landmarks and the corresponding location (lat/long) of a photo based on image recognition. This is particularly helpful when scanning analog images and the location of the photo is unknown.

Refer to this post: https://jmoliver.wordpress.com/2018/05/21/finding-where-a-photo-was-taken-using-google-vision/

It would be a great functionality to add to GeoSetter in which the user could press a button and a suggestion is made to the location and the landmark name, which can be added to the image description or caption.

The user will need to provide a Google API key in a similar way users may need to provide Geoname credentials to use the service.
Tags:
Steps To Reproduce:
Additional Information:
Attached Files:
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
1947 [GeoSetter] User Interface minor always 2018-05-20 23:09 2018-05-20 23:09
Reporter: mherbst Platform: Intel i7  
Assigned To: OS: Windows 10 Pro 64 Bit  
Priority: normal OS Version:  
Status: new Product Version: 3.5  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Bild-Info Anzeige bleibt leer
Description: Seit dem Update auf 3.5 bleibt die Anzeige der Bild-Informationen im separaten Fenster leer. Das Auslesen der EXIF/IPTC-Daten funktioniert allerdings. Bei den einzelnen Bildern werden sie korrekt angezeigt und auch unterhalb der Bild-Info steht z.B. "288 Einträge (Eingebettet und Sidecar-Datei)".

Die Fotos sind im Nikon Raw-Format (.nef) und die EXIF/IPTC-Daten befinden sich dementsprechend in einer XMP-Datei.

Aber auch mit einer jpg-Datei, die ich mit dem Smartphone aufgenommen habe, funktioniert es nicht.
Tags:
Steps To Reproduce:
Additional Information: Ist es evtl. ein Anzeigeproblem? Ich habe einen 4K-Monitor und die Skalierung auf 150% eingestellt.
Attached Files: bug.png (223,104 bytes) 2018-05-20 23:09
https://geosetter.de/mantis/file_download.php?file_id=713&type=bug
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
1878 [GeoSetter] User Interface crash N/A 2018-03-13 01:51 2018-05-18 15:09
Reporter: pbb Platform: Windows 10  
Assigned To: Friedemann OS: Windows 10  
Priority: high OS Version: 10  
Status: assigned Product Version: 3.4.51 beta  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: EStreamError - Expandieren des Speicher-Stream wegen Speichermangel nicht möglich
Description: I am getting *a lot* of these error messages. It's been 2.5 hours now since the last crash, but they can also happen more often.

E-mailing the reports doesn't work (GMail can't handle the big attachment over the command-line), and often I can not save the report either (nothing happens at the moment the file save dialog should show up). But this time I was able to save the crash report.
Tags:
Steps To Reproduce: Just my normal usage of the program. Maybe it happens more often when I'm quickly going through the photos, and when it's saving a lot of changes.

It often happens together with graphics being messed up; either all icons have become black, or the photo preview is seriously damaged, or map tiles are missing.
Additional Information: I guess I'm working with large numbers of files. During this crash, GeoSetter was busy saving the changes to 564 files.
Attached Files: bugreport.txt (20,582 bytes) 2018-03-13 01:51
https://geosetter.de/mantis/file_download.php?file_id=689&type=bug
bugreport2.txt (36,714 bytes) 2018-03-14 00:34
https://geosetter.de/mantis/file_download.php?file_id=690&type=bug
Notes
(0003395)
pbb   
2018-03-14 00:33   
I have attached another crash report. Very similar, but this time it's an "EOutOfResources - Not enough storage is available to process this command" crash.

Not really sure which storage is running out, there's 14.5 GB free on the hard disk, 1640 MB free physical memory, and 126 MB largest free memory block. Would think that is enough, especially after 24 seconds run time :)

Thanks for looking into this!


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
1896 [GeoSetter] User Interface major always 2018-03-26 23:49 2018-05-18 15:08
Reporter: codesuth Platform: Mac Pro  
Assigned To: Friedemann OS: Windows 10 Professional  
Priority: normal OS Version: 10  
Status: assigned Product Version: 3.4.14 Release  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Hangs when over 10k files in directory
Description: If I start the program and there are close to 10k files for example currently 9856 it starts to display thumbnails and the black spinning circle over some of them freeze, when I examine in Resource Monitor it appears that one core of the CPU is 100%. I assume its forking exif for each of those photos because if I let it set long enough usually a few hours it will be come responsive again.I have 32GB and 2x6 core Xenon processors so is just that one core that's pegged rest of server is idle. Also checked the IO on the disk the images are stored on and that's not a bottle neck. Perhaps it exists but a user setting to tell it that it can use more than one core would be nice :-)
Tags:
Steps To Reproduce: Just put 10,000 photos in a single directory and launch the app.
Additional Information:
Attached Files:
Notes
(0003462)
sanantonioglamour   
2018-04-12 10:44   
(Last edited: 2018-04-12 10:44)
HI



View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
1943 [GeoSetter] User Interface block sometimes 2018-05-08 22:30 2018-05-16 23:08
Reporter: GeoUser Platform:  
Assigned To: OS:  
Priority: high OS Version:  
Status: new Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Adress-Suche liefert falsche Werte
Description: Version 3.4.82 beta

Bei einer Vielzahl von Fotos liefert die Adress-Suche falsche Werte / Orte.

- Nordrhein-Westfalen;Dortmund;Ickern existiert nicht. Ickern ist ein Ortsteil von Castrop-Rauxel

Nordrhein-Westfalen;Castrop-Rauxel;Recklinghausen existiert nicht. Recklinghausen ist Stadt und Kreis (in dem sich Castrop-Rauxel) befindet.

Solcherlei Fehler werden ständig geliefert. Abgefragt wird GeoNames mit eigenem Benutzernamen.


Tags:
Steps To Reproduce: Foto-Verzeichnis laden, Track laden, Fotos edit, Online abfragen
Additional Information: Die Software RouteConverterWindows beispielsweise kann für alle Positionen in der Trackliste Vervollständigen -> Postanschrift. Hier wird nicht GeoNames, sondern Nominatim abgefragt und korrekte Straße, Hausnummer, Plz, Ort geliefert. Nominatim kennt auch den Ortsteil. Die Daten von GeoNames sind extrem unzuverlässig und sehr oft falsch.
Attached Files:
Notes
(0003496)
GeoUser   
2018-05-16 11:09   
Hallo! Ich versuche das Problem zu verstehen und zu lernen. Und heraus zu finden ob ich was falsch mache. Und ein Ergebnis der Recherche ist, dass GeoNames eigentlich kaum eine Chance hat korrekte Orte zu liefern. Also überwiegend. Man muss jederzeit zu jedem von hunderten Fotos (auch auf Reisen in unbekanntem Gebiet) genauestens wissen wo man war, wo das Foto aufgenommen wurde, wie die Orte, Ortsteile, Bezirke und Verwaltungsgrenzen heißen. Sonst glaskugelt GeoNames irgendetwas zusammen, von dem man später am Rechner ohne eigene genaue Kenntnis gar nicht weiß, was zusammen passt.


In einem Forum fand ich die Information, dass GeoNames wohl ausschließlich "zentrumsbasiert" funktioniert. Habe ich also eine Koordinate im Foto
51.58729, 7.39241
Korrekt:
Emscherallee, Groppenbruch, Dortmund, Regierungsbezirk Arnsberg, Nordrhein-Westfalen, 44359, Deutschland

kann GeoNames aus folgenden Bestandteilen umliegender Orte alle möglichen Kombinationen würfeln:

Mengeder Straße
Emscherallee

Groppenbruch
Brockenscheidt
Brambauer
Ickern Süd

Dortmund
Waltrop
Lünen
Castrop-Rauxel

Kreis Recklinghausen
Kreis Unna

Regierungsbezirk Arnsberg
Regierungsbezirk Münster

Nordrhein-Westfalen

44359
45731
44536
44581

Deutschland

Und warum das? Weil GeoNames nur nach Entfernungen zu benamten Punkten arbeitet und (anders als OpenStreetMap) nicht mal Boundaries kennt...

Zitat: "The service is based on centroid point coordinates as we don't have boundary data"

Uff. Keine Boundaries. Das muss man erst mal verdauen. Da wird blitzartig klar, wieso aus

- Robert-Bosch-Straße, Hagener Straße, Westhofen, Schwerte, Kreis Unna, Regierungsbezirk Arnsberg, Nordrhein-Westfalen, 58239, Deutschland
Hagen-Westhofen wird

und aus

- 147, Syburger Dorfstraße, Buchholz, Syburg, Dortmund, Regierungsbezirk Arnsberg, Nordrhein-Westfalen, 44265, Deutschland
Hagen-Buchholz

und so weiter...

Ok, das GeoNames Problem dürfte dann vermutlich nicht innerhalb GeoSetter lösbar sein, nehme ich als Laie an. Vielleicht gibt es ja doch eine Chance einen Nominatim-Provider zu finden, dessen API ähnlich nutzbar ist wie GeoNames und das in GeoSetter einzubauen... Lieber Friedemann, dein Programm ist wirklich klasse und ich finde es bewundernswert wenn jemand über so viele Jahre das Gefühl vermittelt mit Herzblut dabei zu sein. Dass dann die Suchergebnisse von Dritter Seite eine so wichtige Funktion nahezu unbrauchbar machen, ist angesichts der vielen Zeit und Liebe zum Detail die Du in die Software gesteckt hat echt schmerzlich.
(0003497)
Friedemann   
2018-05-16 17:43   
Ja, ich weiß, dass die GeoNames-Ergebnisse leider nicht für jeden passen. Für mich tun sie das eigentlich seit Jahren. Allerdings brauche ich für meine Fotos auch keine adressgenauen Daten, den eigentlichen Ort ergänze ich meist selbst.

Wahrscheinlich ist Google eine Alternative, oder? Das habe ich bisher noch nicht eingebaut, weil die Adressenabfragen mein Kontingent zu sehr belasten würden. Nun hat Google allerdings sowieso gerade sein Geschäftsmodell geändert, ich musste z.B. für meinen API-Key nun eine Abrechnungsmöglichkeit hinterlegen. Ich hoffe, dass ich alles richtig eingestellt habe, so dass mir keine Kosten entstehen werden. Es kann durchaus sein, dass ich auch den Zugriff auf die Karte nicht so lassen kann wie er ist, d.h. die Benutzer müssten sich dann selbst einen API-Key registrieren, leider. Wenn das der Fall wäre, könnte ich natürlich auch Google hinzunehmen. Allerdings, ich möchte keine große Hoffnung machen, eins nach dem anderen. Eine Änderung der Ortsdatenabfrage wird sicherlich dieses Jahr nix mehr werden :-/ Wie auf meiner Webseite angekündigt, versuche ich ja ein etwas größeres Update fertig zu bekommen. Erst danach stünde dann eine Änderung der Ortsdatenabfrage, vielleicht ein Hinzufügen kostenpflichtiger Optionen, zur Disposition. Um Missverständnissen entgegen zu wirken: "Kostenpflichtig" natürlich nicht in Bezug auf mich, sondern die Möglichkeit irgendwelche Services einzubinden, bei denen sich der Benutzer dann ggf. selbst registrieren kann/muss.
(0003498)
Friedemann   
2018-05-16 17:51   
Ach, ich sehe gerade erst, Du hast "Nominatim" erwähnt. Das kannte ich bisher nicht. Ist das kostenfrei? Sieht ja fast so aus... Ach so, man braucht einen Provider, der die Datenabfragen kostenfrei zur Verfügung stellt? Also, ich bin ja für alle Aleternativen offen, auch wenn ich das nicht nächste Woche gleich einbauen werde. Änderungen an der Ortsdatenabfrage werde ich definitiv nicht in dieser Version machen. Erst ab der kommenden Version 4, wenn ich sie denn mal fertig habe...
(0003499)
Friedemann   
2018-05-16 18:09   
Hier sind ja 3 Provider aufgeführt, wobei mir LocationIQ (https://locationiq.org/) mit 10.000 möglichen täglichen freien Abfragen durchaus akzeptabel erscheint: https://wiki.openstreetmap.org/wiki/Nominatim#Alternatives_.2F_Third-party_providers Man würde dann natürlich auch zwingend einen eigenen Account benötigen...
(0003500)
GeoUser   
2018-05-16 23:08   
Hallo und ganz lieben Dank schon mal alleine für deine schnelle Antwort, da Du das in der Freizeit machst hätte ich gar nicht so schnell damit gerechnet, top!

Das mit Nominatim ist sicher so eine Sache, was die Abfrage-Kontingente angeht. Abfragen auf den OpenStreetMap-Servern geht, soll aber nur für Testzwecke und einzelne Anfragen genutzt werden und Massenabfragen werden sicher gedrosselt. Aber sich für einen Account irgendwo zu registrieren ist sicher das Letzte woran es scheiten sollte (erst recht nicht, wenn man sich irgendwo im Bereich der kostenfreien aber registrierungspflichtigen Kontingente bewegt), wenn man diese Funktion benötigt oder sehr gerne benutzen möchte. Auch bei GeoNames war ja zumindest ein Account nötig / sinnvoll.

Rein von der Datenqualität sollte das für die größten Teile der Welt ein Quantensprung sein, da es sich um OpenStreetMap Daten handelt, wo gerade bei dem hier scheinbar so wichtigen Punkt der Boundaries extrem viel Wert drauf gelegt wird. Und die Daten sind ja nun auch sehr detailliert, auch wenn man/jeder vielleicht nicht (für jedes) Foto(s) immer Genauigkeit bis auf die Hausnummern- oder Objektebene benötigt. Aber da dort Daten immer innerhalb von Boundaries liegen, kann aus Dortmund-Syburg eben nicht Hagen-Syburg werden, und aus einer Bauernschaft in X kein Stadtteil von Y. Nun ist ja auch die Fotografie so wunderbar vielfältig, dass es ja auch nicht schaden kann, so detaillierte Daten zu haben. Schon alleine wenn man wo ist, wo man sich nicht auskennt und die Abfrage der Koordinaten wirft dir sogar aus, dass es z.B. das BvB Fussballstadion ist (https://nominatim.openstreetmap.org/search.php?q=51.49241%2C+7.450921&viewbox=). Nur mal so als blödes Beispiel, gerade nichts besseres im Kopf wo man wirklich sagen könnte wenn man da war, muss man nicht erkannt haben wo ;-) Gerade da wird ja erst interessant, meine sich permanent wiederholenden Locations beschrifte ich auch blind bzw. habe Kürzel für die Textersetzung.

Mir ist das Problem beim Radfahren aufgefallen, wo man sich eben durch verschiedene Bauernschaften und über Stadtgrenzen hin und her bewegt, dass da die Daten hinten und vorne nicht stimmen können und ich in der Nachbereitung zu einer Kapelle recherchieren wollte, die GeoNames in Dortmund-Leveringhausen verortet hat. Das ist natürlich vollkommener Blödsinn, das wunderschöne kleine Ding steht in der Nachbar-Stadt Waltrop, immerhin stimmte die Bauernschaft ;-)))) Wäre das jetzt nun nicht in meinem Heimatrevier, hätte ich den Fehler wie bei den anderen Fotos zuvor im Archiv nicht bemerkt.

Für die meisten von uns gerade für den privaten Gebrauch nicht realisierbar, daher nur am Rande erwähnt: Bei Nominatim kann man sich theoretisch seine eigene Instanz installieren, planet.osm herunterladen und seinen eigenen Server betreiben. Da gibt es wohl auch noch ein paar andere Engines für eigene Server. Aber wirklich nur ganz am Rande, das werden die wenigsten stemmen können (ich auch nicht ;-) )

Zur Qualität der Daten ein kurzer Schnelltest, vielleicht kann ich damit einen klitzekleinen Beitrag leisten.
GPS-Log von einer Radtour im Grenzbereich der vier Städte Dortmund, Schwerte, Hagen und Herdecke. Geladen in die Software von http://www.routeconverter.de. Die hat eine Funktion "Vervollständigen->Postanschrift" und hat die folgenden Geokodierungsdienste implementiert, deren Ergebnisse:

GeoNames
"51.4188680,7.5052050,Syburg"

Photon by komoot.de
51.4188680,7.5052050,44265 Dortmund; North Rhine-Westphalia; Germany


Google
51.4188680,7.5052050,Syburger Dorfstraße 135; 44265 Dortmund; Deutschland

Nominatim
"51.4188680,7.5052050,Syburger Dorfstraße 135; 44265 Nordrhein-Westfalen; Deutschland"

Nur Google und OpenStreetmap erkennen die Straße und sogar Hausnummer, Google unterschlägt das Bundesland welches bei Nominatim aber neben noch deutlich mehr Details die man verarbeiten _könnte_ natürlich da ist. (135, Syburger Dorfstraße, Buchholz, Syburg, Dortmund, Regierungsbezirk Arnsberg, Nordrhein-Westfalen, 44265, Deutschland (Camp Site) direkte Abfrage https://nominatim.openstreetmap.org/search.php?q=51.4188780%2C7.5053350&viewbox=).

Mir mögen da gar nicht alle Möglichkeiten einfallen, aber man stelle sich vor man mache im Urlaub wo man sich rein gar nicht auskennt ein Foto einer wunderschönen Wegkappelle und OpenStreetMap kann Daten bis hinter zum Namen der Kapelle liefern. Meiner bescheidenen Meinung nach wäre also OSM als zukünftige Datenquelle geradezu prädestiniert, wenn schon Programmierarbeit da hinein gesteckt wird für eine neue Version.

Wobei mich gerade im OpenStreetMap-Umfeld nicht mal wundern würde, wenn da schon jemand einen Referenzcode als OpenSource programmiert hat, den man in seine Anwendung implementieren kann...

In diesem Sinne, meinen Respekt, meinen Dank und Wünsche für Gesundheit und Glück an Dich und deine Familie!


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
1945 [GeoSetter] Image Data major always 2018-05-14 10:50 2018-05-14 10:50
Reporter: Ronny MF Ho Platform: Windows  
Assigned To: OS:  
Priority: high OS Version: 10  
Status: new Product Version: 3.5  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Incorrect diaplay of Sesageminal gps info
Description: I found that GPS location data in Sexagesimal cannot be displayed fully. To be exact, the first digit of "minute" was replaced with a question mark. This happened for previous versions.
Tags:
Steps To Reproduce:
Additional Information:
Attached Files: Screen Shot 2018-05-14 at 12.10.31 PM.png (102,301 bytes) 2018-05-14 10:50
https://geosetter.de/mantis/file_download.php?file_id=712&type=bug
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
1000 [GeoSetter] Image Data major always 2012-11-05 16:09 2018-05-13 00:07
Reporter: johanvranken Platform:  
Assigned To: Friedemann OS:  
Priority: normal OS Version:  
Status: assigned Product Version: 3.4.34 beta  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: In all versions of Geosetter one looses the GeoTag as added through Windows Live Photo Gallery
Description: Unfortunately, I don't know where the Windows program stores these geotags, but they have to be there somewhere, as I can view them on two separate computers, whereby I only copy the image file from one to the other.
As a lot of the photos have been geotagged in this program, and it actually is quite good, it would be a major help to be able to import them, so that they are available in Geosetter and programs using the same geotagging data.
Tags: IPTC, IPTCCore, IPTCExtension, LocationCreated, Windows Photo Gallery, XMP
Steps To Reproduce:
Additional Information:
Attached Files: 2012-10-06Sat12.27-007 Nittel, der Nitteler Hof.JPG (1,776,028 bytes) 2012-11-05 16:09
https://geosetter.de/mantis/file_download.php?file_id=307&type=bug
Image Info example.jpg (59,124 bytes) 2016-05-12 12:09
https://geosetter.de/mantis/file_download.php?file_id=435&type=bug
Notes
(0002301)
SQuarmby   
2016-05-06 15:17   
I also have this issue (May 2016) but there does not seem to be a solution yet.

Issue detail:
a) I import my photos to Photo Gallery; there are no coordinates because my Canon EOS600D is just too old to manage these.
b) I sort my photos in Photo Gallery and add locations <as text> in the geotag field. (I have also used Photo Gallery to add locations to thousands of older images.)
c) Now, I want to filter these images in GeoSetter so that I can add coordinates <as numerical latitude/longitude> using the map function. Because a popular location might have been visited many times in different years, I want to search or filter the images in multiple folders to find these locations.
d) I can view where the data is stored by using ExifTool Image Info (five fields eg "Location Created City") but it is not possible to use these fields in the search or filter tools.

Would it be possible to add these fields to the search and filter functions?
(0002302)
heiko   
2016-05-11 21:11   
what exactly are you missing? I found in the ExifData the following:
Location Created Country Name: Germany
Location Created Province State: RP
Location Created City: Nittel

Is this all that you are missing? Or should any GPS coordinates be available?
(0002303)
johanvranken   
2016-05-11 21:27   
I use Photo Gallery to edit the pictures and add basic place coordinates, as you see in the ExifData. When I use geosetter, I use the map function. It would be ideal if the map function would use those exifdata to get an approximate Latitude/longitude which I then could use to pinpoint the exact location. It would make work a lot easier ...
The ideal would be to get GPS coordinates out of Photo Gallery, however, I fear this is not possible if PG does not put GPS coordinates in the Exif ...
(0002304)
heiko   
2016-05-11 21:35   
I just took a look how to copy the field "Location:LocationCreatedCity" into the standard Exif field, so GeoSetter will show the City

a possible way to do this is to use ExifTool. The command could be like that:

ExifTool "-Location:City<Location:LocationCreatedCity" test.jpg

with this command line a backup copy of the jpg file will be created. The command line can also be changed that a complete directory will be processed. There is also a parameter to do the work recursive.
(0002305)
heiko   
2016-05-11 21:39   
what do you mean with the "Basic place coordinates"? The City and Country?

You could copy the City into the standard Exif field. After that set a filter on each City, search this City in the map and assign the GPS coordinates to your Images.

It's not the fastest way but it should work
(0002306)
johanvranken   
2016-05-11 22:24   
The lowest known entity, so that would be the City.

How could I copy the City (using whatever necessary, but ideally either geosetter or Exiftool.
As I am not a computer expert, I'm not confident to use the Exiftool command line. Where can I find the possibilities thereof (command line manual of some sort)? Is there a GUI that lies on top of Exiftool to use it instead of the command line?
(0002307)
heiko   
2016-05-11 22:47   
(Last edited: 2016-05-11 22:49)
you can use the "Additional ExifTool Commands". you will find these commands in the settings dialog in the tab "ExifTool". I've just tried it with the ".. Commands before GeoSetter ..".

Use this command to copy the city:

-execute "-Location:City<$Location:LocationCreatedCity"

the disadvantage of this way is, that the command will only be executed if you save your images. So you have to change something, save the image and then take back your changes and save the image again.

You can certainly extend the command above to copy more Exif fields into another field.

This is the ExifTool Homepage:
http://www.sno.phy.queensu.ca/~phil/exiftool/
In the forum exists a section "ExifTool Gui", but I can't say anything about the GUI

(0002308)
SQuarmby   
2016-05-12 12:04   
(Last edited: 2016-05-12 12:10)
Hi Heiko

Yes... the fields created by Photo Gallery (PG) are:
 Location Created Country Name: Germany
 Location Created Province State: RP
 Location Created City: Nittel
 ...and...
 Location Created Sublocation: xxx

When you create a GeoTag in PG by entering a text lookup, it uses Bing to find / confirm your entry and it completes the first three fields. You can then choose to keep the Bing proposal or update it further (including adding sublocation). PG then populates these fields and they can be seen in GeoSetter by getting the Image Info using ExifTool (CTRL-I).
See attached file <Image Info example.jpg>

In PG, I use the Sublocation for a street or to identify a landmark (eg restaurant or museum). This info is important when I switch to GeoSetter because it helps me find the the exact location on the map.

You suggested copying the city info using a command line (from Location:LocationCreatedCity to Location:City). Like Johan, I am not so confident about doing this but I can see two big advantages:
- the info can then be seen in thumbnail view in Geosetter so it is easy to select the required images manually
- the info can be Search-ed or Filter-ed easily using the existing functionality
For this solution to be excellent, however, it needs to copy all four fields. How is that done? Is it four command lines in "Commands before GeoSetter"? What are all the correct comnands?

BUT...
When I save my data in GeoSetter it does not update the 'Location Created xxx' fields in the image file. Thus, if I make a correction to the data in GeoSetter (Bing is not very good, is it?) I have a situation where there are two slightly different sets of embedded data in the image file and if I look at the picture in PG it has the old Bing data.

Question: can I use the "Commands after GeoSetter" to update these four fields? What would be the command lines?

Also, if this is not possible, then next time I open the image in GeoSetter the "Commands before GeoSetter" will overwrite my corrections with the old Bing data and I will be back at step 1.

Comments???

Thanks.

(0002309)
heiko   
2016-05-12 21:42   
I think the following should work:

the command to copy the Exif data from Photo Galery to the standard Exif tags:
-execute "-Location:City<$Location:LocationCreatedCity" "-Location:State<$Location:LocationCreatedProvinceState" "-Location:Province-State<$Location:LocationCreatedProvinceState" "-Location:Country<$Location:LocationCreatedCountryName" "-Location:Country-PrimaryLocationName<$Location:LocationCreatedCountryName" "-Location:Location<$Location:LocationCreatedSublocation" "-Location:Sub-location<$Location:LocationCreatedSublocation"

and this command to copy the standard Exif tags to the PG tags:
-execute "-Location:LocationCreatedCity<$Location:City" "-Location:LocationCreatedProvinceState<$Location:State" "-Location:LocationCreatedCountryName<$Location:Country" "-Location:LocationCreatedSublocation<$Location:Sub-location"

I have not tested these commands, so give them a try with test Images.
(0002310)
johanvranken   
2016-05-12 21:49   
Oeps - I'll need some time to get this done and tested ... don't have the time at this moment.
I'll be back!
(0002311)
SQuarmby   
2016-05-13 13:37   
(Last edited: 2016-05-13 13:39)
Hi Heiko, Johan

Thanks for the useful information.

1) Immediate
- I can use the commands described by Heiko to manually move the PG data to the standard Exif fields (after importing them into GS) and then save.
- Similarly, I can copy GS data into the PG fields and save.
- This covers my basic requirements but I still need to:
    a) find and select the files that should be used (because the PG fields are not available in the custom filter / search tools)
    b) work carefully to ensure the "Commands Before / After GeoSetter" are in the correct state (ie with commands or empty) to ensure I do not overwrite other image files by accident

2) Future (no hurry... I can use the immediate solution)
- It would be nice to add these fields to the search and filter tools.
- It would be nice to have a pair of buttons / menu items that run these commands 'on screen'; this would work as follows:
    a) select photos from the thumbnails view
    b.1) click "Copy PG data to image Exif fields" to run the first set of commands on the selection; or
    b.2) click "Copy GS data to image PG fields" to run the second group of commands
    c) the thumbnails would turn red to indicate pending changes (as today)
    d) then the user can save the images (as today)

:-)

(0002312)
johanvranken   
2016-05-13 13:46   
Hi Squarmby, Heiko

Would be ideal indeed !!
And thanks for the help from you both.

KR
Johan
(0002313)
heiko   
2016-05-13 21:00   
you can add something like that to the commands above:

-if "not $Location:LocationCreatedCity eq ''"

the commands will be only executed if the PG tag LocationCreatedCity is not empty.

ExifTool has a very powerful command line. Perhaps it's more secure if you use ExifTool directly. But that's up to you ..
(0002318)
jmoliver   
2016-07-14 20:03   
Interesting discussion. I ran into the same issue SQuarmby described, ending up with mismatched Location information from adding Geotags using Windows Photo Gallery (WPG). WPG reads the legacy "IPTC Core" Location fields which Geosetter uses, but does not write to the "IPTC Core" instead to the "IPTC Extension" Location Created fields.

I used exiftool to read the contents of my "Photos" folder and generate a tab delimited "Photos.txt" file which includes several of the fields:

exiftool -T -Directory -Filename -Sub-Location -Country -State -City -Location -LocationCreatedSublocation -LocationCreatedCountryName -LocationCreatedProvinceState -LocationCreatedCityName -c %.6f -n -r "Photos" > Photos.txt

I then opened up the "Photos.txt" file in Excel and identified all the photos which have mismatched location information. In my case there were not many so I corrected the ones I found using exiftool and similar commands previously mentioned in the comments.

I only use Geosetter for the purpose of geotagging my photos. Also as mentioned in the previous comments I included an exifool command in the GeoSetter settings to run after update operations which copies the "IPTC Core" tags to the corresponding "IPTC Extension" Location Created tags.

Hope this helps.
(0003493)
jmoliver   
2018-05-13 00:07   
I am including a blog post on how to manage Windows Photo Gallery Geotags with GeoSetter- https://jmoliver.wordpress.com/2018/01/25/moving-away-from-windows-photo-gallery-geotags/


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
1784 [GeoSetter] User Interface major always 2017-10-15 22:08 2018-05-11 18:24
Reporter: andrew Platform: PC laptop  
Assigned To: Friedemann OS: Windows  
Priority: high OS Version: 7  
Status: resolved Product Version: 3.4.16 beta  
Product Build: Resolution: no change required  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Google maps not displayed
Description: Updated to Exiftool 10.63

Google maps no longer displayed.
Satellite view says "Sorry we have no imagery here".
Other Google options display a blank window.
Open Street Map still works and displays the photo in the right location
Tags:
Steps To Reproduce: Select a Google map from the dropdown
Additional Information:
Attached Files: geo.jpg (636,219 bytes) 2017-11-25 11:17
https://geosetter.de/mantis/file_download.php?file_id=664&type=bug
Geosetter minus map.jpg (352,224 bytes) 2017-11-30 22:21
https://geosetter.de/mantis/file_download.php?file_id=666&type=bug
Notes
(0003271)
othmarmarti   
2017-11-25 11:19   
The file shows the startup screen. It seems that recent updates of Win 10 changed something in the JavaScript API in Internet explorer. The functionality is still there. I hope that the information helps. Many thanks and best regards, Othmar
(0003274)
andrew   
2017-11-30 22:22   
Thanks Othmar but my startup won't display Google maps and is Windows 7. OSM works fine but I want aerial images.
Also multiple exif edit doesn't work. Maybe need to uninstall and reinstall
(0003492)
andrew   
2018-05-11 17:00   
Just updated laptop to latest Geosetter version (Been using Desktop Win 10 for last few months due to long term issue with satellite image). Google aerial maps are now being displayed.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
1879 [GeoSetter] Image Data feature N/A 2018-03-13 12:45 2018-05-08 20:46
Reporter: PhilM Platform:  
Assigned To: Friedemann OS: Windows 10  
Priority: normal OS Version: 1709  
Status: assigned Product Version: 3.4.14 Release  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: New feature : Add a new map source from Kompass D
Description: I would like to suggest to add a map source to Geosetter.

Kompass maps (www.kompass.de).
I have purchased their paper maps for years to go hiking.

Now, their maps are available on smartphones, but also on the web.

In Geosetter, you give a choice between Google, OSM and MyTopo.
Would it be easy to add Kompass Touristik ?

It covers hiking tracks in Germany, Austria and Italy (France and Switzerland partially). Their maps are excellent quality.

You can see them on : http://www.kompass.de/touren-und-regionen/wanderkarte/

There was a software that downloads their tiles : Mappuzzle
It seems not available anymore on the web.
But here is the section of its config file :

[Kompass.at - Kompass tourism Map]
url=http://ec{2}.cdn.ecmaps.de/WmsGateway.ashx.jpg?Experience=kompass&MapStyle=KOMPASS%20Touristik&TileX={X}&TileY={Y}&ZoomLevel={ZOOM}
[Kompass.at - Winter Map]
url=http://ec{2}.cdn.ecmaps.de/WmsGateway.ashx.jpg?Experience=kompass&MapStyle=Winter%20Touristik&TileX={X}&TileY={Y}&ZoomLevel={ZOOM}
Tags:
Steps To Reproduce: N/A
Additional Information:
Attached Files:
Notes
(0003491)
PhilM   
2018-05-08 20:26   
(Last edited: 2018-05-08 20:46)
Kompass server presents tiles 256 by 256 px.
The numbering is from West to East and from North to South
At zoom level 6, tile 34, 22 is centered around Innsbuck/Austria
Each zoom level increases by a factor 2
The tile number for the left upper quarter of level 6,34,22 will be identified 7,68,44.
The upper right quarter will be 7,69,44
And so on



View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
1825 [GeoSetter] User Interface major always 2017-11-17 20:13 2018-05-08 13:48
Reporter: gabiandrone Platform: PC  
Assigned To: Friedemann OS: Windows  
Priority: normal OS Version: 7  
Status: assigned Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: geosetter does not start
Description: After java update, geosetter does not start at all.
I reinstalled geosetter but the result is the same.
Tags:
Steps To Reproduce:
Additional Information:
Attached Files:
Notes
(0003268)
gabiandrone   
2017-11-20 11:03   
In addition to the problem: It seems that the java update did not create the problem, but the update to exif tools generated it. I installed a geosetter on another computer, it worked, and after exif tools update the same problem occurred. In the previous situation exif tools update followed the java update and I thought it was due to java. It's not java, it looks like it's exiftools.
(0003490)
gabiandrone   
2018-05-08 13:48   
Further details: I have found that the program opens very late, sometimes after half an hour.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
1613 [GeoSetter] Image Data major always 2017-07-10 12:44 2018-05-08 13:11
Reporter: elmario55 Platform:  
Assigned To: Friedemann OS: Windows  
Priority: normal OS Version: Win 10 Prof  
Status: assigned Product Version: 3.4.51 beta  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Save Data not possible
Description: Since version 10.54 of EXIF TOOL it is impossible to save changed date of images.
Until to Version 10.53 it worked proper.
I don't know if only i have this problem and if it is a problem of GEO SETTER, EXIF TOOL or my Windows.
Tags:
Steps To Reproduce: Install diverse Versions of EXIF TOOL
Additional Information:
Attached Files:
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
1603 [GeoSetter] Image Data minor always 2017-07-05 15:59 2018-05-08 13:11
Reporter: IrenicRhonda Platform: chrome  
Assigned To: Friedemann OS: win10  
Priority: normal OS Version:  
Status: assigned Product Version: 3.4.16 beta  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: 200 limit
Description: I have a GeoNames Account and I'm signed in but still getting the 'throttle back message

What am I dong wrong?

Tags:
Steps To Reproduce: Just using GeoSetter for location Data
Additional Information:
Attached Files:
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
1507 [GeoSetter] User Interface feature always 2017-06-05 15:02 2018-05-08 13:11
Reporter: obetz Platform:  
Assigned To: Friedemann OS:  
Priority: normal OS Version:  
Status: assigned Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Synchronize should deal with rounding errors
Description: Synchronize reports coordinates as different even with distances in the order of rounding errors (e.g. 1E-7 degrees or approx. 1cm).

I see differences in destination coordinates where I didn't change anything actively, maybe caused by using different versions of Geosetter.

Synchronize should deal with rounding errors e.g. by using a (user defined) "distance", in it's simplest form a delta value for longitude and latitude, in it's most advanced form in meters.
Tags:
Steps To Reproduce:
Additional Information:
Attached Files:
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
1726 [GeoSetter] User Interface feature N/A 2017-08-31 22:09 2018-05-08 13:11
Reporter: Jeanpierre Platform:  
Assigned To: Friedemann OS:  
Priority: normal OS Version:  
Status: assigned Product Version: 3.4.51 beta  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Einbindung der topographischen Karte "OpenTopoMap"
Description: Gelegentlich fehlt mir bei Tracks von Wanderungen die Information über die Topographie, also insbesondere Höhenlinien. Unter
https://opentopomap.org/about
ist eine sehr detaillierte, kontrastreiche und frei verfügbare topographische Karte im Stil der deutschen topographischen Karten verfügbar.

Es wäre toll, wenn diese in Geosetter ebenfalls verfügbar wäre !
Tags:
Steps To Reproduce:
Additional Information: https://opentopomap.org/about
https://opentopomap.org/credits
Attached Files:
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
1723 [GeoSetter] User Interface major always 2017-08-28 11:15 2018-05-08 13:11
Reporter: Tobi Platform:  
Assigned To: Friedemann OS: Windows  
Priority: urgent OS Version: 7  
Status: assigned Product Version: 3.4.14 Release  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Nach Laden eine Tracks friert Karte ein.
Description: Seit einigen Wochen funktioniert Geosetter bei mir nicht mehr. Nach dem Laden eines Tracks ließ sich die Karten nicht mehr verschieben und nicht mehr zoomen auch der Track wurde nicht angezeigt. Auch nach Entfernen des Tracks und Neustarten des Programms blieb die Karte eingefroren.

Habe Geosetter dann auf einem weiteren Windows 7 Rechner installiert, da funktionierte das Schieben und Zoomen der Karte auch wieder so langen bis ein Track geladen wurde.

Zu guter Letzt habe ich Geosetter nochmal neu heruntergeladen und in einer virtuellen Maschine unter einem frisch installierten Windows XP Pro SP1 installiert und dann einen Track geladen mit dem ich vor einigen Wochen noch ohne Probleme Fotos getagged habe. Auch hier genau das selbe.

Ich davon aus, dass das irgenwas mit der Kartendatein und/oder mit einer Änderung seitens Google Maps zu tun hat, wobei das ja auch alle ander User haben müssten!?
Tags:
Steps To Reproduce: siehe oben
Additional Information: Track wurden auf einem Android Handy mit Locus Map erzeugt und als GPX exportiert.
Attached Files:
Notes
(0003050)
Tobi   
2017-08-28 16:53   
Sorry, sollte Windows XP Pro SP3 heißen.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
1697 [GeoSetter] User Interface minor always 2017-08-13 20:16 2018-05-08 13:11
Reporter: HansS Platform: Windows  
Assigned To: Friedemann OS: Windows  
Priority: normal OS Version: 7  
Status: assigned Product Version: 3.4.51 beta  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Verzeichnisse mit z.B. scharfem S funktionieren nicht als Kommandozeilenparameter
Description: mkdir "C:\temp\groß"
C:\Tools\GeoSetter\GeoSetter.exe "C:\temp\groß"
---
---------------------------
Warnung
---------------------------
GeoSetter wurde mit unbekannten Parametern gestartet:

C:\temp\groß

Die folgenden Parameter können für eine Ausführung von GeoSetter
benutzt werden:

DIRECTORY or FILE1 FILE2 FILE3...
/SHOWPOSITION
/EDIT
/RENAME
/SELECTALL
/ZOOM
/SHOWALLMARKERS=[ON,OFF]
/LOADDIRTRACKS=[ON,OFF]
/CONFIG=[FILE]
/FAVORITES=[FILE]
---------------------------
OK
---------------------------
Tags:
Steps To Reproduce: mkdir "C:\temp\groß"
C:\Tools\GeoSetter\GeoSetter.exe "C:\temp\groß"
Additional Information:
Attached Files:
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
1677 [GeoSetter] User Interface major always 2017-08-06 07:29 2018-05-08 13:11
Reporter: fonebone Platform: Windows  
Assigned To: Friedemann OS: Windows 10  
Priority: normal OS Version: 1703  
Status: assigned Product Version: 3.4.51 beta  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: errors in list of zimezones (outdated)
Description: timezones for e.g. Russia are not correct anymore. Russia has gone through a nunber of timezone and dailightsaving changes in recent years. These changes are not reflected in the list of toimezones offered and also the automatic service does not.
I had the problem with photos froma trip to St.Petersburg where GeoSetter automatically assigned UTC+4 instead of UTC+3 to my pictures.


Tags:
Steps To Reproduce: select a picture with coordinates in St.Petersburg and let Geosetter assign the tomezone from teh web --> UTC+4 instead of UTC+3
Additional Information: from https://en.wikipedia.org/wiki/Time_in_Russia:

On 27 March 2011, clocks were advanced as usual, but they did not go back on 30 October 2011, effectively making Moscow Time UTC+04:00 permanently.[4] On 26 October 2014, following another change in the law, the clocks in most of the country were moved back one hour, but summer Daylight Time was not reintroduced; Moscow Time returned to UTC+03:00 permanently.[5] Since this reform, most Russian territories have a standard time ahead of mean solar time, including time in some cites ahead it even by one hour. For example, St. Petersburg at 30°E [+2h (*solar time)] has UTC+03:00, Yekaterinburg at 60°E (+4h*) has UTC+05:00, and Vladivostok at 132°E (+9h*) has UTC+10:00.
Attached Files:
Notes
(0002943)
fonebone   
2017-08-06 11:28   
not only the automatic "Get from Web" shows the problem but also the manual list is wrong e.g. for Moscow


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
1656 [GeoSetter] Image Data minor N/A 2017-07-29 22:29 2018-05-08 13:11
Reporter: ponte Platform: PC  
Assigned To: Friedemann OS: Windows  
Priority: normal OS Version: 10 64bit  
Status: assigned Product Version: 3.4.51 beta  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: nikon D7200 übernimmt Daten nicht
Description: Nikon D7200: Die Daten von Geosetter in den Exifs werden in anderen Programmen wie View-NX oder Lightroom nicht angezeigt
Tags:
Steps To Reproduce:
Additional Information:
Attached Files:
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
1628 [GeoSetter] Image Data major always 2017-07-23 19:19 2018-05-08 13:11
Reporter: mmm Platform: PC  
Assigned To: Friedemann OS: Windows  
Priority: high OS Version: Windows 10 PRO  
Status: assigned Product Version: 3.4.51 beta  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Ändern der Zeitzone funktioniert nicht
Description: bezieht sich auf Version 3.4.53 Beta (ist oben nicht auswählbar)

Beim Setzen der Zeitzone für 3 versch. Files vom gleichen Bild wird die Zeitzone nicht korrekt gesetzt (Die 3 Dateien haben noch keine GPS-Koordinaten)

Vor GeoSetter:
FD_94981.jpg 27.05.2014 12:00:00 (jeweils Aufnahmezeit)
FD_94981.tif 27.05.2014 12:00:00
FD_94981.dng 27.05.2014 12:00:00

Nach setzen auf Zeitzone: CET - Europa / Berlin ist das Ergebnis
FD_94981.jpg 27.05.2014 12:00:00+02:00
FD_94981.tif 27.05.2014 12:00:00+01:00
FD_94981.dng 27.05.2014 12:00:00
Ergebnis: die Files haben jetzt 3 versch. Zeitzonen.

Mit der vorherigen Beta-Version 3.4.50 beta funktioniert alles richtig:
Ergebnis unter unter 3.4.50 beta:
FD_94981.jpg 27.05.2014 12:00:00+02:00
FD_94981.tif 27.05.2014 12:00:00+02:00
FD_94981.dng 27.05.2014 12:00:00+02:00
Tags:
Steps To Reproduce:
Additional Information:
Attached Files:
Notes
(0002781)
mmm   
2017-07-23 19:28   
Ergänzung:
Nach dem Setzen der Zeitzone in Geosetter wird die neue Zeitzone noch korrekt angezeigt (in rot 12:00:00+02:00 für alle 3 Files)
Erst nach dem Speichern sind die Zeitzonen fehlerhaft.

Bei einem erneuten ändern, also setzen wieder auf CET für alle 3 Files ist dann das Ergebnis richtig.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
1622 [GeoSetter] Image Data minor always 2017-07-19 22:58 2018-05-08 13:11
Reporter: Bleichgesicht Platform:  
Assigned To: Friedemann OS: Windows 10  
Priority: normal OS Version:  
Status: assigned Product Version: 3.4.16 beta  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: RW2 - Image data is not saved
Description: Tags like place, country, author and so on are not saved for RW2 Images (directly into the image). it works properly with jpg and CR2. However, coordinates for example are saved.
Tags:
Steps To Reproduce: open Image, add coordinates, get information on places via I-net, it shows in the files, save, they are gone.
Additional Information: Have a new panasonic camera, therefore I cannot say, if it worked on earlier versions.
Attached Files:
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
1615 [GeoSetter] User Interface minor sometimes 2017-07-11 16:39 2018-05-08 13:11
Reporter: madeonaufo Platform: Win 10  
Assigned To: Friedemann OS:  
Priority: normal OS Version:  
Status: assigned Product Version: 3.4.51 beta  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Blank Map/Error Code
Description: This has been happening for about a week now? I open it and it says there is an error at the bottom. The map appears blank and there are no map options except refresh. I googled the error code and found another forum on this from a couple years ago. My map is set to http://www.geosetter.de/map_google.html like it said it should be.
Tags:
Steps To Reproduce:
Additional Information:
Attached Files: 2017-07-11.png (67,195 bytes) 2017-07-11 16:39
https://geosetter.de/mantis/file_download.php?file_id=555&type=bug
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
1727 [GeoSetter] User Interface feature N/A 2017-08-31 22:15 2018-05-08 13:11
Reporter: Jeanpierre Platform:  
Assigned To: Friedemann OS:  
Priority: normal OS Version:  
Status: assigned Product Version: 3.4.51 beta  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: einfache Bildschirmkopie des Kartenfensters
Description: Wenn mit einem einfachen Button-Klick das Fenster der gerade angezeigten Karte im Bild-Verzeichnis als .jpg- oder .png-Bild abgelegt werden könnte, ist damit eine schnelle Dokumentation / ein Inhaltsverzeichnis der Bilder und ihrer Kartenzuordnung in diesem Verzeichnis erstellbar (gerne mit Geosetter-Logo in einer Ecke).
Dateiname beispielsweise Map000#.jpg, mit 000# als hochzählende Nummer bei mehreren Speicherungen.
Das würde dann in einer Photopräsentation sich gut als Übersichtsbild(er) eignen.
Tags:
Steps To Reproduce:
Additional Information:
Attached Files:
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
1822 [GeoSetter] Image Data minor always 2017-11-01 00:40 2018-05-08 13:11
Reporter: HansS Platform:  
Assigned To: Friedemann OS: Windows  
Priority: normal OS Version: 7  
Status: assigned Product Version: 3.4.51 beta  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Markierung der Personen aus XMP-mwg-rs funktioniert nicht immer
Description: Bei manchen Bildern werden die in XMP-mwg-rs eingetragenen Personen in der Vorschau korrekt angezeigt, bei anderen aber nicht - ich sehe aber keinen Grund in den XMP-Daten.

Z.B. "20170715_113132_Pana-HS_P1050346.jpg" werden keine Personen markiert, bei "20141018_141625_Canon-HS_IMG_2479" aber schon (extrahierte XMP-Daten siehe Anlage).

GeoSetter 3.4.51 (Build 2164) BETA unter Win7-65-Ult-SP2

Tags:
Steps To Reproduce:
Additional Information:
Attached Files: 2017-11-01_XMP-mwg-rs.7z (894 bytes) 2017-11-01 00:40
https://geosetter.de/mantis/file_download.php?file_id=660&type=bug
Notes
(0003266)
HansS   
2017-11-04 20:26   
Ich denke ich habe den Grund gefunden: GeoSetter unterstützt wohl Gesichert wenn sie von digiKam eingetragen sind (in XMP-MP und in XMP-mwg-rs), aber nicht in XMP-mwg-rs alleine (was Picasa verwendet) und nicht in XMP-MP alleine (was PicFace erzeugt). Offenbar wird aber zusätzlich ".picasa.ini" ausgewertet, und darin gab es nur Einträge für das eine Bild.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
1821 [GeoSetter] Image Data minor always 2017-10-31 11:21 2018-05-08 13:11
Reporter: jonny Platform: Windows  
Assigned To: Friedemann OS: 10 Pro 64 bit  
Priority: normal OS Version: 1703  
Status: assigned Product Version: 3.4.16 beta  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: State/Province suddenly in German
Description: Seit einiger Zeit sehe ich öfters deutsche Namen für gleiche Locations.
Tags:
Steps To Reproduce:
Additional Information:
Attached Files: geosetter language problem.PNG (74,818 bytes) 2017-10-31 11:21
https://geosetter.de/mantis/file_download.php?file_id=659&type=bug
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
1793 [GeoSetter] Image Data feature N/A 2017-10-21 20:26 2018-05-08 13:11
Reporter: ml Platform:  
Assigned To: Friedemann OS:  
Priority: normal OS Version:  
Status: assigned Product Version: 3.4.51 beta  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Zeitzone aus EXIF 2.31 auslesen
Description: Seit letztem Jahr gibt es die EXIF Spec 2.31. Sie enthaelt neue Felder „OffsetTime“, „OffsetTimeOriginal“ und „OffsetTimeDigitized“, um die Zeitzone zu speichern. Meine Kamera fuellt diese Felder korrekt aus. Daher meine Frage: kann geosetter erweitert werden, um diese Felder zu unterstuetzen?
Tags:
Steps To Reproduce:
Additional Information:
Attached Files:
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
1779 [GeoSetter] Image Data feature N/A 2017-10-15 00:59 2018-05-08 13:11
Reporter: wumpus Platform: x64  
Assigned To: Friedemann OS: Windows  
Priority: none OS Version: 10 Pro  
Status: assigned Product Version: 3.4.51 beta  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Add support for PNG
Description: Please add support for reading and writing PNG image files.
Tags:
Steps To Reproduce:
Additional Information: Using v3.4.53 (build 217) BETA
Attached Files:
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
1763 [GeoSetter] User Interface tweak always 2017-10-10 20:21 2018-05-08 13:11
Reporter: Sickbock Platform:  
Assigned To: Friedemann OS: Windows 10  
Priority: normal OS Version:  
Status: assigned Product Version: 3.4.16 beta  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Fail of copy paste function
Description: I would like to retrieve the location coordinates from my images to a word document.
When I select an image and then activate the button “Copy data of selected image to the clipboard” nothing appears in my document when I activate the paste function.
Tags:
Steps To Reproduce:
Additional Information:
Attached Files:
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
1745 [GeoSetter] Image Data tweak always 2017-10-02 01:11 2018-05-08 13:11
Reporter: geobeachman Platform: PC  
Assigned To: Friedemann OS: Windows  
Priority: normal OS Version: 7  
Status: assigned Product Version: 3.4.51 beta  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Comupute Destination Coordinated from GPS Direction and Entered Distance or Focal Length
Description: I have a Canon 5D Mark III with a GP-E3 GPS receiver that records geodetic location and direction, unfortunately the destination coordinates are always set to zero. I have to manually set all photo destinations coordinates individually. It would be nice to have the ability of computing the destination coordinates based on the direction and a distance that is manually entered or from the focal length some how.
Tags:
Steps To Reproduce: Happens all the time, no steps to reproduce.
Additional Information:
Attached Files:
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
1834 [GeoSetter] Image Data major always 2017-12-31 15:08 2018-05-08 13:11
Reporter: cefau Platform:  
Assigned To: Friedemann OS: Windows 10  
Priority: high OS Version:  
Status: assigned Product Version: 3.4.16 beta  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: localization data not saved
Description: When doing CTRL+S the localization data are not saved. I think it is linked to the exiftool version, this error appears after updating the exiftool version. I do not know how to downgrade.
Tags:
Steps To Reproduce:
Additional Information:
Attached Files: bugreport.txt (21,324 bytes) 2017-12-31 15:08
https://geosetter.de/mantis/file_download.php?file_id=668&type=bug
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
1830 [GeoSetter] User Interface minor always 2017-11-28 15:43 2018-05-08 13:11
Reporter: jmoliver Platform:  
Assigned To: Friedemann OS:  
Priority: normal OS Version:  
Status: assigned Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: OpenStreetMap zoom in is limited
Description: When Openstreetmap view is selected, one can zoom in to a certain point when compared to say Google Maps. It would be great if the zoom factor can be increased as to get better zoom in capability on openstreetmap.
Tags:
Steps To Reproduce: 1. Launch GeoSetter
2. Open Map View, select OpenStreetView, zoom in to closest point.
3. Select Google Maps view and zoom in.

Result: You can zoom in in Google Maps versus OpenStreetMap
Additional Information:
Attached Files:
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
1823 [GeoSetter] Image Data major always 2017-11-10 22:25 2018-05-08 13:11
Reporter: meokeefe Platform:  
Assigned To: Friedemann OS:  
Priority: urgent OS Version:  
Status: assigned Product Version: 3.4.16 beta  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: 'Save' does not save geographic info to JPG file
Description: After syncing non-geo-tagged photos with a matching track point, selecting all,syncing all photos with track points, and verifying, selecting save changes or the save icon does not save geographic information to the file. No errors are reported. No files in the folder of origin have been geotagged. I have tried adjusting settings to overwrite existing files when saved and other settings as well. I am not python-savvy. Is there something I am doing wrong? I have not been able to troubleshoot my way out of this. I have to wait for approval to be able to download the newest update.
Tags:
Steps To Reproduce:
Additional Information:
Attached Files:
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
1841 [GeoSetter] Image Data minor always 2018-01-21 16:34 2018-05-08 13:11
Reporter: Matthieu Platform: pc Aspire E15  
Assigned To: Friedemann OS: windows10  
Priority: normal OS Version: 10  
Status: assigned Product Version: 3.4.16 beta  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Exported pictures in GoogleEarthPro from GeoSetter are wrongfully rotated (180°)
Description: I export some pictures from GeoSetter to GoogleEarthPro
Those with exif parameter orientation set to "Rotate 180" are not correctly displayed in GoogleEarthPro. They have not been rotated.
All the other pictures with parameter set to "Rotate 90 CW", "Rotate 270 CW" or "Horizontal (normal)" are correctly displayed in GoogleEarth.
Tags:
Steps To Reproduce: 1. Load pictures with "Rotate 180" orientation in GeoSetter.
2. From GeoSetter export these pictures in a kmz file
3. open the generated kmz file in GoogleEarthPro
4. the pictures are not correctly rotated (up/down)
Additional Information:
Attached Files:
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
1840 [GeoSetter] User Interface minor unable to reproduce 2018-01-15 12:02 2018-05-08 13:11
Reporter: zava Platform: PC  
Assigned To: Friedemann OS: Win10  
Priority: normal OS Version:  
Status: assigned Product Version: 3.4.51 beta  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Context menu integration seems gone after installing V3.4.82Beta
Description: Hello,
I recently installed V3.4.82Beta and the integration with Windows right click menu seems to have gone.
I had selected integration during installation, and have also repeated installation/restart but the context menu seems gone.
I am attaching the context menu as seen with Geosetter V3.4.16 which is working fine and is the same I used to see with the Beta version prior to this upgrade.
I am also attaching the same right click menu as it now appears with the Beta version.
Any reference to the Beta has also disappeared from the Windows context menu (see attached image, where only reference to GS V3.4.16 has remained).
How can I restore the right click menu?
Basically, I neet it to "Open" images in my external viewer after selecting them within GS, so if "Open" was among the native right-click menu options, this would already be a solution).
Thank you!
Tags:
Steps To Reproduce:
Additional Information:
Attached Files: GS Menu.zip (351,151 bytes) 2018-01-15 12:02
https://geosetter.de/mantis/file_download.php?file_id=681&type=bug
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
1839 [GeoSetter] User Interface text always 2018-01-10 08:58 2018-05-08 13:11
Reporter: Stoffel Platform:  
Assigned To: Friedemann OS:  
Priority: normal OS Version:  
Status: assigned Product Version: 3.4.51 beta  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Option controls too small (3.4.82 Build 2184) BETA (earlier betas too)
Description: Some fields in "Settings" are too small and partially cut off.

The height of all fields should increased that become multi-line because of their long text.

Affected controls are for example (at least in English and German):

Settings -> [tab] "Data Preferences":
"Set Auto Fields Immediately After Reading Image Data (this may result in images shown with changed status)"

Settings -> [tab] "ExifTool":
"Create Backups of Changed Image Files"


(There might be some more, depending on their translation, especially if the original English text is already close to be wrapped)

With kind regards and many thanks for the new beta.

Tags:
Steps To Reproduce: Open GeoSetter "Settings", then go to tab "Data Preferences" and/or "ExifTool".
Additional Information:
Attached Files: bug.png (51,276 bytes) 2018-01-10 08:58
https://geosetter.de/mantis/file_download.php?file_id=675&type=bug
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
1835 [GeoSetter] Image Data major always 2018-01-08 19:29 2018-05-08 13:11
Reporter: zava Platform: PC  
Assigned To: Friedemann OS: Win10  
Priority: normal OS Version:  
Status: assigned Product Version: 3.4.51 beta  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: IPTC character code error prevents saving GPS coordinate
Description: Hello,
after a trip to Jordan I find that several images, after being synced with GS logs, cannot be saved with the assigned GPS coordinates.
An error window is displayed referencing "IPTC character conversion error".
I tried selecting "OK" or "Ignore" but both result in the image not being saved or at least in GPS coordinates not being incorporated.
A screenshot of an example error window is attached.
For testing purposes I can provide the GPS coordinates for the image, which probably result in the questionable IPTC data:

N31°43'8.76" E35°47'36.16"

Am running V3.4.53 (build 2170) BETA
Tags:
Steps To Reproduce: Assign reported position (for instance N31°43'8.76" E35°47'36.16") to any image; GPS coordinates do appear.
Then try to save changes.
Additional Information:
Attached Files: IPTC code error.jpg (67,386 bytes) 2018-01-08 19:29
https://geosetter.de/mantis/file_download.php?file_id=670&type=bug
Example.png (172,137 bytes) 2018-01-10 20:53
https://geosetter.de/mantis/file_download.php?file_id=676&type=bug
Notes
(0003325)
Stoffel   
2018-01-10 20:52   
(Last edited: 2018-01-10 20:54)
Hi zava,

trying to reproduce your trouble (using the same version 3.4.53 (build 2170) BETA), there was no problem for me in saving your giving cordinates including the geotag (country/city/...). See my screenshot "example.png"

In "Settings" -> tab "File Options", did you ...

... check "Save IPTC Data as Unicode (Instead of Local Character Coding)",
... uncheck "If IPTC Data Exists Already, Use It As Is (Unicode or Local Character Coding)"?

Regards,
Stoffel

(0003328)
zava   
2018-01-12 12:24   
Thank you Stoffel,
I checked those settigns as you suggested (plus, installed the now released latest BETA update), it does seem to work now!
Thank you!


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
1832 [GeoSetter] Image Data minor always 2017-12-10 15:18 2018-05-08 13:11
Reporter: frank_gaertner Platform: WIN  
Assigned To: Friedemann OS: WIN  
Priority: normal OS Version: 10  
Status: assigned Product Version: 3.4.51 beta  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Questin about development of Geosetter
Description: Is Geosetter developed further? There were no Updates since Years?

Just a Question
Tags:
Steps To Reproduce:
Additional Information:
Attached Files:
Notes
(0003290)
Friedemann   
2018-01-08 16:27   
Yes, it is. I started developing a new version 4 about 1/2 year ago. I didn't work on it now for 2 months but I will start again in the next days... ;-)


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
1870 [GeoSetter] User Interface minor always 2018-03-11 17:45 2018-05-08 13:11
Reporter: pbb Platform: Windows 10  
Assigned To: Friedemann OS: Windows 10  
Priority: normal OS Version: 10  
Status: assigned Product Version: 3.4.51 beta  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: GMail says request was too large when sending crash report
Description: GeoSetter 3.4.82 (this is not listed as an option in the bug report)

I have GMail as my default e-mail client through a handler in Chrome. When GeoSetter crashed, I choose to send the e-mail report.

Chrome open the following URL: https://mail.google.com/mail/?extsrc=mailto&url=mailto%3Asupport%40geosetter.de%3Fsubject%3Dbug%2520report%26body%3Ddate%252Ftime%2520%2520%2520%2520%252... (etc etc etc) and gives the message:

413. That’s an error.
Your client issued a request that was too large. That’s all we know.
Tags:
Steps To Reproduce: 1. Activate the Chrome GMail handler.
2. Double-check that Chrome is the default handler for Email in the Windows settings.
3. Crash GeoSetter (if you're like me, that happens about every hour)
4. If you're lucky, an information window popup up, allowing to e-mail or save the crash report.
5. Click the e-mail button. Chrome opens, with the above error message.
Additional Information:
Attached Files:
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
1852 [GeoSetter] User Interface feature N/A 2018-03-03 14:38 2018-05-08 13:11
Reporter: Ronald Platform: Laptop  
Assigned To: Friedemann OS: Windows 7 Pro 64bit  
Priority: normal OS Version: 7  
Status: assigned Product Version: 3.4.51 beta  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Fehlende Vollbild Diaschau mit JPG-Kommentar als Untertitel und Bild in Bild Einblendung der Geo-Position
Description: 3.4.82 beta ist einstalliert.

Ich suche ein Widows7 Tool, um einen Bildervortrag mit einer Vollbild Präsentation samt Untertiteln (aus dem JPG-Kommentar) zu begleiten und bedarfsweise die Geo-Position in einem Karten-Fenster ins Bild einzublenden.

Die Präsentation der 439 Bilder samt Untertiteln habe ich schon mal mit IrfanView hinbekommen, aber dort fehlt leider die Anzeige-Funktion der Geo-Position.

Auf der Suche nach dem geeigneten Tool habe ich nun Ihren GeoSetter installiert und bin begeistert von dessen Funktionsumfang.

Eigentlich wären ja alle Komponeneten vorhanden, aber ich habe (noch) nirgends die Möglichkeit der Darstellung (aller Bilder eines Verzeichnisses) als Diaschau gefunden, wo auch das wahlweise Einblenden des Karten-Fensters mit der Geo-Position zum angezeigten Bild (mit Funktionstaste/Esc) integriert sein sollte.

Dies meine Anregung zur Funktionserweiterung, die hoffentlich auf Ihre Zustimmung und baldige Realisierung stösst...

Oder kennen Sie ein Tool, das meine Anforderung bereits erfüllt..?

Besten Dank,
Ronald
Tags:
Steps To Reproduce:
Additional Information:
Attached Files:
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
1849 [GeoSetter] User Interface feature always 2018-02-07 11:47 2018-05-08 13:11
Reporter: youGene Platform: Windows10 Pro  
Assigned To: Friedemann OS:  
Priority: normal OS Version:  
Status: assigned Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Kommandozeilenparameter DIRECTORY und Umlaute
Description: Aufruf von GeoSetter über Kommanda-Zeile oder Shell-Command mit Übergabe eines Directorys geht nicht, wenn Directory-Name Umlaute enthält.
Gibt es inzwischen eine Änderung gegenüber dem Zustand von April 2015 als dieses Problem mit der Issue-Nummer 1254 schon einmal angesprochen wurde.

Im Exif-Tool selbst können solche Directory-Namen verwendet werden, wenn man den richtigen Parameter für -charset filename= benutzt.
Tags:
Steps To Reproduce:
Additional Information:
Attached Files:
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
1847 [GeoSetter] Image Data feature always 2018-02-05 16:58 2018-05-08 13:11
Reporter: Durand Platform: PC  
Assigned To: Friedemann OS: Window  
Priority: normal OS Version: 10  
Status: assigned Product Version: 3.4.16 beta  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: No GPS coordinate updated in .ORF for Olympus pictures
Description: After a synchro with a GPS file (.gpx) and an Olympus pictures for both JPEG and ORF, only JPEG pictures are updated with the GPS coordinates after the register modification command.
Tags:
Steps To Reproduce:
Additional Information:
Attached Files:
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
1845 [GeoSetter] Image Data minor random 2018-02-01 21:56 2018-05-08 13:11
Reporter: ABIZAHI Platform: WINDOW  
Assigned To: Friedemann OS:  
Priority: high OS Version: 8.1  
Status: assigned Product Version: 3.4.51 beta  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: CAMBIO DE COORDENADAS A UTM
Description: QUISIERA SABER SI SE PUEDE OBTENER O CAMBIAR DE COORDENADAS GEOGRÁFICAS QUE MUESTRE COORDENADAS UTM(Universal Transverse Mercator)
Tags:
Steps To Reproduce:
Additional Information:
Attached Files:
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
1844 [GeoSetter] Image Data major always 2018-01-29 04:13 2018-05-08 13:11
Reporter: cheerful Platform: Windows  
Assigned To: Friedemann OS: Windows 10  
Priority: normal OS Version: 1709  
Status: assigned Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Error while saving with exiftool is not reported
Description: Version 3.4.16 will report the error: exiftool Error: [minor] IFD1 pointer references previous GPS directory

3.4.82 beta with the latest exiftool will not pop up the error log. The files remains unsaved with the red/purple color
Tags:
Steps To Reproduce:
Additional Information:
Attached Files:
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
1843 [GeoSetter] User Interface minor always 2018-01-29 00:32 2018-05-08 13:11
Reporter: bselbmann Platform: Windows  
Assigned To: Friedemann OS: Win 7  
Priority: normal OS Version: 64bit  
Status: assigned Product Version: 3.4.51 beta  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Tagging with gps-files at timezone "Russia" - no summertime
Description: As a result, that Russia don't have a summertime anymore from October 2014 on(test from 2011 - 2014)

so during tagging i have to set manually +1h
Tags:
Steps To Reproduce: I have this issue since 2015 I can send you some files to reproduce
Additional Information: https://diepresse.com/home/panorama/welt/4197206/Russland_Permanente-Winterzeit-loest-DauerSommerzeit-ab

https://de.wikipedia.org/wiki/Zonenzeiten_in_Russland
Attached Files: Russland +1std.JPG (122,205 bytes) 2018-01-29 00:32
https://geosetter.de/mantis/file_download.php?file_id=682&type=bug
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
1842 [GeoSetter] User Interface feature have not tried 2018-01-24 06:19 2018-05-08 13:11
Reporter: sp Platform:  
Assigned To: Friedemann OS:  
Priority: normal OS Version:  
Status: assigned Product Version: 3.4.51 beta  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Map browser issue
Description: You are using a browser that is not supported by the Google Maps JavaScript API. Consider changing your browser.Learn more, Dismiss

I get this message on Map browser, I tried IE-11, Firefox, Chrome but still get the same meassage

Pls suggest a solution
Tags:
Steps To Reproduce:
Additional Information:
Attached Files:
Notes
(0003343)
zava   
2018-01-24 12:25   
Hello,
this issue has been already reported and solved.
Pls see http://www.geosetter.de/mantis/view.php?id=1829


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
1938 [GeoSetter] Image Data minor always 2018-04-27 09:08 2018-05-08 13:11
Reporter: johnboz Platform:  
Assigned To: Friedemann OS:  
Priority: normal OS Version:  
Status: assigned Product Version: 3.4.51 beta  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Time Zone not correct
Description: I've made pictures in Boston, Massachusetts, USA.
When I pin the picture to the map, the location data are perfect.
But the timezone that (automatically) is chosen: (UTC-05:00+01:00) America / Detroit, is not correct.
After clicking on the Time Zone button "Get from the web", the correct Time Zone is inserted: (UTC-05:00,DST+01:00) America / New York
Tags:
Steps To Reproduce: See above
Additional Information:
Attached Files:
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
1935 [GeoSetter] Image Data feature always 2018-04-18 10:25 2018-05-08 13:11
Reporter: boss23 Platform: Win7  
Assigned To: Friedemann OS:  
Priority: high OS Version:  
Status: assigned Product Version: 3.4.51 beta  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: HEIC Support
Description: Hi,

Any support of Apple HEIC file coming?

Thx!
Tags:
Steps To Reproduce:
Additional Information:
Attached Files:
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
1853 [GeoSetter] User Interface major always 2018-03-04 07:27 2018-05-08 13:10
Reporter: lucian Platform: windows 7 ultimate  
Assigned To: Friedemann OS:  
Priority: high OS Version:  
Status: resolved Product Version:  
Product Build: Resolution: no change required  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: versions 3.4.82 beta and 3.4.16
Description: Map not displayed at all after installation.
Tags:
Steps To Reproduce: Installed and uninstalled multiple times.
The same result like the one shown in the attached picture.
Additional Information:
Attached Files: geosetter_error.jpg (402,798 bytes) 2018-03-04 07:27
https://geosetter.de/mantis/file_download.php?file_id=685&type=bug
Notes
(0003367)
lucian   
2018-03-04 07:51   
I'm using only two browsers: the last firefox version and chrome version. No internet exporer installed on my win 7 ultimate.
(0003370)
heiko   
2018-03-05 21:55   
GeoSetter is using the Internet Explorer to show the map. Without an actual version of IE the map will not be displayed.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
1939 [GeoSetter] User Interface major always 2018-04-28 20:02 2018-05-05 17:20
Reporter: jhansen Platform: Win10  
Assigned To: Friedemann OS:  
Priority: normal OS Version:  
Status: resolved Product Version:  
Product Build: Resolution: fixed  
Projection: none      
ETA: none Fixed in Version: 3.5  
    Target Version:  
Summary: Sehr lange Ladezeiten bei iPhone-Fotos
Description: Hallo,
es dauert extrem lange, ein Verzeichniss in Geosetter (Version 3.4.82) zu öffne/laden, welches iPhone-Fotos (jpg, IOS 11.3, iPhone 7)) beinhaltet. Bei nur 4 Fotos (jeweils 4MB) dauert das über 30s. Ein Verzeichnis mit 4 Olympus-Fotos (jpg, jeweils 3MB) öffnet praktisch sofort.

Vile Grüße
Tags:
Steps To Reproduce: Verzeichnisse öffnen
Additional Information: Ich sende ein ZIP mit Beisipeuel per Email.
Attached Files:
Notes
(0003487)
Friedemann   
2018-04-28 20:04   
Ja, ich weiß. Siehe auch hier: 0001932 Will mich heute oder morgen drum kümmern. Kann das auch reproduzieren...
(0003488)
Friedemann   
2018-04-29 05:56   
Das Einlesen von 1200 iPhone-Dateien dauert bei mir jetzt nur noch 30 Sekunden :-)


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
1932 [GeoSetter] User Interface minor have not tried 2018-04-15 16:16 2018-05-05 17:20
Reporter: cbbob Platform: Windows  
Assigned To: Friedemann OS: Windows  
Priority: normal OS Version: 10  
Status: resolved Product Version: 3.4.16 beta  
Product Build: Resolution: fixed  
Projection: none      
ETA: none Fixed in Version: 3.5  
    Target Version:  
Summary: UI hangs when loading folder with iPhone pictures in it
Description: Since a couple of weeks I have the problem of not beeing able to "regulary" load folders that countian pictures taken by my iPhone.
The symtom is that in the details view the filenames first are only shown in grey (see picture) and then it takes up to 10 minutes or longer to load one list. Once I scoll down the long load process starts again for the next page.
This symptom is only present with my iPhone pictures and not with folders that contain DSRL pictures only.
I thought the problem might me due to having descriptive XML files in the same folder, that have been produced by the iPhone. That was not the case.
Then I thought It might be due to a new meta data type of the iPhone X. That was not true either. It happens with iPhone 7 imeags as well.

It looks like it is due to the iOS Version. I can't tell for sure, but it seems that the problem only occurs for pictures taken since I have updated to iOS 11. :-(

Any ideas?
Tags:
Steps To Reproduce: navigate to folder
Additional Information:
Attached Files: Geosetter problem.JPG (20,265 bytes) 2018-04-15 16:16
https://geosetter.de/mantis/file_download.php?file_id=710&type=bug
Notes
(0003489)
Friedemann   
2018-04-29 05:57   
Reading 1200 iPhone files now takes about 30 seconds on my machine :-) I will create an updated version as soon as possible...


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
998 [GeoSetter] Image Data minor always 2012-10-28 13:10 2018-04-27 08:44
Reporter: ksuehring Platform:  
Assigned To: Friedemann OS:  
Priority: normal OS Version:  
Status: assigned Product Version: 3.4.34 beta  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Time Zone data is no applied to all pictures wth time shift
Description: Multiple pictures are selected (Canon cr2 raw with XMP files)
The time and time zone is changed using Edit Data -> Date tab -> Time shift
"Set current value for all selected images" is chosen

The time zone does not get updated.
Tags:
Steps To Reproduce:
Additional Information: This seems to happen only for the "Time shift" option. Using "Set to Fixed Date" allows updating the time zone.
Attached Files:
Notes
(0002553)
DenisPac   
2017-05-18 10:19   
This is not new for me.
Actually only the current picture is updated with time zone while the others are not.
This is only when saving that GS asks to apply a time zone to all pictures that this actually applies to all.
GeoSetter beta v3.4.53
(0003485)
johnboz   
2018-04-27 08:02   
I have the same problem. Only one picture at the time can be updated.
I've tried several combinations of changing the timezone, but it didn't make any difference.
I even changed the time with one second to see if this made any difference, but it didn't.

I used the normal Geosetter version and the beta version 3.4.82 with Exif tools 10.94.

I noticed that Geosetter has some (speed) trouble with reading a CR2 map with 1400 pictures. For quit a time the reading process is standing still on 11%. After quite a while it continues normally.
(0003486)
johnboz   
2018-04-27 08:44   
I did the following and the timezone changed.
I added to every picture GPS coordinates and let GeoSetter add the location items.

Than I switched to the Tab and let Geosetter determine the Time Zone through "Getting from Web".

After saving the picture settings (316 photo's) the Exif time zone data where changed.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
1294 [GeoSetter] User Interface minor always 2016-01-08 18:36 2018-04-22 16:17
Reporter: gregglee Platform: AMD FX(tm)-8350 Eight-Core  
Assigned To: Friedemann OS: windows  
Priority: normal OS Version: 7-64  
Status: assigned Product Version: 3.4.16 beta  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Image preview with Sony A99 ARW
Description: With any ARW from Sony A99 the image preview pane shows colors inaccurately - greenish and low contrast.

Only the image preview window is affected. Thumbnails display correctly and appear to be the same as preview in windows explorer.
Tags:
Steps To Reproduce: select any A99 ARW
Additional Information:
System Description MB is ASUS SABERTOOTH 990FX R2.0
Attached Files: geosetter screen save.JPG (210,225 bytes) 2016-01-08 18:36
https://geosetter.de/mantis/file_download.php?file_id=428&type=bug
Notes
(0003484)
gregglee   
2018-04-22 16:17   
Same issue with A99M2 ARW. Greenish, low contrast and often darker than geosetter thumbnails or windows explorer preview pane or Windows Paint. (I don't mean Windows photo viewer which has a well known bug.)


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
1934 [GeoSetter] User Interface major always 2018-04-17 17:08 2018-04-17 20:00
Reporter: SantiMB Platform:  
Assigned To: Friedemann OS:  
Priority: high OS Version:  
Status: resolved Product Version: 3.4.16 beta  
Product Build: Resolution: no change required  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Map is not shown
Description: The map window can't load http://www.geosetter.de/map_google.html. If I open this URL in a web browser I get a blank page. I happens from today, and yesterday it worked well.
Tags:
Steps To Reproduce:
Additional Information:
Attached Files:
Notes
(0003479)
Friedemann   
2018-04-17 17:39   
The blank page in a web browser is absolutely ok. So what's the problem???
(0003480)
SantiMB   
2018-04-17 18:19   
OK. I thought that this could help in the diagnosis. :(

The problem is that the map does not appear in the map window, only an error that says the map could not be found in http://www.geosetter.de/map_google.html, and that I have to the URL in the configuration. Yesterday it worked.
(0003481)
Friedemann   
2018-04-17 18:42   
If it worked yesterday, than it was maybe an update on your system which causes it now to work not. Are you sing maybe a special firewall which maybe blocks GeoSetter now? Maybe an antivirus software which blocks it now after an update? Which Windows version are you using?
(0003482)
SantiMB   
2018-04-17 19:37   
It was from the computer of my work. We have corporate firewall (I think Cisco) and corporate antivirus (McAfee). Both warn when there is an access problem.

Anyway it has to be something related to the LAN of the office because I just tried it on my home computer and the map is displayed correctly.

You can close the issue.

Thanks for everything.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
1909 [GeoSetter] User Interface minor always 2018-04-07 11:07 2018-04-07 12:37
Reporter: Xavmart Platform: Desktop  
Assigned To: Friedemann OS: Windows 10 Professional  
Priority: normal OS Version: 16299.309  
Status: assigned Product Version: 3.4.16 beta  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Browser incompatibility error
Description: Dear all,

I always get the follwowing errorr message :
"Le navigateur que vous utilisez n'est pas compatible avec l'API JavaScript de Google Maps. Nous vous recommandons de changer de navigateur."
meaning :
"the bowser that you use is not compatible with the API JavaScript of Google Maps. Change your browser.".
What should I do :
1) change some GeoSetter settings ? where ?
2) change my default browser to "Edge" ? I tried but it does not have an effect.

Thank you in advance.
Best regards,
Xavier

Tags:
Steps To Reproduce:
Additional Information:
Attached Files:
Notes
(0003443)
Friedemann   
2018-04-07 12:37   
Presse see here: 0001829


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
1851 [GeoSetter] User Interface block always 2018-02-19 15:06 2018-02-19 17:39
Reporter: slart Platform: Windows  
Assigned To: Friedemann OS: Windows 7 64  
Priority: immediate OS Version: 7  
Status: resolved Product Version: 3.4.16 beta  
Product Build: Resolution: no change required  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Browser wird von der Google Maps JavaScript API nicht unterstützt
Description: "Der von Ihnen verwendete Browser wird von der Google Maps JavaScript API nicht unterstützt. Verwenden Sie einen anderen Browser. Weitere Informationen Schließen"

Habe mir das geosetter.zip neu geladen. Das Problem besteht weiterhin.

Die installierten Browser:
IE 8 (ungenutzte, niemals upgedatete originale Win 7 Version)
Firefox neueste Version
Chromium neueste Version
Opera neueste Version

Habe diese Issues gefunden, die das Problem nicht lösen:
http://www.geosetter.de/mantis/view.php?id=1828
http://www.geosetter.de/mantis/view.php?id=1829
http://www.geosetter.de/mantis/view.php?id=1836

Ich verwende ausschließlich die Portable (zip) Version.
Tags:
Steps To Reproduce:
Additional Information:
Attached Files:
Notes
(0003345)
slart   
2018-02-19 15:11   
Aha, es gibt auch eine beta als zip. Muss man nur selbst drauf kommen.
www.geosetter.de/geosetter_beta.zip

OK, mit der Beta zip besteht das Problem genauso.

Geosetter 3.4.82 (Build 2184):
"Der von Ihnen verwendete Browser wird von der Google Maps JavaScript API nicht unterstützt. Verwenden Sie einen anderen Browser. Weitere Informationen Schließen"
(0003346)
Friedemann   
2018-02-19 15:12   
Google setzt aktuell für die Google Maps API den IE 10 voraus. Sobald der installiert ist, sollte es klappen, mit der in 0001829 beschriebenen Änderung...
(0003347)
slart   
2018-02-19 15:16   
Im unteren Fenster steht das:
19.02.2018 15:09:45 ERROR: Der Vorgang konnte aufgrund des folgenden Fehlers nicht fortgesetzt werden: 80020101
  showMap3(2, 1, 52.4971527727, 13.4702112525, 20);

Wie krieg ich den IE 10 in Win 7? Den Update-Wahnsinn mach ich nicht mit.
(0003348)
Friedemann   
2018-02-19 15:29   
(Last edited: 2018-02-19 15:29)
Wie gesagt, ich kann da nix für, die aktuelle API von Google fordert halt den IE 10. Ansonsten kann es halt an diversen Stellen zu Fehlern kommen.

> Den Update-Wahnsinn mach ich nicht mit.

Musst Du ja auch nicht. Dann kannst Du aber auch nicht erwarten, dass aktuellere Software weiterhin läuft ;-) Verstehe nicht, was daran so schlimm ist, einen Browser zu aktualisieren. Beim Firefox, Chrome und Opera tust Du das ja anscheinend auch. Und wenn man schon 3 Browser aktuell hält, schafft man das doch auch mit vieren. Der IE 11 wird ja von Microsoft zum Download angeboten.

Auch nur zur Info: Der IE ist der einzige mir bekannte Browser, den man eingebettet in eigenen Anwendungen benutzen kann. Deshalb halt der IE.

(0003349)
Friedemann   
2018-02-19 15:31   
Siehe auch hier: https://developers.google.com/maps/documentation/javascript/browsersupport?hl=de
(0003350)
slart   
2018-02-19 15:36   
Schwierig. Der IE 11 Offline Installer will ins Internet, bzw. bricht ohne Internet die Installation ab. Schmuh!
Ja, blöd, wenn nur der IE für sowas funzt. Aber muss es denn unbedingt ein ganzer Browser sein? Würde es mit OSM / OpenLayer nicht funktionieren? OK, mit Applications hab ich keine Ahnung, aber OL4 ist eine feine Sache.

... ich sitz wohl ziemlich in der Klemme. Am Ende muss ich mir noch selbst was basteln...
(0003351)
Friedemann   
2018-02-19 15:39   
Ob nun Google Maps oder OL, für beides benötigt man einen JavaScript-fähigen Browser. Mag sein, dass OL auch mit einer niedrigeren Version des IE zufrieden wäre. Ein Umbau auf OL ist schon längst auf meiner Todo-Liste, aber relativ weit unten ;-) Aber wie gesagt, einen Browser benötigt man dafür genauso...
(0003352)
Friedemann   
2018-02-19 15:40   
> Aber muss es denn unbedingt ein ganzer Browser sein?

und was heißt "ein ganzer Browser"? Einen halben gibt's halt nich... ;-)
(0003353)
Friedemann   
2018-02-19 15:45   
Und OL benötigt mindestens den IE 9, wenn ich das richtig lese: https://openlayers.org/en/latest/doc/tutorials/introduction.html
(0003354)
slart   
2018-02-19 15:50   
(Last edited: 2018-02-19 15:52)
Gibts JS nicht standalone?
PhantomJS kriegt das ja auch hin und rennt exakt.
https://superuser.com/questions/946244/is-there-a-way-to-run-javascript-without-a-browser-like-a-shell-or-batch-script

Ich musste jetzt den untouched IE 8 aus der Win 7 Installation für Geosetter opfern. Dabei brauch ich den fürs Webseiten testen. Hartes Opfer ...

Zumindest scheint jetzt der Fehler weg zu sein, bei dem immer die Karte eingefroren war.

(0003355)
Friedemann   
2018-02-19 15:56   
(Last edited: 2018-02-19 15:56)
> Gibts JS nicht standalone?

Ja natürlich, das beste Beispiel ist NodeJS. Aber vergiss doch bitte nicht, dass Du irgendwo eine Karte sehen willst, etwas visuelles. Du brauchst also jemanden, der JavaScript-Code ausführt und das ganze schön präsentiert und auch Eingaben entgegen nimmt, Mausklicks etc. Und wer macht sowas wohl??? Ein Browser ;-)

> Dabei brauch ich den fürs Webseiten testen.

Super-Argument :-D Zum Testen von Webseiten sollte es ein möglichst alter Webbrowser sein? Das macht Sinn? Du kannst bei jedem IE auch einstellen, in welchem Modus er arbeitet, Du kannst ihn zum Testen also weiterhin als IE 8 benutzen...

(0003357)
slart   
2018-02-19 17:26   
(Last edited: 2018-02-19 17:27)
Wie auch immer. Jetzt funktioniert alles wieder einwandfrei, als wenn nichts gewesen wäre. Gab es ein Problem? ^^ Hab den IE 11 genommen.
Warum man bei einer Offline Installation online sein muss ist halt mal wieder typisch Windows.
Jetzt kann das Issue geschlossen werden.

(0003358)
Friedemann   
2018-02-19 17:39   
> Jetzt funktioniert alles wieder einwandfrei

wunderbar! :-)

> Gab es ein Problem?

ich weiß von nüscht :-D

> Warum man bei einer Offline Installation online sein muss ist halt
> mal wieder typisch Windows.

bei manchen Installationen lädt man ja nur einen kleinen Installer runter, der dann während der Installation den großen Rest erst nachlädt...


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
1235 [GeoSetter] User Interface block always 2015-01-07 18:26 2018-01-29 12:50
Reporter: bselbmann Platform: Microsoft  
Assigned To: Friedemann OS: Windows  
Priority: high OS Version: 7 Enterprise 64b  
Status: assigned Product Version: 3.4.51 beta  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: EXIF Tool processes (up to 5) have to be kill manually
Description: Hallo Herr Friedemann,

ersteinmal vielen lieben Dank für dieses wunderschöne aus meinem Alltag nicht mehr wegzudenkende Tool.

Ich fotografiere mit der Nikon D4 und tagge/tracke mit dem Solmeta Pro.

Aber jedesmal, wenn ich nach den etwas umständlichen (meinerseits, da ich die Kamera auf Ortszeit umstelle: z.B. Thailand (erst mit, dann ohne Sommerzeit - muß ich die Zeiten nachkorrigieren da etwas nicht so ganz stimmt ;-( ) synchronisieren meine jpegs und NEFs tagge - geht es nicht mehr weiter:

ich muß manuell alle exiftool.exe *32 Prozesse abbrechen, damit es weitergeht - Das passiert auf meinem Lenovo Laptop T520 (8 Kern) als auch auf meinem Heimrechner (Intel X79 mit 8 kern Intel CPU) auf beides Windows 7 Enterprise

was mache ich verkehrt?

Gruß

Bernd Selbmann
Tags:
Steps To Reproduce: tag many pictures and press save changes (all NEF/JPG) and watch the task manager
Additional Information:
Attached Files: jfiiccdi.png (1,496,554 bytes) 2015-01-07 18:26
https://geosetter.de/mantis/file_download.php?file_id=412&type=bug
Notes
(0002174)
heiko   
2015-01-07 21:55   
wie lange wartest du denn bis du die ExifTool Prozesse abbrichst (ich nehme an über den Taskmanager)? Ich habe durchaus schon gelesen, dass es Dateitypen gibt, für die ExifTool recht lange zum Speichern braucht.

was für eine ExifTool Version verwendest du?

was passiert wenn du nur JPGs änderst?
was passiert wenn du nur NEFs änderst?
(0002176)
bselbmann   
2015-01-09 13:27   
Hallo,

in der Regel nur noch 5min - hatte am Anfang 8std und mit einem anschliessendem Neustart gewartet.

Das kann ich nicht bestätigen - es starten 4 exiftool Prozesse, die jpg sowie NEF rasend schnell abändern, bis es nach und nach alle 4 Prozesse (exiftool.exe) nicht mehr schaffen sich zu beenden - ob sie auf lese/schreib zugriffe warten kann ich nicht so wirklich beobachten aber es passiert schon bei taggen von 6 bildern (1 prozess hängt) - mal erst nach 225 Bildern (dann hängen alle 4 Prozesse)

Jeweils mit der letzten von geosetter vorgeschlagenen Version vom Exiftool, das hat sich bestimmt in dem Letzen Jahr 12x geupdated

bei nur jpg oder nur NEF passiert exakt das selbe
(0003344)
bselbmann   
2018-01-29 12:50   
Nach Einbau einer schnelleren Festplatte und neuinstallation (immer noch Win 7 64bit) im Laptop trat das Problem nicht mehr auf.

Auf dem Desktop Rechner ist das Problem von alleine verschwunden (MS Patches? exif tool?)


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
1838 [GeoSetter] User Interface minor always 2018-01-09 18:27 2018-01-09 19:02
Reporter: Wilfried Platform:  
Assigned To: Friedemann OS: Windows  
Priority: low OS Version: 10 64Bit  
Status: resolved Product Version:  
Product Build: Resolution: fixed  
Projection: none      
ETA: none Fixed in Version: 3.4.82 beta  
    Target Version:  
Summary: Download of Beta 3.4.82 not possible or wrong URL
Description: GeoSetter 3.4.53BETA suggest new version 3.4.82 (released 08.01.18) but the link www.geosetter.de/geosetter_beta.exe still points to the previous version.
Tags:
Steps To Reproduce:
Additional Information:
Attached Files:
Notes
(0003296)
Friedemann   
2018-01-09 18:33   
Yes, please excuse me, it seems that I didn't overwrite it on the server yesterday. It should work now: http://www.geosetter.de/geosetter_beta.exe
(0003301)
Wilfried   
2018-01-09 18:59   
Thank you! It did work now.
Interestingly the difference in size of the two exe is so small they both show in explorer with the same size of 22.807 KB.
During install, it was not able to close all other programs (the same as with 3.42.53). However ignoring the condition and restarting Windows (10 1709) seemed to finish the installation successfully. It does show 3.4.82 beta now and the message from Google disappeared.
(0003302)
Friedemann   
2018-01-09 19:02   
Fine :-) The version I'm just working on will contain an integrated update mechanism, so restarting the system should not be necessary then anymore...


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
1836 [GeoSetter] User Interface minor always 2018-01-09 14:18 2018-01-09 18:35
Reporter: mmm Platform:  
Assigned To: Friedemann OS: Windows 10 Pro  
Priority: normal OS Version: v1709  
Status: resolved Product Version:  
Product Build: Resolution: fixed  
Projection: none      
ETA: none Fixed in Version: 3.4.82 beta  
    Target Version:  
Summary: Fehler bei Installation von v 3.4.82 BETA
Description: Bei Ausführung der aktuellen Setup Datei "geosetter_beta.exe" wird immer noch die Version 3.4.53 BETA installiert.
Tags:
Steps To Reproduce:
Additional Information:
Attached Files:
Notes
(0003294)
Friedemann   
2018-01-09 14:20   
Jaaaa, ich weiß :-( Tut mir leid, sehr merkwürdig, da scheint beim Erstellen des Setup was schief gelaufen zu sein! Ich schaue heute Abend...
(0003297)
Friedemann   
2018-01-09 18:34   
Ich bitte nochmals um Entschuldigung, ich hatte die Dateien auf dem Server wohl nicht korrekt überschrieben. Nun sollte es aber klappen: http://www.geosetter.de/geosetter_beta.exe


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
1829 [GeoSetter] User Interface minor always 2017-11-27 23:54 2018-01-09 14:23
Reporter: ajft Platform: Windows  
Assigned To: Friedemann OS: Windows10  
Priority: normal OS Version: 10.0.14393  
Status: resolved Product Version: 3.4.16 beta  
Product Build: Resolution: fixed  
Projection: none      
ETA: none Fixed in Version: 3.4.82 beta  
    Target Version:  
Summary: geosetter warning regarding embedded Google Maps -- unsupported browser
Description: The embedded map in Geosetter (on my Windows10 system) is now displaying:

You are using a browser that is not supported by the Google Maps JavaScript
API. Considering changing your browser. Learn more Dismiss

Note: Geosetter is version 3.4.16 (Build 2119) but that version is not available in the "Product Version" drop-down list above.
Tags:
Steps To Reproduce: Open geosetter, warning appears as soon as map is displayed
Additional Information:
Attached Files: geosetter_internet_explorer.reg (358 bytes) 2018-01-08 16:24
https://geosetter.de/mantis/file_download.php?file_id=669&type=bug
Notes
(0003275)
ceroni   
2017-12-05 14:17   
Exactly the same warning here:
"You are using a browser that is not supported by the Google Maps JavaScript API. Considering changing your browser. Learn more Dismiss"

Despite the warning, everything seems to be working fine after clicking “Dismiss”.

Windows 10 Pro 1709 build 16299.64 (64bit)
Microsoft Internet Explorer 11.64.16299.0 (default browser is Opera 49.0.2725.47)
Geosetter 3.4.16 (build 2119)
Exiftool 10.67
(0003282)
alan-g   
2017-12-18 20:48   
Same here
(0003283)
Malcolm_Ferguson   
2017-12-18 22:31   
I'm running Windows 7 with the IE 11. The link in the error message leads to a page with some hints:
https://developers.google.com/maps/documentation/javascript/error-messages#unsupported-browsers
(0003284)
Malcolm_Ferguson   
2017-12-18 22:35   
I guess this is a duplicate (or English version) of: 0001828
(0003287)
rlsmith46   
2018-01-06 17:34   
The same error message with the same symptoms occurred recently in Picasa as well.

On the Picasa forum the source of the error was attributed to a Windows 10 update and was solved by a user (Christine) with a registry entry change:

  
Christine Schulze-Dammert said:
I found a solution
regedit:
HKey_Current_User\Software\Microsoft\Internet Explorer\Main\FeatureControl\Feature_Browser_Emulation
Add a DWORD named "picasa3.exe" and set to 2af8.
Then Picasa shows the location of a picture again.
I guess, this was changed during the last upgrade of Windows 10

That solved the problem for Picasa

See the post in the forum at: https://productforums.google.com/d/msg/picasa/mHZcTDkUrMQ/USfnZNlqAwAJ

Perhaps this will be of help in tracking down the error in Geosetter (??)
(0003288)
Friedemann   
2018-01-08 16:25   
(Last edited: 2018-01-09 14:23)
For the regular release 3.4.16 I attached the needed registry file here, which can be imported by double click.

The new beta version 3.4.82 always adds the registry entry on startup.

(0003293)
Friedemann   
2018-01-09 12:03   
(Last edited: 2018-01-09 12:03)
The beta version is available at http://www.geosetter.de/geosetter_beta.exe

(0003295)
Friedemann   
2018-01-09 14:23   
Please note: The current beta version mentioned above is wrong, it still seems to be the old version. Will be fixed today... See also 0001836


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
1828 [GeoSetter] User Interface minor always 2017-11-26 13:31 2018-01-09 12:24
Reporter: atomar Platform: MS  
Assigned To: Friedemann OS: Win 10  
Priority: normal OS Version: 1703  
Status: resolved Product Version: 3.4.16 beta  
Product Build: Resolution: fixed  
Projection: none      
ETA: none Fixed in Version: 3.4.82 beta  
    Target Version:  
Summary: Google Maps
Description: Der von Ihnen verwendete Browser wird von der Google Maps JavaScript API nicht unterstützt.
Tags:
Steps To Reproduce: Bei jedem Start von 3.4.16 (Build 2119) und 3.4.53 (Build 2170)
Additional Information:
Attached Files: Aufnahme2.jpg (99,021 bytes) 2017-11-27 20:44
https://geosetter.de/mantis/file_download.php?file_id=665&type=bug
Notes
(0003272)
heiko   
2017-11-27 17:13   
was für ein Betriebssystem hast du?

Ist der Internet Explorer aktuell? Sprich werden die Microsoft Updates für den IE ausgeführt
(0003273)
atomar   
2017-11-27 20:51   
MS / Win 10 / V 1703 (Build 15063.726)
IE 11 / V 11.726.15063.0

2017-11 Update für Windows 10 Version 1703 für x64-basierte Systeme (KB4049011)
Erfolgreich installiert am 15.11.2017
(0003285)
Malcolm_Ferguson   
2017-12-18 22:35   
Possibly duplicated by: 0001829
(0003286)
Harald   
2017-12-25 19:26   
Ich habe den selben Fehler mit Windows 7 64bit
IE 11.0.9600.18860 KB 4052978
(0003289)
Friedemann   
2018-01-08 16:26   
(Last edited: 2018-01-09 12:24)
Please see 0001829



View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
1316 [GeoSetter] Image Data minor always 2016-04-20 22:57 2017-11-24 17:52
Reporter: meesoft Platform:  
Assigned To: Friedemann OS:  
Priority: normal OS Version:  
Status: assigned Product Version: 3.4.14 Release  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Cannot import coordinates from KML files from Google maps timeline
Description: Google timeline is a very easy way to get your location tracked whenever you are carrying your phone and it can export a full day of locations to a KML file. Unfortunately GeoSetter cannot geotag images from such a file - it just says that it doesn't contain time information.
Tags:
Steps To Reproduce:
Additional Information: I have attached an example file from a days trace.
Attached Files: history-2016-03-12.kml (41,493 bytes) 2016-04-20 22:57
https://geosetter.de/mantis/file_download.php?file_id=434&type=bug
history-2017-04-04.kml (98,282 bytes) 2017-04-10 01:32
https://geosetter.de/mantis/file_download.php?file_id=463&type=bug
Notes
(0002460)
Mark.Michaelis   
2017-04-10 01:33   
Just to confirm, I have the same issue. The file was downloaded fro Google Location History. Here is the error:
---------------------------
Confirm
---------------------------
You didn't select a track file or your selected track file doesn't
contain any coordinates including date time information.

Would you like to try again?
---------------------------
Yes No
---------------------------
(0003269)
vadimpl   
2017-11-24 11:21   
Hello. I see the problem not decided. Do exist any method (e.g. convert to gpx) to solve it? GPSBabel and gpsvisualizer.com didn't help.
(0003270)
Mark.Michaelis   
2017-11-24 17:52   
I don't know of a workaround. I think it would be possible to make a minor modification to the file in order to get it to import but I'm not sure what that modification would be, unfortunately. :(


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
1210 [GeoSetter] Image Data feature always 2014-08-17 13:58 2017-10-12 09:43
Reporter: Mark.Michaelis Platform: Windows 8.1  
Assigned To: Friedemann OS:  
Priority: normal OS Version:  
Status: assigned Product Version: 3.4.16 beta  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Your selected track file doesn't contain any coordinates
Description: While trying to synchronize images with a track it errors out with the following dialog:
You didn't select a track file or your selected track file doesn't
contain any coordinates including date time information.

Would you like to try again?
Tags:
Steps To Reproduce: Click to synchronize with GPS Data Files and select the file. Attempts to get synchronization all fail with the message above.

Additional Information: Additional notes:
The "Assign waypoint" dialog doesn't list any waypoints and neither do the "Get from Synchronization Tracks" or "Open Waypoint Files(s)" list them.
The "Use Track Point From Map" option has the message, "You didn't select a time value by setting the red position marker in the main window nearby a track containing time values by now." even though before opening the dialog I went to a specific track point and placed the red maker exactly there.
Attached Files: backitude-daily-kml-08-11-2014.kml (135,385 bytes) 2014-08-17 13:58
https://geosetter.de/mantis/file_download.php?file_id=403&type=bug
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
1738 [GeoSetter] User Interface crash always 2017-09-23 15:29 2017-09-25 13:17
Reporter: ChrisGorringe Platform: Intel x64  
Assigned To: Friedemann OS: Windows 10  
Priority: normal OS Version: 10.0.15063  
Status: assigned Product Version: 3.4.51 beta  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Exif tool update crash
Description: With 3.4.53 beta, I have found a conflict with Netgear Powerline Utility 3.1.0.4.
Tags:
Steps To Reproduce: With this software installed, Geosetter goes into an endless loop whilst trying to update the Exif tool. Using Sysinternals Procmon, it is related to the reading on an XML file using msxml6.dll. Comparing the same process on another machine without the Powerline utility, Geosetter appears to use msxml3.dll.
The Powerline utility installs msxml4.dll and when it is uninstalled, Geosetter works perfectly without any further changes having to be made. Reinstalling the Powerline utility then causes Geosetter to stop working again. If left, the process memory allocation keeps increasing and the CPU utilisation endlessly consumes about 15 to 25%.
Let me know if you need anything else.
Additional Information:
Attached Files:
Notes
(0003058)
Friedemann   
2017-09-25 13:02   
Hi! Thank you very much for finding this out. I will not resolve it. I'm just working a lot on a new version of GeoSetter, where I replace the XML library by an independent library which does not use any external DLLs anymore. But thank you very much, it's good to know! :-)


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
1296 [GeoSetter] User Interface minor unable to reproduce 2016-01-25 00:02 2017-07-11 19:32
Reporter: eddydaddy27 Platform: win  
Assigned To: Friedemann OS:  
Priority: normal OS Version: 7  
Status: assigned Product Version: 3.4.16 beta  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Interface language
Description: The italian interface is not complete.
It's possible to give me the opportunity to translate the whole interface.
(the italian .po file not cover the whole interface).
thaks
ed
Tags:
Steps To Reproduce:
Additional Information:
Attached Files: default.pot (96,006 bytes) 2017-07-11 19:03
https://geosetter.de/mantis/file_download.php?file_id=556&type=bug
Notes
(0002725)
eddydaddy27   
2017-07-02 12:17   
I'm waiting for reply.
Thanks
(0002777)
Stoffel   
2017-07-11 18:09   
(Last edited: 2017-07-11 18:13)
Why not take the existing .\locale\en\default.mo or .\locale\de\default.mo, convert it, using "msgunfmt.exe" (may be included in Poedit) and run "msgunfmt default.mo > default.po" (PO-files are plain text files).
Then use that PO-file as a template for Italian language.

On the other hand side ... Friedemann already announced a new version to be released within the next weeks. Maybe it will be worthy to wait for it and translate the new version instead (if incomplete).

(0002779)
Stoffel   
2017-07-11 19:03   
(Last edited: 2017-07-11 19:32)
I attached a "default.pot" for you.
This file includes even more strings than the original MO-files (that were missing some translations in the latest GUI).
My file is for the latest version "3.4.53 (build 2170) BETA" (date: 04.01.2017).

You can open that file with Poedit and create a new translation.



View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
1544 [GeoSetter] User Interface major always 2017-06-25 16:10 2017-06-26 14:19
Reporter: erioho Platform: PC  
Assigned To: Friedemann OS: Windows  
Priority: normal OS Version: 10  
Status: assigned Product Version: 3.4.51 beta  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Incorrect thumbnail
Description: I use geosetter to tag some scanned image (16bit TIFF with alpha channel, from vuescan, they call it RAW Scan), the thumbnail on the left panel are corrupted as attached.

The image can be view normally in Vuescan, Windows, and any another program.
Tags:
Steps To Reproduce: Just launch and as it generate thumbnail, it happens.
Additional Information:
Attached Files: Untitled.jpg (72,936 bytes) 2017-06-25 16:10
https://geosetter.de/mantis/file_download.php?file_id=516&type=bug
Notes
(0002643)
Friedemann   
2017-06-25 16:14   
Can you send me such a TIFF example image please (support@geosetter.de) or Dropbox or whatever...
(0002645)
erioho   
2017-06-26 14:19   
Just send you the file, a link from google drive. A huge file as 160MB.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
1034 [GeoSetter] Image Data minor always 2013-04-27 06:11 2017-06-19 23:49
Reporter: thelordsmurf Platform:  
Assigned To: Friedemann OS:  
Priority: normal OS Version:  
Status: assigned Product Version: 3.4.34 beta  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Can you add support for Samsung SRW files?
Description: Hello,
I see that GeoSetter does not support/add geodata for Samsung's silly RAW format, SRW. I see that ExifTools itself does support SRW. Any way to add that for GeoSetter?
Thanks
Tags:
Steps To Reproduce:
Additional Information: NX300
Attached Files:
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
1464 [GeoSetter] User Interface major always 2017-05-16 07:44 2017-06-19 23:43
Reporter: sjmcmurray Platform: Windows  
Assigned To: Friedemann OS: Windows 10  
Priority: normal OS Version:  
Status: resolved Product Version: 3.4.16 beta  
Product Build: Resolution: fixed  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: The google map doesnt display and shows an error message
Description: There is no map in the map window
Tags:
Steps To Reproduce:
Additional Information:
Attached Files: aaa.pdf (44,044 bytes) 2017-05-16 07:44
https://geosetter.de/mantis/file_download.php?file_id=482&type=bug
google_maps_loads.jpg (101,401 bytes) 2017-05-17 07:44
https://geosetter.de/mantis/file_download.php?file_id=485&type=bug
download.png (29,229 bytes) 2017-05-17 10:29
https://geosetter.de/mantis/file_download.php?file_id=487&type=bug
Notes
(0002492)
Stoffel   
2017-05-16 08:08   
(Last edited: 2017-05-16 08:16)
Exactly the same for me (running Windows 8.1)

Map File: http://www.geosetter.de/map_google.html

(0002493)
Friedemann   
2017-05-16 08:54   
(Last edited: 2017-05-16 09:18)
Yes, I can confirm this problem. There's an error message which says:

You have exceeded your daily request quota for this API. We recommend enabling billing to get a higher quota: https://developers.google.com/maps/documentation/javascript/usage

And it's true, as I see there were over 100.000 requests today with my Google key. Normally it's about 15.000 requests per day. The maximum of free requests is 25.000. Each 1.000 request exceeding will cost 50 Cent. Fortunately I didn't enable this feature :-)

I really hope that this won't occur each day now. Of course I could change the Google key (I hope), but I will wait now to see what will happen today...

I apologize for the inconvenience!!! :-(

(0002498)
Friedemann   
2017-05-16 18:19   
An additional note: As I first noticed today, GeoSetter's key was not secure, it was possible to be used by everybody. I changed it now, it should now only possible to use it when called by geosetter.de. But I don't know at the moment, where the massive amount of requests came from. I really hope, that it didn't come from GeoSetter.exe itself. I assume and hope that somebody grabbed my Google key and used it for his own. By now, there are 344.982 request today!!! The limit for free request ist 25.000. As I said already, normally I have between 10.000 and 15.000 request per day.

We will see tomorrow...

Regards
Friedemann
(0002499)
Suedlicht   
2017-05-16 18:31   
Thank you very much for these statements, Friedemann. From time to time I'm a quite heavy user. I remember a message of geonames.org about my quota of 2000 per hour to be exhaustet - when I had about 800 photos and I ran it several times.
Sometimes I want the references to be very exact, so I run the whole thing two times: One time with the local windows setting, and then once again with a point on the map - which I could choose after the first run. I do so mostly when I had pictures taken out of a moving vehicle.
Knowing of the problem I will change this and do the first run just with a single photo.

Regards
S.
(0002500)
Friedemann   
2017-05-16 18:35   
> Knowing of the problem I will change this and do the first run just with a single photo.

I think you can register your own GeoNames user. 2.000 requests is not so much and reached quickly. For GeoNames each request counts. But for Google Maps a request is only the first opening of the map. It doesn't matter how much then the map will be moved etc. So the free limit of 25.000 request per day should be enough by now - normally :-/
(0002501)
Friedemann   
2017-05-16 18:36   
BTW: I work very hard on GeoSetter right now to release a new major version in a few weeks. Maybe months, it's difficult to say at the moment :-)
(0002502)
Suedlicht   
2017-05-16 19:24   
Thanks again, Friedemann. I have my own account on Geonames - 2000 may be the limit for free accounts. Thank you very, very much for your work!
(0002503)
othmarmarti   
2017-05-16 20:22   
Dear Friedemann,
I noticed that the Google address is called even if the map is set to Openstreetmap.org. Is there a possibility to use OSM without having to call Google? That would be a way to reduce the load. Google is nice, but I often use OSM
Thanks for the great program!
(0002504)
Friedemann   
2017-05-16 21:46   
No, regardless which map is used, GeoSetter uses the Google Maps API for all the functionalety of the map, showing markers etc. That dioesn't have anything to do with the background map itself. An alternative would be OpenLayers. Then it would be possible for example to use it all offline without an internet connection by installing a local map server. Maybe I will do it in the future. but by now, I'm very happy with Google Maps...
(0002505)
othmarmarti   
2017-05-16 21:51   
Thanks for the clarification. Google works well - if there were not those floods of requests :_(
(0002509)
sjmcmurray   
2017-05-17 01:40   
Thanks for the reply - your software is amazing and is one of the easiest to use geotagging programs around. Thanks for your hardwork.

It seems that the user base is quite large as I still cannot get it too load up the Google map image so that I can geotag my imagery
(0002512)
Stoffel   
2017-05-17 05:55   
Many thanks, Friedemann. Unfortunately the same error occurs also today.
(0002513)
Friedemann   
2017-05-17 07:42   
The day ends at 0 o'clock Pacific Time, which will be 9 o'clock here in Europe. I attached an image where you can see the amount of requests in the last days :-/
(0002516)
Stoffel   
2017-05-17 09:10   
9:06 (Central European Summer Time) - Nothing changed. Still (or already again) the same error. :-(
(0002517)
Friedemann   
2017-05-17 09:45   
Yes, by now it's not working :-(

To fix it for yourself, you could register your own Google Maps API key here: https://developers.google.com/maps/documentation/javascript/get-api-key

Then you can download the map files of GeoSetter here http://download.friedemann.info/geosetter_map.zip and unpack them somewhere on your harddisk and put in your Google key in the HTML file. After changing the map file now in GeoSetter settings, it should work again.

Of course this is not a good solution, but it should work for now...
(0002520)
kh1234567890   
2017-05-17 10:30   
I've tried using my own key etc. Unless I'm doing something wrong - I'm no expert at the API - Geosetter appears to generate many requests to my brand new key (1000+ in a short interval). Any ideas ?
(0002521)
Friedemann   
2017-05-17 10:39   
Really??? A request should only count when opening the map, for example by starting GeoSetter. That's 1 request... Ok, then something with the map file seems to be wrong and I have to care about in the evening after work. I will remove it now...
(0002522)
sipeoutdoor   
2017-05-17 10:42   
Good morning, was done as suggested, I downloaded the files and inserted the Google api key, but there are some errors in the code inspection:

Google Maps API warning: RetiredVersion https://developers.google.com/maps/documentation/javascript/error-messages#retired-version

Google Maps API warning: SensorNotRequired https://developers.google.com/maps/documentation/javascript/error-messages#sensor-not-required

also as in other posts, i confirm that are generated by Geosetter many requests, in the span of a few seconds. the api key went from 0 to 1465 requests.

Any ideas ?
(0002523)
Friedemann   
2017-05-17 10:48   
I didn't change the code for a long time now. Maybe it crashes somewhere since yesterday and always created a new instance of the map? That would maybe explain the high amount of requests. I will care about after closing time...
(0002524)
kh1234567890   
2017-05-17 10:54   
Thanks Friedemann, Geosetter is such an incredibly useful program. Hopefully it will be fixable.
(0002525)
denis1807   
2017-05-17 11:38   
I have the same extact problem, 1068 requess in less then 2 minutes.
I really hope you can solve this problem quickly, I'm really in trouble without Geosetter.
Thanks a lot for your works Mr. Friedmann, I really appreciate your works!!!
(0002526)
sipeoutdoor   
2017-05-17 12:17   
I did some tests in the code that refers to the API KEY, I removed the version and tried to handle it all on a host that does not need the Key (here are the explanations about inserting the api key https: //www.latecnosfera.com/2016/06/google-maps-api-error-missingkeymaperror-risolto.html), everything seems to work, but the map does not show because geosetter continues to make requests, most likely there is a Error in compiling the code.
(0002528)
Malcolm_Ferguson   
2017-05-17 12:43   
(Last edited: 2017-05-17 12:46)
Glad to hear an update is coming. I like your software so much that I use it in a virtual machine, despite my workflow all being in Lightroom on a Mac.

I'm seeing the same problems in 2.4.53 (build 2170) BETA, and I'm also seeing the retired API message in the Java script console using the maps URL in Safari

I right-clicked on the map pane to bring up the context menu and chose "properties". This gave me the URL "http://www.geosetter.de/map_google.html", which I copied in to Safari. Plus of course the expected error now that you've locked your API key down to the application:

[Warning] Google Maps API warning: RetiredVersion https://developers.google.com/maps/documentation/javascript/error-messages#retired-version (util.js, line 210)
[Warning] Google Maps API warning: SensorNotRequired https://developers.google.com/maps/documentation/javascript/error-messages#sensor-not-required (util.js, line 210)
[Error] Google Maps API error: RefererNotAllowedMapError https://developers.google.com/maps/documentation/javascript/error-messages#referer-not-allowed-map-error
Your site URL to be authorized: http://www.geosetter.de/map_google.html
    kb (js:34:336)
    (anonymous function) (common.js:53:462)
    (anonymous function) (common.js:194:173)
    c (common.js:49:407)
    Global Code (AuthenticationService.Authenticate:1)

(0002529)
Friedemann   
2017-05-17 12:50   
> [Error] Google Maps API error: RefererNotAllowedMapError https://developers.google.com/maps/documentation/javascript/error messages#referer-not-allowed-map-error
> Your site URL to be authorized: http://www.geosetter.de/map_google.html

yes, that's new and I did it yesterday. It prevents that anybody else uses my Google key, except the map file on geosetter.de.
(0002530)
gabiandrone   
2017-05-17 12:50   
I suspected the problem was due to the new version of java so I uninstalled it and installed an older version. I tested on my own map file (with the two warnings fixed) with my key, and there are still a lot of requests. In conclusion, the problem is not from the java update.
(0002531)
Friedemann   
2017-05-17 12:52   
> In conclusion, the problem is not from the java update.

no, it isn't! It's my part now ;-) I think you can't do anything now, many thanks! You simply have to wait. I'll care about it after closing time...
(0002532)
Friedemann   
2017-05-17 12:57   
@Malcolm_Ferguson: Thanks! It was my mistake, I secured the key with "geosetter.de", but it has to be "http://www.geosetter.de/*". I changed it now. But I think the main problem still does exist...
(0002533)
Malcolm_Ferguson   
2017-05-17 13:17   
(Last edited: 2017-05-17 13:21)
That's certainly made a change, but after re-starting the app it seems to be stuck in a loop constantly reloading the map pane. I have to kill it using Task Manager. WireShark shows it repeatedly requesting: /maps/api/js/QuotaService.RecordEvent?[...]

I can post the whole Wireshark trace if it will help

Workaround: start the app with the network interface disabled. Re-enable it later, and I can still use interlet lookups for timezone and location. I've already added GPS locations in Lightroom, so I suppose this won't be helpful for all people.

(0002534)
Friedemann   
2017-05-17 13:19   
It worked for a short time. Now the requests exceed again my free amount. So there's definetely a problem in the code. Maybe the reloads you are talking about are causing the problem. As I said, I will see in the afternoon. I created a new GMail adress and a new key for testing :-)
(0002535)
Friedemann   
2017-05-17 13:21   
> I can post the whole Wireshark trace if it will help

oh yes please, you can also send it per mail to me (support@geosetter.de). Thanks!
(0002536)
Malcolm_Ferguson   
2017-05-17 13:22   
Yeah maybe there was an API change (behaviour, not necessarily interface) on the Google side, and it's confusing the app.
(0002537)
Friedemann   
2017-05-17 13:24   
I found this:

> The QuotaService will count things that are affected by
> usage-limits(e.g. Map-loads)

so it is ok. But why it will be called so much times, this is the question. And I'm pretty sure there's an answer to it ;-) Many thanks to you by now!
(0002538)
Friedemann   
2017-05-17 18:22   
I found the problem :-) It really was GeoSetter itself. To whom it may concern: In GeoSetter.exe there's code which will be called on DocumentComplete from within the EXE file. In this code a function of the map file (JavaScript) will be called which initializes the map. This initialization is what counts as a request for Google. Unfortunately since yesterday, this code has been called again and again. In the map file I added the code "if (map) { return }" right at the beginning. With this change it works.

As I said, I'm working a lot at the moment on a new major version of GeoSetter. A few weeks ago, I've nearly totally rewritten also the map file. The new version doesn't have this problem. I think I will finish it in about 2 months, I will see. Maybe 3...

To all of you, who were in trouble with this problem, I apologize for the inconvenience this may have caused. I really thought that someone else have stolen my Google API key for doing bad things.

The map still doesn't work as the free requests still are exceeded for today. So we have to wait until 0:00 o'clock Pacific Time (9:00 o'clock here in Germany) to see if it all works again. But I just tested it with another API key and it works well again.

Best regards
Friedemann
(0002540)
Stoffel   
2017-05-17 19:18   
Wonderful news! :-) and many thanks to you, Friedemann.
Hopefully everything will be fine again tomorrow.

And I am quite excited for the new Geosetter version.

With kind regards.
(0002541)
kh1234567890   
2017-05-17 19:25   
Great !

Could you repost the changed map file zip so that I could try running it with my own key until Google count resets ?
(0002543)
zava   
2017-05-17 21:51   
Thank you Friedemann for fixing it so fast!
Very exciting that a new version of GS will be issued, although I can't really see how much better it may get!
(0002544)
gabiandrone   
2017-05-17 22:08   
I used my own api key and the program works!
Many thanks, Friedemann!
I look forward to the new version of the program.
All the best!
(0002545)
Friedemann   
2017-05-17 22:22   
@kh1234567890: In showMap3() you have to insert

if (map) {
  return;
}

at the beginning.

BTW: I didn't know JavaScript when I wrote this code, that's why there are showMap1, showMap2 and showMap3 ;-)
(0002546)
andrew   
2017-05-17 23:51   
Is this why Geosetter displays Los Angeles in top left corner for a moment then disappears and says "Sorry! Something went wrong - The page didn't load Google Maps correctly. See the JavaScript console for technical details"
 - or is that a separate error?
(0002547)
samfares   
2017-05-18 02:46   
Hi
When i try to download the zip file it state file not found
(0002548)
naneyoo   
2017-05-18 03:50   
me too cant find the file..help
(0002549)
mantis   
2017-05-18 07:22   
Registered an account here just to say thank you to Friedemann!
(0002550)
Stoffel   
2017-05-18 09:03   
9:01 (Central European Summer Time): Perfect! :-) It seems to work and the map is loading correctly again. Thanks a lot!
(0002551)
obetz   
2017-05-18 09:09   
the map doesn't work correctly with a copy on my hosting account:

I downloaded http://www.geosetter.de/map_google.html, inserted my own Google API key, uploaded it to my own web site and changed the path in config.ini to my own URL.

Now it shows the map and the track, but not the image locations and viewing directions/angles.

What did I miss?

After all, the map on geosetter.de seems to work now, but if I can, I want to put the load on my own key and site.
(0002552)
DenisPac   
2017-05-18 10:14   
@obetz, you don't need this workaround anymore since the regular map file is working just fine since this morning.
(0002554)
denis1807   
2017-05-18 10:27   
Thanks a lot, for your works Friedemann, now works flawlessly!!!
(0002555)
Friedemann   
2017-05-18 10:35   
Yesterday I removed the zip file from my server as it still did contain the wrong map file. I didn't replace it. When using your own API key with your own copy of the map file, then you won't notice any changes I do maybe on the map. It's not very often I do it, but sometimes I will. Do I maybe have to consider this in the next version of GeoSetter, maybe a versioning functionalety and automatic download of all needed files for using it with your private key?

@obetz:

> Now it shows the map and the track, but not the image locations
> and viewing directions/angles.

yes, of course, there are some images which will be referenced. And BTW, you don't have to upload it to any server, you can simply put the files in a folder located on your harddisk, for example into a subfolder of your GeoSetter folder.
(0002556)
Jonesthemap   
2017-05-18 11:53   
I'm newly registered, great software, been using for some years. I ended up removing the software because of problems in the last few days. Can you explain how I can re-install and get going again? I'm afraid I'm not savvy with regard to making programme changes, do I need to wait for an upgrade? Thanks
(0002557)
Friedemann   
2017-05-18 12:07   
@Jonesthemap: No, you don't have to wait. Simply reinstall it. I recommend the "beta" version (http://www.geosetter.de/geosetter_setup.exe) which contains some changes from the last years. You can see some changes here: http://www.geosetter.de/mantis/changelog_page.php

It looks a bit strange, the "beta" now exists for about 6 years. I simply didn't release it as an official version because of all the things I had to do then, changing the website etc.. As I said already I'm just working on a new major version. But until then, I recommend the beta version which runs as stable as the officiual version 3.4.16 does...
(0002558)
naneyoo   
2017-05-18 12:12   
Thank you.. the map is working now..
(0002559)
Malcolm_Ferguson   
2017-05-18 12:58   
Vielen Dank Friedemann. It's working well again.
(0002562)
Jonesthemap   
2017-05-20 13:46   
Friedemann thank you so much for your prompt reply, I'm up and running again! It's a great piece of software. Cheers
(0002575)
arvid   
2017-06-01 09:20   
Friedemann, it show the file:
http://download.friedemann.info/geosetter_map.zip
not found!


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
1508 [GeoSetter] Image Data major always 2017-06-05 17:29 2017-06-16 14:08
Reporter: obetz Platform:  
Assigned To: Friedemann OS:  
Priority: high OS Version:  
Status: assigned Product Version: 3.4.16 beta  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Inadvertent cnage of GPS Destination Coordinates
Description: Opening images for editing changes the GPS target coordinates before I change any field, just by looking at the entries.

The change less than 1E-6 degrees but nevertheless it's bad to touch any entry.

The image was previously edited with Geosetter 3.4.53 and another version of Exiftool.

Viewing the images with Geosetter 3.4.53 doesn't change the target coordinates. I donÄt know whether the error is fixed in 3.4.53 or whether it's caused by using different versions subsequently.

After all, 3.4.16 does not announce itself as "beta" but there is no 3.4.16 release in the mantis drop down field.
Tags:
Steps To Reproduce: 1. mark two or more images with destination coordinates
2. Press Ctrl-E to edit them
3. switch between the images -> dest coordinates get printed bold and slightly changed

Additional Information:
Attached Files:
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
1503 [GeoSetter] Image Data major always 2017-06-04 13:35 2017-06-10 15:44
Reporter: onurbi Platform: Dell Latitude 830  
Assigned To: Friedemann OS: Windows  
Priority: high OS Version: 10  
Status: assigned Product Version: 3.4.16 beta  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Aufnahmedatum eines JPG-Files wird nicht erkannt
Description: Es liegen zwei Aufnahmen der selben Kamera vor, die innerhalb von einer Minute erstellt wurden.

Bei Foto1 wird das Aufnahmedatum im Ballon angezeigt, im anderen nicht.

Der Exifviewer zeigt bei beiden Files unter Zeit die Daten komplett an.

Dadurch ist natürlich kein Koordinatenabgleich möglich und das Foto2 ist nicht geocodierbar.
Tags:
Steps To Reproduce: Anzeige in Bildinfo
Additional Information: Man kann hier nur ein Attachment anhängen. Ich habe das kritische Foto2 drangehängt.
Attached Files: Aufnahmedatum-wird-nicht-angezeigt.JPG (770,490 bytes) 2017-06-04 13:35
https://geosetter.de/mantis/file_download.php?file_id=503&type=bug
Aufnahmedatum-wird-angezeigt.jpg (755,285 bytes) 2017-06-05 22:40
https://geosetter.de/mantis/file_download.php?file_id=506&type=bug
Exit-Daten-Foto1.png (4,827 bytes) 2017-06-05 22:41
https://geosetter.de/mantis/file_download.php?file_id=507&type=bug
Exit-Daten-Foto2.png (8,036 bytes) 2017-06-05 22:41
https://geosetter.de/mantis/file_download.php?file_id=508&type=bug
Notes
(0002583)
onurbi   
2017-06-04 13:39   
There are two iamges from the same Camera. They have been recorded in a time distance of under 1 minute.

For Photo1 the recorded time will be displayed in the balloon. For photo2 not.

The Exifviewer shows for both images under time the complete data.

Therefore geocoding is not possible for photo 2.
(0002584)
Friedemann   
2017-06-05 20:00   
Wurde das Bild denn mit irgendeiner Software behandelt. Es enthält das Aufnahmedatum in den Exif-Daten nicht (TAG-ID 36867 bzw. 0x9003). Das kannst Du auch mit Strg+I anzeigen lassen... Weiß nicht, ob ich da was machen muss, vielleicht ein anderes Datum nehmen? Komisch...
(0002585)
onurbi   
2017-06-05 22:47   
Hallo Friedemann,

bei der Auswahl der Zeitfelder ist die Entscheidung schwer.

Bei dem Foto2 ist neben "Digitalisierungsdatum" (Tag-ID 0x9004) auch noch "Datum/Uhrzeit der Digitalisierung" (die Tag-ID wird dort nicht angezeigt) dabei. Das nimmst Du anscheinend.

Spricht etwas dagegen, die Tag-Id 0x-9004 zu nehmen?

Gruß, Onurbi
(0002586)
onurbi   
2017-06-05 23:02   
Ich habe mich bei den Namen der Screenshots vertan.
Wollte es korrigieren und finde nicht, wo ich Attachments löschen kann?
Inzwischen habe ich entdeckt, wie man die Tag-IDs mit anzeigen lassen kann. Das wäre jetzt auch auf dem Screenshot drauf.

Was ich als Foto1 bezeichne (Aufnahmedatum-angezeigt) habe ich jetzt ebenfalls drangehängt.

Ich habe beide Fotos mal mit dem exitTool -H untersucht

Es fällt auf, dass nicht alle Felder in den EXIF-Daten Tag-IDs haben.

0x9003 ist auch in Foto nicht enthalten. Zumindest nicht als ID.

Dort gibt es wie erwähnt "Datum/Uhrzeit der Digitalisierung". Hat das Feld normalerweise die 0x9003?
(0002587)
onurbi   
2017-06-05 23:03   
Und: Die Fotos habe ich im irfanview verkleinert. Der Effekt ist aber trotzdem der Gleiche. Der Irfan läßt die Exifdaten offenbar unberührt.
(0002588)
onurbi   
2017-06-10 15:44   
Spricht etwas dagegen, die Tag-Id 0x-9004 zu nehmen?


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
1501 [GeoSetter] User Interface minor always 2017-06-02 20:30 2017-06-02 20:30
Reporter: obetz Platform:  
Assigned To: OS:  
Priority: normal OS Version:  
Status: new Product Version: 3.4.51 beta  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Synchronize: Saved files stay red / "dirty"
Description: After saving changes in the Synchronize dialog, the saved images stay red and an attempt to leave the dialog rises the warning about unsaved changes. It seems the dirty flag isn't reset after saving.

BTW: The dialog of the bug tracker doesn't allow to select 3.4.53 beta which is the version I tested. 3.4.16 doesn't have this error.
Tags:
Steps To Reproduce: Synchronize
Save
Watch colour: still red indicating unsaved changes
try to close dialog -> warning

Additional Information:
Attached Files:
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
1491 [GeoSetter] User Interface minor always 2017-05-31 12:55 2017-05-31 12:55
Reporter: obetz Platform:  
Assigned To: OS:  
Priority: normal OS Version:  
Status: new Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Caption and Headline text boxes shall be larger
Description: The Caption and Headline text boxes are fixed size although the dialog window is resizeable.

It's difficult to edit longer descriptions in the small edit fields since you have to scroll forward and backward.

I suggest to make the text boxes larger or even sizeable.
Tags:
Steps To Reproduce:
Additional Information:
Attached Files:
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
1344 [GeoSetter] Image Data minor always 2016-10-03 13:46 2017-05-30 19:10
Reporter: obetz Platform:  
Assigned To: Friedemann OS:  
Priority: low OS Version:  
Status: assigned Product Version:  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Destination coordinates for location lookup?
Description: Can I use the destination coordinates for geonames location lookup? This would be useful for aerial photos where the destination is to be described, not the location of the camera.
Tags:
Steps To Reproduce:
Additional Information:
Attached Files:
Notes
(0002358)
obetz   
2016-10-15 18:41   
The more aerial pictures I tag the more I would like to have the possibility to use the destination coordinates for geonames location lookup! The "location" is mostly not usable because the distance between camera and destination is more than 1km.
(0002574)
obetz   
2017-05-30 19:10   
I suggest a checkbox "prefer the destination coordinates for geonames query". If an image has no destination coordinates, a fallback to the camera coordinates makes sense.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
1490 [GeoSetter] Image Data feature always 2017-05-29 08:53 2017-05-29 20:22
Reporter: kljklj Platform: WIN  
Assigned To: OS: 7  
Priority: normal OS Version:  
Status: new Product Version: 3.4.16 beta  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Use GPS Date and Time
Description: I have (mobile phone) pictures with no date, time and gps information. They have a filled GPS-Time field though (see attachment). Geosetter can't use this time stamp for synchro with GPS tracks.
Would be good to have one of the functionalities:
- Use GPS time stamp for synchro
- batch copy GPS time stamp to standard time field.
Tags:
Steps To Reproduce:
Additional Information:
Attached Files: GPS Datum.JPG (60,440 bytes) 2017-05-29 08:53
https://geosetter.de/mantis/file_download.php?file_id=495&type=bug
Notes
(0002573)
heiko   
2017-05-29 20:22   
nachdem GeoSetter auf Deutsch eingestellt ist, antworte ich jetzt mal auf Deutsch.

Es gibt den Menüpunkt "Bearbeiten | GPS-Datum auf Aufnahmedatum setzen".


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
1476 [GeoSetter] User Interface crash always 2017-05-18 18:22 2017-05-19 10:03
Reporter: pische Platform: Intel Xeon E3-1240 v5 3,5GHz  
Assigned To: Friedemann OS: Windows  
Priority: normal OS Version: 10 64bit  
Status: resolved Product Version: 3.4.14 Release  
Product Build: Resolution: fixed  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Programm beendet gleich nach Start (noch vor Öffnen des Fensters)
Description: Da ich Probleme mit der Darstellung der Karte hatte (mittlerweile weiß ich, dass ich nicht der Einzige war), habe ich die Beta-Version deinstalliert und die offiziell freigegebene Version 3.4.14 installiert.
Seither stürzt das Programm sofort nach dem Start wieder ab ohne dass irgendein Fenster oder eine Fehlermeldung erscheint.
Ein Deinstallieren, manuelles Löschen aller Dateien und Registry-Einträge und Neuinstallieren ist auch erfolglos. Sowohl mit Version 3.4.14 als auch mit der Beta-Version passiert dasselbe.
Im Verzeichnis C:\ProgramData\Microsoft\Windows\WER\ReportArchive werden beim Absturz Report.wer Dateien erzeugt (siehe Anhang). Leider hift mir deren Inhalt nicht weiter.
Andere Programme (Firefox, Internet Explorer, Photoshop, Lightroom, PTGui, ThumbsPlus, OpenOffice,...) bereiten mir keinerlei Probleme.
Betriebssystem ist Windows 10 64bit mit aktuellem Patch-Stand
Tags:
Steps To Reproduce:
Additional Information:
Attached Files: ReportArchive.zip (6,604 bytes) 2017-05-18 18:22
https://geosetter.de/mantis/file_download.php?file_id=488&type=bug
Notes
(0002560)
pische   
2017-05-18 19:10   
GELÖST!
Hätte den Issue doch noch nicht öffnen sollen :-(
Habe nun die in http://www.geosetter.de/mantis/view.php?id=1464 empfohlene Beta-Version heruntergeladen. Nochmals alles deinstalliert, anschließend manuell Profildaten und Programmverzeichnis gelöscht und neu installiert.
Nun funktioniert wieder alles problemlos.
Habe wohl bei den vielen Versuchen zu wenig konsequent bereinigt und irgendetwas übersehen.
Danke übrigens für dieses wunderbare Programm! Werde mich demnächst erkenntlich zeigen. Mir wurde jetzt wieder bewusst, wie viel Zeit mir Geosetter spart.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
1477 [GeoSetter] Image Data major always 2017-05-19 01:59 2017-05-19 01:59
Reporter: Harry O Platform: Microsoft Windows  
Assigned To: OS: WIN 10  
Priority: normal OS Version: 10.0.14393  
Status: new Product Version: 3.4.51 beta  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Version 3.4.53 beta; cannot copy and paste dates and time anymore
Description: In the past I could batch paste date and time to multiple images.
Tags:
Steps To Reproduce:
Additional Information:
System Description
Attached Files:
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
1197 [GeoSetter] Image Data block always 2014-06-21 12:47 2017-05-18 22:35
Reporter: stavn Platform:  
Assigned To: Friedemann OS:  
Priority: normal OS Version:  
Status: assigned Product Version: 3.4.16 beta  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Unable to save positioned images
Description: Sync with GPS data file seems to work fine, but when saving images I get:

Error: Error reading OtherImageStart data in ExifIFD - //SERVER/Pictures/Photos/Røsnæs 2014/2014-06-15 08.55.48.jpg

C:\Users\Jan\AppData\Roaming\GeoSetter\tools\exiftool.exe -@ "C:\Users\Jan\AppData\Local\Temp\et00C14E44.arg" "\\SERVER\Pictures\Photos\Røsnæs 2014\2014-06-15 08.55.48.jpg"

-EXIF:GPSLatitude=55.73592770
-EXIF:GPSLongitude=10.89691400
-EXIF:GPSLatitudeRef=N
-EXIF:GPSLongitudeRef=E
-EXIF:GPSMapDatum=WGS-84
-EXIF:GPSVersionID=2.2.0.0
-EXIF:GPSAltitude=56.000000
-EXIF:GPSAltitudeRef=Above Sea Level
-EXIF:GPSDateStamp=2014:06:15
-EXIF:GPSTimeStamp=06:55:48
-XMP:GPSLatitude=55.73592770
-XMP:GPSLongitude=10.89691400
-XMP:GPSVersionID=2.2.0.0
-XMP:GPSMapDatum=WGS-84
-XMP:GPSAltitude=56.000000
-XMP:GPSAltitudeRef=Above Sea Level
-XMP:GPSDateTime=2014-06-15T06:55:48Z
-XMP:Creator=
-XMP:AuthorsPosition=
-XMP:CountryCode=
-XMP:Country=
-XMP:State=
-XMP:City=
-XMP:Location=
-XMP:Artist=
-XMP:Description=
-XMP:Instructions=
-XMP:Title=
-XMP:Headline=
-XMP:Credit=
-XMP:Rights=
-XMP:CaptionWriter=
-XMP:Source=
-XMP:BaseUrl=
-XMP:Category=
-XMP:DateCreated=2014-06-15T08:55:48Z+02:00
-xmp:rating=
-xmp:ratingpercent=
-XMP:Label=
-XMP:CreatorAddress=
-XMP:CreatorPostalCode=
-XMP:CreatorCity=
-XMP:CreatorRegion=
-XMP:CreatorCountry=
-XMP:CreatorWorkTelephone=
-XMP:CreatorWorkEmail=
-XMP:CreatorWorkURL=
Tags:
Steps To Reproduce: 1. Set a position marker on attached image
2. Try to save it
Additional Information: Exif was recently updated to 9.65

I got an error when trying to attach picture. You can get the image here: https://dl.dropboxusercontent.com/u/528734/2014-06-15%2008.55.48.jpg
Attached Files:
Notes
(0002561)
stavn   
2017-05-18 22:35   
Image is too big to attach https://drive.google.com/open?id=0B8twqaXNjHC5X3hDU0xyekFNR3c


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
1474 [GeoSetter] User Interface minor have not tried 2017-05-17 21:26 2017-05-17 21:26
Reporter: toMMasz Platform:  
Assigned To: OS:  
Priority: normal OS Version:  
Status: new Product Version: 3.4.51 beta  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: nie wczytuje si? mapa, wy?wietla si? komunikat jak poni?ej
Description: 2017-05-17 21:23:24 setMapDimension(577, 396);
2017-05-17 21:23:31 setMapDimension(577, 313);
Tags:
Steps To Reproduce:
Additional Information:
Attached Files:
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
1001 [GeoSetter] Image Data minor always 2012-11-07 19:46 2017-05-17 12:35
Reporter: flightfollowing Platform:  
Assigned To: Friedemann OS:  
Priority: normal OS Version:  
Status: assigned Product Version: 3.4.14 Release  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: Importing Pitch and Roll into exif data
Description: I have attempted to import lat long data which includes pitch and roll into imagery using geosetter and nmea track files, but have no success using geosetter. This functionality is available in exiftool, but apparently not in geosetter? Is this functionality implemented in geosetter, and how would this be done?
Also, when I load the help file, it is empty, how is this connected?
Tags:
Steps To Reproduce:
Additional Information:
Attached Files:
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
999 [GeoSetter] User Interface major always 2012-11-03 16:34 2017-05-17 12:35
Reporter: Ecke81 Platform:  
Assigned To: Friedemann OS:  
Priority: normal OS Version:  
Status: assigned Product Version: 3.4.34 beta  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
    Target Version:  
Summary: nmea-Datei von Royaltek RGM 3800 wird nicht erkannt
Description: Beim Synchronisierungsversuch von Fotos mit Dateien vom RGM 3800 erhalte ich ständig diese Meldung:
"Sie haben keine Trackdatei ausgewählt oder die gewählte Trackdatei enthält keine Koordinaten mit Datums- und Zeitinformationen"
Mit einer früheren Version von Geosetter hatte ich keine Probleme.
Tags:
Steps To Reproduce:
Additional Information: Das Problem tritt sowohl mit der 3.4.31 beta, als auch mit der 3.4.16 auf.
Attached Files: 00031_20120411.nmea (1,199,686 bytes) 2012-11-03 16:34
https://geosetter.de/mantis/file_download.php?file_id=306&type=bug
There are no notes attached to this issue.


View Issue Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
1469 [GeoSetter] Image Data feature N/A 2017-05-17 01:41 2017-05-17 12:35
Reporter: Tillomar Platform: PC  
Assigned To: Friedemann OS: Windows  
Priority: normal OS Version: 7 x64 SP1 b7601  
Status: assigned Product Version: 3.4.16 beta