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

More conservative approach to handle errors in area_def_names_to_extent() #30

Merged
merged 1 commit into from Aug 29, 2016

Conversation

ch-k
Copy link
Contributor

@ch-k ch-k commented May 10, 2016

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 :

On further examination of the GEOS projection I find that PROJ (the library that QGIS uses to do reprojection) cannot handle long/lat data greater than +/- 81.3 degrees (approximately) from the projection center, either forward or reverse. Anything outside of this range will cause a projection failure, consequently the object may not be displayed, or there will be an error message detailing the failure.

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).

@mraspaud mraspaud merged commit e5baeb3 into pytroll:pre-master Aug 29, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants