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

Join user and package area files #62

Closed
djhoese opened this issue Jun 27, 2017 · 1 comment
Closed

Join user and package area files #62

djhoese opened this issue Jun 27, 2017 · 1 comment
Assignees

Comments

@djhoese
Copy link
Member

djhoese commented Jun 27, 2017

Currently the parse_area_file function only allows one single file. This causes limitations in software like satpy where we may want to have a "user" area file and a "package" area file. The easiest/cleanest way to handle this is to make a pyresample allow more than one file. This is even more useful for the new yaml files which could allow users area files to "update" existing information in the "package" area file.

I propose that there be a new function (for backwards compatibility) that accepts one of the following input formats for the areas files:

  1. single area file name
  2. single file-like object
  3. single file content string
  4. iterable of area file name or file-like object
@djhoese
Copy link
Member Author

djhoese commented Sep 9, 2017

Fixed by #63

@djhoese djhoese closed this as completed Sep 9, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant