07-22-2024 04:11 PM - last edited on 07-22-2024 04:39 PM by StevenMOD
I have an EOS R6 Mark 11 connected to my iPhone 13 for GPS. The camera GPS is always off by several miles. Obviously, my iPhone can locate me within a few feet. Why the huge discrepancy?
Thanks.
Solved! Go to Solution.
07-30-2024 05:14 PM
Just in case you are still out there...
Most GPS is formatted as either deg, min, sec.sec, or Deg.deg. That is with fractional degrees or fractional seconds.
Yours is formatted with fractional *minutes*, which is a bit odd.
With the help of my Prime, I figured out how to convert it.
So, somehow, AA°BB'22.1"N is equivalent to 0AA,BB.3670000N.
To convert it, take the fractional part of the minutes and multiply by 60 to turn it into seconds:
.367 * 60 = 22.02, which is pretty close to 22.1 seconds.
It also works for the other:
.7700999 * 60 = 46.206, again, pretty close to 46.1.
07-25-2024 05:25 PM
kvbarkley: how do I label and separate the data? Commas, descriptors, or what?
07-25-2024 06:41 PM
Where I took this photo:
07-27-2024 12:05 PM
Hey,
Thanks so much. I can do it but not correctly with my data.
The GPS data from my Canon seems to be in DMS format. Correct?
This is the actual GPS of my address I pulled off of Google:
Actual GPS: AA°BB'22.1"N DD°EE'46.1"W
Here's the GPS location data from my Canon from a pic shot from home:
It appears in the metadata as 0AA,BB.3670000N and 0DD,EE.7700999W
So my home address and the GPS from my Canon match (with a lead zero) except for the seconds. I can't configure the Canon GPS data in Google for the seconds in a way that doesn't produce an error. How do I do configure the seconds? (Where does the decimal go?) And longitude is a long number.
Thanks again.
07-30-2024 05:14 PM
Just in case you are still out there...
Most GPS is formatted as either deg, min, sec.sec, or Deg.deg. That is with fractional degrees or fractional seconds.
Yours is formatted with fractional *minutes*, which is a bit odd.
With the help of my Prime, I figured out how to convert it.
So, somehow, AA°BB'22.1"N is equivalent to 0AA,BB.3670000N.
To convert it, take the fractional part of the minutes and multiply by 60 to turn it into seconds:
.367 * 60 = 22.02, which is pretty close to 22.1 seconds.
It also works for the other:
.7700999 * 60 = 46.206, again, pretty close to 46.1.
07-31-2024 10:14 AM
Wow. You are my hero. I'm out of town but when I get home, I'll test it out. Thanks SOOO much....
08-04-2024 04:42 PM
This works really well. When I put in the seconds as they calculated in the gps-coordinates.org website, I got my home address exactly but the seconds changed to something else:
Lat: 22.02 became 22.0194
Lon: 46.206 became 46.05
… and my address pops up. Why is that?
Thanks again!
08-05-2024 09:07 AM
Either some weird round off, or they only return certain GPS coordinates, say every 100 feet or so.
08-05-2024 09:43 AM
Excellent thread guys!
~Rick
Bay Area - CA
~R5 C (1.0.7.1) ~RF Trinity, ~RF 100 Macro, ~RF 100~400, ~RF 100~500, ~RF 200-800 +RF 1.4x TC, BG-R10, 430EX III-RT ~DxO PhotoLab Elite ~DaVinci Resolve ~ImageClass MF644Cdw/MF656Cdw ~Pixel 8 ~CarePaks Are Worth It
09/26/2024: New firmware updates are available.
EOS R5 Mark II - Version 1.0.1
EOS R6 Mark II - Version 1.5.0
07/01/2024: New firmware updates are available.
04/16/2024: New firmware updates are available.
RF100-300mm F2.8 L IS USM - Version 1.0.6
RF400mm F2.8 L IS USM - Version 1.0.6
RF600mm F4 L IS USM - Version 1.0.6
RF800mm F5.6 L IS USM - Version 1.0.4
RF1200mm F8 L IS USM - Version 1.0.4
Canon U.S.A Inc. All Rights Reserved. Reproduction in whole or part without permission is prohibited.