Latitude, longitude vs. system number format.

[NotNull]

(discovered together with @tuska)

On systems where the comma (",") is used as the decimal separator, Everything will use comma as a separator in GPS coordinates too, instead of the dot (".").

Now a search has to be done as

Code: Select all

latitude:48,13..48,23  longitude:16,17..16,52

instead of

Code: Select all

latitude:48.13..48.23  longitude:16.17..16.52

I'm assuming this is a bug?

[void]

Thank you for the bug report NotNull and tuska,

Everything doesn't use localization when parsing numbers.

. is always the decimal point.

There's something else going on here.

Could you please send the debug output when performing this search:

Cut your search to the clipboard.
Make sure the search is empty.
In Everything, from the Tools menu, under the Debug submenu, click Start Debug Logging...
Paste your search back into the search box.
In Everything, from the Tools menu, under the Debug submenu, click Stop Debug Logging...
---This will open your Everything Debug Log.txt in Notepad.
Could you please reply with the contents of this file.

[tuska]

The search query in Everything that returns NO results for the language ‘German’ is:

Code: Select all

latitude:48.814888549776946..48.89666125059261  longitude:2.1845652972982514..2.444117299251376

(The search query was performed using a script).

Code: Select all

latitude:48.814888549776946..48.89666125059261  longitude:2.1845652972982514..2.444117299251376	  | No result (point -> longitude)
latitude:48,814888549776946..48,89666125059261  longitude:2,1845652972982514..2,444117299251376	  | works!    (comma)

latitude:48.814888549776946..48.89666125059261  	works!  	(point)
latitude:48,814888549776946..48,89666125059261  	works!  	(comma)

d: longitude:2.1845652972982514..2.444117299251376 	NO result 	(point)
   longitude:2.1845652972982514..2.444117299251376	NO result	(point)
d: longitude:2,1845652972982514..2,444117299251376	works!		(comma)

My conclusions:
- Specifying longitudes with a dot in the search query does NOT work.
- Latitude and longitude are always displayed with a comma in the search results when the language is set to ‘German’ in Windows.
 

2025-11-07_GPS - Geotagging - Latitude, longitude vs. system number format.png (133.83 KiB) Viewed 4592 times

 
Maybe that helps?
_________________
Btw, is there a way to align column values by comma or decimal point in Everything?
 

2025-11-07_Align column values at the comma or decimal point.png (3.09 KiB) Viewed 4571 times

[NotNull]

Seaqrch =

pic: latitude:47.9241613715029..48.355789303918705 longitude:15.884170532226564..16.798782348632816

Debug log:

Code: Select all

2025-11-07 22:29:23.363: search 'pic:  latitude:47.9241613715029..48.355789303918705  longitude:15.884170532226564..16.798782348632816' filter '' sort 5 ascending 0
2025-11-07 22:29:23.364: expanded: image:  latitude:47.9241613715029..48.355789303918705  longitude:15.884170532226564..16.798782348632816
2025-11-07 22:29:23.364: expanded: nofiltercase:nofilterpath:nofilterwholeword:nofilterdiacritics:nofilterprefix:nofiltersuffix:nofilterignorepunctuation:nofilterignorewhitespace:nofilterregex:< ext:ani;apng;avif;avifs;bmp;bpg;cur;dds;gif;heic;heics;heif;heifs;hif;ico;jfi;jfif;jif;jpe;jpeg;jpg;jxl;jxr;pcx;png;psb;psd;svg;tga;tif;tiff;wdp;webp;wmf >   latitude:47.9241613715029..48.355789303918705  longitude:15.884170532226564..16.798782348632816
2025-11-07 22:29:23.364: expr 47.924161
2025-11-07 22:29:23.364: expr 47.924161
2025-11-07 22:29:23.364: expr 48.355788
2025-11-07 22:29:23.364:         RANGE 47924162 48005302
2025-11-07 22:29:23.364: expr 15.884170
2025-11-07 22:29:23.364: expr 15.884170
2025-11-07 22:29:23.364: expr 16.798782
2025-11-07 22:29:23.364:         RANGE 15017174 16005573
2025-11-07 22:29:23.364: FOLDER TERM START 000000000038d790 M 000000000038d8c0 N 000000000038d790
2025-11-07 22:29:23.364: FILE TERM START 0000000002e8f2b8 M 000000000038d8c0 N 000000000038d790
2025-11-07 22:29:23.364: 0000000002e8f2b8 20e01100 M 0000000006634348 N 000000000038d790 OP 197 ani;apng;avif;avifs;bmp;bpg;cur;dds;gif;heic;heics;heif;heifs;hif;ico;jfi;jfif;jif;jpe;jpeg;jpg;jxl;jxr;pcx;png;psb;psd;svg;tga;tif;tiff;wdp;webp;wmf
2025-11-07 22:29:23.364: 0000000006634348 20e01100 M 00000000066348c8 N 000000000038d790 OP 357 47.9241613715029..48.355789303918705
2025-11-07 22:29:23.364: 00000000066348c8 20e01100 M 000000000038d8c0 N 000000000038d790 OP 357 15.884170532226564..16.798782348632816

