[Geoserver-users] Exception Error - ctl:SchematronValidatingParser type Mandatory default result

[Dipak Gupta]

Hi Geoserver Team,
I installed geoserver 2.14.0 version and whenever I am executing
OGC(CSW-2.0.2) test suite it will giving

  Error 1: assertion failed:
  The exception report must have @version = "1.2.0".
  The reported version number is 1.0.0.

Please Help me what am I doing wrong?


-- 
Dipak Gupta
Associate IT Developer
Ph no.- +917587113200
___
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

[Geoserver-users] geoserver doesn't render features at certain zooms

[cowo123456]

hi, 
im using geoserver 2.11.0, with elasticsearch as datasource. 
i also use leaflet vector tiles plugin to request the tiles. 

i have noticed that when use leaflet map controller, in certain zooms the
geoserver doesn't return all geometries (in deeper zoom it shows more
geometries). 
i checked with wireshark the result the geoserver recieves from
elasticsearch, and it recieves the same geometries in both zoom levels. 
i wondered if there is some configuration that determine whether the
geoserver "ignore" geometries in low zoom to simplify the response ? 


any ideas how to solve my problem ?



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


___
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

Re: [Geoserver-users] 16bit image rendering problem

[Simone Giannecchini]

Ciao Pedro,
I don't see anything strange from this info.
You might want to make this geotiff available for us to have a look at
(if/when we have time :) ).

Regards,
Simone Giannecchini
==
GeoServer Professional Services from the experts!
Visit http://goo.gl/it488V for more information.
==
Ing. Simone Giannecchini
@simogeo
Founder/Director

GeoSolutions S.A.S.
Via di Montramito 3/A
55054  Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob:   +39  333 8128928

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.


On Wed, Oct 31, 2018 at 4:15 PM Briones Garcia, Pedro  wrote:

