date:20171002

[Geoserver-users] cascading WMTS over HTTPS

2017-10-02 Thread nueve

Hi everyone,

I'm trying to cascade WMTS service over https, but still got an error /"WMTS
Connection test failed: java.security.NoSuchAlgorithmException: Error
constructing implementation (algorithm: Default, provider: SunJSSE, class:
sun.security.ssl.SSLContextImpl$DefaultSSLContext)"/. Application server is
running on Windows with jdk 1.8.0_144, Tomcat 7 and geoserver 2.12-RC1.
I added a SSL certificate of wmts service to cacerts, but it didn't work. Do
you have same issue or I miss something? 
thanks in advance

Peter



--
Sent from: http://osgeo-org.1560.x6.nabble.com/GeoServer-User-f3786390.html

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
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

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

Re: [Geoserver-users] ImagePyramid using Postgresql for granules

2017-10-02 Thread Daniele Romagnoli

Hi Darell,

On Mon, Oct 2, 2017 at 11:30 AM, Darell van der Voort 
wrote:

> Hello Daniele,
>
> Thank you for your input! I now use a schema per workspace, but creating a
> schema per imagepyramid would indeed solve the problem of duplicate table
> names. So do I understand correctly that there is no possibility to change
> the table names?
>

Nope, you can do that, instead.
You can specify the same "schema" name in all the level's
datastore.properties but you should specify a different "TypeName" property
in each indexer file. The specific ImageMosaic level will index granules in
that "TypeName" table.

Hope this helps.
Regards,
Daniele




> For example to: schema.imagepyramid0, schema.imagepyramid1 etc. In which
> schema is the unique workspace schema and imagepyramid is the name of the
> layer. Thank you!
>
> Kind regards,
> Darell
>
> On Mon, Oct 2, 2017 at 11:19 AM, Daniele Romagnoli  solutions.it> wrote:
>
>> Hi Darell,
>> as you said, the imagePyramid is basically a set of imageMosaics: an
>> ImageMosaic for each pyramid level.
>> Therefore, each level should have its own indexer and, optionally, a
>> datastore.properties if you want to catalog the granules into a DB instead
>> of default shapefile.
>>
>> When using DB instead of shapefile, you may want to use a single database
>> (as an instance, "pyramid") and store each level granule's index into a
>> different schema name. Therefore, the datastore.properties of each level
>> should define a different schema name, as an instance:
>>
>> pyramid/0/datastore.properties contains a "schema=level0" property
>> pyramid/1/datastore.properties contains a "schema=level1" property
>> pyramid/2/datastore.properties contains a "schema=level2" property
>>
>> Note that you should create the schemas (with "CREATE SCHEMA levelx" sql
>> statements) in advance on your DB, before configuring the imagePyramid
>> store in GeoServer.
>>
>> Hope this helps.
>> Regards,
>> Daniele
>>
>>
>>
>>
>>
>> On Mon, Oct 2, 2017 at 10:54 AM, Darell van der Voort <
>> darell...@gmail.com> wrote:
>>
>>> Hi Peter,
>>>
>>> Thank you for the examples, very helpful! Using a indexer.xml indeed
>>> seems like a better set-up. Have you ever tried this in combination with
>>> the imagepyramid plugin? I know that the imagepyramid are basically just
>>> imagemoasics per folder level. However as the folder structure is different
>>> it causes some problems. My folder structure looks like:
>>>
>>> /geoserver/data/workspace//0/.tiffs
>>> /geoserver/data/workspace//1/.tiffs
>>> /geoserver/data/workspace//2/.tiffs
>>> etc..
>>>
>>> Where the numbers stand for the pyramid levels which are filled with
>>> multiple tiffs, the indexer.properties and the foldername.properties. I put
>>> tiffs from different dates in the same folder and use a unique date in the
>>> filename. Should I put the indexer.xml and datastore.properties in each
>>> pyramid directory? I can try it later this week and will let you know if it
>>> works.
>>>
>>> Kind regards,
>>> Darell
>>>
>>> On Fri, Sep 29, 2017 at 11:43 AM, Peter Kovac <
>>> peter.ko...@microstep-mis.com> wrote:
>>>
 I usually configure ImageMosaic for time-series plain GeoTIFF granules
 so my advice might not be 100% accurate but I hope it helps anyway.

 Firstly, your schema seems wrong to me: you have two types specified
 for ingestion - java.util.Date and a Double after that. Perhaps another
 attribute of double type is missing or the :Double part should be deleted.

 Otherwise, I recommend using indexer.xml instead of indexer.properties
 for configuration. In your case it might look like this:

 
 

   
  ingestion<
 /attribute>
   


   
 *the_geom:Polygon,location:String,ingestion:java
 .util.Date
   


   
  your_coverage_name
  
  
 
  
   


   
  
 regex=([0-9]{14}),format=MMddHHmmss,fullPath=true
  TimestampFileNameExtractorSPI
  ingestion
   


 
 
 
 >>> value="/path/to/directory/to/be/indexed" />
 
 
 
 
 
 Usually my ImageMosaic folder structure is like this (
 /opt/geoserver_data is the GEOSERVER_DATA_DIR)
 * the indexer.xml and datastore.properties files are in a
 /opt/geoserver_data/data/
 * there is a subdirectory, usually with a date tree structure for
 storing granules from separate days in separate directories:
 /opt/geoserver_data/data//tiff//M
 M/DD/some_file_MMDDHHmss.tiff
 * in indexer.xml I have *Recursive *parameter set to
 *true ** I usually use absolute path to the tiff directory as
 *IndexingDirectories* parameter value,

Re: [Geoserver-users] ImagePyramid using Postgresql for granules

2017-10-02 Thread Darell van der Voort

Hello Daniele,

Thank you for your input! I now use a schema per workspace, but creating a
schema per imagepyramid would indeed solve the problem of duplicate table
names. So do I understand correctly that there is no possibility to change
the table names? For example to: schema.imagepyramid0, schema.imagepyramid1
etc. In which schema is the unique workspace schema and imagepyramid is the
name of the layer. Thank you!

Kind regards,
Darell

On Mon, Oct 2, 2017 at 11:19 AM, Daniele Romagnoli <
daniele.romagn...@geo-solutions.it> wrote:

> Hi Darell,
> as you said, the imagePyramid is basically a set of imageMosaics: an
> ImageMosaic for each pyramid level.
> Therefore, each level should have its own indexer and, optionally, a
> datastore.properties if you want to catalog the granules into a DB instead
> of default shapefile.
>
> When using DB instead of shapefile, you may want to use a single database
> (as an instance, "pyramid") and store each level granule's index into a
> different schema name. Therefore, the datastore.properties of each level
> should define a different schema name, as an instance:
>
> pyramid/0/datastore.properties contains a "schema=level0" property
> pyramid/1/datastore.properties contains a "schema=level1" property
> pyramid/2/datastore.properties contains a "schema=level2" property
>
> Note that you should create the schemas (with "CREATE SCHEMA levelx" sql
> statements) in advance on your DB, before configuring the imagePyramid
> store in GeoServer.
>
> Hope this helps.
> Regards,
> Daniele
>
>
>
>
>
> On Mon, Oct 2, 2017 at 10:54 AM, Darell van der Voort  > wrote:
>
>> Hi Peter,
>>
>> Thank you for the examples, very helpful! Using a indexer.xml indeed
>> seems like a better set-up. Have you ever tried this in combination with
>> the imagepyramid plugin? I know that the imagepyramid are basically just
>> imagemoasics per folder level. However as the folder structure is different
>> it causes some problems. My folder structure looks like:
>>
>> /geoserver/data/workspace//0/.tiffs
>> /geoserver/data/workspace//1/.tiffs
>> /geoserver/data/workspace//2/.tiffs
>> etc..
>>
>> Where the numbers stand for the pyramid levels which are filled with
>> multiple tiffs, the indexer.properties and the foldername.properties. I put
>> tiffs from different dates in the same folder and use a unique date in the
>> filename. Should I put the indexer.xml and datastore.properties in each
>> pyramid directory? I can try it later this week and will let you know if it
>> works.
>>
>> Kind regards,
>> Darell
>>
>> On Fri, Sep 29, 2017 at 11:43 AM, Peter Kovac <
>> peter.ko...@microstep-mis.com> wrote:
>>
>>> I usually configure ImageMosaic for time-series plain GeoTIFF granules
>>> so my advice might not be 100% accurate but I hope it helps anyway.
>>>
>>> Firstly, your schema seems wrong to me: you have two types specified for
>>> ingestion - java.util.Date and a Double after that. Perhaps another
>>> attribute of double type is missing or the :Double part should be deleted.
>>>
>>> Otherwise, I recommend using indexer.xml instead of indexer.properties
>>> for configuration. In your case it might look like this:
>>>
>>> 
>>> 
>>>
>>>   
>>>  ingestion<
>>> /attribute>
>>>   
>>>
>>>
>>>   
>>> *the_geom:Polygon,location:String,ingestion:java
>>> .util.Date
>>>   
>>>
>>>
>>>   
>>>  your_coverage_name
>>>  
>>>  
>>> 
>>>  
>>>   
>>>
>>>
>>>   
>>>  
>>> regex=([0-9]{14}),format=MMddHHmmss,fullPath=true
>>>  TimestampFileNameExtractorSPI
>>>  ingestion
>>>   
>>>
>>>
>>> 
>>> 
>>> 
>>> >> value="/path/to/directory/to/be/indexed" />
>>> 
>>> 
>>> 
>>> 
>>> 
>>> Usually my ImageMosaic folder structure is like this (
>>> /opt/geoserver_data is the GEOSERVER_DATA_DIR)
>>> * the indexer.xml and datastore.properties files are in a
>>> /opt/geoserver_data/data/
>>> * there is a subdirectory, usually with a date tree structure for
>>> storing granules from separate days in separate directories:
>>> /opt/geoserver_data/data//tiff//M
>>> M/DD/some_file_MMDDHHmss.tiff
>>> * in indexer.xml I have *Recursive *parameter set to
>>> *true ** I usually use absolute path to the tiff directory as
>>> *IndexingDirectories* parameter value, e.g.
>>> /opt/geoserver_data/data//tiff
>>>
>>> Finally, if I encounter any problems during ImageMosaic creation I
>>> ensure to:
>>> * set GeoServer logging to VERBOSE
>>> * drop any database table created (ImageMosaic will refuse to create
>>> store if a table with the same name already exists), along with index and
>>> metadata (if using Oracle)
>>> * try it again and look into the log (usually the problem is not
>>> revealed in the last stacktrace in the log, but in some before last)
>>> * if it doesn't help or I still cannot figure out what

[Geoserver-users] GetFeatureInfo changes date value

2017-10-02 Thread Per Reinholdt

Hi

If you sent a GetFeatureInfo-request to a layer that have a column with the 
date-format in a PostGisDatabase, Geoserver sometimes add a time to the date. 
This is a problem when it is changed into UTC-time and the date is changed 
which happens with json.

INFO_FORMAT

result

text/html

2017-06-01 00:00

text/plain

2017-06-01

text/xml

2017-06-01

application/vnd.ogc.gml

2017-06-01

application/json

2017-05-31Z


Postgis (date)

2017-06-01



Best Regards

Per

--
Per Reinholdt
GIS-konsult

Metria
Postadress: Box 851, 971 26 Luleå
Gatuadress: Stationsgatan 7A, 972 38 Luleå
Telefon 010-121 81 52 * Växel 010-121 80 00
per.reinho...@metria.se * 
www.metria.se

[cid:image001.png@01D33B6F.A30C3050]





Metria - experter på geografisk information




--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
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

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

Re: [Geoserver-users] ImagePyramid using Postgresql for granules

2017-10-02 Thread Daniele Romagnoli

Hi Darell,
as you said, the imagePyramid is basically a set of imageMosaics: an
ImageMosaic for each pyramid level.
Therefore, each level should have its own indexer and, optionally, a
datastore.properties if you want to catalog the granules into a DB instead
of default shapefile.

When using DB instead of shapefile, you may want to use a single database
(as an instance, "pyramid") and store each level granule's index into a
different schema name. Therefore, the datastore.properties of each level
should define a different schema name, as an instance:

pyramid/0/datastore.properties contains a "schema=level0" property
pyramid/1/datastore.properties contains a "schema=level1" property
pyramid/2/datastore.properties contains a "schema=level2" property

Note that you should create the schemas (with "CREATE SCHEMA levelx" sql
statements) in advance on your DB, before configuring the imagePyramid
store in GeoServer.

Hope this helps.
Regards,
Daniele





On Mon, Oct 2, 2017 at 10:54 AM, Darell van der Voort 
wrote:

> Hi Peter,
>
> Thank you for the examples, very helpful! Using a indexer.xml indeed seems
> like a better set-up. Have you ever tried this in combination with the
> imagepyramid plugin? I know that the imagepyramid are basically just
> imagemoasics per folder level. However as the folder structure is different
> it causes some problems. My folder structure looks like:
>
> /geoserver/data/workspace//0/.tiffs
> /geoserver/data/workspace//1/.tiffs
> /geoserver/data/workspace//2/.tiffs
> etc..
>
> Where the numbers stand for the pyramid levels which are filled with
> multiple tiffs, the indexer.properties and the foldername.properties. I put
> tiffs from different dates in the same folder and use a unique date in the
> filename. Should I put the indexer.xml and datastore.properties in each
> pyramid directory? I can try it later this week and will let you know if it
> works.
>
> Kind regards,
> Darell
>
> On Fri, Sep 29, 2017 at 11:43 AM, Peter Kovac <
> peter.ko...@microstep-mis.com> wrote:
>
>> I usually configure ImageMosaic for time-series plain GeoTIFF granules so
>> my advice might not be 100% accurate but I hope it helps anyway.
>>
>> Firstly, your schema seems wrong to me: you have two types specified for
>> ingestion - java.util.Date and a Double after that. Perhaps another
>> attribute of double type is missing or the :Double part should be deleted.
>>
>> Otherwise, I recommend using indexer.xml instead of indexer.properties
>> for configuration. In your case it might look like this:
>>
>> 
>> 
>>
>>   
>>  ingestion<
>> /attribute>
>>   
>>
>>
>>   
>> *the_geom:Polygon,location:String,ingestion:java
>> .util.Date
>>   
>>
>>
>>   
>>  your_coverage_name
>>  
>>  
>> 
>>  
>>   
>>
>>
>>   
>>  
>> regex=([0-9]{14}),format=MMddHHmmss,fullPath=true
>>  TimestampFileNameExtractorSPI
>>  ingestion
>>   
>>
>>
>> 
>> 
>> 
>> > value="/path/to/directory/to/be/indexed" />
>> 
>> 
>> 
>> 
>> 
>> Usually my ImageMosaic folder structure is like this (/opt/geoserver_data
>> is the GEOSERVER_DATA_DIR)
>> * the indexer.xml and datastore.properties files are in a
>> /opt/geoserver_data/data/
>> * there is a subdirectory, usually with a date tree structure for storing
>> granules from separate days in separate directories:
>> /opt/geoserver_data/data//tiff//
>> MM/DD/some_file_MMDDHHmss.tiff
>> * in indexer.xml I have *Recursive *parameter set to
>> *true ** I usually use absolute path to the tiff directory as
>> *IndexingDirectories* parameter value, e.g.
>> /opt/geoserver_data/data//tiff
>>
>> Finally, if I encounter any problems during ImageMosaic creation I ensure
>> to:
>> * set GeoServer logging to VERBOSE
>> * drop any database table created (ImageMosaic will refuse to create
>> store if a table with the same name already exists), along with index and
>> metadata (if using Oracle)
>> * try it again and look into the log (usually the problem is not revealed
>> in the last stacktrace in the log, but in some before last)
>> * if it doesn't help or I still cannot figure out what is wrong I launch
>> Eclipse debugger and examine what EXACTLY is wrong (I used it a lot until I
>> figured out how to properly configure time parsing regexes)
>>
>> Regards,
>>
>> Peter Kovac
>>
>>
>>
>> On 29. 9. 2017 10:40, Darell van der Voort wrote:
>>
>> Hi Peter,
>>
>> This is my indexer.properties configuration:
>>
>> Caching=false
>> TimeAttribute=ingestion
>> Schema=*the_geom:Polygon,location:String,ingestion:java.util.Date:Double
>> PropertyCollectors=TimestampFileNameExtractorSPI[timeregex](ingestion)
>>
>> And this is my 0.properties which is automatically generated for the
>> lowest zoomlevel (0):
>>
>> #-Automagically created from GeoTools-
>> #Wed Sep 27 14:50:18 UTC

Re: [Geoserver-users] ImagePyramid using Postgresql for granules

2017-10-02 Thread Darell van der Voort

Hi Peter,

Thank you for the examples, very helpful! Using a indexer.xml indeed seems
like a better set-up. Have you ever tried this in combination with the
imagepyramid plugin? I know that the imagepyramid are basically just
imagemoasics per folder level. However as the folder structure is different
it causes some problems. My folder structure looks like:

/geoserver/data/workspace//0/.tiffs
/geoserver/data/workspace//1/.tiffs
/geoserver/data/workspace//2/.tiffs
etc..

Where the numbers stand for the pyramid levels which are filled with
multiple tiffs, the indexer.properties and the foldername.properties. I put
tiffs from different dates in the same folder and use a unique date in the
filename. Should I put the indexer.xml and datastore.properties in each
pyramid directory? I can try it later this week and will let you know if it
works.

Kind regards,
Darell

On Fri, Sep 29, 2017 at 11:43 AM, Peter Kovac  wrote:

> I usually configure ImageMosaic for time-series plain GeoTIFF granules so
> my advice might not be 100% accurate but I hope it helps anyway.
>
> Firstly, your schema seems wrong to me: you have two types specified for
> ingestion - java.util.Date and a Double after that. Perhaps another
> attribute of double type is missing or the :Double part should be deleted.
>
> Otherwise, I recommend using indexer.xml instead of indexer.properties for
> configuration. In your case it might look like this:
>
> 
> 
>
>   
>  ingestion<
> /attribute>
>   
>
>
>   
> *the_geom:Polygon,location:String,ingestion:
> java.util.Date
>   
>
>
>   
>  your_coverage_name
>  
>  
> 
>  
>   
>
>
>   
>  
> regex=([0-9]{14}),format=MMddHHmmss,fullPath=true
>  TimestampFileNameExtractorSPI
>  ingestion
>   
>
>
> 
> 
> 
>  value="/path/to/directory/to/be/indexed"
> />
> 
> 
> 
> 
> 
> Usually my ImageMosaic folder structure is like this (/opt/geoserver_data
> is the GEOSERVER_DATA_DIR)
> * the indexer.xml and datastore.properties files are in a
> /opt/geoserver_data/data/
> * there is a subdirectory, usually with a date tree structure for storing
> granules from separate days in separate directories:
> /opt/geoserver_data/data//tiff/
> /MM/DD/some_file_MMDDHHmss.tiff
> * in indexer.xml I have *Recursive *parameter set to
> *true ** I usually use absolute path to the tiff directory as
> *IndexingDirectories* parameter value, e.g. /opt/geoserver_data/data/<
> IMAGEMOSAIC_DIRECTORY>/tiff
>
> Finally, if I encounter any problems during ImageMosaic creation I ensure
> to:
> * set GeoServer logging to VERBOSE
> * drop any database table created (ImageMosaic will refuse to create store
> if a table with the same name already exists), along with index and
> metadata (if using Oracle)
> * try it again and look into the log (usually the problem is not revealed
> in the last stacktrace in the log, but in some before last)
> * if it doesn't help or I still cannot figure out what is wrong I launch
> Eclipse debugger and examine what EXACTLY is wrong (I used it a lot until I
> figured out how to properly configure time parsing regexes)
>
> Regards,
>
> Peter Kovac
>
>
>
> On 29. 9. 2017 10:40, Darell van der Voort wrote:
>
> Hi Peter,
>
> This is my indexer.properties configuration:
>
> Caching=false
> TimeAttribute=ingestion
> Schema=*the_geom:Polygon,location:String,ingestion:java.util.Date:Double
> PropertyCollectors=TimestampFileNameExtractorSPI[timeregex](ingestion)
>
> And this is my 0.properties which is automatically generated for the
> lowest zoomlevel (0):
>
> #-Automagically created from GeoTools-
> #Wed Sep 27 14:50:18 UTC 2017
> MosaicCRS=EPSG\:32617
> Levels=0.062,0.062
> Heterogeneous=false
> TimeAttribute=ingestion
> AbsolutePath=false
> Name=0
> TypeName=0
> Caching=false
> ExpandToRGB=false
> LocationAttribute=location
> SuggestedSPI=it.geosolutions.imageioimpl.plugins.tiff.TIFFImageReaderSpi
> CheckAuxiliaryMetadata=false
> LevelsNum=1
>
> So like I said, the plugin automatically configures level 0 to the
> PostgreSQL DB if I add the datastore.properties files, but refuses to do so
> for other levels if I add the datastore.properties file to the folder
> levels. If I do not add the datastore.properties file to the additional
> levels, the plugin automatically creates a shapefile for these levels,
> while using the DB connection for level 0. This combination works, even
> with a time dimension. However I would like to use the DB connection for
> all levels and use unique table names in the DB.
>
> Kind regards,
> Darell
>
>
>
>
> On Fri, Sep 29, 2017 at 9:59 AM, Peter Kovac <
> peter.ko...@microstep-mis.com> wrote:
>
>> Hi Darell,
>>
>> can you post your indexer.xml configuration for the imagemosaic?
>>
>> Regards,
>>
>> Peter Kovac
>>
>> On 28. 9. 2017 9:59,

[Geoserver-users] cascading WMTS over HTTPS

Re: [Geoserver-users] ImagePyramid using Postgresql for granules

Re: [Geoserver-users] ImagePyramid using Postgresql for granules

[Geoserver-users] GetFeatureInfo changes date value

Re: [Geoserver-users] ImagePyramid using Postgresql for granules

Re: [Geoserver-users] ImagePyramid using Postgresql for granules

6 matches

Site Navigation

Mail list logo

Footer information