However...
With 6 decimals accuracy (up to 11 digits seems OK)
Search =

pic: latitude:47.924161..48.355789 longitude:15.884170..16.798782

Debug log =

Code: Select all

2025-11-07 22:33:09.211: search 'pic:  latitude:47.924161..48.355789  longitude:15.884170..16.798782' filter '' sort 5 ascending 0
2025-11-07 22:33:09.211: expanded: image:  latitude:47.924161..48.355789  longitude:15.884170..16.798782
2025-11-07 22:33:09.211: expanded: nofiltercase:nofilterpath:nofilterwholeword:nofilterdiacritics:nofilterprefix:nofiltersuffix:nofilterignorepunctuation:nofilterignorewhitespace:nofilterregex:< ext:ani;apng;avif;avifs;bmp;bpg;cur;dds;gif;heic;heics;heif;heifs;hif;ico;jfi;jfif;jif;jpe;jpeg;jpg;jxl;jxr;pcx;png;psb;psd;svg;tga;tif;tiff;wdp;webp;wmf >   latitude:47.924161..48.355789  longitude:15.884170..16.798782
2025-11-07 22:33:09.211: expr 47.924161
2025-11-07 22:33:09.211: expr 47.924161
2025-11-07 22:33:09.211: expr 48.355788
2025-11-07 22:33:09.211:         RANGE 47924161 48355789
2025-11-07 22:33:09.211: expr 15.884170
2025-11-07 22:33:09.211: expr 15.884170
2025-11-07 22:33:09.211: expr 16.798782
2025-11-07 22:33:09.211:         RANGE 15884170 16798782
2025-11-07 22:33:09.211: FOLDER TERM START 000000000038cbf0 M 000000000038cd20 N 000000000038cbf0
2025-11-07 22:33:09.211: FILE TERM START 0000000002e8e268 M 000000000038cd20 N 000000000038cbf0
2025-11-07 22:33:09.211: 0000000002e8e268 20e01100 M 00000000065d2658 N 000000000038cbf0 OP 197 ani;apng;avif;avifs;bmp;bpg;cur;dds;gif;heic;heics;heif;heifs;hif;ico;jfi;jfif;jif;jpe;jpeg;jpg;jxl;jxr;pcx;png;psb;psd;svg;tga;tif;tiff;wdp;webp;wmf
2025-11-07 22:33:09.211: 00000000065d2658 20e01100 M 00000000065d1e78 N 000000000038cbf0 OP 357 47.924161..48.355789
2025-11-07 22:33:09.211: 00000000065d1e78 20e01100 M 000000000038cd20 N 000000000038cbf0 OP 357 15.884170..16.798782

EDIT:

This one also gives the expected results:

pic: latitude:47.942563318831574..48.3379913533744 longitude:15.884170532226564..16.7987823486328

[void]

Thanks for the logs.

14 or more decimal places overflows the value.

I will cap the number of decimal places to 12 in the next alpha update.



The , in

latitude:48,13..48,23

is not a valid input character, so Everything stops parsing at the ,

latitude:48,13..48,23

is seen as:

latitude:48

I have put on my TODO list to show parse errors temporarily in the status bar.

eg: Unexpected character , in latitude:48,

[tuska]

The , in

latitude:48,13..48,23

is not a valid input character, so Everything stops parsing at the ,

latitude:48,13..48,23

is seen as:

latitude:48

I have put on my TODO list to show parse errors temporarily in the status bar.

eg: Unexpected character , in latitude:48,

Hmm, seems to be working for me.
Please also see the examples above with commas.
 

2025-11-08_Latitude_Longitude_2 Decimal places.png (36.73 KiB) Viewed 4549 times

[void]

latitude:48,81..48,89 longitude:2,18..2,44

Is seen as:

latitude:48 longitude:2

This will match your file.
Everything matches with the precision specified.
For example:

latitude:48 will match a file where the latitude is >=48 and <49
latitude:48.0 will match a file where the latitude is >=48.0 and <48.1
latitude:48.00 will match a file where the latitude is >=48.00 and <48.01

[tuska]

2void

Thank you for the detailed explanations!
That clarifies everything for me.

Therefore, in future, I will only use the decimal point ‘.’ and
a maximum of 12 decimal places for searches on this topic.

[tuska]

2void

I feel like I'm back at the beginning.

D:\Bilder\GPS ext:jpg latitude:48.016592..longitude:15.189574   NO search result
D:\Bilder\GPS ext:jpg latitude:48,016592..longitude:15,189574   Search results!

[void]

What's the latitude and longitude of the file you want to match?

Put a space before longitude, currently it is ignored.
.. should be used to specify a range.

latitude:48,016592..longitude:15,189574

