About coordinates search

[abr01]

After having re-indexed Everything, including latitude and longitude now, i'm not sure about the correct syntax, even though i believe i have replicated the code format from your search functions page, in the format

latitude 53°31'2.388"N;longitude 10°3'7.02"E

However, no search is initiated. I have tried slight variations of this, but get still no search process. So, how would be the proper syntax look like?

[NotNull]

latitude 53°31'2.388"N;longitude 10°3'7.02"E

Whhat happens with the semicolon removed? (those are 2 separate search functions):

Code: Select all

latitude 53°31'2.388"N   longitude 10°3'7.02"E

[abr01]

Yes, i tried that already. I don't see any progress bar building up (waited a couple of minutes, since this kind oft search can be slow). I have also added the drive to the search, to see, if it might speed up the process. Maybe the format isn't right yet?

[NotNull]

It looks like the syntax used in the latitude: and longitude: example to me.

Results should be instant (take way less than one second) as you already indexed these properties:

After having re-indexed Everything, including latitude and longitude now

[abr01]

Well, that's strange. I took the values directly from one of my photos, and also tried to shorten them at the lower decimals, but i didn't get any results.
Also tried the decimal values, latitude:53.51733N longitude:10.05195E, nothing. Here's how my setting looks, same for longitude. I had the indexing running through properly. Correct file types are included.

[abr01]

Found something: with this type of format

latitude:<53.1497N> longitude:<09.3462E>

i started to get plausible results. So the coordinate values have to be in angled brackets, in decimal format, and with four digits after the decimal point.

Edit: since i get the coordinates with more than four digits from Directory Opus, i would suggest that Everything would ignore the excess digits in its search. At the moment, searching wouldn't start with those extra digits. This would spare the users to shorten the values by hand, unless in some cases the extra digits would be accepted (which i can't rule out yet. I had only a couple of tests).

[void]

Everything 1.5.0.1371a fixes an issue with searching for GPS coordinates.

GPS coordinate search syntax:

latitude:53 longitude:09
latitude:53.1 longitude:09.3
latitude:53.1S longitude:09.3W
latitude:-53.1 longitude:-9.3
latitude:53.14 longitude:09.34
latitude:53.149 longitude:09.346
latitude:53.1497 longitude:09.3462

latitude:53°08 longitude:9°20
latitude:53°08S longitude:9°20W
latitude:53°08'58 longitude:9°20'46
latitude:53°08'58.92 longitude:9°20'46.32
latitude:53°08'58.92''N longitude:9°20'46.32''E

latitude:53d08'58 longitude:9d20'46
latitude:53d08'58.92 longitude:9d20'46.32
latitude:53d08'58.92''N longitude:9d20'46.32''E

latitude:53:08:58 longitude:9:20:46
latitude:53:08:58.92 longitude:9:20:46.32
latitude:53:08:58.92N longitude:9:20:46.32E

[Phlashman]

When searching by coordinates is Everything searching by numeric characters or numerically to the number of decimal places?

In the example formats you gave

latitude:53.14 longitude:09.34
latitude:53.149 longitude:09.346
latitude:53.1497 longitude:09.3462

rounding numerically of 53.1497 to say 2 decimals is 53.15, will using this 2 decimal place value in search find coordinate where to 4 decimals it's 53.1497?

[void]

As a number range to the number of decimal places specified.

Values are floored.



Searching for:

53.1

is the same as:

>=53.1
< 53.2

A search for 53.1 will match 53.1497



Searching for:

53.14

is the same as:

>=53.14
< 53.15

A search for 53.14 will match 53.1497



Searching for:

53.149

is the same as:

>=53.149
< 53.150

A search for 53.149 will match 53.1497



A search of 53.15 will not match 53.1497
Use 53.1 or 53.14

[abr01]

Thanks void. Looking forward to test the new format. I'm also hoping, that some script guru will provide some script for Directory Opus, that will automatically generate collections of locations, based on the coordinates, that would be fed into Everything, and afterwords back to Opus, to generate a collection for that location. Something along those lines. At the moment, i will have to do it manually, but it's great already.