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
I kept get an error that my bbox was out of of coverage extent even though the polygon I am trying to sample is well within the bounds of the data (checked with map viewer, data is available for the location).
here is my query code:
#layers[i] is "emodnet__vesseldensity_all" however the problem is recurrent for all human_activities layers
Error in check_cov_contains_bbox():
! bbox boundaries "xmin" and "xmax" lie outside coverage extent. No overlapping data to download.
Run rlang::last_error() to see where the error occurred.
bbox.E is on the same projection as the data (EPSG:3857) (I also tried querying on the WGS84 extent)
I kept get an error that my bbox was out of of coverage extent even though the polygon I am trying to sample is well within the bounds of the data (checked with map viewer, data is available for the location).
here is my query code:
#layers[i] is "emodnet__vesseldensity_all" however the problem is recurrent for all human_activities layers
assign(paste(layers[i]), emdn_get_coverage(Ewcs, coverage_id = layers[i], bbox = bbox.E))
Error in
check_cov_contains_bbox()
:!
bbox
boundaries "xmin" and "xmax" lie outside coverage extent. No overlapping data to download.Run
rlang::last_error()
to see where the error occurred.bbox.E is on the same projection as the data (EPSG:3857) (I also tried querying on the WGS84 extent)
if I go to the database summary directly (https://ows.emodnet-humanactivities.eu/wcs?service=WCS&request=GetCapabilities&version=2.0) I find that the BBox for that coverage is:
ows:LowerCorner-9763441.130289372 1684718.7349552144</ows:LowerCorner>
ows:UpperCorner1.086845880678606E7 2.28223599215428E7</ows:UpperCorner>
yet if I query what the bbox is via EMODnetWCS, I get:
emdn_get_bbox(emdn_get_coverage_summaries(Ewcs,"emodnet__vesseldensity_all")[[1]])
xmin ymin xmax ymax
1684719 -9763441 22822360 10868459
it looks like the axes have been swapped around (ymin is xmin and ymax is xmax)?
The text was updated successfully, but these errors were encountered: