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

"geos" projection documentation - contradiction in the sweep angle axis explanation #1179

Closed
magau opened this issue Nov 16, 2018 · 5 comments
Labels
Documentation Issues relating to documentation

Comments

@magau
Copy link
Contributor

magau commented Nov 16, 2018

While reading the "geos" projection documentation I've found, what is in my opinion, a contradiction in the sweep angle axis explanation.

https://github.com/OSGeo/proj.4/blob/master/docs/source/operations/projections/geos.rst

Actually what seems to be wrong isn't the sweep angle axis explanation it self but the GOES/Meteosat respective values x or y.

Consider the following citations:

"In the image above, the outer-gimbal axis, or sweep-angle axis, is the N/S axis (y) (...). This example represents the scanning geometry of the Meteosat series satellite. However, the GOES satellite series use the opposite scanning geometry, with the E/W axis (x) as the sweep-angle axis, ..."

"Thus, the scanning geometry of the Meteosat series satellite should take sweep as x, and GOES should take sweep as y."

My usage experience tells me that the last sentence is wrong (i.e. "+sweep=y" should be for the Meteosat while "sweep=x" for GOES).

Thanks in advance. Please clarify me if I'm wrong... :)

@rouault
Copy link
Member

rouault commented Nov 19, 2018

Yes, you're right: the MSG and MSGN drivers in GDAL for Meteosat use the default value for +sweep, that is y. I'm going to correct the last sentence "Thus, the scanning geometry..."

rouault added a commit that referenced this issue Nov 19, 2018
…the sweep parameter depending on the satellite (fixes #1179)
@rouault rouault added Documentation Issues relating to documentation and removed help wanted labels Nov 19, 2018
@magau
Copy link
Contributor Author

magau commented Nov 19, 2018

Thanks Even!
By the way, in the "Language bindings" section I've noticed that there are no official bindings for Fortran.
I've being recently working on updating an old git repository:
https://gitlab.com/joao.macedo/proj4-fortran
It would be nice if it could be integrated in future releases.
Can you advice me what's the right procedure?

@kbevers
Copy link
Member

kbevers commented Nov 19, 2018

@magau What do you mean by "integrating"? That PROJ should come with the fortran bindings as a default? Or do you simply just want to link to the fortran bindings on the website (as we do with most bindings for other languages)?

@magau
Copy link
Contributor Author

magau commented Nov 20, 2018

@kbevers, whatever you would find useful. For me a link on the website wold be great!
Actually the original code wasn't written by me, its from Magnus Hagdorn ([email protected]), that I'd need to consult.
He did a very nice job, but it hasn't being updated since 2013... I've just refactor it and create a new release v1.1.0 in a forked repository.
Thanks for the opportunity of contribute for such a nice Proj-ect!

@kbevers
Copy link
Member

kbevers commented Nov 20, 2018

whatever you would find useful. For me a link on the website wold be great!

That is what I prefer. You are welcome to submit a PR adding it to https://github.com/OSGeo/proj.4/blob/master/docs/source/development/bindings.rst

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

No branches or pull requests

3 participants