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

area_extent unit scale #31

Open
anikfal opened this issue Oct 8, 2019 · 4 comments
Open

area_extent unit scale #31

anikfal opened this issue Oct 8, 2019 · 4 comments
Assignees
Labels

Comments

@anikfal
Copy link

anikfal commented Oct 8, 2019

Code:

from PIL import Image
from pycoast import ContourWriterAGG
img = Image.open('BMNG_clouds_201109181715_areaT2.png')
proj4_string = '+proj=stere +lon_0=8.00 +lat_0=50.00 +lat_ts=50.00 +ellps=WGS84'
area_extent = (-3363403.31,-2291879.85,2630596.69,2203620.1)
area_def = (proj4_string, area_extent)
...

Question:

What is the unit scale of the values of area_extent?

@djhoese djhoese self-assigned this Oct 8, 2019
@djhoese
Copy link
Member

djhoese commented Oct 8, 2019

The area extents are the coordinates for the outer edges of the outer pixels in the projected space. Typically these are meters. You can probably find more useful information on the pyresample documentation: https://pyresample.readthedocs.io/en/latest/geometry_utils.html

Let me know if this doesn't answer your question. We can use this issue as a sign that we need to update the documentation.

@anikfal
Copy link
Author

anikfal commented Oct 8, 2019

Thank you for your reply. Seems to be the exact documentation I needed.
However, I think it is necessary to add this information in the pycoast's documentation and user manual. I was frustrated in my attempts to find any bit of information about the unit scale.

@djhoese
Copy link
Member

djhoese commented Oct 8, 2019

However, I think it is necessary to add this information in the pycoast's documentation and user manual.

Agreed. It is a concept carried over from the pyresample package (and projections in general) and since people have often used both together (or through satpy) there was less work put in to pycoast's documentation. If you have any ideas of how this can be updated, feel free to make a pull request for the changes you think could help users in the future. Otherwise, this will have to wait until someone has the time.

@anikfal
Copy link
Author

anikfal commented Oct 8, 2019

feel free to make a pull request for the changes you think could help users in the future.

Sure. Thank you.

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

No branches or pull requests

2 participants