[Geoserver-users] GeoServer 2.16-RC Released!

[Torben Barsballe via Geoserver-users]

We are happy to announce the release of GeoServer 2.16-RC
.
Downloads are available (zip

 and war
)
along with docs and extensions.

This is a GeoServer release candidate made in conjunction with GeoTools
22-RC.

We want to encourage people to test the release thoroughly and report back
any issue found. With no further delay, let’s see what’s new, that is, what
is there to test!
Faster map rendering of complex styles

If you have very complex styles, with lots of rules and complex filtering
conditions you’ll be pleased to hear that GeoServer 2.16.x can locate the
right symbolizer much quicker than previous versions. This is useful, for
example, in the GeoServer home page  demo map,
rendered from OSM data using a OSM Bright clone built with the CSS module.
The GeoSolutions offices in Massarosa (Viareggio), Italy, in the
geoserver.org demo mapDynamic densification on reprojection

GeoServer has always reprojected data “point by point”, this typically
caused long lines represented by just two points to be turn into straight
lines, instead of curves, as they were supposed to.

In GeoServer there is a new “advanced projection handling” option in WMS
enabling on the fly densification of data, the rendering engine computes
how much deformation the projection applies in the area being rendered, and
densifies the long lines before reprojection, resulting in eye pleasing
curves in output. See a “before and after” comparison here:
Reprojection, original point by point versus densified mode in 2.16.xEPSG
database updated to v 9.6

Thanks to the sponsorship of GeoScience Australia  the
EPSG database has been updated to version 9.6, including roughly a thousand
more codes than the previous version available in GeoServer. The code has
also been updated to ensure the NTv2 grid shift files between GDA94 and
GDA2020 work properly.
Complex GeoJSON output changes

GeoServer WFS can already output GeoJSON out of complex features data
sources (app-schema). However, the output can be less than pleasing at
times, the following improvements have been made:

   - The property/element alternation typical of GML is preserved, causing
   deeply nested and ugly to look structures. Not everyone loves to write a
   “container.x.x” access to reach the x value, with 2.16.x the output skips
   one of the containers and exposes a direct “container.x” structure
   - XML attributes are now turned into plain JSON properties, and prefixed
   with a “@”
   - Feature and data types are not lost anymore in translations, preserved
   by a “@feaureType” and “@dataType” attributes
   - Full nested features are encoded as GeoJSON again, keeping their
   identifiers

Here is an example of output from 2.16.x:

