More conservative approach to handle errors in area_def_names_to_extent() #30
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As discussed on slack-channel "trollduction" (2016/05/04):
Calculation of bounding box fails due to proj4 issues. A related issue can be found in https://hub.qgis.org/issues/4302 :
Without this patch, the function ignores invalid values. This results in wrong area extents and mpop/mipp does not read necessary satellite date from file.
With this patch, you can set the parameter "default_extent" to None. If so and invalid values occur during calculation of area_extent, "None" will be returned. In that case, scene.load will be called with no area_extent and (hopefully) loads all data (tested with Himawri 8 reader).