Deva_Rishi:
How many calculations are you going to do ? sure floating point calculation is slow compared to integer calculations, but these microprocessors are might quick (compared to the Z80 i started out with)
Who cares about speed?
We're talking about accuracy here.
AWOL:
Who cares about speed?
We're talking about accuracy here.
i thought speed would be fine as well but
MrMajd:
I'm working with Latitudes and Longitudes and since processing floats takes more time that processing integers and due to the fact that the lats always have the same first 2 digits and the same first decimal digits (similiary lons), I thought that I could get rid of those digits and work with the last 4 or 5 decimal digits as integers
the whole idea of the post to begin with was to increase the speed of the process by using integer computation.
See reply #6.
Besides, even if we're talking about a relatively high-end hobby 10Hz GPS, we're hardly likely to be stressing the processor.
I bet we're talking about 1Hz updates.
I agree but then what is the whole point of the calculation with the last 4 digits of a float to save time ??
No! Because the numbers never were a float!
They came from an NMEA sentence.
AWOL:
No! Because the numbers never were a float!
They came from an NMEA sentence.
In the GPS, they were floating point values. Lets not overlook that. But, they are communicated to the Arduino as strings. And the string CAN be collected and parsed (as TinyGPSPlus does) with the resulting token processed however is appropriate. It would be nice if TinyGPSPlus offered a method to return the lat and lon values as strings, so the user could process them however was appropriate.