Hi Ryan,
I'll ask our admin to upgrade or spin up a vm. In the meantime, here's a simple
script to generate a file with similar issues (WMS page appears, but no layers).
# get some blue marble data (small):
wget
http://earthobservatory.nasa.gov/Features/BlueMarble/Images/land_shallow_topo_2048.tif
# add a projection
gdal_translate -a_srs '+proj=longlat' -a_ullr -180 90 180 -90
land_shallow_topo_2048.tif map.tif
# remap the data to our location (actually, use 80.5 due to dateline artefacts)
# output CF netcdf
gdalwarp -r cubic -tr 4000 4000 -t_srs "+proj=geos +lon_0=80.5 +h=35785863
+a=6378137.0 +b=6356752.3" -te -5500000 -5500000 5500000 5500000 map.tif
geos.nc -of NETCDF -co "COMPRESS=DEFLATE"
Cheers,
Leon
From: Ryan May [mailto:rmay@xxxxxxxx]
Sent: Tuesday, 19 May 2015 1:56 AM
To: Leon Majewski
Cc: netcdf-java@xxxxxxxxxxxxxxxx
Subject: Re: [netcdf-java] Geostationary CF grid_mapping problem: "HTTP Status
500 - Internal Server Error" [SEC=UNCLASSIFIED]
Leon,
Version 4.6.1 of THREDDS was just released. Could you see if that fixes your
problem?
ftp://ftp.unidata.ucar.edu/pub/thredds/4.6/current/thredds.war
If not, it would be really helpful to get a sample of the problematic file so
we can try to reproduce locally.
Thanks,
Ryan
On Wed, May 13, 2015 at 12:06 AM, Leon Majewski
<Leon.Majewski@xxxxxxxxxx<mailto:Leon.Majewski@xxxxxxxxxx>> wrote:
Hi all,
> It's been suggested that I use the CF1.7 grid_mapping geostationary
I found that I need to set the grid_mapping_name to "geostationary_satellite"
float geostationary ;
geostationary:grid_mapping_name = "geostationary_satellite" ;
> HTTP Status 500
This fixes the HTTP Status 500. However, this results in their being no
queryable layers in the WMS and netcdf subset service fails [both worked with
vertical_perspective].
The WMS GetCapabilities for the vertical perspective version includes:
<Layer><Title>AGLS observations product suite</Title>
<Layer queryable="1"><Name>channel_0013_brightness_temperature</Name>
<Title>brightness temperature for channel 13 at 10.41 um</Title>
<Abstract>brightness temperature for channel 13 at 10.41 um</Abstract>
<EX_GeographicBoundingBox><westBoundLongitude>-180.0</westBoundLongitude><eastBoundLongitude>180.0</eastBoundLongitude><southBoundLatitude>-90.0</southBoundLatitude><northBoundLatitude>90.0</northBoundLatitude></EX_GeographicBoundingBox>
<BoundingBox CRS="CRS:84" minx="-180.0" maxx="180.0" miny="-90.0"
maxy="90.0"/>
<Dimension name="time" units="ISO8601" multipleValues="true"
current="true"
default="2015-02-20T00:00:20.000Z">2015-02-20T00:00:20.000Z</Dimension>
...
</Layer>
While the geostationary_satellite version has:
<Layer><Title>AGLS observations product suite</Title>
</Layer>
Has anyone see this behaviour/been able to work around it?
Thanks,
Leon
_______________________________________________
netcdf-java mailing list
netcdf-java@xxxxxxxxxxxxxxxx<mailto:netcdf-java@xxxxxxxxxxxxxxxx>
For list information or to unsubscribe, visit:
http://www.unidata.ucar.edu/mailing_lists/
--
Ryan May
Software Engineer
UCAR/Unidata
Boulder, CO
