View Issue Details

IDProjectCategoryView StatusLast Update
0002465GeoSetterImage Datapublic2023-02-23 18:17
Reporterdydxdx Assigned ToFriedemann  
PrioritynormalSeverityminorReproducibilityalways
Status resolvedResolutionfixed 
Product Version3.5.1 
Target VersionFixed in Version 
Summary0002465: Beta 4.0.33 build 2177 Unable to get Location data from WEB
DescriptionUnable to get location data, as I have in previous beta versions. The setting in v4.0.33 and v3.5.3 are identical: v3.5 works, v4.0 doesn't
Steps To ReproduceRegular synchronization
Additional InformationHad this problem in early beta version, and changing ""use http instead of https"" solved it then....but not now.
TagsNo tags attached.

Activities

dydxdx

2023-01-27 23:57

reporter  

2023-01-27_153800.jpg (742,017 bytes)
2023-01-27_154443.jpg (766,529 bytes)

mak_kawa

2023-01-28 06:06

reporter   ~0004472

Weird... I can get Location Data with no problem by "Get from the Web" with address setting of "http://api.geonames.org" in Geosetter 4.0.33 build 2177. I am not sure what is different between us.

WilfriedB

2023-01-28 09:05

reporter   ~0004474

Does work for me in 4.0.33 and I used almost all previous 4.0.xx betas without any problems.

However, trying again just now, I realized Get Location from Web does work, but trying to get the ALTITUDE from the web DOES NOT. I.e. pressing the button does not do anything and no error message visible.

mak_kawa

2023-01-28 09:17

reporter   ~0004475

At least for me, getting altitude from the Web also does work with no problem. Strange...

heiko

2023-01-28 14:22

developer   ~0004481

I have no problems retrieving the location and altitude data. There were problems with this function, but they should be fixed by now.

xyzzy

2023-01-28 14:28

reporter   ~0004482

It sometimes happens that the tool used by GeoSetter does not find an elevation.
for example: In Ha Long Bay
-Latitude: 20.87946000
-Longitude: 107.18094200

dydxdx

2023-01-28 14:49

reporter   ~0004483

Manually sync'g location data works, just no auto pop-up following acceptance of "GPS data has been found for all XX images. Would you like to continue with this result?"

2023-01-28_064027.jpg (1,006,985 bytes)
2023-01-28_064834.jpg (919,686 bytes)

dydxdx

2023-01-28 19:21

reporter   ~0004484

The two 20 second videos below demonstrate the different synching behavior of 3.0 and 4.0.....the lack of a pop-up GEONAMES data location window in the beta. The beta will connect to GEONAMES manually (Get from WEB button), but not automatically.
Geosetter 3.0 https://youtu.be/tsmq8Ppokh0
Geosetter 4.0 https://youtu.be/aMj1M5fKeVg

WilfriedB

2023-01-29 13:04

reporter   ~0004485

@dydxdx I do get the message ""GPS data has been found for all XX images. Would you like to continue with this result?" in 4.0.33. Are you sure, the coordinates are not in your favorites? In that case the metadata is changed silently. I believe, the massage also does not come up, if you assigned the same or similar location to other images shortly before.

My statement in 0004474 regarding the altitude was incorrect: It does work correctly. You just need to wait a couple of seconds and watch carefully, since the numbers change silently.

dydxdx

2023-01-29 14:40

reporter   ~0004486

WilfriedB, thanks for your suggestions:
"Are you sure, the coordinates are not in your favorites?" >>>>> they are not in favorites.
" I believe, the massage also does not come up...." >>>>> not so, deleting location data then resynching same problem.

My thoughts are that there is clearly a coding difference in synching between the 2 versions. They behave differently.

dydxdx

2023-01-29 16:41

reporter   ~0004487

In response to the following, if I understand correctly, see the video below with blanked-out location data...same problem:
" I believe, the massage also does not come up, if you assigned the same or similar location to other images shortly before."

https://youtu.be/bqAaeJHw8e0

dydxdx

2023-02-02 22:06

reporter   ~0004512

Installed beta 4.0.38 on Surface Pro 7 Model 1866 i5....same problem. Both desktop and Surface Pro are Win10 machines. I'm surprised no one else has observed this issue.

dydxdx

2023-02-03 00:29

reporter   ~0004515

Solved...totally missed this in settings, default apparently is null.

2023-02-02_162518.jpg (182,235 bytes)
2023-02-02_162518.jpg (182,235 bytes)

andregallegos

2023-02-23 12:31

reporter   ~0004635

Solved...totally missed this in settings, default apparently is null.

Issue History

Date Modified Username Field Change
2023-01-27 23:57 dydxdx New Issue
2023-01-27 23:57 dydxdx File Added: 2023-01-27_153800.jpg
2023-01-27 23:57 dydxdx File Added: 2023-01-27_154443.jpg
2023-01-28 06:06 mak_kawa Note Added: 0004472
2023-01-28 09:05 WilfriedB Note Added: 0004474
2023-01-28 09:17 mak_kawa Note Added: 0004475
2023-01-28 14:22 heiko Note Added: 0004481
2023-01-28 14:28 xyzzy Note Added: 0004482
2023-01-28 14:49 dydxdx File Added: 2023-01-28_064027.jpg
2023-01-28 14:49 dydxdx File Added: 2023-01-28_064834.jpg
2023-01-28 14:49 dydxdx Note Added: 0004483
2023-01-28 19:21 dydxdx Note Added: 0004484
2023-01-29 13:04 WilfriedB Note Added: 0004485
2023-01-29 14:40 dydxdx Note Added: 0004486
2023-01-29 16:41 dydxdx Note Added: 0004487
2023-02-02 22:06 dydxdx Note Added: 0004512
2023-02-03 00:29 dydxdx File Added: 2023-02-02_162518.jpg
2023-02-03 00:29 dydxdx Note Added: 0004515
2023-02-23 12:31 andregallegos Note Added: 0004635
2023-02-23 18:17 Friedemann Assigned To => Friedemann
2023-02-23 18:17 Friedemann Status new => assigned
2023-02-23 18:17 Friedemann Status assigned => resolved
2023-02-23 18:17 Friedemann Resolution open => fixed