Open jamesdoyle21 opened 2 years ago
http://tds.eds.ioos.us/ncWMS2/wms?SERVICE=WMS&REQUEST=GetCapabilities&VERSION=1.3.0
Source data will have to be updated. Getcap is also returning global extents.
<westBoundLongitude>-180.0</westBoundLongitude>
<eastBoundLongitude>180.0</eastBoundLongitude>
<southBoundLatitude>-90.0</southBoundLatitude>
<northBoundLatitude>90.0</northBoundLatitude>
Also noticed issues with the East Pacific GFS Wave boundaries
Hey @patrick-tripp can you take a look at this issue and give us your thoughts? Maybe Ben, or someone from the backend can tackle this. We have several features in OM3 that use this bounding box, so it is important we have those correct. Thanks
I updated the THREDDS metadata for all of the gfswave collections. Hopefully they will provide the correct extents after tonight's restart. Let me know if it works or not. Thanks.
Hey I am still seeing the big bounding box here
@jamesdoyle21 I'm rebuilding the catalog atm, the updated bbox will show after that's done.
The rebuilt catalog is up on dev, but the bbox is still big.
https://eds.ioos.us/wms/?SERVICE=WMS&REQUEST=GetCapabilities&VERSION=1.1.1&DATASET=GFS_WAVE_ARCTIC Checking getCap, the boundary doesn't look like it's been updated.
<LatLonBoundingBox minx="-180.0" maxx="180.0" miny="-90.0" maxy="90.0"/>
<BoundingBox SRS="CRS:84" minx="-180.0" maxx="180.0" miny="-90.0" maxy="90.0"/>
and ncWMS last updated time for Arctic is Last update date: 2021-12-13
@patrick-tripp
@patrick-tripp did you have someone in mind who could take a look at this?
The East pacific one is correct actually, you can see how it wraps. This is fine for me, theres not really a better way to handle this cuz it wraps the date line
The boundaries cover the global scale but the layer ends at about the US/ Canada border. We found this when testing the new real time map view feature. This includes the Arctic Wave Height, Wave Period, and Wave Direction layers.