{
  "type": "FeatureCollection",
  "features": [
{
  "type": "Feature",
  "id": "000101",
  "geometry": {
"type": "Point",
"coordinates": [51.0684, 1.4298]
  },
  "properties": {
"@featureType": "Borehole",
"identifier": {
  "value": "BSS000",
  "@codeSpace": "http://www.ietf.org/rfc/rfc2616";
},
"bholeHeadworks": [
  {
"type": "Feature",
"geometry": {
  "type": "Point",
  "coordinates": [51.0684, 1.4298]
},
"properties": {
  "@featureType": "BoreCollar",
  "collarElevation": {
"value": -32,
"@srsName": "http://www.opengis.net/def/crs/EPSG/0/5720";,
"@srsDimension": "1",
"@uomLabels": "m"
  }
}
  }
],


Status Monitoring module promoted to Core

The Status Monitoring module

has
been promoted to core, and is now included in GeoServer by default!

This module adds a new tab to the Server Status page, with system
statistics so that you can monitor the system which GeoServer is running on
from the Web GUI.
[image: ../../_images/gui.png]Authentication key module graduated to
extension

The “Authkey” module has been graduated to extension, allowing security
unaware applications to access GeoServer. Reminder, in order to keep the
system secure the keys should be managed as temporary session tokens by an
external application (e.g. MapStore can do this).
PostGIS data store improvements

The PostGIS data store sees a few improvements, including:

   - TWKB encoding for geometries for all WMS/WMTS requests, reducing the
   amount of data travelling from the database to GeoServer
   - The JDBC driver used to transfer all data as ASCII, the code was
   modified to all

Re: [Geoserver-users] gt-imagemosaic projections

[Bessette-Halsema, Dominique E]

If I add in the hardcoded 3832 information to the "setRequestGridGeometry" 
method, imagemosaic projects correctly.  How do I ensure that the class is 
getting the correct GridGeometry2D object?

Dominique Bessette


From: Bessette-Halsema, Dominique E 
Sent: Wednesday, August 28, 2019 1:26 PM
To: geoserver-users@lists.sourceforge.net
Subject: [Geoserver-users] gt-imagemosaic projections

Hello

I'm looking at imagemosaic using gt-imagemosaic v21.1 GeoServer 2.15.1.  I 
created an imagemosaic coverage with native CRS EPSG:4326.  When I make a 
getMap request using CRS EPSG:3832,  the objects requestCRS and 
coverageProperties.crs2D are both EPSG:4326 which causes the grid to not 
reproject.

line 293 in the gt-imagemosaic SpatialRequestHelper.java
//
// Check if the request CRS is different from the coverage native CRS
//
if (!CRS.equalsIgnoreMetadata(requestCRS, coverageProperties.crs2D))

Shouldn't they be different?


Dominique Bessette




SpatialRequestHelper.java.patch
Description: SpatialRequestHelper.java.patch
___
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] gt-imagemosaic projections

[Bessette-Halsema, Dominique E]

Hello

I'm looking at imagemosaic using gt-imagemosaic v21.1 GeoServer 2.15.1.  I 
created an imagemosaic coverage with native CRS EPSG:4326.  When I make a 
getMap request using CRS EPSG:3832,  the objects requestCRS and 
coverageProperties.crs2D are both EPSG:4326 which causes the grid to not 
reproject.

line 293 in the gt-imagemosaic SpatialRequestHelper.java
//
// Check if the request CRS is different from the coverage native CRS
//
if (!CRS.equalsIgnoreMetadata(requestCRS, coverageProperties.crs2D))

Shouldn't they be different?


Dominique Bessette


___
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] How to add a prefix to Literal tag in SLD?

[Nuno Oliveira]

Hi,
In SQL server the N prefix is need because you are using an Unicode
string:
https://docs.microsoft.com/en-us/sql/t-sql/data-types/nchar-and-nvarcha
r-transact-sql?view=sql-server-2017
I never used SQL server with Unicode text, I did a quick look in
GeoTools tickets and looks like that issue was fixed long time ago:
https://osgeo-org.atlassian.net/browse/GEOT-3609
If you use the style you shared, what's the actual exception you get?
The logs would help understand what is goign on.
Best regards,
Nuno Oliveira
On Sat, 2019-08-24 at 00:03 -0700, alich65 wrote:
> I have a Sql Server Store in Geoserver. I want to create Attribute-
> based sld.
> I used Persian characters in Literal tag. Like this:
> 
> 
> 
>   
>   
> Rank is ''
>   
>   http://www.opengis.net/ogc";>;
> 
>   Rank
>   
> 
>   
>   
> 
>   #ed56ef
> 
> 
>   #01
>   1
>   
> linejoin">bevel
> 
>   
> 
> 
>   خیلی زیاد
>   
> خیلی زیاد
>   
>   http://www.opengis.net/ogc";>;
> 
>   Rank
>   خیلی زیاد
> 
>   
>   
> 
>   #70a7dd
> 
> 
>   #01
>   1
>   
> linejoin">bevel
> 
>   
> 
> 
>   زیاد
>   
> زیاد
>   
>   http://www.opengis.net/ogc";>;
> 
>   Rank
>   زیاد
> 
>   
>   
> 
>   #76cc75
> 
> 
>   #01
>   1
>   
> linejoin">bevel
> 
>   
> 
> 
>   متوسط
>   
> متوسط
>   
>   http://www.opengis.net/ogc";>;
> 
>   Rank
>   متوسط
> 
>   
>   
> 
>   #da8a3f
> 
> 
>   #01
>   1
>   
> linejoin">bevel
> 
>   
> 
>   
> 
> 
> But Sql Server query not working without prefix "N". Like
> this(Attached
> images): 
> 
>  
> 
>  
> 
> Now I want to add "N" to Literal tag as prefix. how to do that? 
> thanks in advance for your reply
> 
> 
> 
> --
> Sent from: http://osgeo-org.1560.x6.nabble.com/GeoServer-User-f378639
> 0.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://w
> ww.ianturton.com/talks/foss4g.html#/
> - The GeoServer user list posting guidelines: http://geoserver.org/co
> mm/userlist-guidelines.html
> 
> If you want to request a feature or an improvement, also see this: ht
> tps://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,
Nuno Oliveira
==
GeoServer Professional Services from the
experts! 
Visit http://goo.gl/it488V for more information.
==

Nuno Miguel Carvalho Oliveira
@nmcoliveira
Software Engineer

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

http://www.geo-solutions.it
http://twitter.com/geosolutions_it

---

Con riferimento alla normativa sul trattamento dei dati 
personali (Reg. UE 2016/679 - Regolamento generale sulla 
protezione dei dati “GDPR”), si precisa che ogni 
circostanza inerente alla presente email (il suo contenuto, 
gli eventuali allegati, etc.) è un dato la cui conoscenza 
è riservata al/i solo/i destinatario/i indicati dallo 
scrivente. Se il messaggio Le è giunto per errore, è 
tenuta/o a cancellarlo, ogni altra operazione è illecita. 
Le sarei comunque grato se potesse darmene notizia.

This email is intended only for the person or entity to 
which it is addressed and may contain information that 
is privileged, confidential or otherwise protected from 
disclosure. We remind that - as provided by European 
Regulation 2016/679 “GDPR” - copying, dissemination or 
use of this e-mail or the information herein by anyone 
other than the intended recipient is prohibited. If you 
have received this email by mistake, please notify 
us immediately by telephone or e-mail.
___
Geoserver-users mailing list

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

If you want to request a feature or an improvement, also see this: 
https://github.com/geoserver/geos

Re: [Geoserver-users] Geoserver Store NetCDF issue: Could not list layers

[Daniele Romagnoli]

Hi Frank,
If my memory serves me right the current code allows to deal with different
2D grids of the same type (let's say multiple set of GeoX/GeoY grids),
provided that multiple dimensions exist for them, in order to define the
coordinates variables.
Your case is different and your lon/lat variables will be handled as
standard variables (not a coordinate variable, as X and Y will do instead).
So I think that the culprit on your case is still the WKT not being
properly setup on the initial dataset since it uses quotes instead of
double quotes, which result in the reader being unable to recognize the
coordinate reference system for the underlying variables.

WKT spatial reference definition uses double quotes for texts. Since I was
documenting myself on that, I have also looked for some formal
documentation and I have found the specification:
https://portal.opengeospatial.org/files/12-063r5
Chapter 6.1 of the WKT specification reports:


*EXAMPLE KEYWORD1[attribute1,KEYWORD2[attribute2,attribute3]]  *
*Attributes may be from an enumeration, be numbers or be text. Text is
enclosed in double quotes  *

Indeed, the classic: https://spatialreference.org/ref/epsg/4326/prettywkt/

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.01745329251994328,
AUTHORITY["EPSG","9122"]],
AUTHORITY["EPSG","4326"]]

And same for custom CRS defined in NetCDF.  This is the output from a
netcdf sample provided in GDAL datasets (
https://github.com/OSGeo/gdal/raw/master/autotest/gdrivers/data/cf_lcc2sp.nc
):
PROJCS["unnamed",GEOGCS["unknown",DATUM["unknown",SPHEROID["Sphere",6371200,0]],PRIMEM["Greenwich",0],UNIT["degree",0.0174532925199433]],PROJECTION["Lambert_Conformal_Conic_1SP"],PARAMETER["latitude_of_origin",25],PARAMETER["central_meridian",265],PARAMETER["scale_factor",1],PARAMETER["false_easting",0],PARAMETER["false_northing",0],PARAMETER["standard_parallel_1",25],UNIT["kilometre",1000,AUTHORITY["EPSG","9036"]]]

And this is how spatial_ref from your sample data is defined
PROJCS['unnamed',GEOGCS['GRS
1980(IUGG,1980)',DATUM['unknown',SPHEROID['GRS80',6378137,298.257222101],TOWGS84[0,0,0,0,0,0,0]],PRIMEM['Greenwich',0],UNIT['degree',0.0174532925199433]],PROJECTION['Transverse_Mercator'],PARAMETER['latitude_of_origin',0],PARAMETER['central_meridian',18],PARAMETER['scale_factor',1],PARAMETER['false_easting',15],PARAMETER['false_northing',0],UNIT['Meter',1]]
which uses single quotes instead of required double quotes.

Hope this helps.
Regards,
Daniele


On Tue, Aug 27, 2019 at 8:51 AM Van Der Stelt Frank <
frank.vanderst...@smhi.se> wrote:

> Hi Daniele,
>
> When I open ToolsUI I get five axisTypes, one for *time* and the other
> four for location as you suspected; l*on, lat, GeoX *and* GeoY.*
> You mention that there is code to deal with this case, is that already
> implemented in the NetCDF-plugin?
>
> Thank you for your help!
>
> Kind regards,
>
> Frank
>
> --
> *Från:* Daniele Romagnoli [daniele.romagn...@geo-solutions.it]
> *Skickat:* den 26 augusti 2019 16:39
> *Till:* Van Der Stelt Frank
> *Kopia:* Alexander Petkov; geoserver-users@lists.sourceforge.net
> *Ämne:* Re: [Geoserver-users] Geoserver Store NetCDF issue: Could not
> list layers
>
> Hi Frank,
> not 100% sure about the longitude variable issue.
> I'm wondering if, for any reason, the datasets looks like having 4 2D Axis
> (both longitude,latitude and x,y projected coordinate axis) so it's like
> having both meter and degree coordinates being defined and supported (some
> very peculiar datasets contain multiple 2D grids definitions and multiple
> 2D dimensions and there is code to deal with that case).
> If you open the dataset with ToolsUI and go through the "CoordSys" tab,
> how many "axisType" rows is reporting on the bottom table?
>
> The alternative hypothesis I have in mind is that being the dataset a
> projected one, the lon and lat variables are handled as normal 2D variables
> (and not as coordinates since there is no dimensions for them). Being "lon"
> the first variable listed in your NetCDF, it's the first one spotting the
> WKT parsing problem when looking for the associated coordinate reference
> system during the variables scan.
>
> Please, let us know.
> Regards,
> Daniele
>
>
>
> On Thu, Aug 22, 2019 at 10:57 PM Van Der Stelt Frank <
> frank.vanderst...@smhi.se> wrote:
>
>> Thank you for your answer. I looked at this and found that this is a
>> problem in geotools. When the WKT string is parsed the single quotes are
>> changed to double quotes and the CRS factory doesn't like that. So I
>> patched this part of geotools to get around this problem. The question
>> remains why the NetCDF plugin looks at the lon variable at all. That one is
>> included in the crun variable that has the projection defined.
>>
>> Kind r

Re: [Geoserver-users] Separate WMS settings ?

[mark]

On 8/28/19 11:11 AM, Lars I. Nielsen, LIFA A/S wrote:


Hi list.

We have some customer data which are exposed as WMS with a limited SRS 
list (5 projections: 25832, 25833, 4326, 4258, 3857).


This works fine for most clients, but we have a problem with ArcMap 
which default selects one of the projections (4326), unfortunately is 
not the best (25832).


Problem 1: It doesn’t look like we can control which projection that 
is chosen as default, even if we set the desired projection first in 
the list. Is this even possible to control ?


the srs used to generate requests is a decision of the client, it seems 
a bug in arcmap if it fails to use the srs of the map/project and if 
that matches one of the service provided srs. In a capabilities document 
there is no notion of a default or best srs afaik.


I then created a new workspace, and added a separate setting for its 
WMS. I then limited this setting to a single projection (25832).


Problem 2: When I fetch the Capabilities document – even with the 
addition of the optional “namespace” parameter – the document contains 
all 5 projections from the general setting, not just the one from the 
separate setting. Is this WAD or a bug ?


if you have fully defined a (virtual) WMS and it offers srs that outside 
of the limited list then that would be a bug.


-M


___
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] Separate WMS settings ?

[Lars I. Nielsen, LIFA A/S]

Hi list.

We have some customer data which are exposed as WMS with a limited SRS list (5 
projections: 25832, 25833, 4326, 4258, 3857).

This works fine for most clients, but we have a problem with ArcMap which 
default selects one of the projections (4326), unfortunately is not the best 
(25832).

Problem 1: It doesn't look like we can control which projection that is chosen 
as default, even if we set the desired projection first in the list. Is this 
even possible to control ?


I then created a new workspace, and added a separate setting for its WMS. I 
then limited this setting to a single projection (25832).

Problem 2: When I fetch the Capabilities document - even with the addition of 
the optional "namespace" parameter - the document contains all 5 projections 
from the general setting, not just the one from the separate setting. Is this 
WAD or a bug ?


Has anyone run into similar problems, and have insights to share ?



Med venlig hilsen

Lars I. Nielsen, LIFA A/S
GIS-konsulent, FME Certified Professional
Geoinformatik
[Beskrivelse: 
C:\Users\lin\AppData\Roaming\Microsoft\signatures\284x82-3741133837051347070]
T

6313 6800

@

l...@lifa.dk

D

6313 6849

W

www.lifa.dk

M

2492 4866

CVR

20937289


[Beskrivelse: 
C:\Users\lin\AppData\Roaming\Microsoft\signatures\21x21-3019966288736195652]
Følg os på LinkedIn og læs de seneste nyheder fra LIFA A/S
___
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] Unable to download GeoServer 2.15.2 Windows Installer

[Andrea Aime]

Hi Ronald,
a new section at the end of the developer guide, top level, would seem fine
to me.
I still hope it's just a temporary arrangement, and that eventually we'll
get back a Windows build
server, but there is no ETA, for the being a page there will be fine.

Cheers
Andrea


On Mon, Aug 26, 2019 at 10:02 AM Ronald Hoek - ComponentAgro B.V. <
ronald.h...@componentagro.nl> wrote:

> Hi Andrea,
>
>
>
> I was thinking about where to add this instruction about creating the
> Windows installer.
>
>
>
> Adding it to the ‘release’ section in the dev-manual is not a realy good
> place as this is not (no longer) a part of the release progress.
>
> However, adding it to the USER manual is also a bit ‘strange’ – surely for
> non-tech users.
>
>
>
> So I was thinking about a new section somewhere inside the DEV manual, to
> which can be pointed from the USER manual page of the Windows installer.
>
>
>
> If you’re OK with this idea, l’ll try to make a suggestion/PULL how and
> where exactly…
>
>
>
> Regards,
>
> *Ronald Hoek*
>
> The information in this e-mail message, including any files sent with it,
> is exclusively intended for the addressee. Disclosure to third parties in
> whatever form, is only permitted with permission from ComponentAgro. If you
> receive this message but you are not the addressee of this e-mail, then you
> must permanently delete the message from your system and files.
>
>
>
> *Van:* Andrea Aime 
> *Verzonden:* dinsdag 13 augustus 2019 14:02
> *Aan:* Ronald Hoek 
> *CC:* Jody Garnett ; GeoServer Mailing List List <
> geoserver-users@lists.sourceforge.net>
> *Onderwerp:* Re: [Geoserver-users] Unable to download GeoServer 2.15.2
> Windows Installer
>
>
>
> On Tue, Aug 13, 2019 at 1:59 PM Ronald Hoek - ComponentAgro B.V. <
> ronald.h...@componentagro.nl> wrote:
>
> Hi Andreas,
>
>
>
> I already found the link to the old docs – thanks.
>
>
>
> But from your point of view, there’s no longer need to add it again to the
> live documentation…?
>
>
>
> It could be added if you want, make a pull request.
>
>
>
>  If so, then I’ll add it to our own documentation, as we use GeoServer
> (in production) on a Windows machine only for serving WFS, with IIS as a
> gateway to foreward (SSL) requests to Geoserver (for which we did not setup
> SSL).
>
> This works just fine for us based on the default settings supplied by the
> Windows Setup (running it as a Windows 32-bit service).
>
>
>
> Note: this is not a public webservice, so the loads are not very high…
>
>
>
> Oh dear, yes, if you can live with 32bit addressing space only, load is
> indeed quite light ;-)
>
>
>
> 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.*
>


-- 

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 fo