Hi Daniele:

Maybe I should find a way to strip all the GRIB metadata tags.

==============
gdalinfo rtma2p5.20191011/rtma2p5.t02z.2dvaranl_ndfd.grb2_wexp
Driver: GTiff/GeoTIFF
Files: rtma2p5.20191011/rtma2p5.t02z.2dvaranl_ndfd.grb2_wexp
Size is 2345, 1597
Coordinate System is:
PROJCRS["unknown",
    BASEGEOGCRS["unknown",
        DATUM["unknown",
            ELLIPSOID["unknown",6367470,0,
                LENGTHUNIT["metre",1,
                    ID["EPSG",9001]]]],
        PRIMEM["Greenwich",0,
            ANGLEUNIT["degree",0.0174532925199433,
                ID["EPSG",9122]]]],
    CONVERSION["unnamed",
        METHOD["Lambert Conic Conformal (2SP)",
            ID["EPSG",9802]],
        PARAMETER["Latitude of false origin",0,
            ANGLEUNIT["degree",0.0174532925199433],
            ID["EPSG",8821]],
        PARAMETER["Longitude of false origin",-95,
            ANGLEUNIT["degree",0.0174532925199433],
            ID["EPSG",8822]],
        PARAMETER["Latitude of 1st standard parallel",25,
            ANGLEUNIT["degree",0.0174532925199433],
            ID["EPSG",8823]],
        PARAMETER["Latitude of 2nd standard parallel",25,
            ANGLEUNIT["degree",0.0174532925199433],
            ID["EPSG",8824]],
        PARAMETER["Easting at false origin",0,
            LENGTHUNIT["metre",1],
            ID["EPSG",8826]],
        PARAMETER["Northing at false origin",0,
            LENGTHUNIT["metre",1],
            ID["EPSG",8827]]],
    CS[Cartesian,2],
        AXIS["easting",east,
            ORDER[1],
            LENGTHUNIT["metre",1,
                ID["EPSG",9001]]],
        AXIS["northing",north,
            ORDER[2],
            LENGTHUNIT["metre",1,
                ID["EPSG",9001]]]]
Data axis to CRS axis mapping: 1,2
Origin = (-3270502.204889984335750,6657841.387057464569807)
Pixel Size = (2540.000000000000000,-2540.000000000000000)
Metadata:
  AREA_OR_POINT=Area
Image Structure Metadata:
  INTERLEAVE=BAND
Corner Coordinates:
Upper Left  (-3270502.205, 6657841.387) (138d24'20.95"W, 53d 4'40.97"N)
Lower Left  (-3270502.205, 2601461.387) (126d17' 7.88"W, 19d12'55.10"N)
Upper Right ( 2685797.795, 6657841.387) ( 58d57'29.04"W, 54d23'32.59"N)
Lower Right ( 2685797.795, 2601461.387) ( 69d 9'33.48"W, 20d18'40.56"N)
Center      ( -292352.205, 4629651.387) ( 98d19'56.32"W, 40d37'45.89"N)
Band 1 Block=2345x1 Type=Float64, ColorInterp=Gray
  Description = 2[m] HTGL="Specified height level above ground"
  Metadata:
    GRIB_COMMENT=Relative humidity [%]
    GRIB_DISCIPLINE=0(Meteorological)
    GRIB_ELEMENT=RH
    GRIB_FORECAST_SECONDS=0 sec
    GRIB_IDS=CENTER=98(ECMWF) SUBCENTER=0 MASTER_TABLE=4 LOCAL_TABLE=0
SIGNF_REF_TIME=1(Start_of_Forecast) REF_TIME=2019-10-11T02:00:00Z
PROD_STATUS=0(Operational) TYPE=2(Analysis_and_forecast)
    GRIB_PDS_PDTN=0
    GRIB_PDS_TEMPLATE_ASSEMBLED_VALUES=1 1 0 0 128 0 0 1 0 103 0 2 255
-127 -2147483647
    GRIB_PDS_TEMPLATE_NUMBERS=1 1 0 0 128 0 0 0 1 0 0 0 0 103 0 0 0 0
2 255 255 255 255 255 255
    GRIB_REF_TIME=1570759200 sec UTC
    GRIB_SHORT_NAME=2-HTGL
    GRIB_UNIT=[%]
    GRIB_VALID_TIME=1570759200 sec UTC

On 10/23/19, Daniele Romagnoli <daniele.romagn...@geo-solutions.it> wrote:
> Hi Alexander,
> in theory, the format and the SPI are determined by finders which look for
> a ServiceProviderInterface / GridCoverageFormat being able to decode that
> file. The lookup goes through a scan of the registered SPIs/Factories until
> one of them declares to be able to decode that file, by usually parsing a
> magic number or recognizing a format header or something like that.
>
> So my first question is:
> are you pretty sure that the files you are trying to mosaic are actually
> GeoTiffs and not NetCDFs/Gribs?
> Can you run a gdalinfo on one of them?
>
> Second question: any chance that you are trying to create a mosaic on top
> of a folder containing both GeoTiffs and NetCDFs?
> In that case, if the first file to be analyzed by the mosaic configurator
> is a NetCDF, it will be used as reference format.
>
> Please, let us know.
> Regards,
> Daniele
>
>
> On Wed, Oct 23, 2019 at 9:48 AM Alexander Petkov <green...@gmail.com>
> wrote:
>
>> Is it possible to force the use of a particular raster format through
>> SuggestedSPI and SuggestedFormat parameters?
>>
>> I have the following config options in mosaic.properties:
>> SuggestedSPI=it.geosolutions.imageioimpl.plugins.tiff.TIFFImageReaderSpi
>> SuggestedFormat=org.geotools.gce.geotiff.GeoTiffFormat
>>
>> Despite of this, generated .properties file forces the use of NetCDF
>> format:
>>
>>
>> Relative_humidity.properties:SuggestedSPI=org.geotools.imageio.netcdf.NetCDFImageReaderSpi
>>
>> I believe this is because of the file names--Geotiffs generated from
>> grib files, with the same file names for ease of syncing to a remote
>> ftp archive:
>> -----------
>> ls rtma2p5.20191011/
>> rtma2p5.t02z.2dvaranl_ndfd.grb2_wexp
>> rtma2p5.t10z.2dvaranl_ndfd.grb2_wexp
>> rtma2p5.t18z.2dvaranl_ndfd.grb2_wexp
>> ... and so on
>> -----------
>>
>> Any ideas about enforcing use of Geotiff format, despite of file name
>> extension?
>>
>>
>> Thanks in advance,
>> Alex
>>
>>
>> _______________________________________________
>> Geoserver-users mailing list
>>
>> Please make sure you read the following two resources before posting to
>> this list:
>> - Earning your support instead of buying it, but Ian Turton:
>> http://www.ianturton.com/talks/foss4g.html#/
>> - The GeoServer user list posting guidelines:
>> http://geoserver.org/comm/userlist-guidelines.html
>>
>> If you want to request a feature or an improvement, also see this:
>> https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer
>>
>>
>> Geoserver-users@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/geoserver-users
>>
>
>
> --
> Regards,
> Daniele Romagnoli
> ==
> GeoServer Professional Services from the experts! Visit
> http://goo.gl/it488V
> for more information.
> ==
>
> Ing. Daniele Romagnoli
> Senior Software Engineer
>
> GeoSolutions S.A.S.
> Via di Montramito 3/A
> 55054  Massarosa (LU)
> Italy
> phone: +39 0584 962313
> fax:      +39 0584 1660272
>
> http://www.geo-solutions.it
> http://twitter.com/geosolutions_it
>
> -------------------------------------------------------
>
> Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE
> 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si
> precisa che ogni circostanza inerente alla presente email (il suo
> contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è
> riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il
> messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra
> operazione è illecita. Le sarei comunque grato se potesse darmene notizia.
>
> This email is intended only for the person or entity to which it is
> addressed and may contain information that is privileged, confidential or
> otherwise protected from disclosure. We remind that - as provided by
> European Regulation 2016/679 “GDPR” - copying, dissemination or use of this
> e-mail or the information herein by anyone other than the intended
> recipient is prohibited. If you have received this email by mistake, please
> notify us immediately by telephone or e-mail.
>


_______________________________________________
Geoserver-users mailing list

Please make sure you read the following two resources before posting to this 
list:
- Earning your support instead of buying it, but Ian Turton: 
http://www.ianturton.com/talks/foss4g.html#/
- The GeoServer user list posting guidelines: 
http://geoserver.org/comm/userlist-guidelines.html

If you want to request a feature or an improvement, also see this: 
https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer


Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

Reply via email to