Closed tlvu closed 3 years ago
At a quick glance, I find it weird that the returned polygon collection has different attributes with only a server upgrade, this seems quite an easy fix anyway.
This is exactly the type of error I was expecting post-upgrade. It appears that one version of the quebec_mrc_boundaries had a BBOX
field, and we dropped that particular version in the upgrade. By chance, If anything, this might result in cleaner code. I wonder if this field was automatically generated by the previous GeoServer, given that the files are the same...
I am guessing the field was automatically generated! In the WFS calls, we have propertyname=['the_geom', 'MRS_NM_MRC']
, so it was kinda strange that an additional "bbox" field was also provided.
@aulemahal I'll test both PR on Jenkins once power is back tomorrow and will merge. Thanks for the fix !
Description
Since our notebooks are unable to test Geoserver from a dev machine (issue https://github.com/Ouranosinc/pavics-sdi/issues/183), this error is caught only after a go-live on prod of PR https://github.com/bird-house/birdhouse-deploy/pull/136.
Steps to Reproduce
Jenkins build error: http://jenkins.ouranos.ca/job/PAVICS-e2e-workflow-tests/job/master/1276/console
KeyError: "['bbox'] not found in axis"
regridding.ipynb:
subset.ipynb:
Additional Information
Similar Raven issue https://github.com/Ouranosinc/raven/issues/410