Hi John, From the top of my head, indexes on long are less efficient than on text values ; I have a doubt, perhaps only for updating. You could test adding two fields with longitude and latitude converted in text values with appropriate leading zéros for search ?
Cordialement, Bernard Escaich > Le 13 avr. 2020 à 15:54, John J Foster via 4D_Tech <[email protected]> a > écrit : > > Hey Bernard, > > Ah yes the Math4D component. I had forgotten about that! I’ll take a look. > > If I add a field and split the longitude into degrees I’d likely use a long. > I think that would give me the most flexible approach. > > Then searching for specific values like 115 or -47 would be easy. > > Creating a compound search with longitude degree and Country and I’m able to > find the Olson timecode. > > And I think it might make the distance searching easier. > > Appreciate your help, > John… > > > >> You have geodesic functions in Math4D, component available here : >> https://forums.4d.com/Post/EN/31847250/1/31847251#31847251 > >> Cluster is meant when there are many duplicates. To do queries I would make >> a duplicate field and use a string conversion or a long code version. and >> not a real. Reals in my opinion are the slowest when it comes to queries. Or >> manipulation > > ********************************************************************** > 4D Internet Users Group (4D iNUG) > Archive: http://lists.4d.com/archives.html > Options: https://lists.4d.com/mailman/options/4d_tech > Unsub: mailto:[email protected] > ********************************************************************** ********************************************************************** 4D Internet Users Group (4D iNUG) Archive: http://lists.4d.com/archives.html Options: https://lists.4d.com/mailman/options/4d_tech Unsub: mailto:[email protected] **********************************************************************
