Announcement

Collapse
No announcement yet.

Problem serving Blue Marble imagery

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • Problem serving Blue Marble imagery

    This isn't specifically a WWJ server problem, but maybe someone here can help me figure out what is going wrong.

    I can't use the public WMS servers and need to serve all imagery and elevation data locally because the target platform for my WWJ app will not have Internet access. I've added two image pyramids to my geoserver/wms server. One is a mosaic of Landsat scenes and the other is constructed from the Blue Marble NG imagery. I added the map projection information to the BMNG images using gdal_translate. The images tile properly when displayed in OpenEV.

    Both pyramids were constructed using gdal_retile, then transferred to the server, and finally I created the new Image Pyramid stores using the GeoServer admin interface. Both image layers display properly when viewed with the GeoServer Layer Preview.

    The problem is that, while the Landsat mosaic loads properly in the WWJ WMS Viewer, the BMNG image does not. I started the viewer and added my server to the data source list. The layers list for the server shows all the layers that I have published there. When I click the checkbox for the Landsat mosaic it gets added to the main panel layer list and is displayed on the globe. All is well. However, nothing happens when I click the checkbox for the BMNG layer. The main panel layer list does not change to show the new layer and, obviously, the image does not show on the globe. (I have both of the default Blue Marble layers turned off.)

    The only clue I have as to what might be happening is in the tomcat log. When I add my wms server to the data source list this text is output to the log:

    Code:
    13 Mar 11:49:09 INFO [geoserver.wms] - 
    Request: getCapabilities
    	Namespace = null
    	UpdateSequence = null
    	Version = 1.3.0
    	Request = GetCapabilities
    	RawKvp = {EXCEPTIONS=application/vnd.ogc.se_xml, VERSION=1.3.0, SERVICE=WMS, REQUEST=GetCapabilities}
    	Get = false
    	BaseUrl = http://orlalabvm184:80/geoserver/
    	RequestCharset = null
    13 Mar 11:49:09 WARN [wms.capabilities] - Map output format text/html does not include mime type in output format names. Will be excluded from capabilities document.
    13 Mar 11:49:09 WARN [wms.capabilities] - Map output format application/xml does not include mime type in output format names. Will be excluded from capabilities document.
    Can anyone tell me why the BMNG layer fails where the Landsat layer succeeds?

    Thanks!
    Thom

  • #2
    Is it a map projection problem?

    Ok, this is killing me. I've tried reprocessing the Blue Marble image pyramids every way that I can think of, with no success at all.

    Could WWJ's failure to load the layer from the GeoServer be caused by a map projection problem? This is unprojected, equirectangular, data. Do I need to reproject it into something else to make WWJ happy?

    This is the info for one of my BMNG files:


    Code:
    E:\imagery\BlueMarble>gdalinfo a1.tif
    Driver: GTiff/GeoTIFF
    Files: a1.tif
    Size is 21600, 21600
    Coordinate System is:
    GEOGCS["WGS 84",
        DATUM["WGS_1984",
            SPHEROID["WGS 84",6378137,298.257223563,
                AUTHORITY["EPSG","7030"]],
            AUTHORITY["EPSG","6326"]],
        PRIMEM["Greenwich",0],
        UNIT["degree",0.0174532925199433],
        AUTHORITY["EPSG","4326"]]
    Origin = (-180.002083333333330,90.002083333333331)
    Pixel Size = (0.004166666666667,-0.004166666666667)
    Metadata:
      AREA_OR_POINT=Area
    Image Structure Metadata:
      COMPRESSION=LZW
      INTERLEAVE=PIXEL
    Corner Coordinates:
    Upper Left  (-180.0020833,  90.0020833) (180d 0'7.50"W, 90d 0'7.50"N)
    Lower Left  (-180.0020833,   0.0020833) (180d 0'7.50"W,  0d 0'7.50"N)
    Upper Right ( -90.0020833,  90.0020833) ( 90d 0'7.50"W, 90d 0'7.50"N)
    Lower Right ( -90.0020833,   0.0020833) ( 90d 0'7.50"W,  0d 0'7.50"N)
    Center      (-135.0020833,  45.0020833) (135d 0'7.50"W, 45d 0'7.50"N)
    Band 1 Block=256x256 Type=Byte, ColorInterp=Red
    Band 2 Block=256x256 Type=Byte, ColorInterp=Green
    Band 3 Block=256x256 Type=Byte, ColorInterp=Blue
    Notice that there is no PROJCS definition. I tried adding a PROJCS="LONGLAT", but it didn't help.

    Please! Any ideas?

    Comment


    • #3
      Sorry, I don't have an answer. But did you get your Blue Marble data from 128.102.3.228?

      Comment


      • #4
        trying and failing to get the imagery from that website. My downloads have never made it farther than 60% complete. I've been trying all morning.

        I got my BMNG imagery directly from the NASA Visible Earth site and used GDAL to translate it into GeoTIFF and add the map projection information (EPSG:4326).

        Comment


        • #5
          My downloads failed too.

          It worked when I downloaded from a faster internet connection.

          Comment


          • #6
            Hmmm... I was getting up to 750 kB/s. I don't think I have access to anything faster. I really wish the data was on an ftp site so I could use more reliable file transfer tools.

            Thanks for your response, though! I guess everyone has been at the DoD Applications Conference for the past couple days.

            Comment


            • #7
              It turns out that the files I have been downloading weren't complete even though it said it was complete.

              I downloaded a "Download Manager" add-on to my FireFox browser and everything downloads fine.

              Comment


              • #8
                Dang! Nothing seems to work when loading these Blue Marble images into a WWJ application. My GeoServer serves up the imagery to the OpenLayers web browser client. The WMSLayerManager WWJ app sees the layer when I point it at the geoserver/wms server. But, nothing happens when I select the checkbox that is supposed to activate the layer in the viewer. And I haven't been able to figure out where any error messages might be displayed or saved. There certainly aren't any showing on my desktop.

                Can anyone give instructions for serving the BMNG imagery? The imagery on the data repository doesn't seem to have any associated geo-reference information. How can this work at all???

                Comment


                • #9
                  Success!

                  I finally figured out what I was doing wrong. Somehow, during the processing of my Blue Marble imagery, I managed to set the coordinates of the image corners incorrectly. (UL= -180.002179, 90.002179; LR= 180.002179, -90.002179). I fixed this by running "gdal_translate -a_ullr -180.0 90.0 180.0 -90.0 ..." on the merged image.

                  A full rundown of the steps it took to get this working:
                  I downloaded the world+topo+bathymetry image for August from the NASA Visible Earth web site. After decompressing the archive I ran this set of commands against the files to produce a single geotiff image and then retile the image into a pyramid.

                  Code:
                  gdal_translate -a_ullr -180 90 -90.0   0.0 -a_srs "EPSG:4326" -co "TILED=YES" -co "BLOCKXSIZE=256" -co "BLOCKYSIZE=256" -co "BIGTIFF=YES" -co "COMPRESS=LZW" world.topo.bathy.200408.3x21600x21600.A1.png A1.tif
                  gdal_translate -a_ullr -180  0 -90.0 -90.0 -a_srs "EPSG:4326" -co "TILED=YES" -co "BLOCKXSIZE=256" -co "BLOCKYSIZE=256" -co "BIGTIFF=YES" -co "COMPRESS=LZW" world.topo.bathy.200408.3x21600x21600.A2.png A2.tif
                  
                  gdal_translate -a_ullr  -90 90   0.0   0.0 -a_srs "EPSG:4326" -co "TILED=YES" -co "BLOCKXSIZE=256" -co "BLOCKYSIZE=256" -co "BIGTIFF=YES" -co "COMPRESS=LZW" world.topo.bathy.200408.3x21600x21600.B1.png B1.tif
                  gdal_translate -a_ullr  -90  0   0.0 -90.0 -a_srs "EPSG:4326" -co "TILED=YES" -co "BLOCKXSIZE=256" -co "BLOCKYSIZE=256" -co "BIGTIFF=YES" -co "COMPRESS=LZW" world.topo.bathy.200408.3x21600x21600.B2.png B2.tif
                  
                  gdal_translate -a_ullr    0 90  90.0   0.0 -a_srs "EPSG:4326" -co "TILED=YES" -co "BLOCKXSIZE=256" -co "BLOCKYSIZE=256" -co "BIGTIFF=YES" -co "COMPRESS=LZW" world.topo.bathy.200408.3x21600x21600.C1.png C1.tif
                  gdal_translate -a_ullr    0  0  90.0 -90.0 -a_srs "EPSG:4326" -co "TILED=YES" -co "BLOCKXSIZE=256" -co "BLOCKYSIZE=256" -co "BIGTIFF=YES" -co "COMPRESS=LZW" world.topo.bathy.200408.3x21600x21600.C2.png C2.tif
                  
                  gdal_translate -a_ullr   90 90 180.0   0.0 -a_srs "EPSG:4326" -co "TILED=YES" -co "BLOCKXSIZE=256" -co "BLOCKYSIZE=256" -co "BIGTIFF=YES" -co "COMPRESS=LZW" world.topo.bathy.200408.3x21600x21600.D1.png D1.tif
                  gdal_translate -a_ullr   90  0 180.0 -90.0 -a_srs "EPSG:4326" -co "TILED=YES" -co "BLOCKXSIZE=256" -co "BLOCKYSIZE=256" -co "BIGTIFF=YES" -co "COMPRESS=LZW" world.topo.bathy.200408.3x21600x21600.D2.png D2.tif
                  
                  gdal_merge -o BlueMarble_WTB_200408.tif -co "TILED=YES" -co "BLOCKXSIZE=256" -co "BLOCKYSIZE=256" -co "BIGTIFF=YES" -co "COMPRESS=LZW" A1.tif A2.tif B1.tif B2.tif C1.tif C2.tif D1.tif D2.tif
                  
                  mkdir BlueMarble_WTB_200408
                  gdal_retile -levels 5 -ps 512 512 -r bilinear -co "TILED=YES" -co "COMPRESS=LZW" -targetDir BlueMarble_WTB_200408 BlueMarble_WTB_200408.tif
                  Then I uploaded the BlueMarble_WTB_200408 directory to my GeoServer data directory. I needed to change the owner of the entire hierarchy to tomcat.tomcat so the import would work.

                  I brought up the GeoServer's webpage and logged in as "admin". I created the workspace and then created a new store using the ImagePyramid plugin. The pyramid creation took longer than I expected, so be patient. It is not finished even when the spinning wheel stops spinning. Hopefully, you will be able to look in the server directory and see the *.prj and *.properties files when they are generated. You may then need to go into the "Layers" page on GeoServer admin page to publish the new layer.

                  Comment

                  Working...
                  X