Closed fvanderbiest closed 7 years ago
We had a problem with the projection of the first set of GEM rasters delivered. This error looks to be the same issue. The errors were corrected in new layers; the layers on old geonode were replaced with ones that we then successfully processed in TH v1.
The transfer of data from old to new geonode may have been done before the problematic files were replaced. Please copy the latest set of data from old geonode to new geonode, and try this again - the problem should be fixed
I'll try that, thanks !
I've added, in complete task, a test on rasters. If bounds.bottom > bounds.top, hazardset is considered incomplete and this displayed in admin interface.
@arnaud-morvan @fvanderbiest is this fixed now? the above layers seem to show as imported to TH at http://int.thinkhazard.org/admin/hazardsets
On our dev server,
make process
yields