Re: [Geoserver-users] ImageMosaic JDBC entering in null values for attributes
Hello. This code is in the imagemosaic and jdbc geotools v24 modules. Sorry
for the confusion
Dominique Bessette
From: Andrea Aime
Sent: Saturday, January 22, 2022 9:12 AM
To: Bessette-Halsema, Dominique E
Cc: GeoServer Users
Subject: Re: [Geoserver-users] ImageMosaic JDBC entering in null values for
attributes
[External: Use caution with links & attachments]
Hi Dominique,
the imagemosaic jdbc module has been removed from both the GeoTools and
GeoServer
source code, due to persistent lack of a maintainer. It's also generating no
business for core
developers (which could have justified other developers picking up the module).
Long story short, the module is gone.
If you or someone from your organization is interested in stepping up and
maintaining the module,
it can be restored from the version control. Same could happen if any of the
core devs would get
business around it.
Cheers
Andrea
On Wed, Jan 19, 2022 at 12:35 AM Bessette-Halsema, Dominique E via
Geoserver-users
mailto:geoserver-users@lists.sourceforge.net>>
wrote:
I also found in the logs that for the file that failed it could not find the
property collectors
022-01-18 20:05:33,900 DEBUG [org.geotools.gce.imagemosaic] (default task-83)
No properties collector have been found
2022-01-18 20:05:33,900 INFO [org.geotools.gce.imagemosaic] (default task-83)
Now indexing file
COAMPS-AFGHAN-W1800S0900E1800N0900-FNMOC_GRID_2022011800_007315.0_20220118.tif
Dominique Bessette
Senior Software Engineer
T 619.881.2478
From: Bessette-Halsema, Dominique E via Geoserver-users
mailto:geoserver-users@lists.sourceforge.net>>
Sent: Tuesday, January 18, 2022 2:15 PM
To:
geoserver-users@lists.sourceforge.net<mailto:geoserver-users@lists.sourceforge.net>
Subject: Re: [Geoserver-users] ImageMosaic JDBC entering in null values for
attributes
[External: Use caution with links & attachments]
Is there a configuration or way to make it so the imagemosaic tables for the
granules are “Not Null”? This way at least the bad entry will be thrown out
and all other ingested layers can be used.
Dominique
From: Bessette-Halsema, Dominique E via Geoserver-users
mailto:geoserver-users@lists.sourceforge.net>>
Sent: Tuesday, January 18, 2022 12:54 PM
To:
geoserver-users@lists.sourceforge.net<mailto:geoserver-users@lists.sourceforge.net>
Subject: [Geoserver-users] ImageMosaic JDBC entering in null values for
attributes
[External: Use caution with links & attachments]
Hello
I’m using ImageMosaic with the JDBC extension. I found that when GeoServer is
under heavy load, intermittently the JDBC code will insert null values for the
attributes. This causes the WMS getCapabilities to fail with the following
Warning
WARN [org.geoserver.wms.capabilities] (default task-91) Error writing
metadata; skipping layer: AFGHAN-n2-a1.grad_mod_refr.ht_sfc:
java.lang.NullPointerException
This essentially makes that layer unusable until the database entry is deleted.
I extracted the geotools jdbc code where it is setting the values to null.
What I’m looking for is some insight into why this is happening or a possible
fix. Has this issue been documented?
2022-01-18 20:05:34,023 DEBUG [org.geotools.data.jdbc] (default task-83)
exporting LogicFilter
2022-01-18 20:05:34,023 DEBUG [org.geotools.data.jdbc] (default task-83)
exporting SQL ComparisonFilter
2022-01-18 20:05:34,023 DEBUG [org.geotools.data.jdbc] (default task-83)
exporting PropertyName
2022-01-18 20:05:34,023 DEBUG [org.geotools.data.jdbc] (default task-83)
exporting PropertyName
2022-01-18 20:05:34,023 DEBUG [org.geotools.jdbc] (default task-83) SELECT
count(*) FROM
"forecast_grid_mosaic"."COAMPS-AFGHAN^AFGHAN-n2-a1^grad_mod_refr^ht_sfc" WHERE
("location" = ? AND "location" IS NOT NULL )
2022-01-18 20:05:34,023 DEBUG [org.geotools.jdbc] (default task-83) 1 =
COAMPS-AFGHAN-W1800S0900E1800N0900-FNMOC_GRID_2022011800_007315.0_20220118.tif
2022-01-18 20:05:34,024 DEBUG [org.geotools.jdbc] (default task-83) SELECT
"fid",ST_AsEWKB("the_geom") as
"the_geom","location","validtime","analysis_time","elevation" FROM
"forecast_grid_mosaic"."COAMPS-AFGHAN^AFGHAN-n2-a1^grad_mod_refr^ht_sfc" LIMIT 1
2022-01-18 20:05:34,029 DEBUG [org.geotools.jdbc] (default task-83) SELECT
ST_AsText(ST_Force2D(ST_Envelope(ST_Extent("the_geom"::geometry FROM
"forecast_grid_mosaic"."COAMPS-AFGHAN^AFGHAN-n2-a1^grad_mod_refr^ht_sfc"
2022-01-18 20:05:34,029 WARN [org.hibernate.orm.deprecation] (default task-55)
HHH9022: Hibernate's legacy org.hibernate.Criteria API is deprecated; use
the JPA javax.persistence.criteria.CriteriaQuery instead
2022-01-18 20:05:34,030 DEBUG [org.geotools.jdbc] (default task-83) SELECT
"fid",ST_AsE
Re: [Geoserver-users] ImageMosaic JDBC entering in null values for attributes
Hi Dominique,
the imagemosaic jdbc module has been removed from both the GeoTools and
GeoServer
source code, due to persistent lack of a maintainer. It's also generating
no business for core
developers (which could have justified other developers picking up the
module).
Long story short, the module is gone.
If you or someone from your organization is interested in stepping up and
maintaining the module,
it can be restored from the version control. Same could happen if any of
the core devs would get
business around it.
Cheers
Andrea
On Wed, Jan 19, 2022 at 12:35 AM Bessette-Halsema, Dominique E via
Geoserver-users wrote:
> I also found in the logs that for the file that failed it could not find
> the property collectors
>
>
>
> 022-01-18 20:05:33,900 DEBUG [org.geotools.gce.imagemosaic] (default
> task-83) No properties collector have been found
>
> 2022-01-18 20:05:33,900 INFO [org.geotools.gce.imagemosaic] (default
> task-83) Now indexing file
> COAMPS-AFGHAN-W1800S0900E1800N0900-FNMOC_GRID_2022011800_007315.0_20220118.tif
>
>
>
> Dominique Bessette
>
> Senior Software Engineer
> T 619.881.2478
>
>
>
> *From:* Bessette-Halsema, Dominique E via Geoserver-users <
> geoserver-users@lists.sourceforge.net>
> *Sent:* Tuesday, January 18, 2022 2:15 PM
> *To:* geoserver-users@lists.sourceforge.net
> *Subject:* Re: [Geoserver-users] ImageMosaic JDBC entering in null values
> for attributes
>
>
>
>
>
> *[External: Use caution with links & attachments]*
>
>
>
> Is there a configuration or way to make it so the imagemosaic tables for
> the granules are “Not Null”? This way at least the bad entry will be
> thrown out and all other ingested layers can be used.
>
>
>
> Dominique
>
>
>
> *From:* Bessette-Halsema, Dominique E via Geoserver-users <
> geoserver-users@lists.sourceforge.net>
> *Sent:* Tuesday, January 18, 2022 12:54 PM
> *To:* geoserver-users@lists.sourceforge.net
> *Subject:* [Geoserver-users] ImageMosaic JDBC entering in null values for
> attributes
>
>
>
>
>
> *[External: Use caution with links & attachments]*
>
>
>
> Hello
>
>
>
> I’m using ImageMosaic with the JDBC extension. I found that when
> GeoServer is under heavy load, intermittently the JDBC code will insert
> null values for the attributes. This causes the WMS getCapabilities to
> fail with the following Warning
>
>
>
> WARN [org.geoserver.wms.capabilities] (default task-91) Error writing
> metadata; skipping layer: AFGHAN-n2-a1.grad_mod_refr.ht_sfc:
> java.lang.NullPointerException
>
>
>
> This essentially makes that layer unusable until the database entry is
> deleted. I extracted the geotools jdbc code where it is setting the values
> to null. What I’m looking for is some insight into why this is happening
> or a possible fix. Has this issue been documented?
>
>
>
> 2022-01-18 20:05:34,023 DEBUG [org.geotools.data.jdbc] (default task-83)
> exporting LogicFilter
>
> 2022-01-18 20:05:34,023 DEBUG [org.geotools.data.jdbc] (default task-83)
> exporting SQL ComparisonFilter
>
> 2022-01-18 20:05:34,023 DEBUG [org.geotools.data.jdbc] (default task-83)
> exporting PropertyName
>
> 2022-01-18 20:05:34,023 DEBUG [org.geotools.data.jdbc] (default task-83)
> exporting PropertyName
>
> 2022-01-18 20:05:34,023 DEBUG [org.geotools.jdbc] (default task-83) SELECT
> count(*) FROM
> "forecast_grid_mosaic"."COAMPS-AFGHAN^AFGHAN-n2-a1^grad_mod_refr^ht_sfc"
> WHERE ("location" = ? AND "location" IS NOT NULL )
>
> 2022-01-18 20:05:34,023 DEBUG [org.geotools.jdbc] (default task-83) 1 =
> COAMPS-AFGHAN-W1800S0900E1800N0900-FNMOC_GRID_2022011800_007315.0_20220118.tif
>
> 2022-01-18 20:05:34,024 DEBUG [org.geotools.jdbc] (default task-83) SELECT
> "fid",ST_AsEWKB("the_geom") as
> "the_geom","location","validtime","analysis_time","elevation" FROM
> "forecast_grid_mosaic"."COAMPS-AFGHAN^AFGHAN-n2-a1^grad_mod_refr^ht_sfc"
> LIMIT 1
>
> 2022-01-18 20:05:34,029 DEBUG [org.geotools.jdbc] (default task-83) SELECT
> ST_AsText(ST_Force2D(ST_Envelope(ST_Extent("the_geom"::geometry FROM
> "forecast_grid_mosaic"."COAMPS-AFGHAN^AFGHAN-n2-a1^grad_mod_refr^ht_sfc"
>
> 2022-01-18 20:05:34,029 WARN [org.hibernate.orm.deprecation] (default
> task-55) HHH9022: Hibernate's legacy org.hibernate.Criteria API is
> deprecated; use the JPA javax.persistence.criteria.CriteriaQuery instead
>
> 2022-01-18 20:05:34,030 DEBUG [org.geotools.jdbc] (default task-83) SELECT
&
Re: [Geoserver-users] ImageMosaic JDBC entering in null values for attributes
I also found in the logs that for the file that failed it could not find the
property collectors
022-01-18 20:05:33,900 DEBUG [org.geotools.gce.imagemosaic] (default task-83)
No properties collector have been found
2022-01-18 20:05:33,900 INFO [org.geotools.gce.imagemosaic] (default task-83)
Now indexing file
COAMPS-AFGHAN-W1800S0900E1800N0900-FNMOC_GRID_2022011800_007315.0_20220118.tif
Dominique Bessette
Senior Software Engineer
T 619.881.2478
From: Bessette-Halsema, Dominique E via Geoserver-users
Sent: Tuesday, January 18, 2022 2:15 PM
To: geoserver-users@lists.sourceforge.net
Subject: Re: [Geoserver-users] ImageMosaic JDBC entering in null values for
attributes
[External: Use caution with links & attachments]
Is there a configuration or way to make it so the imagemosaic tables for the
granules are "Not Null"? This way at least the bad entry will be thrown out
and all other ingested layers can be used.
Dominique
From: Bessette-Halsema, Dominique E via Geoserver-users
mailto:geoserver-users@lists.sourceforge.net>>
Sent: Tuesday, January 18, 2022 12:54 PM
To:
geoserver-users@lists.sourceforge.net<mailto:geoserver-users@lists.sourceforge.net>
Subject: [Geoserver-users] ImageMosaic JDBC entering in null values for
attributes
[External: Use caution with links & attachments]
Hello
I'm using ImageMosaic with the JDBC extension. I found that when GeoServer is
under heavy load, intermittently the JDBC code will insert null values for the
attributes. This causes the WMS getCapabilities to fail with the following
Warning
WARN [org.geoserver.wms.capabilities] (default task-91) Error writing
metadata; skipping layer: AFGHAN-n2-a1.grad_mod_refr.ht_sfc:
java.lang.NullPointerException
This essentially makes that layer unusable until the database entry is deleted.
I extracted the geotools jdbc code where it is setting the values to null.
What I'm looking for is some insight into why this is happening or a possible
fix. Has this issue been documented?
2022-01-18 20:05:34,023 DEBUG [org.geotools.data.jdbc] (default task-83)
exporting LogicFilter
2022-01-18 20:05:34,023 DEBUG [org.geotools.data.jdbc] (default task-83)
exporting SQL ComparisonFilter
2022-01-18 20:05:34,023 DEBUG [org.geotools.data.jdbc] (default task-83)
exporting PropertyName
2022-01-18 20:05:34,023 DEBUG [org.geotools.data.jdbc] (default task-83)
exporting PropertyName
2022-01-18 20:05:34,023 DEBUG [org.geotools.jdbc] (default task-83) SELECT
count(*) FROM
"forecast_grid_mosaic"."COAMPS-AFGHAN^AFGHAN-n2-a1^grad_mod_refr^ht_sfc" WHERE
("location" = ? AND "location" IS NOT NULL )
2022-01-18 20:05:34,023 DEBUG [org.geotools.jdbc] (default task-83) 1 =
COAMPS-AFGHAN-W1800S0900E1800N0900-FNMOC_GRID_2022011800_007315.0_20220118.tif
2022-01-18 20:05:34,024 DEBUG [org.geotools.jdbc] (default task-83) SELECT
"fid",ST_AsEWKB("the_geom") as
"the_geom","location","validtime","analysis_time","elevation" FROM
"forecast_grid_mosaic"."COAMPS-AFGHAN^AFGHAN-n2-a1^grad_mod_refr^ht_sfc" LIMIT 1
2022-01-18 20:05:34,029 DEBUG [org.geotools.jdbc] (default task-83) SELECT
ST_AsText(ST_Force2D(ST_Envelope(ST_Extent("the_geom"::geometry FROM
"forecast_grid_mosaic"."COAMPS-AFGHAN^AFGHAN-n2-a1^grad_mod_refr^ht_sfc"
2022-01-18 20:05:34,029 WARN [org.hibernate.orm.deprecation] (default task-55)
HHH9022: Hibernate's legacy org.hibernate.Criteria API is deprecated; use
the JPA javax.persistence.criteria.CriteriaQuery instead
2022-01-18 20:05:34,030 DEBUG [org.geotools.jdbc] (default task-83) SELECT
"fid",ST_AsEWKB("the_geom") as
"the_geom","location","validtime","analysis_time","elevation" FROM
"forecast_grid_mosaic"."COAMPS-AFGHAN^AFGHAN-n2-a1^grad_mod_refr^ht_sfc" WHERE
0 = 1
2022-01-18 20:05:34,030 DEBUG [org.geotools.jdbc] (default task-83) Setting
the_geom to POLYGON ((47.4749994 19.025, 47.4749994 40.775,
78.525 40.775, 78.525 19.025, 47.4749994 19.025))
2022-01-18 20:05:34,030 DEBUG [org.geotools.jdbc] (default task-83) Setting 0
to POLYGON ((47.4749994 19.025, 47.4749994 40.775, 78.525
40.775, 78.525 19.025, 47.4749994 19.025))
2022-01-18 20:05:34,030 DEBUG [org.geotools.jdbc] (default task-83) Setting
location to
COAMPS-AFGHAN-W1800S0900E1800N0900-FNMOC_GRID_2022011800_007315.0_20220118.tif
2022-01-18 20:05:34,030 DEBUG [org.geotools.jdbc] (default task-83) Setting 1
to
COAMPS-AFGHAN-W1800S0900E1800N0900-FNMOC_GRID_2022011800_007315.0_20220118.tif
2022-01-18 20:05:34,030 DEBUG [org.geotools.jdbc] (default task-83) Setting
validtime to null
2022-01
Re: [Geoserver-users] ImageMosaic JDBC entering in null values for attributes
Is there a configuration or way to make it so the imagemosaic tables for the
granules are "Not Null"? This way at least the bad entry will be thrown out
and all other ingested layers can be used.
Dominique
From: Bessette-Halsema, Dominique E via Geoserver-users
Sent: Tuesday, January 18, 2022 12:54 PM
To: geoserver-users@lists.sourceforge.net
Subject: [Geoserver-users] ImageMosaic JDBC entering in null values for
attributes
[External: Use caution with links & attachments]
Hello
I'm using ImageMosaic with the JDBC extension. I found that when GeoServer is
under heavy load, intermittently the JDBC code will insert null values for the
attributes. This causes the WMS getCapabilities to fail with the following
Warning
WARN [org.geoserver.wms.capabilities] (default task-91) Error writing
metadata; skipping layer: AFGHAN-n2-a1.grad_mod_refr.ht_sfc:
java.lang.NullPointerException
This essentially makes that layer unusable until the database entry is deleted.
I extracted the geotools jdbc code where it is setting the values to null.
What I'm looking for is some insight into why this is happening or a possible
fix. Has this issue been documented?
2022-01-18 20:05:34,023 DEBUG [org.geotools.data.jdbc] (default task-83)
exporting LogicFilter
2022-01-18 20:05:34,023 DEBUG [org.geotools.data.jdbc] (default task-83)
exporting SQL ComparisonFilter
2022-01-18 20:05:34,023 DEBUG [org.geotools.data.jdbc] (default task-83)
exporting PropertyName
2022-01-18 20:05:34,023 DEBUG [org.geotools.data.jdbc] (default task-83)
exporting PropertyName
2022-01-18 20:05:34,023 DEBUG [org.geotools.jdbc] (default task-83) SELECT
count(*) FROM
"forecast_grid_mosaic"."COAMPS-AFGHAN^AFGHAN-n2-a1^grad_mod_refr^ht_sfc" WHERE
("location" = ? AND "location" IS NOT NULL )
2022-01-18 20:05:34,023 DEBUG [org.geotools.jdbc] (default task-83) 1 =
COAMPS-AFGHAN-W1800S0900E1800N0900-FNMOC_GRID_2022011800_007315.0_20220118.tif
2022-01-18 20:05:34,024 DEBUG [org.geotools.jdbc] (default task-83) SELECT
"fid",ST_AsEWKB("the_geom") as
"the_geom","location","validtime","analysis_time","elevation" FROM
"forecast_grid_mosaic"."COAMPS-AFGHAN^AFGHAN-n2-a1^grad_mod_refr^ht_sfc" LIMIT 1
2022-01-18 20:05:34,029 DEBUG [org.geotools.jdbc] (default task-83) SELECT
ST_AsText(ST_Force2D(ST_Envelope(ST_Extent("the_geom"::geometry FROM
"forecast_grid_mosaic"."COAMPS-AFGHAN^AFGHAN-n2-a1^grad_mod_refr^ht_sfc"
2022-01-18 20:05:34,029 WARN [org.hibernate.orm.deprecation] (default task-55)
HHH9022: Hibernate's legacy org.hibernate.Criteria API is deprecated; use
the JPA javax.persistence.criteria.CriteriaQuery instead
2022-01-18 20:05:34,030 DEBUG [org.geotools.jdbc] (default task-83) SELECT
"fid",ST_AsEWKB("the_geom") as
"the_geom","location","validtime","analysis_time","elevation" FROM
"forecast_grid_mosaic"."COAMPS-AFGHAN^AFGHAN-n2-a1^grad_mod_refr^ht_sfc" WHERE
0 = 1
2022-01-18 20:05:34,030 DEBUG [org.geotools.jdbc] (default task-83) Setting
the_geom to POLYGON ((47.4749994 19.025, 47.4749994 40.775,
78.525 40.775, 78.525 19.025, 47.4749994 19.025))
2022-01-18 20:05:34,030 DEBUG [org.geotools.jdbc] (default task-83) Setting 0
to POLYGON ((47.4749994 19.025, 47.4749994 40.775, 78.525
40.775, 78.525 19.025, 47.4749994 19.025))
2022-01-18 20:05:34,030 DEBUG [org.geotools.jdbc] (default task-83) Setting
location to
COAMPS-AFGHAN-W1800S0900E1800N0900-FNMOC_GRID_2022011800_007315.0_20220118.tif
2022-01-18 20:05:34,030 DEBUG [org.geotools.jdbc] (default task-83) Setting 1
to
COAMPS-AFGHAN-W1800S0900E1800N0900-FNMOC_GRID_2022011800_007315.0_20220118.tif
2022-01-18 20:05:34,030 DEBUG [org.geotools.jdbc] (default task-83) Setting
validtime to null
2022-01-18 20:05:34,030 DEBUG [org.geotools.jdbc] (default task-83) Setting 2
to null
2022-01-18 20:05:34,030 DEBUG [org.geotools.jdbc] (default task-83) Setting
analysis_time to null
2022-01-18 20:05:34,030 DEBUG [org.geotools.jdbc] (default task-83) Setting 3
to null
2022-01-18 20:05:34,030 DEBUG [org.geotools.jdbc] (default task-83) Setting
elevation to null
2022-01-18 20:05:34,030 DEBUG [org.geotools.jdbc] (default task-83) Setting 4
to null
2022-01-18 20:05:34,031 DEBUG [org.geotools.jdbc] (default task-83) Inserting
new features with ps: INSERT INTO
"forecast_grid_mosaic"."COAMPS-AFGHAN^AFGHAN-n2-a1^grad_mod_refr^ht_sfc" (
"the_geom","location","validtime","analysis_time","elevation" ) VALUES (
ST_GeomFromWKB(?, 4326),?,?,?,?)
2022-01-18 20:05:34,031 DEBUG [org.geotools.jdbc] (defau
[Geoserver-users] ImageMosaic JDBC entering in null values for attributes
Hello
I'm using ImageMosaic with the JDBC extension. I found that when GeoServer is
under heavy load, intermittently the JDBC code will insert null values for the
attributes. This causes the WMS getCapabilities to fail with the following
Warning
WARN [org.geoserver.wms.capabilities] (default task-91) Error writing
metadata; skipping layer: AFGHAN-n2-a1.grad_mod_refr.ht_sfc:
java.lang.NullPointerException
This essentially makes that layer unusable until the database entry is deleted.
I extracted the geotools jdbc code where it is setting the values to null.
What I'm looking for is some insight into why this is happening or a possible
fix. Has this issue been documented?
2022-01-18 20:05:34,023 DEBUG [org.geotools.data.jdbc] (default task-83)
exporting LogicFilter
2022-01-18 20:05:34,023 DEBUG [org.geotools.data.jdbc] (default task-83)
exporting SQL ComparisonFilter
2022-01-18 20:05:34,023 DEBUG [org.geotools.data.jdbc] (default task-83)
exporting PropertyName
2022-01-18 20:05:34,023 DEBUG [org.geotools.data.jdbc] (default task-83)
exporting PropertyName
2022-01-18 20:05:34,023 DEBUG [org.geotools.jdbc] (default task-83) SELECT
count(*) FROM
"forecast_grid_mosaic"."COAMPS-AFGHAN^AFGHAN-n2-a1^grad_mod_refr^ht_sfc" WHERE
("location" = ? AND "location" IS NOT NULL )
2022-01-18 20:05:34,023 DEBUG [org.geotools.jdbc] (default task-83) 1 =
COAMPS-AFGHAN-W1800S0900E1800N0900-FNMOC_GRID_2022011800_007315.0_20220118.tif
2022-01-18 20:05:34,024 DEBUG [org.geotools.jdbc] (default task-83) SELECT
"fid",ST_AsEWKB("the_geom") as
"the_geom","location","validtime","analysis_time","elevation" FROM
"forecast_grid_mosaic"."COAMPS-AFGHAN^AFGHAN-n2-a1^grad_mod_refr^ht_sfc" LIMIT 1
2022-01-18 20:05:34,029 DEBUG [org.geotools.jdbc] (default task-83) SELECT
ST_AsText(ST_Force2D(ST_Envelope(ST_Extent("the_geom"::geometry FROM
"forecast_grid_mosaic"."COAMPS-AFGHAN^AFGHAN-n2-a1^grad_mod_refr^ht_sfc"
2022-01-18 20:05:34,029 WARN [org.hibernate.orm.deprecation] (default task-55)
HHH9022: Hibernate's legacy org.hibernate.Criteria API is deprecated; use
the JPA javax.persistence.criteria.CriteriaQuery instead
2022-01-18 20:05:34,030 DEBUG [org.geotools.jdbc] (default task-83) SELECT
"fid",ST_AsEWKB("the_geom") as
"the_geom","location","validtime","analysis_time","elevation" FROM
"forecast_grid_mosaic"."COAMPS-AFGHAN^AFGHAN-n2-a1^grad_mod_refr^ht_sfc" WHERE
0 = 1
2022-01-18 20:05:34,030 DEBUG [org.geotools.jdbc] (default task-83) Setting
the_geom to POLYGON ((47.4749994 19.025, 47.4749994 40.775,
78.525 40.775, 78.525 19.025, 47.4749994 19.025))
2022-01-18 20:05:34,030 DEBUG [org.geotools.jdbc] (default task-83) Setting 0
to POLYGON ((47.4749994 19.025, 47.4749994 40.775, 78.525
40.775, 78.525 19.025, 47.4749994 19.025))
2022-01-18 20:05:34,030 DEBUG [org.geotools.jdbc] (default task-83) Setting
location to
COAMPS-AFGHAN-W1800S0900E1800N0900-FNMOC_GRID_2022011800_007315.0_20220118.tif
2022-01-18 20:05:34,030 DEBUG [org.geotools.jdbc] (default task-83) Setting 1
to
COAMPS-AFGHAN-W1800S0900E1800N0900-FNMOC_GRID_2022011800_007315.0_20220118.tif
2022-01-18 20:05:34,030 DEBUG [org.geotools.jdbc] (default task-83) Setting
validtime to null
2022-01-18 20:05:34,030 DEBUG [org.geotools.jdbc] (default task-83) Setting 2
to null
2022-01-18 20:05:34,030 DEBUG [org.geotools.jdbc] (default task-83) Setting
analysis_time to null
2022-01-18 20:05:34,030 DEBUG [org.geotools.jdbc] (default task-83) Setting 3
to null
2022-01-18 20:05:34,030 DEBUG [org.geotools.jdbc] (default task-83) Setting
elevation to null
2022-01-18 20:05:34,030 DEBUG [org.geotools.jdbc] (default task-83) Setting 4
to null
2022-01-18 20:05:34,031 DEBUG [org.geotools.jdbc] (default task-83) Inserting
new features with ps: INSERT INTO
"forecast_grid_mosaic"."COAMPS-AFGHAN^AFGHAN-n2-a1^grad_mod_refr^ht_sfc" (
"the_geom","location","validtime","analysis_time","elevation" ) VALUES (
ST_GeomFromWKB(?, 4326),?,?,?,?)
2022-01-18 20:05:34,031 DEBUG [org.geotools.jdbc] (default task-83) 1 = POLYGON
((47.4749994 19.025, 47.4749994 40.775, 78.525 40.775, 78.525
19.025, 47.4749994 19.025))
2022-01-18 20:05:34,031 DEBUG [org.geotools.jdbc] (default task-83) 2 =
COAMPS-AFGHAN-W1800S0900E1800N0900-FNMOC_GRID_2022011800_007315.0_20220118.tif
2022-01-18 20:05:34,031 DEBUG [org.geotools.jdbc] (default task-83) 3 = null
2022-01-18 20:05:34,031 DEBUG [org.geotools.jdbc] (default task-83) 4 = null
2022-01-18 20:05:34,031 DEBUG [org.geotools.jdbc] (default task-83) 5 = null
2022-01-18 20:05:34,049 DEBUG [org.geotools.gce.imagemosaic] (default task-83)
Done with file
/gis/geoserver/external/data/dynamic/isisgridcoverage/COAMPS-AFGHAN/AFGHAN-n2-a1/grad_mod_refr/COAMPS-AFGHAN^AFGHAN-n2-a1^grad_mod_refr^ht_sfc/COAMPS-AFGHAN-W1800S0900E1800N0900-FNMOC