text underlined is ignored.

[tuska]

To be searched:

Code: Select all

latitude:48.203705 longitude:16.370231	<-- Everything
latitude:48.203706 longitude:16.370231	... IrfanView

is NOT found with:
D:\Bilder\GPS ext:jpg latitude:48.016592..latitude:48.301789 longitude:15.907890..longitude:16.489574
D:\Bilder\GPS ext:jpg latitude:48..latitude:49 longitude:15..longitude:17
D:\Bilder\GPS ext:jpg latitude:48,..latitude:48, longitude:15,..longitude:16,
D:\Bilder\GPS ext:jpg latitude:48,016592..latitude:48,301789 longitude:15,907890..longitude:16,489574
D:\Bilder\GPS ext:jpg latitude:48,..latitude:48, longitude:15,..longitude:16,

is found with:
D:\Bilder\GPS ext:jpg latitude:48.203705
D:\Bilder\GPS ext:jpg latitude:48,203705
D:\Bilder\GPS ext:jpg longitude:16,370231
D:\Bilder\GPS ext:jpg longitude:16.370231

[void]

D:\Bilder\GPS ext:jpg latitude:48.016592..latitude:48.301789 longitude:15.907890..longitude:16.489574
D:\Bilder\GPS ext:jpg latitude:48..latitude:49 longitude:15..longitude:17
D:\Bilder\GPS ext:jpg latitude:48,..latitude:48, longitude:15,..longitude:16,
D:\Bilder\GPS ext:jpg latitude:48,016592..latitude:48,301789 longitude:15,907890..longitude:16,489574
D:\Bilder\GPS ext:jpg latitude:48,..latitude:48, longitude:15,..longitude:16,

Don't specify latitude: twice, use

latitude:x..y

where x and y is your latitude range.
Same for longitude.
, is not a valid input character.

Please try:

Code: Select all

D:\Bilder\GPS ext:jpg latitude:48.016592..48.301789 longitude:15.907890..16.489574
D:\Bilder\GPS ext:jpg latitude:48..49 longitude:15..17

[tuska]

Please try:

Code: Select all

D:\Bilder\GPS ext:jpg latitude:48.016592..48.301789 longitude:15.907890..16.489574
D:\Bilder\GPS ext:jpg latitude:48..49 longitude:15..17

That works.
Thanks a lot!

[void]

Everything 1.5.0.1401a fixes an issue with parsing numbers with a decimal place.

[tuska]

2void
Thank you for your efforts!

I had search queries above that did not work with a '.' dot -> "NO result (point)".
I now received the expected results for these search queries.

...
14 or more decimal places overflows the value.
I will cap the number of decimal places to 12 in the next alpha update.

The , in

latitude:48,13..48,23

is not a valid input character, so Everything stops parsing at the ,

latitude:48,13..48,23

is seen as:

latitude:48

I have put on my TODO list to show parse errors temporarily in the status bar.
eg: Unexpected character , in latitude:48,

Number of decimal places: 12
Entering more than 12 decimal places is still permitted, e.g.

latitude:48.814888549776946..48.89666125059261 longitude:2.1845652972982514..2.444117299251376

Does this mean that internally the number will be reduced/rounded down/rounded up to 12 decimal places?

Show parse errors temporarily in the status bar
When I make this query, incorrectly using a ',' comma, instead of a '.' dot

latitude:48,814888549776946..48,89666125059261 longitude:2,1845652972982514..2,444117299251376

- OR - ...

latitude:48,

shouldn't I then receive a message (Unexpected character...) in the status bar?

Currently, for example, the following is displayed in the status bar: 5 items (5 files, folders)
and there is no indication of an "unexpected character". Is this topic still on your TODO list?

[void]

More than ~19 digits are truncated (ignored)

48.814888549776946123 => 48.81488854977694612

The trailing 20th digit: 3 is ignored.



Then there's also double precision.
Some precision will be lost.

48.81488854977694612 => ~48.814888549776946



Showing parse errors is on my TODO list.

[tuska]

2void
Thank you for the info!

[NotNull]

This fixes an issue I was having. Thanks!


Note: the latitude/ longitude columns show a 6 decimals resolution. Same for the output of ES.exe.
The Windows property property-system:System.GPS.LatitudeDecimal and the matching longitude property do show the full resolution.

Is there a way to show and use the full resolution for the Everything property too?


(6 decimals means an error accuracy of 3 to 12 meter, so not a real problem, I guess)

[void]

Everything doesn't use full precision for latitude and longitude.

Internally, latitude and longitude are converted to fixed point with 6 decimal places.
This makes searching fast, and is accurate to ~1 meter, more than enough for Everything.

addcol:System.GPS.Latitude;System.GPS.Longitude

give the full precision.

[NotNull]

accurate to ~1 meter

See Level of Resolution of Longitude and Latitude Measurements

EDIT: My bad! CM instead of meters ...