Thanks Ralph. To answer your questions: 1. I left the mobileStartTrackingSensor to the default second parameter, i.e. I didn’t put anything. The LC dictionary says that the default value is false which means
> readings are determined using accurate (but power consuming) sources such as > GPS of course I could put in “false” explicitly. But looking at the actual output data from the GPS functions, I think it’s evident that the GPS is actually being used. Nevertheless I will try including “false”. 2. Yes, I do require GPS as well as Location Services So, those bits seem OK. Still thinking about it, obviously. Graham > On 4 May 2020, at 16:22, Ralph DiMola via use-livecode > <use-livecode@lists.runrev.com> wrote: > > 1) Did you set the second parameter of mobileStartTrackingSensor to "false"? > 2) Did you require "GPS" as well as "Location Services" in the standalone > settings? If you don’t tick GPS then the GPS chip will not be used and you > will get rough location readings. > > Ralph DiMola > IT Director > Evergreen Information Services > rdim...@evergreeninfo.net > > -----Original Message----- > From: use-livecode [mailto:use-livecode-boun...@lists.runrev.com] On Behalf > Of Graham Samuel via use-livecode > Sent: Monday, May 04, 2020 8:07 AM > To: How to use LiveCode > Cc: Graham Samuel > Subject: Has anyone experience of GPS on iPhone? > > I’m using GPS on iPhone using the various commands and functions available in > LC. Most of this works, but I am having difficulty with the quantity > “horizontal accuracy”. This can be queried via an array which is returned > when mobileCurrentLocation() is executed. > > Looking at other iOS apps that use GPS and allow one to examine their data, I > find that in my part of the world, accuracy for them is of the order of 5 > metres: but when I query it using LC I get much higher numbers, indeed some > of them look like nonsense, being hundreds of metres! > > I am aware that it takes time for a GPS signal to settle down after > mobileStartTrackingSensor “location” has been called, but even if I script > the examination of accuracy to wait for it to settle down (I look for a run > of similar or identical readings against a ‘reasonable’ criterion, such as 5 > metres), it still sometimes settles on very large numbers comparatively > speaking, for example it might stabilise at 65 metres. With that level of > inaccuracy any cumulative use, as in working out the number of kilometres in > a trip, would not be reliable. > > I wonder if my expectation is wrong, or if there is something different about > LC’s encapsulation of these iOS outputs, or if there is some other > explanation. > > In the short term, I’m simply going to have to relax my search for a > reasonable accuracy of the order of 5 metres, and just go for the first run > of stable readings. But I would love to hear any further insight from anyone > who’s already tried it. > > Graham > _______________________________________________ > use-livecode mailing list > use-livecode@lists.runrev.com > Please visit this url to subscribe, unsubscribe and manage your subscription > preferences: > http://lists.runrev.com/mailman/listinfo/use-livecode > > > _______________________________________________ > use-livecode mailing list > use-livecode@lists.runrev.com > Please visit this url to subscribe, unsubscribe and manage your subscription > preferences: > http://lists.runrev.com/mailman/listinfo/use-livecode _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