> Hi, Simone.
>
>
>
> The style:
>
> **
>
> * xmlns="http://www.opengis.net/sld "
> xmlns:gml="http://www.opengis.net/gml "
> xmlns:ogc="http://www.opengis.net/ogc "
> xmlns:sld="http://www.opengis.net/sld ">*
>
> **
>
> **
>
> **
>
> **
>
> **
>
> *PrecipAnual-2016i*
>
> **
>
> **
>
> **
>
> **
>
> **
>
> **
>
> *grid*
>
> **
>
> *1*
>
> **
>
> * label="279.00" opacity="1.0" quantity="279"/>*
>
> * label="463.21" opacity="1.0" quantity="463.21"/>*
>
> * label="647.42" opacity="1.0" quantity="647.42"/>*
>
> * label="831.63" opacity="1.0" quantity="831.63"/>*
>
> * label="1015.84" opacity="1.0" quantity="1015.84"/>*
>
> * label="1200.05" opacity="1.0" quantity="1200.05"/>*
>
> * label="1384.26" opacity="1.0" quantity="1384.26"/>*
>
> * label="1554.30" opacity="1.0" quantity="1554.3"/>*
>
> * label="1696.00" opacity="1.0" quantity="1696"/>*
>
> **
>
> **
>
> **
>
> **
>
> **
>
> **
>
> **
>
>
>
> And gdalinfo output:
>
> *Driver: GTiff/GeoTIFF*
>
> *Files: C:\Procesos_TMP\SIAR_Teledeteccion\PrecipAnual-2016i.tif*
>
> *Size is 107809, 88498*
>
> *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,*
>
> *AUTHORITY["EPSG","8901"]],*
>
> *UNIT["degree",0.0174532925199433,*
>
> *AUTHORITY["EPSG","9122"]],*
>
> *AUTHORITY["EPSG","4326"]],*
>
> *PROJECTION["Transverse_Mercator"],*
>
> *PARAMETER["latitude_of_origin",0],*
>
> *PARAMETER["central_meridian",-3],*
>
> *PARAMETER["scale_factor",0.9996],*
>
> *PARAMETER["false_easting",50],*
>
> *PARAMETER["false_northing",0],*
>
> *UNIT["metre",1,*
>
> *AUTHORITY["EPSG","9001"]],*
>
> *AXIS["Easting",EAST],*
>
> *AXIS["Northing",NORTH],*
>
> *AUTHORITY["EPSG","32630"]]*
>
> *Origin = (-37200.5897000,4880153.3210050)*
>
> *Pixel Size = (10.000,-10.000)*
>
> *Metadata:*
>
> *  AREA_OR_POINT=Area*
>
> *  Band_1=Mosaic (Band 1)*
>
> *Image Structure Metadata:*
>
> *  INTERLEAVE=BAND*
>
> *Corner Coordinates:*
>
> *Upper Left  (  -37200.590, 4880153.321) (  9d41'10.33"W, 43d52'42.55"N)*
>
> *Lower Left  (  -37200.590, 3995173.321) (  8d57'12.87"W, 35d57'11.34"N)*
>
> *Upper Right ( 1040889.410, 4880153.321) (  3d43'54.49"E, 43d52'32.87"N)*
>
> *Lower Right ( 1040889.410, 3995173.321) (  2d59'39.32"E, 35d57' 4.03"N)*
>
> *Center  (  501844.410, 

Re: [Geoserver-users] 16bit image rendering problem

[Briones Garcia, Pedro]

Hi, Simone.

The style:

http://www.opengis.net/sld; 
xmlns:gml="http://www.opengis.net/gml; xmlns:ogc="http://www.opengis.net/ogc; 
xmlns:sld="http://www.opengis.net/sld;>





PrecipAnual-2016i






grid

1


















And gdalinfo output:
Driver: GTiff/GeoTIFF
Files: C:\Procesos_TMP\SIAR_Teledeteccion\PrecipAnual-2016i.tif
Size is 107809, 88498
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,
AUTHORITY["EPSG","8901"]],
UNIT["degree",0.0174532925199433,
AUTHORITY["EPSG","9122"]],
AUTHORITY["EPSG","4326"]],
PROJECTION["Transverse_Mercator"],
PARAMETER["latitude_of_origin",0],
PARAMETER["central_meridian",-3],
PARAMETER["scale_factor",0.9996],
PARAMETER["false_easting",50],
PARAMETER["false_northing",0],
UNIT["metre",1,
AUTHORITY["EPSG","9001"]],
AXIS["Easting",EAST],
AXIS["Northing",NORTH],
AUTHORITY["EPSG","32630"]]
Origin = (-37200.5897000,4880153.3210050)
Pixel Size = (10.000,-10.000)
Metadata:
  AREA_OR_POINT=Area
  Band_1=Mosaic (Band 1)
Image Structure Metadata:
  INTERLEAVE=BAND
Corner Coordinates:
Upper Left  (  -37200.590, 4880153.321) (  9d41'10.33"W, 43d52'42.55"N)
Lower Left  (  -37200.590, 3995173.321) (  8d57'12.87"W, 35d57'11.34"N)
Upper Right ( 1040889.410, 4880153.321) (  3d43'54.49"E, 43d52'32.87"N)
Lower Right ( 1040889.410, 3995173.321) (  2d59'39.32"E, 35d57' 4.03"N)
Center  (  501844.410, 4437663.321) (  2d58'42.11"W, 40d 5'21.30"N)
Band 1 Block=107809x1 Type=Int16, ColorInterp=Gray
  Description = Mosaic (Band 1)
  Minimum=172.000, Maximum=2450.000, Mean=570.734, StdDev=280.509
  NoData Value=0
  Metadata:
STATISTICS_MAXIMUM=2450
STATISTICS_MEAN=570.73436824794
STATISTICS_MINIMUM=172
STATISTICS_STDDEV=280.50861764515

Thanks.

Un saludo.
[http://www.tragsa.es/SiteCollectionImages/Relaciones%20Institucionales%20(Prensa)/FIRMA%20OUTLOOK/Tragsatec.png]

[http://www.tragsa.es/SiteCollectionImages/Relaciones%20Institucionales%20(Prensa)/FIRMA%20OUTLOOK/cenefa.png]

Briones Garcia, Pedro
Grupo Tragsa - SEPI

[http://www.tragsa.es/SiteCollectionImages/Relaciones%20Institucionales%20(Prensa)/FIRMA%20OUTLOOK/Tragsatec_SEPI.png]

Calle Julián Camarillo 6B - 28037 Madrid
Tel.: 913226489 - 88216 - Fax: 913226005
p...@tragsa.es
www.tragsa.es 


En beneficio del medio ambiente, imprime este e-mail sólo si realmente es 
necesario
For the benefit of the environment, print this e-mail only if you really need to


De: Simone Giannecchini [mailto:simone.giannecch...@geo-solutions.it]
Enviado el: miércoles, 31 de octubre de 2018 14:47
Para: Briones Garcia, Pedro 
CC: geoserver-users 
Asunto: Re: [Geoserver-users] 16bit image rendering problem

Dear Pedro,
we need to see the styles and the output of gdalinfo --stats on this image 
before saying anything.
Can you provide them?

Regards,
Simone Giannecchini
==
GeoServer Professional Services from the experts!
Visit http://goo.gl/it488V for more information.
==
Ing. Simone Giannecchini
@simogeo
Founder/Director

GeoSolutions S.A.S.
Via di Montramito 3/A
55054  Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob:   +39  333 8128928

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 

Re: [Geoserver-users] ImagePyramid layer black when no granule at all

[Rahkonen Jukka (MML)]

Hi,

May not be related to just this case, but if image mosaic is built from images 
having different CRS then the calculated levels in the .properties file may 
need manual fix. For example, if coverage is published in EPSG:3067 but 
originals are either in EPSG:2393 or EPSG:3067, both having pixel size of 0.50 
m in the native CRS, then the .properties file may get populated with levels 
like
Levels=0.4997989782761352

That is 0.50 m in EPSG:2393 projected into EPSG:3067. I suppose that Geoserver 
generates levels by the first images it reads. Only way to fix the resolutions 
is to edit the .properties file directly but Geoserver tends to write over the 
level values when the index is updated.

-Jukka Rahkonen-

Lähettäjä: Andrea Aime [mailto:andrea.a...@geo-solutions.it]
Lähetetty: 31. lokakuuta 2018 16:11
Vastaanottaja: arnaud.lis...@codata.eu
Kopio: GeoServer Mailing List List 
Aihe: Re: [Geoserver-users] ImagePyramid layer black when no granule at all

Hi Arnaud,
I don't know what's happening there honestly, the property files that GeoServer
generates normally match the gdalinfo output... but I haven't worked with a 
simple, uniform
mosaic in a while (most of what comes my way these days is either heterogeneous 
in resolutions
or has downright different coordinate reference systems).

Can you share the entire generated property file? How many geotiffs do you have 
in it, any
chance one out of many has the resolution being reported?

Cheers
Andrea


On Wed, Oct 31, 2018 at 2:59 PM Arnaud L. 
mailto:arnaud.lis...@codata.eu>> wrote:
Le 31/10/2018 à 14:03, Andrea Aime a écrit :
> No, you are still supposed to let the mosaic configure itself. Never,
> ever, generate
> the mosaic property file manually, setup a indexer and a datastore
> config files
> and let the mosaic do its work, regardless of where the index is stored.

OK Andrea, thanks for making this clear.
I did as suggested :
- copied only the datastore.properties in a folder
- added an indexer.properties in the same folder, basic configuration
taken from
https://geoserver.geo-solutions.it/edu/en/multidim/imagemosaic/mosaic_indexer.html,
i.e.:
Name=georasters_17
Schema=*the_geom:Polygon,location:String
PropertyCollectors=
Caching=false
AbsolutePath=true
CanBeEmpty=true
UseExistingSchema=true
- created a new imagemosaic datastore pointing to this folder

Everything went fine, mosaic "georasters_17.properties" and
"sample_image.dat" created successfully.
Now, comparing this properties file with the one I created manually,
there is one major difference (and some minor ones like expandToRGB),
Levels!
In the automatically created file :
Levels=2.54,2.54
In my file, where I computed the levels myself :
Levels=0.15875,0.15875

The "correct" one, i.e. the one that renders correctly is mine.
Gdalinfo on the underlying GeoTIFFs gives the correct pixelsize, i.e :
Pixel Size = (0.1587500,-0.1587500)

Why would the imagemosaic plugin guess that levels are 2.54 ? Is there
something wrong in the way I configured the imagemosaic ?



Best regards
--
Arnaud



--

Regards, Andrea Aime == GeoServer Professional Services from the experts! Visit 
http://goo.gl/it488V for more information. == Ing. Andrea Aime @geowolf 
Technical Lead GeoSolutions S.A.S. Via di Montramito 3/A 55054 Massarosa (LU) 
phone: +39 0584 962313 fax: +39 0584 1660272 mob: +39 339 8844549 
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: 

Re: [Geoserver-users] ImagePyramid layer black when no granule at all

[Arnaud L.]

Le 31/10/2018 à 15:21, Andrea Aime a écrit :

Hum.. I cannot exclude it (but I'm not sure without checking the code).
Did you provide a TypeName in the indexer, to tell the mosaic which 
table to use? Wondering if doing so might convince it to actually use 
the table in question.


No, indeed. Excellent suggestion, because the first table it might 
encounter with the correct schema (i.e. location and the_geom fields) is 
the index for a 2.54 level mosaic !

I added the TypeName, and lo!, levels are correct !

Thanks a lot Andrea !

Best regards
--
Arnaud


___
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

Re: [Geoserver-users] ImagePyramid layer black when no granule at all

[Andrea Aime]

On Wed, Oct 31, 2018 at 3:16 PM Arnaud L.  wrote:

> OK, I have a guess.
> In the FOLDER referenced by the index there are some GeoTIFFs whose
> level is 2.54.
> None of these GeoTIFFs are referenced in the index though.
> Could it be that the imagemosaic plugin does a scan on the entire
> folder, even though I have set UseExistingSchema=true ?
>

Hum.. I cannot exclude it (but I'm not sure without checking the code).
Did you provide a TypeName in the indexer, to tell the mosaic which table
to use? Wondering if doing so might convince it to actually use the table
in question.

Cheers
Andrea

==

GeoServer Professional Services from the experts! Visit http://goo.gl/it488V
for more information. == Ing. Andrea Aime @geowolf Technical Lead
GeoSolutions S.A.S. Via di Montramito 3/A 55054 Massarosa (LU) phone: +39
0584 962313 fax: +39 0584 1660272 mob: +39 339 8844549
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

Re: [Geoserver-users] ImagePyramid layer black when no granule at all

[Andrea Aime]

Hi Arnaud,
I don't know what's happening there honestly, the property files that
GeoServer
generates normally match the gdalinfo output... but I haven't worked with a
simple, uniform
mosaic in a while (most of what comes my way these days is either
heterogeneous in resolutions
or has downright different coordinate reference systems).

Can you share the entire generated property file? How many geotiffs do you
have in it, any
chance one out of many has the resolution being reported?

Cheers
Andrea


On Wed, Oct 31, 2018 at 2:59 PM Arnaud L.  wrote:

> Le 31/10/2018 à 14:03, Andrea Aime a écrit :
> > No, you are still supposed to let the mosaic configure itself. Never,
> > ever, generate
> > the mosaic property file manually, setup a indexer and a datastore
> > config files
> > and let the mosaic do its work, regardless of where the index is stored.
>
> OK Andrea, thanks for making this clear.
> I did as suggested :
> - copied only the datastore.properties in a folder
> - added an indexer.properties in the same folder, basic configuration
> taken from
>
> https://geoserver.geo-solutions.it/edu/en/multidim/imagemosaic/mosaic_indexer.html,
>
> i.e.:
> Name=georasters_17
> Schema=*the_geom:Polygon,location:String
> PropertyCollectors=
> Caching=false
> AbsolutePath=true
> CanBeEmpty=true
> UseExistingSchema=true
> - created a new imagemosaic datastore pointing to this folder
>
> Everything went fine, mosaic "georasters_17.properties" and
> "sample_image.dat" created successfully.
> Now, comparing this properties file with the one I created manually,
> there is one major difference (and some minor ones like expandToRGB),
> Levels!
> In the automatically created file :
> Levels=2.54,2.54
> In my file, where I computed the levels myself :
> Levels=0.15875,0.15875
>
> The "correct" one, i.e. the one that renders correctly is mine.
> Gdalinfo on the underlying GeoTIFFs gives the correct pixelsize, i.e :
> Pixel Size = (0.1587500,-0.1587500)
>
> Why would the imagemosaic plugin guess that levels are 2.54 ? Is there
> something wrong in the way I configured the imagemosaic ?
>
>
>
> Best regards
> --
> Arnaud
>
>
>

-- 

Regards, Andrea Aime == GeoServer Professional Services from the experts!
Visit http://goo.gl/it488V for more information. == Ing. Andrea Aime
@geowolf Technical Lead GeoSolutions S.A.S. Via di Montramito 3/A 55054
Massarosa (LU) phone: +39 0584 962313 fax: +39 0584 1660272 mob: +39 339
8844549 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

Re: [Geoserver-users] ImagePyramid layer black when no granule at all

[Arnaud L.]

Le 31/10/2018 à 14:59, Arnaud L. a écrit :

Why would the imagemosaic plugin guess that levels are 2.54 ? Is there
something wrong in the way I configured the imagemosaic ?


OK, I have a guess.
In the FOLDER referenced by the index there are some GeoTIFFs whose 
level is 2.54.

None of these GeoTIFFs are referenced in the index though.
Could it be that the imagemosaic plugin does a scan on the entire 
folder, even though I have set UseExistingSchema=true ?


Best regards
--
Arnaud


___
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

Re: [Geoserver-users] ImagePyramid layer black when no granule at all

[Arnaud L.]

Le 31/10/2018 à 14:03, Andrea Aime a écrit :
No, you are still supposed to let the mosaic configure itself. Never, 
ever, generate
the mosaic property file manually, setup a indexer and a datastore 
config files

and let the mosaic do its work, regardless of where the index is stored.


OK Andrea, thanks for making this clear.
I did as suggested :
- copied only the datastore.properties in a folder
- added an indexer.properties in the same folder, basic configuration 
taken from 
https://geoserver.geo-solutions.it/edu/en/multidim/imagemosaic/mosaic_indexer.html, 
i.e.:

Name=georasters_17
Schema=*the_geom:Polygon,location:String
PropertyCollectors=
Caching=false
AbsolutePath=true
CanBeEmpty=true
UseExistingSchema=true
- created a new imagemosaic datastore pointing to this folder

Everything went fine, mosaic "georasters_17.properties" and 
"sample_image.dat" created successfully.
Now, comparing this properties file with the one I created manually, 
there is one major difference (and some minor ones like expandToRGB), 
Levels!

In the automatically created file :
Levels=2.54,2.54
In my file, where I computed the levels myself :
Levels=0.15875,0.15875

The "correct" one, i.e. the one that renders correctly is mine.
Gdalinfo on the underlying GeoTIFFs gives the correct pixelsize, i.e :
Pixel Size = (0.1587500,-0.1587500)

Why would the imagemosaic plugin guess that levels are 2.54 ? Is there 
something wrong in the way I configured the imagemosaic ?




Best regards
--
Arnaud




___
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

[Geoserver-users] Database views referencing other databases

[Paul Wittle via Geoserver-users]

Hi,

This is almost definitely really niche but I thought I'd send the message in 
case it is relevant for any reason. We have a view in our Oracle database which 
takes a spatial table (source of GeoServer store) and joins it with non-spatial 
data from another Oracle database which is not in our control. The view is slow 
as you would expect however it cannot be loaded into GeoServer because 
GeoServer is discovering the reference to an alternate database somehow. The 
reason I thought I'd email is that it does work if you view it in a viewer's 
such as Toad but it also works fine in other GIS capable applications such QGIS 
and FME.

Please note, the reference to the other database should be in the database view 
not an SQL view in GeoServer. I think it is logical that GeoServer may not 
accept that sort of thing but I'm confused by why GeoServer even knows the view 
is referencing another database, I would have expected it to just query the 
view in the source database and let the database handle the joins but I think 
it is something to do with the way GeoServer gets the metadata (although I'm 
guessing).

I'm hoping it would be easy to check in other database types, just create a 
view which references another database / schema and then see if the view can be 
published in GeoServer and rendered by QGIS.

It is probably too niche to log it as a bug and so I'm not necessarily 
expecting that we do anything but I thought I'd ask round to see if others can 
easily recreate the situation to see if it is just me as usual.

Best Regards,

Paul Wittle

"This e-mail is intended for the named addressee(s) only and may contain 
information about individuals or other sensitive information and should be 
handled accordingly. Unless you are the named addressee (or authorised to 
receive it for the addressee) you may not copy or use it, or disclose it to 
anyone else. If you have received this email in error, kindly disregard the 
content of the message and notify the sender immediately. Please be aware that 
all email may be subject to recording and/or monitoring in accordance with 
relevant legislation."
___
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

Re: [Geoserver-users] 16bit image rendering problem

[Simone Giannecchini]

Dear Pedro,
we need to see the styles and the output of gdalinfo --stats on this image
before saying anything.
Can you provide them?

Regards,
Simone Giannecchini
==
GeoServer Professional Services from the experts!
Visit http://goo.gl/it488V for more information.
==
Ing. Simone Giannecchini
@simogeo
Founder/Director

GeoSolutions S.A.S.
Via di Montramito 3/A
55054  Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob:   +39  333 8128928

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.


On Wed, Oct 31, 2018 at 12:41 PM Briones Garcia, Pedro 
wrote:

> Hi all.
>
>
>
> I’m having problems rendering a *16 bit GeoTIFF image* in GeoServer. I’ve
> created an SLD and I’ve associated it with the image, but the colors don’t
> correspond to the ones of the SLD. Looking for information in this list, I
> found that the GeoTIFF is stretched to 8 bits before being rendered by
> GeoServer. I’ve tried too  option, but I get an error.
> I can’t convert the image to 8 bit because I have values greater than 255.
>
>
>
> Is there any workaround?
>
>
>
> Thanks in advance.
>
>
>
> [image:
> http://www.tragsa.es/SiteCollectionImages/Relaciones%20Institucionales%20(Prensa)/FIRMA%20OUTLOOK/Tragsatec.png]
>
> [image:
> http://www.tragsa.es/SiteCollectionImages/Relaciones%20Institucionales%20(Prensa)/FIRMA%20OUTLOOK/cenefa.png]
>
> *Briones Garcia, Pedro *
> JGAP Sist Inform Geográfica
> S.Información Geográfica / G.Sist.Inf. Geografica
>
> Grupo Tragsa - SEPI
>
> [image:
> http://www.tragsa.es/SiteCollectionImages/Relaciones%20Institucionales%20(Prensa)/FIRMA%20OUTLOOK/Tragsatec_SEPI.png]
>
> Calle Julián Camarillo 6B - 28037 Madrid
> Tel.: 913226489 - 88216 - Fax: 913226005
> p...@tragsa.es
> *www.tragsa.es * 
>
>
> En beneficio del medio ambiente, imprime este e-mail sólo si realmente es
> necesario
> For the benefit of the environment, print this e-mail only if you really
> need to
>
>
>
>
>
>
> *--
> **
> El consumo de papel es perjudicial para el medio ambiente. Por favor,
> téngalo en cuenta antes de imprimir este mensaje. AVISO LEGAL: Este mensaje
> y sus anexos pueden contener información confidencial o legalmente
> protegida. Está dirigido únicamente a la persona o entidad indicada como
> destinatarios del mensaje. Si este mensaje le hubiera llegado por error,
> por favor elimínelo sin revisarlo ni reenviarlo y notifíquelo
> inmediatamente al remitente.
> **
> --*
> ___
> 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
>
___
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

Re: [Geoserver-users] Sub-layer-level security

[Andrea Aime]

On Mon, Oct 29, 2018 at 12:45 PM Nanaso via Geoserver-users <
geoserver-users@lists.sourceforge.net> wrote:

> Hi,
> Thanks a lot Nuno for your reply.
> There are two issues:
> 1- The Geofence extention can satisfy my needs in the following way: I
> have an attribute in my layer called "user_name", I can check if the logged
> in username equals to this attribute, then I will allow the logged in user
> to access this feature, and vise versa.
> The problem is how to get the current logged in username. Is there an
> environment varaible that holds the current logged in user?
>

You can use the GSUSER environment variable, to be extracted caling
env('GSUSER') in a CQL filter


>
> 2- The other issue is regarding installation of Geofence. I've tried to
> install version 13 of Geofence extention in a Geoserver of version 13, it
> works fine, but the place where I should enter the CQL filter is not exist.
> According to the documentation:
>
> https://docs.geoserver.org/stable/en/user/community/geofence-server/gui.html#rule-page
>

I can't remember which version it got in, but those filters can only be
placed in a LIMIT type rule, not in a ACCEPT or DENY one.


> There should be a place to specify the CQL fitler for read and write. But
> it looks like this part of the configuration doesn't exist in version 13 of
> Geofence.
> I've then tried to install verison 14 of Geofence in a veriosn 14 of
> Geoserver, but the server failed to launch with many exceptions. My machine
> is Mac OS High Sierra. And here you're the exceptions I recieve when
> launching geoserver after adding Geofence to it:
>
> 29 Oct 14:31:44 WARN [geoserver.config] - Error reading resource
> ServletContext resource [/${geofence-ovr}]
> java.io.FileNotFoundException: ServletContext resource [/${geofence-ovr}]
> cannot be resolved to absolute file path - web application archive not
> expanded?
>

Unsure about this one, Alessio (cc'ed) do you know?


> org.springframework.beans.factory.CannotLoadBeanClassException: Error
> loading class [org.geoserver.monitor.hib.HibernateMonitorDAO2] for bean
> with name 'hibMonitorDAO' defined in URL
> [jar:file:/Volumes/MyData/projects/GIS/the_proj/temp/geoserver-2.14.0/webapps/geoserver/WEB-INF/lib/gs-monitor-hibernate-2.14-SNAPSHOT.jar!/applicationContext-hib2.xml]:
> problem with class file or dependent class; nested exception is
> java.lang.NoClassDefFoundError: org/geoserver/monitor/MonitorDAO
>

The hibernate monitoring was dropped down to community status due to lack
of maintainer in 2.14.x, and has been removed from the
build completely in 2.15.x (the module broke due to other updates, with no
maintainer the was no other choice but to kill it).
I'd advise against using it (or else, find someone that wants to maintain
the module and resurrect it, this would actually be even better ;-) )

Cheers
Andrea

==

GeoServer Professional Services from the experts! Visit http://goo.gl/it488V
for more information. == Ing. Andrea Aime @geowolf Technical Lead
GeoSolutions S.A.S. Via di Montramito 3/A 55054 Massarosa (LU) phone: +39
0584 962313 fax: +39 0584 1660272 mob: +39 339 8844549
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

Re: [Geoserver-users] Sub-layer-level security

[Stefan Overkamp]

Hi,

I don't think the WFS-Insert could resolve the postgresql function
current_setting().
You should insert your user data with SQL.

GeoServers SQL View can resolve current_setting() and can combine/join
it with your user data to return only records the current myapp.user
should see.

Regards,
Stefan


Am 31.10.2018 um 13:13 schrieb Nanaso:
> Hi,
> Thanks a lot Stefan for your perfect solution.
> I have tested what you mentioned and it works pretty fine. But there
> is one remaining issue. That is how to pass the current geoserver's
> username to the database? I've a field in the geometries table called
> "user_name". It should hold the owner of the record (the user that can
> view the record). I need to fill this field with the current geoserver
> username. How can I do that?
> I tried the following WFS request:
> 
>   
>  
>     http://www.opengis.net/gml;
> srsName="urn:ogc:def:crs:EPSG::4326">
>    21.958021949698434
> 14.533349892039715
>     
>  
>  city h
>  current_setting('myapp.user', TRUE)
>   
>    
> But it didn't substitute the username variable with its value.
>
> Can you help me how to do that using WFS, or whatever other solutions?
>
> Best regards,
> Nanaso
>
>
>
>
>
>
> Sent with ProtonMail  Secure Email.
>
> ‐‐‐ Original Message ‐‐‐
> On Wednesday, October 31, 2018 12:43 PM, Stefan Overkamp
>  wrote:
>
>> Hi,
>>
>> "Is it possible to decide which users can access which features in a
>> layer?"
>> I'm using the following solution for postgis datastore/layer:
>>
>>  *
>> set a Session startup SQL (and session close-up SQL) in the
>> datastore. This will set a variable with the current GeoServer user.
>> e.g. startup "SELECT set_config('myapp.user',
>> '${GSUSER,geoserver}', FALSE)
>> close-up "SELECT set_config('myapp.user', '', FALSE)
>>  *
>> create a sql view, restricting the returned records with the set
>> variable (current_setting('myapp.user', TRUE))
>> normally you would have an additional table in your database with
>> mapping of usernames to records/spatial entities
>>
>> Regards,
>> Stefan
>>
>>
>> Am 29.10.2018 um 12:36 schrieb Nanaso via Geoserver-users:
>>
>>> Hi,
>>> Thanks a lot Nuno for your reply.
>>> There are two issues:
>>> 1- The Geofence extention can satisfy my needs in the following way:
>>> I have an attribute in my layer called "user_name", I can check if
>>> the logged in username equals to this attribute, then I will allow
>>> the logged in user to access this feature, and vise versa.
>>> The problem is how to get the current logged in username. Is there
>>> an environment varaible that holds the current logged in user?
>>>
>>> 2- The other issue is regarding installation of Geofence. I've tried
>>> to install version 13 of Geofence extention in a Geoserver of
>>> version 13, it works fine, but the place where I should enter the
>>> CQL filter is not exist. According to the documentation:
>>> https://docs.geoserver.org/stable/en/user/community/geofence-server/gui.html#rule-page
>>> There should be a place to specify the CQL fitler for read and
>>> write. But it looks like this part of the configuration doesn't
>>> exist in version 13 of Geofence.
>>> I've then tried to install verison 14 of Geofence in a veriosn 14 of
>>> Geoserver, but the server failed to launch with many exceptions. My
>>> machine is Mac OS High Sierra. And here you're the exceptions I
>>> recieve when launching geoserver after adding Geofence to it:
>>
>> --
>> =
>> Dipl.Ing. Stefan Overkamp
>> tel: 02052 / 814184
>> mobil: 0177 / 7976159
>>
>

-- 
=
Dipl.Ing. Stefan Overkamp
tel: 02052 / 814184
mobil: 0177 / 7976159

___
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

Re: [Geoserver-users] ImagePyramid layer black when no granule at all

[Andrea Aime]

On Wed, Oct 31, 2018 at 1:04 PM Arnaud L.  wrote:

> Hi Andrea
>
> Le 31/10/2018 à 13:00, Andrea Aime a écrit :
> > thanks for sharing! It would have been hard to guess that you had a
> > image mosaic without sample image,
> > those files are mandatory and manual generation of the mosaic setup is
> > uncommon.
>
> Is it ? But manual generation is mandatory when one uses a PostGIS based
> mosaic index, isn't it ?
>

No, you are still supposed to let the mosaic configure itself. Never, ever,
generate
the mosaic property file manually, setup a indexer and a datastore config
files
and let the mosaic do its work, regardless of where the index is stored.


> Are most users relying on shapefiles ? They are very impractical when
> dealing with dynamic data though.
>

I don't have statistics on what most users do, but see above.

Cheers
Andrea

==

GeoServer Professional Services from the experts! Visit http://goo.gl/it488V
for more information. == Ing. Andrea Aime @geowolf Technical Lead
GeoSolutions S.A.S. Via di Montramito 3/A 55054 Massarosa (LU) phone: +39
0584 962313 fax: +39 0584 1660272 mob: +39 339 8844549
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

Re: [Geoserver-users] Sub-layer-level security

[Nanaso via Geoserver-users]

Hi,
Thanks a lot Stefan for your perfect solution.
I have tested what you mentioned and it works pretty fine. But there is one 
remaining issue. That is how to pass the current geoserver's username to the 
database? I've a field in the geometries table called "user_name". It should 
hold the owner of the record (the user that can view the record). I need to 
fill this field with the current geoserver username. How can I do that?
I tried the following WFS request:

  
 
http://www.opengis.net/gml; 
srsName="urn:ogc:def:crs:EPSG::4326">
   21.958021949698434 14.533349892039715

 
 city h
 current_setting('myapp.user', TRUE)
  
   
But it didn't substitute the username variable with its value.

Can you help me how to do that using WFS, or whatever other solutions?

Best regards,
Nanaso

Sent with [ProtonMail](https://protonmail.com) Secure Email.

‐‐‐ Original Message ‐‐‐
On Wednesday, October 31, 2018 12:43 PM, Stefan Overkamp 
 wrote:

> Hi,
>
> "Is it possible to decide which users can access which features in a layer?"
> I'm using the following solution for postgis datastore/layer:
>
> - set a Session startup SQL (and session close-up SQL) in the datastore. This 
> will set a variable with the current GeoServer user.
> e.g. startup "SELECT set_config('myapp.user', '${GSUSER,geoserver}', FALSE)
> close-up "SELECT set_config('myapp.user', '', FALSE)
> - create a sql view, restricting the returned records with the set variable 
> (current_setting('myapp.user', TRUE))
> normally you would have an additional table in your database with mapping of 
> usernames to records/spatial entities
>
> Regards,
> Stefan
>
> Am 29.10.2018 um 12:36 schrieb Nanaso via Geoserver-users:
>
>> Hi,
>> Thanks a lot Nuno for your reply.
>> There are two issues:
>> 1- The Geofence extention can satisfy my needs in the following way: I have 
>> an attribute in my layer called "user_name", I can check if the logged in 
>> username equals to this attribute, then I will allow the logged in user to 
>> access this feature, and vise versa.
>> The problem is how to get the current logged in username. Is there an 
>> environment varaible that holds the current logged in user?
>>
>> 2- The other issue is regarding installation of Geofence. I've tried to 
>> install version 13 of Geofence extention in a Geoserver of version 13, it 
>> works fine, but the place where I should enter the CQL filter is not exist. 
>> According to the documentation:
>> https://docs.geoserver.org/stable/en/user/community/geofence-server/gui.html#rule-page
>> There should be a place to specify the CQL fitler for read and write. But it 
>> looks like this part of the configuration doesn't exist in version 13 of 
>> Geofence.
>> I've then tried to install verison 14 of Geofence in a veriosn 14 of 
>> Geoserver, but the server failed to launch with many exceptions. My machine 
>> is Mac OS High Sierra. And here you're the exceptions I recieve when 
>> launching geoserver after adding Geofence to it:
>
> --
> =
> Dipl.Ing. Stefan Overkamp
> tel: 02052 / 814184
> mobil: 0177 / 7976159___
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

Re: [Geoserver-users] ImagePyramid layer black when no granule at all

[Arnaud L.]

Hi Andrea

Le 31/10/2018 à 13:00, Andrea Aime a écrit :
thanks for sharing! It would have been hard to guess that you had a 
image mosaic without sample image,
those files are mandatory and manual generation of the mosaic setup is 
uncommon.


Is it ? But manual generation is mandatory when one uses a PostGIS based 
mosaic index, isn't it ?
Are most users relying on shapefiles ? They are very impractical when 
dealing with dynamic data though.


Best regards
--
Arnaud


___
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

Re: [Geoserver-users] ImagePyramid layer black when no granule at all

[Andrea Aime]

Hi,
thanks for sharing! It would have been hard to guess that you had a image
mosaic without sample image,
those files are mandatory and manual generation of the mosaic setup is
uncommon.

Cheers
Andrea

On Wed, Oct 31, 2018 at 12:01 PM Arnaud L.  wrote:

> Le 30/10/2018 à 14:04, Arnaud L. a écrit :
> > When there are granules in the bbox, even when they only partially cover
> > the area, the region where there is no granule is transparent.
> > But when there are really no granule to load at all, the resulting PNG
> > is fully black, with no transparency.
> >
> > [...]
> > So how can I have a fully transparent PNG image when there is no granule
> > in the queried bbox ?
>
> All right, I found the solution !
> For the record :
> In the log, the problem obviously appeared when no granule was found,
> and the problematic part was : "[org.geotools.gce.imagemosaic] -
> Creating constant image for area with no data"
> This was logged by createBlankResponse() in RasterLayerResponse.
> Trying to understand what happened in there, I saw that it created a
> blank image based on the default color model and default sample model.
> Then I realized I had no sample_image in the underlying mosaics, because
> they are managed by my own processes.
>
> So the solution was simply to generate a sample_image file which would
> have the same RGBA color model as my dataset. For that I created a dummy
> imagemosaic datastore with a single GeoTIFF from my dataset. GeoServer
> automatically generated the index file and the sample_image.dat file.
> I copied this image at the root of all the imagemosaics in my pyramid,
> and it instantly worked !
>
> Best regards
> --
> Arnaud
>
>
> ___
> 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, Andrea Aime == GeoServer Professional Services from the experts!
Visit http://goo.gl/it488V for more information. == Ing. Andrea Aime
@geowolf Technical Lead GeoSolutions S.A.S. Via di Montramito 3/A 55054
Massarosa (LU) phone: +39 0584 962313 fax: +39 0584 1660272 mob: +39 339
8844549 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

Re: [Geoserver-users] Configuring WMS-Time range for capabilities document

[Andrea Aime]

On Wed, Oct 31, 2018 at 12:45 PM Johannes Weskamm 
wrote:

> Maybe you could give me a hint where (files / classes) development for
> this should start off.
>
I don't have time to produce a list, but this commit added "nearest match"
for time in WMS, and it touches
many of the same files/classes that a static range configuration would have
to modify, so with some patience
you can extract a list of starting points from there:

https://github.com/geoserver/geoserver/commit/f85a5f1e9c2184fbf3a1c31b14eafa26e634081d

Please, remember to discuss the changes you would like to make on the
geoserver-devel list before
getting down and writing code, having to ask significant changes after the
fact is painful for both sides (the reviewer
and the submitter).

Cheers
Andrea

==

GeoServer Professional Services from the experts! Visit http://goo.gl/it488V
for more information. == Ing. Andrea Aime @geowolf Technical Lead
GeoSolutions S.A.S. Via di Montramito 3/A 55054 Massarosa (LU) phone: +39
0584 962313 fax: +39 0584 1660272 mob: +39 339 8844549
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

Re: [Geoserver-users] Configuring WMS-Time range for capabilities document

[Johannes Weskamm]

Hi,

You are right, the queries itself could be fast. I identified my
SQL-View of the layer to be the problem.

When requesting the layer via WMS, the resulting SQL query made by
geoserver will always contain an AND filter for the timestamp, which
makes the service working fast.

But when requesting capabilities, the SQL View seems not not be filtered
(for obvious reasons) which then takes a lot of time.

So i will discuss this with my colleagues, way may have some capacity
left to develop such a feature (manual configuration) for geoserver.

Maybe you could give me a hint where (files / classes) development for
this should start off.

Thanks,

Johannes


Am 31.10.2018 um 11:45 schrieb Andrea Aime:
> Hi,
> there is indeed no way to configure GeoServer with static time domain
> values (could be done, needs coding, preventive discussion on the
> devel list and then implementation according to the published
> contribution rules).
> However, finding min and max should be fast if you have an index on
> the time column (unless the database in question is
> Oracle, in that case there are fixes to speed that up on the
> development branch only)
>
> Cheers
> Andrea
>
>
> On Wed, Oct 31, 2018 at 11:41 AM Johannes Weskamm
> mailto:wesk...@terrestris.de>> wrote:
>
> I have already checked that, and tried the different options, sadly it
> does not change the time it takes to generate the capabilities
> document.
>
> I tried dynamic values and also hardcoded timestamps, the result
> is the
> same (timeouts).
>
> I think geoserver is still asking the database for the min and max
> values.
>
>
>
> Am 31.10.2018 um 11:28 schrieb br...@frogmouth.net
> :
> > How are you specifying the Default value strategy?
> >
> > If you change that to Reference Value, you can use a form like
> > fromValue/toValue. It's also possible to use relative times like
> > P1M/PRESENT, but note that the reference value is copied
> verbatim into the
> > capabilities document, which might not be what you want.
> (Adapted from
> >
> 
> https://docs.geoserver.org/stable/en/user/data/webadmin/layers.html#data-web
> > admin-layers-edit-dimensions)
> >
> > Brad
> >
> >
>
> -- 
>   Dipl.-Geogr. Johannes Weskamm
>   — Anwendungsentwickler —
>
>   terrestris GmbH & Co. KG
>   Kölnstraße 99
>   53111 Bonn
>
>   Tel: +49 (0)228 / 96 28 99 -555
>   Fax: +49 (0)228 / 96 28 99 -57
>
>   Email: wesk...@terrestris.de 
>   Web: https://www.terrestris.de
>
>   Amtsgericht Bonn, HRA 6835
>   Komplementärin: terrestris Verwaltungsgesellschaft mbH
>   vertreten durch: Torsten Brassat, Marc Jansen,
>   Hinrich Paulsen, Till Adams
>
>   Informationen über Ihre gespeicherten Daten finden Sie auf
>   unserer Homepage unter folgendem Link:
>   https://www.terrestris.de/datenschutzerklaerung/
>
>
>
> ___
> 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, Andrea Aime == GeoServer Professional Services from the
> experts! Visit http://goo.gl/it488V for more information. == Ing.
> Andrea Aime @geowolf Technical Lead GeoSolutions S.A.S. Via di
> Montramito 3/A 55054 Massarosa (LU) phone: +39 0584 962313 fax: +39
> 0584 1660272 mob: +39 339 8844549 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 

Re: [Geoserver-users] ImagePyramid layer black when no granule at all

[Arnaud L.]

Le 30/10/2018 à 14:04, Arnaud L. a écrit :

When there are granules in the bbox, even when they only partially cover
the area, the region where there is no granule is transparent.
But when there are really no granule to load at all, the resulting PNG
is fully black, with no transparency.

[...]
So how can I have a fully transparent PNG image when there is no granule
in the queried bbox ?


All right, I found the solution !
For the record :
In the log, the problem obviously appeared when no granule was found, 
and the problematic part was : "[org.geotools.gce.imagemosaic] - 
Creating constant image for area with no data"

This was logged by createBlankResponse() in RasterLayerResponse.
Trying to understand what happened in there, I saw that it created a 
blank image based on the default color model and default sample model.
Then I realized I had no sample_image in the underlying mosaics, because 
they are managed by my own processes.


So the solution was simply to generate a sample_image file which would 
have the same RGBA color model as my dataset. For that I created a dummy 
imagemosaic datastore with a single GeoTIFF from my dataset. GeoServer 
automatically generated the index file and the sample_image.dat file.
I copied this image at the root of all the imagemosaics in my pyramid, 
and it instantly worked !


Best regards
--
Arnaud


___
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

Re: [Geoserver-users] Configuring WMS-Time range for capabilities document

[Andrea Aime]

Hi,
there is indeed no way to configure GeoServer with static time domain
values (could be done, needs coding, preventive discussion on the
devel list and then implementation according to the published contribution
rules).
However, finding min and max should be fast if you have an index on the
time column (unless the database in question is
Oracle, in that case there are fixes to speed that up on the development
branch only)

Cheers
Andrea


On Wed, Oct 31, 2018 at 11:41 AM Johannes Weskamm 
wrote:

> I have already checked that, and tried the different options, sadly it
> does not change the time it takes to generate the capabilities document.
>
> I tried dynamic values and also hardcoded timestamps, the result is the
> same (timeouts).
>
> I think geoserver is still asking the database for the min and max values.
>
>
>
> Am 31.10.2018 um 11:28 schrieb br...@frogmouth.net:
> > How are you specifying the Default value strategy?
> >
> > If you change that to Reference Value, you can use a form like
> > fromValue/toValue. It's also possible to use relative times like
> > P1M/PRESENT, but note that the reference value is copied verbatim into
> the
> > capabilities document, which might not be what you want. (Adapted from
> >
> https://docs.geoserver.org/stable/en/user/data/webadmin/layers.html#data-web
> > admin-layers-edit-dimensions)
> >
> > Brad
> >
> >
>
> --
>   Dipl.-Geogr. Johannes Weskamm
>   — Anwendungsentwickler —
>
>   terrestris GmbH & Co. KG
>   Kölnstraße 99
>   53111 Bonn
>
>   Tel: +49 (0)228 / 96 28 99 -555
>   Fax: +49 (0)228 / 96 28 99 -57
>
>   Email: wesk...@terrestris.de
>   Web: https://www.terrestris.de
>
>   Amtsgericht Bonn, HRA 6835
>   Komplementärin: terrestris Verwaltungsgesellschaft mbH
>   vertreten durch: Torsten Brassat, Marc Jansen,
>   Hinrich Paulsen, Till Adams
>
>   Informationen über Ihre gespeicherten Daten finden Sie auf
>   unserer Homepage unter folgendem Link:
>   https://www.terrestris.de/datenschutzerklaerung/
>
>
>
> ___
> 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, Andrea Aime == GeoServer Professional Services from the experts!
Visit http://goo.gl/it488V for more information. == Ing. Andrea Aime
@geowolf Technical Lead GeoSolutions S.A.S. Via di Montramito 3/A 55054
Massarosa (LU) phone: +39 0584 962313 fax: +39 0584 1660272 mob: +39 339
8844549 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

Re: [Geoserver-users] Configuring WMS-Time range for capabilities document

[Johannes Weskamm]

I have already checked that, and tried the different options, sadly it
does not change the time it takes to generate the capabilities document.

I tried dynamic values and also hardcoded timestamps, the result is the
same (timeouts).

I think geoserver is still asking the database for the min and max values.



Am 31.10.2018 um 11:28 schrieb br...@frogmouth.net:
> How are you specifying the Default value strategy?
>
> If you change that to Reference Value, you can use a form like
> fromValue/toValue. It's also possible to use relative times like
> P1M/PRESENT, but note that the reference value is copied verbatim into the
> capabilities document, which might not be what you want. (Adapted from
> https://docs.geoserver.org/stable/en/user/data/webadmin/layers.html#data-web
> admin-layers-edit-dimensions)
>
> Brad
>
>

-- 
  Dipl.-Geogr. Johannes Weskamm
  — Anwendungsentwickler —

  terrestris GmbH & Co. KG
  Kölnstraße 99
  53111 Bonn

  Tel: +49 (0)228 / 96 28 99 -555
  Fax: +49 (0)228 / 96 28 99 -57

  Email: wesk...@terrestris.de
  Web: https://www.terrestris.de

  Amtsgericht Bonn, HRA 6835
  Komplementärin: terrestris Verwaltungsgesellschaft mbH
  vertreten durch: Torsten Brassat, Marc Jansen, 
  Hinrich Paulsen, Till Adams
  
  Informationen über Ihre gespeicherten Daten finden Sie auf
  unserer Homepage unter folgendem Link: 
  https://www.terrestris.de/datenschutzerklaerung/ 



___
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

Re: [Geoserver-users] Removing SHP layer via REST using it.geosolutions library

[bradh]

You can create a ticket (see standard footer on email), but please be aware
that this probably isn't a high priority right now.

Brad

-Original Message-
From: mikeluz  
Sent: Wednesday, 31 October 2018 9:27 PM
To: geoserver-users@lists.sourceforge.net
Subject: Re: [Geoserver-users] Removing SHP layer via REST using
it.geosolutions library

Hi Brad,

yes, I figured that unpublished would not delete system files, but removing
story would. But as you said this is just not implemented... anyway, is
there anything I can do, create a ticket or to do something about it ? Was
this done deliberately, or just someone has forgotten about it ? 

cheers



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


___
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-inte
grating-new-features-and-improvements-in-GeoServer


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



___
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

Re: [Geoserver-users] Configuring WMS-Time range for capabilities document

[bradh]

How are you specifying the Default value strategy?

If you change that to Reference Value, you can use a form like
fromValue/toValue. It's also possible to use relative times like
P1M/PRESENT, but note that the reference value is copied verbatim into the
capabilities document, which might not be what you want. (Adapted from
https://docs.geoserver.org/stable/en/user/data/webadmin/layers.html#data-web
admin-layers-edit-dimensions)

Brad




___
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

Re: [Geoserver-users] Removing SHP layer via REST using it.geosolutions library

[mikeluz]

Hi Brad,

yes, I figured that unpublished would not delete system files, but removing
story would. But as you said this is just not implemented... anyway, is
there anything I can do, create a ticket or to do something about it ? Was
this done deliberately, or just someone has forgotten about it ? 

cheers



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


___
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

[Geoserver-users] Configuring WMS-Time range for capabilities document

[Johannes Weskamm]

Hi list,


I am trying to configure the range of time my WMS-Time enabled Layer can
be used for.

The problem i have is, that requesting the capabilities document slows
down the machine for several minutes and i receive a timeout.

Diving deeper into the issue i realized that geoserver asks my database
for the min and max values of the configured attribute, which is of type
timestamp.

As my database contains a lot of data, these queries take some minutes
to complete, for every single layer.

This leads to timeouts when requesting the capabilities.

So my questions is:

Can i manually configure a valid range for my layer, which will appear
in the capabilities document?

This way geoserver would not need to ask the database, which currently
is unusable slow.

Something like

Startvalue: "2013-11-11T12:30:00:000Z"

Endvalue: "NOW() + 7 days" or "2018-11-07T12:30:00:000Z"

Do i miss something or is this something that is not configurable at the
moment?


Thanks for feedback,

Johannes




___
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

Re: [Geoserver-users] Removing SHP layer via REST using it.geosolutions library

[bradh]

Conceptually you should be removing the data store, not just unpublishing
the layer.

However from
https://github.com/geoserver/geoserver/blob/master/src/restconfig/src/main/j
ava/org/geoserver/rest/catalog/DataStoreController.java#L217 it looks like
the purge (deleteType) option didn't actually get implemented.

Brad 




___
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

Re: [Geoserver-users] Sub-layer-level security

[Stefan Overkamp]

Hi,

"Is it possible to decide which users can access which features in a layer?"
I'm using the following solution for postgis datastore/layer:

  * set a Session startup SQL (and session close-up SQL) in the
datastore. This will set a variable with the current GeoServer user.
e.g. startup "SELECT set_config('myapp.user', '${GSUSER,geoserver}',
FALSE)
close-up "SELECT set_config('myapp.user', '', FALSE)
  * create a sql view, restricting the returned records with the set
variable (current_setting('myapp.user', TRUE))
normally you would have an additional table in your database with
mapping of usernames to records/spatial entities

Regards,
Stefan


Am 29.10.2018 um 12:36 schrieb Nanaso via Geoserver-users:
> Hi,
> Thanks a lot Nuno for your reply.
> There are two issues:
> 1- The Geofence extention can satisfy my needs in the following way: I
> have an attribute in my layer called "user_name", I can check if the
> logged in username equals to this attribute, then I will allow the
> logged in user to access this feature, and vise versa.
> The problem is how to get the current logged in username. Is there an
> environment varaible that holds the current logged in user?
>
> 2- The other issue is regarding installation of Geofence. I've tried
> to install version 13 of Geofence extention in a Geoserver of version
> 13, it works fine, but the place where I should enter the CQL filter
> is not exist. According to the documentation:
> https://docs.geoserver.org/stable/en/user/community/geofence-server/gui.html#rule-page
> There should be a place to specify the CQL fitler for read and write.
> But it looks like this part of the configuration doesn't exist in
> version 13 of Geofence.
> I've then tried to install verison 14 of Geofence in a veriosn 14 of
> Geoserver, but the server failed to launch with many exceptions. My
> machine is Mac OS High Sierra. And here you're the exceptions I
> recieve when launching geoserver after adding Geofence to it:

-- 
=
Dipl.Ing. Stefan Overkamp
tel: 02052 / 814184
mobil: 0177 / 7976159

___
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

[Geoserver-users] Removing SHP layer via REST using it.geosolutions library

[mikeluz]

Hi everyone,

I am have a bit problem with removing the SHP layer using the
it.geosolutions library, but I think it is general Geoserver REST API
problem. My question or problem is that when I unpublish/remove a layer
using:
/
publisher.unpublishFeatureType(WORKSPACE, STORE, layerName);
/

the layer itself is removed from the geoserver but all the related files
(*.shp, *.proj etc) are still keept in the file system ? I am using
it.geosolutions with version 1.6 and geoserver with version 2.5.1, but I
checked it also for it.geosolutions 1.7 - lates one, and geoserver 2.11
version and I did not see any code that would be responsible for removing
those file system (I also checked the repos).  I know that REST api allows
to remove SLD file, when you unpublish a style, and this same it possible
when you remove a coverage story, but if it is a feature/shapefile story or
a layer it just does not work. Can anyone please tell me if I am right ? Or
is there a way to remove those system files when I remove a layer via REST
using it.geosolutions/ geoserver REST API ?

cheers,
Pawel





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


___
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

Re: [Geoserver-users] DEbug with oracle extension

[Andrea Aime]

On Wed, Oct 31, 2018 at 10:07 AM Ian Turton  wrote:

> It's been a while since I did this but I think I set the profile in the
> maven -> set maven profiles menu for the gs-web module. Though I use the
> built in maven in eclipse rather than eclipse:eclipse so it may not work
> for you.
>

Been a while here too :-)
By a quick look in the pom file it seems that two profiles need to be
enabled, a "oracle" one to get the extension in, but it will
still not work as the oracle driver is not included (it's not
redistributable), then add a "oracleDriver" profile after manually
installing the
driver in maven matching this description:

   
   
   
 com.oracle
 ojdbc7
 12.1.0.2
   

Cheers
Andrea

==

GeoServer Professional Services from the experts! Visit http://goo.gl/it488V
for more information. == Ing. Andrea Aime @geowolf Technical Lead
GeoSolutions S.A.S. Via di Montramito 3/A 55054 Massarosa (LU) phone: +39
0584 962313 fax: +39 0584 1660272 mob: +39 339 8844549
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

Re: [Geoserver-users] DEbug with oracle extension

[Ian Turton]

It's been a while since I did this but I think I set the profile in the
maven -> set maven profiles menu for the gs-web module. Though I use the
built in maven in eclipse rather than eclipse:eclipse so it may not work
for you.

Ian

On Tue, 30 Oct 2018 at 20:21, Olyster  wrote:

> Hi,
>
> I have an instance of Geoserver running in debug in eclipse.
>
> I want to debug with the oracle extension but Oracle NG never shows in the
> add store page.
>
> I compiled with the extension using mvn eclipse:eclipse -P oracle
> successfully but still Oracle NG isn't showing up.
>
> Thanks for your help.
>
>
>
> --
> Sent from:
> http://osgeo-org.1560.x6.nabble.com/GeoServer-User-f3786390.html
>
>
> ___
> 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
>


-- 
Ian Turton
___
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