Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[geomesa-users] Use of Landsat 8 imagery with GeoMesa
Hi,

As part of our agriculture-based project we need to store and process Landsat 8 imagery for large areas in various countries in Europe.

We are interested in using GeoMesa as solution since it seems to provide many of the features we need to store, visualize and process (using the additional Geoserver plugins) the large amount raster images  we have to consider in the project .

I managed to set up a working environment (Apache Accumulo + Geomesa + Geoserver) and followed the raster ingestion example as indicated here: http://www.geomesa.org/geomesa-raster/

The natural earth example can be visualized without problem, however when it comes to visualizing the ingested Landsat 8 image via a WMS request I am getting the following:

request: http://SERVER/geoserver/foodie_raster/wms?service=WMS&version=1.1.0&request=GetMap&layers=foodie_raster:LANDSAT8_B3&styles=&bbox=-6.794064,39.21167183399542,-3.937779107693501,41.43063&width=512&height=397&srs=EPSG:4326&format=image%2Fpng


Error:
<?xml version="1.0" encoding="UTF-8" standalone="no"?><!DOCTYPE ServiceExceptionReport SYSTEM "http://5.79.69.49:28080/geoserver/schemas/wms/1.1.1/WMS_exception_1_1_1.dtd"> <ServiceExceptionReport version="1.1.1" >   <ServiceException>
      Error rendering coverage on the fast path
org.locationtech.geomesa.shade.google.common.util.concurrent.UncheckedExecutionException: java.lang.IllegalArgumentException: duplicate key: 0.002526
java.lang.IllegalArgumentException: duplicate key: 0.002526
duplicate key: 0.002526
</ServiceException></ServiceExceptionReport>

Somethings regarding the steps I followed for ingesting the Landsat rasters:

- We need to store the 11 (B1 to B11) bands that compose a Landsat 8 scene, therefore we created one layer per band (AFAIK multiband rasters are not supported yet by Geomesa)

- The Landsat 8 scene is reprojected to EPSG:4326 (from EPSG:32630): gdalwarp -t_srs EPSG:4326 LC82020322015275LGN00_B3.TIF LC82020322015275LGN00_B3_4326.TIF

- Image pyramid creation: gdal_retile.py -v -pyramidOnly -r lanczos -levels 4 -ps 675 675 -targetDir ./ LC82020322015275LGN00_B3_4326.TIF

- Rasters ingestion: geomesa ingestraster -u geomesa -p geomesa -t LANDSAT8_B3 -f "./1/" -fmt geotiff 

Same procedure for pyramid levels 2, 3 and 4

Do you have any idea about what may be causing the duplicate key problem? 

I am attaching also the output from gdalinfo command applied to the LC82020322015275LGN00_B3.TIF  image in case the info might be of help.

Best regards


Miguel A. Esbrí
Driver: GTiff/GeoTIFF
Files: LC82020322015275LGN00_B3.TIF
Size is 7881, 8011
Coordinate System is:
PROJCS["WGS 84 / UTM zone 30N",
    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"]],
    PROJECTION["Transverse_Mercator"],
    PARAMETER["latitude_of_origin",0],
    PARAMETER["central_meridian",-3],
    PARAMETER["scale_factor",0.9996],
    PARAMETER["false_easting",500000],
    PARAMETER["false_northing",0],
    UNIT["metre",1,
        AUTHORITY["EPSG","9001"]],
    AUTHORITY["EPSG","32630"]]
Origin = (182685.000000000000000,4587015.000000000000000)
Pixel Size = (30.000000000000000,-30.000000000000000)
Metadata:
  AREA_OR_POINT=Point
Image Structure Metadata:
  COMPRESSION=DEFLATE
  INTERLEAVE=BAND
Corner Coordinates:
Upper Left  (  182685.000, 4587015.000) (  6d47'38.63"W, 41d22'19.58"N)
Lower Left  (  182685.000, 4346685.000) (  6d40'29.82"W, 39d12'41.38"N)
Upper Right (  419115.000, 4587015.000) (  3d58' 5.08"W, 41d25'50.27"N)
Lower Right (  419115.000, 4346685.000) (  3d56'15.38"W, 39d15'56.64"N)
Center      (  300900.000, 4466850.000) (  5d20'37.12"W, 40d19'42.45"N)
Band 1 Block=512x512 Type=UInt16, ColorInterp=Gray

Back to the top