Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Getting utm coordinates instead of latitude and longitude #207

Open
yanivbm88 opened this issue Jan 25, 2021 · 1 comment
Open

Getting utm coordinates instead of latitude and longitude #207

yanivbm88 opened this issue Jan 25, 2021 · 1 comment

Comments

@yanivbm88
Copy link

Hi,

Documentation states that parser should return location by latitude and longitude coordinates.
However, the output I'm getting is in utm coordinates (x,y).
What could cause that behavior?
Does that depend on my input file structure? If it is, below I provided a sample signal, and will be happy to know which part causes this configuration and what should I put there instead.

Thank you

\g:1-2-1489,c:1609779346,s:rORBCOMM000m*30\!AIVDM,2,1,0,A,55@H`20284no<DQ?P008U8<P00000000000000168H=744Ae`;j0BAP@0000,0*74
\g:2-2-1489*59\!AIVDM,2,2,0,A,00000000000,2*24
@LordKobra
Copy link

From my experience x = Longitude and y = Latitude. Check out, how the decoded data looks. UTM should be an integer like 12345, Longitude in float representation like 12,3456.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants