You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
single area file name
single file-like object
single file content string
iterable of area file name or file-like object
The text was updated successfully, but these errors were encountered:
Currently the
parse_area_file
function only allows one single file. This causes limitations in software likesatpy
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:
The text was updated successfully, but these errors were encountered: