[Geoserver-users] Getting Unable to transform referenced envelope, crs has not yet been provided ERROR on GetCapabilities

Hi,

I have a problem when requesting WMS GetCapabilities from geoserver 2.12 and can not figure out what happens.
We are using an Oracle 12c database to store our features. Most of our features are in EPSG:4326 but also have some in our local Hungarian coordinate system EPSG:23700.

The application using the geoserver always need the features in EPSG:4326, so we try to use geoserver to reproject between the coordinate systems.

This is the way we define these layers:
Native CRS: EPSG:23700
Declared CRS: EPSG:4326

SRS handling: Reproject native to declared

In the Bounding Boxes section on the web UI for the Native Bounding Box I click Compute from data, I get EPSG:4236 numbers, definitely not EPSG:23700 numbers, I do not understand why since this should be the Native bounding box. When I set Compute from SRS bounds -180,-90,180,90 is set. If at Lat/Lon Bounding box I click Compute from native bounds I get the same values.

When I save this layer, after running a GetCapabilities WMS request I get the following error at the end of the produced XML:

<<?xml version="1.0" encoding="UTF-8" standalone="no"?><!DOCTYPE ServiceExceptionReport SYSTEM "http://192.168.96.33:8080/geoserver/schemas/wms/1.1.1/WMS_exception_1_1_1.dtd&quot;&gt; <ServiceExceptionReport version="1.1.1" > <ServiceException>
      javax.xml.transform.TransformerException: org.geoserver.platform.ServiceException: Error occurred trying to write out metadata for layer: PLAN_INPUT_IGENYHELY
org.geoserver.platform.ServiceException: Error occurred trying to write out metadata for layer: PLAN_INPUT_IGENYHELY
Error occurred trying to write out metadata for layer: PLAN_INPUT_IGENYHELY
Unexpected error obtaining bounding box for layer PLAN_INPUT_IGENYHELY
Unable to transform referenced envelope, crs has not yet been provided.
</ServiceException></ServiceExceptionReport>

Thank you,
Laszlo

I experience the same when going to Layer preview and try to download the layer as GML:

java.lang.RuntimeException: java.lang.NullPointerException: Unable to transform referenced envelope, crs has not yet been provided. java.lang.NullPointerException: Unable to transform referenced envelope, crs has not yet been provided. Unable to transform referenced envelope, crs has not yet been provided.

The wierd thing is that some of my layers with the same settings work, some gives the above error.
I have already restarted Tomcat to force reload configuration but no change.

Laszlo

On 2018. Apr 18., at 19:35, László Németh <nlaszlo1976@anonymised.com> wrote:

Hi,

I have a problem when requesting WMS GetCapabilities from geoserver 2.12 and can not figure out what happens.
We are using an Oracle 12c database to store our features. Most of our features are in EPSG:4326 but also have some in our local Hungarian coordinate system EPSG:23700.

The application using the geoserver always need the features in EPSG:4326, so we try to use geoserver to reproject between the coordinate systems.

This is the way we define these layers:
Native CRS: EPSG:23700
Declared CRS: EPSG:4326

SRS handling: Reproject native to declared

In the Bounding Boxes section on the web UI for the Native Bounding Box I click Compute from data, I get EPSG:4236 numbers, definitely not EPSG:23700 numbers, I do not understand why since this should be the Native bounding box. When I set Compute from SRS bounds -180,-90,180,90 is set. If at Lat/Lon Bounding box I click Compute from native bounds I get the same values.

When I save this layer, after running a GetCapabilities WMS request I get the following error at the end of the produced XML:

<<?xml version="1.0" encoding="UTF-8" standalone="no"?>
javax.xml.transform.TransformerException: org.geoserver.platform.ServiceException: Error occurred trying to write out metadata for layer: PLAN_INPUT_IGENYHELY
org.geoserver.platform.ServiceException: Error occurred trying to write out metadata for layer: PLAN_INPUT_IGENYHELY
Error occurred trying to write out metadata for layer: PLAN_INPUT_IGENYHELY
Unexpected error obtaining bounding box for layer PLAN_INPUT_IGENYHELY
Unable to transform referenced envelope, crs has not yet been provided.

Thank you,
Laszlo

When you first configured them, did GeoServer recognize a native SRS?
If not, that might be the cause, it might not have a CRS in the native bounding box config,
which is required in order to use “reproject to declared”.
Try forcing a “compute from data” or manually updating the bbox, or even re-create the layer,
to see if that works.

Alternatively, check if the tables in question really declare the SRS you’re think they are using,
at the database level.

Cheers
Andrea

···

On Wed, Apr 18, 2018 at 7:44 PM, László Németh <nlaszlo1976@anonymised.com> wrote:

I experience the same when going to Layer preview and try to download the layer as GML:

java.lang.RuntimeException: java.lang.NullPointerException: Unable to transform referenced envelope, crs has not yet been provided. java.lang.NullPointerException: Unable to transform referenced envelope, crs has not yet been provided. Unable to transform referenced envelope, crs has not yet been provided.

The wierd thing is that some of my layers with the same settings work, some gives the above error.
I have already restarted Tomcat to force reload configuration but no change.

Laszlo

On 2018. Apr 18., at 19:35, László Németh <nlaszlo1976@anonymised.com> wrote:

Hi,

I have a problem when requesting WMS GetCapabilities from geoserver 2.12 and can not figure out what happens.
We are using an Oracle 12c database to store our features. Most of our features are in EPSG:4326 but also have some in our local Hungarian coordinate system EPSG:23700.

The application using the geoserver always need the features in EPSG:4326, so we try to use geoserver to reproject between the coordinate systems.

This is the way we define these layers:
Native CRS: EPSG:23700
Declared CRS: EPSG:4326

SRS handling: Reproject native to declared

In the Bounding Boxes section on the web UI for the Native Bounding Box I click Compute from data, I get EPSG:4236 numbers, definitely not EPSG:23700 numbers, I do not understand why since this should be the Native bounding box. When I set Compute from SRS bounds -180,-90,180,90 is set. If at Lat/Lon Bounding box I click Compute from native bounds I get the same values.

When I save this layer, after running a GetCapabilities WMS request I get the following error at the end of the produced XML:

<<?xml version="1.0" encoding="UTF-8" standalone="no"?>
javax.xml.transform.TransformerException: org.geoserver.platform.ServiceException: Error occurred trying to write out metadata for layer: PLAN_INPUT_IGENYHELY
org.geoserver.platform.ServiceException: Error occurred trying to write out metadata for layer: PLAN_INPUT_IGENYHELY
Error occurred trying to write out metadata for layer: PLAN_INPUT_IGENYHELY
Unexpected error obtaining bounding box for layer PLAN_INPUT_IGENYHELY
Unable to transform referenced envelope, crs has not yet been provided.

Thank you,
Laszlo


Check out the vibrant tech community on one of the world’s most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot


Geoserver-users mailing list

Please make sure you read the following two resources before posting to this list:

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@anonymised.com.382…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

AVVERTENZE AI SENSI DEL D.Lgs. 196/2003

Le informazioni contenute in questo messaggio di posta elettronica e/o nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il loro utilizzo è consentito esclusivamente al destinatario del messaggio, per le finalità indicate nel messaggio stesso. Qualora riceviate questo messaggio senza esserne il destinatario, Vi preghiamo cortesemente di darcene notizia via e-mail e di procedere alla distruzione del messaggio stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso, divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od utilizzarlo per finalità diverse, costituisce comportamento contrario ai principi dettati dal D.Lgs. 196/2003.

The information in this message and/or attachments, is intended solely for the attention and use of the named addressee(s) and may be confidential or proprietary in nature or covered by the provisions of privacy act (Legislative Decree June, 30 2003, no.196 - Italy’s New Data Protection Code).Any use not in accord with its purpose, any disclosure, reproduction, copying, distribution, or either dissemination, either whole or partial, is strictly forbidden except previous formal approval of the named addressee(s). If you are not the intended recipient, please contact immediately the sender by telephone, fax or e-mail and delete the information in this message that has been received in error. The sender does not give any warranty or accept liability as the content, accuracy or completeness of sent messages and accepts no responsibility for changes made after they were sent or for other risks which arise as a result of e-mail transmission, viruses, etc.

Hi Andrea,

Thank you for your answer. I did some tests.

  1. Deleted all workspaces in the workspaces configuration except the tested one.
  2. Tried downloading Layer preview in KML for the problematic layer → I get the error.
  3. Deleted the layer and recreated as new. Geoserver did figure our the Native SRS based on DB info. If I use “compute from data” I get 0,0,-1-1, since the table is empty, so I used “compute from SRS” and I get -180,-90,180,90.
  4. Tried downloading Layer preview in KML for the problematic layer → SUCCESS
  5. Diffed the two featuretype XML files and the only difference I see that the one with the error has a line: EPSG:23700 in the nativeboundingbox XML section.

I attached the two XMLs. Removing the line and inserting EPSG:4326 instead solved the problem on other problematic layers as well. Could you please clarify why?

Thank you,
Laszlo

···

On Wed, Apr 18, 2018 at 7:44 PM, László Németh <nlaszlo1976@anonymised.com> wrote:

I experience the same when going to Layer preview and try to download the layer as GML:

java.lang.RuntimeException: java.lang.NullPointerException: Unable to transform referenced envelope, crs has not yet been provided. java.lang.NullPointerException: Unable to transform referenced envelope, crs has not yet been provided. Unable to transform referenced envelope, crs has not yet been provided.

The wierd thing is that some of my layers with the same settings work, some gives the above error.
I have already restarted Tomcat to force reload configuration but no change.

Laszlo

On 2018. Apr 18., at 19:35, László Németh <nlaszlo1976@anonymised.com> wrote:

Hi,

I have a problem when requesting WMS GetCapabilities from geoserver 2.12 and can not figure out what happens.
We are using an Oracle 12c database to store our features. Most of our features are in EPSG:4326 but also have some in our local Hungarian coordinate system EPSG:23700.

The application using the geoserver always need the features in EPSG:4326, so we try to use geoserver to reproject between the coordinate systems.

This is the way we define these layers:
Native CRS: EPSG:23700
Declared CRS: EPSG:4326

SRS handling: Reproject native to declared

In the Bounding Boxes section on the web UI for the Native Bounding Box I click Compute from data, I get EPSG:4236 numbers, definitely not EPSG:23700 numbers, I do not understand why since this should be the Native bounding box. When I set Compute from SRS bounds -180,-90,180,90 is set. If at Lat/Lon Bounding box I click Compute from native bounds I get the same values.

When I save this layer, after running a GetCapabilities WMS request I get the following error at the end of the produced XML:

<<?xml version="1.0" encoding="UTF-8" standalone="no"?>
javax.xml.transform.TransformerException: org.geoserver.platform.ServiceException: Error occurred trying to write out metadata for layer: PLAN_INPUT_IGENYHELY
org.geoserver.platform.ServiceException: Error occurred trying to write out metadata for layer: PLAN_INPUT_IGENYHELY
Error occurred trying to write out metadata for layer: PLAN_INPUT_IGENYHELY
Unexpected error obtaining bounding box for layer PLAN_INPUT_IGENYHELY
Unable to transform referenced envelope, crs has not yet been provided.

Thank you,
Laszlo


Check out the vibrant tech community on one of the world’s most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot


Geoserver-users mailing list

Please make sure you read the following two resources before posting to this list:

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@anonymised.comsourceforge.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

AVVERTENZE AI SENSI DEL D.Lgs. 196/2003
Le informazioni contenute in questo messaggio di posta elettronica e/o nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il loro utilizzo è consentito esclusivamente al destinatario del messaggio, per le finalità indicate nel messaggio stesso. Qualora riceviate questo messaggio senza esserne il destinatario, Vi preghiamo cortesemente di darcene notizia via e-mail e di procedere alla distruzione del messaggio stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso, divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od utilizzarlo per finalità diverse, costituisce comportamento contrario ai principi dettati dal D.Lgs. 196/2003.

The information in this message and/or attachments, is intended solely for the attention and use of the named addressee(s) and may be confidential or proprietary in nature or covered by the provisions of privacy act (Legislative Decree June, 30 2003, no.196 - Italy’s New Data Protection Code).Any use not in accord with its purpose, any disclosure, reproduction, copying, distribution, or either dissemination, either whole or partial, is strictly forbidden except previous formal approval of the named addressee(s). If you are not the intended recipient, please contact immediately the sender by telephone, fax or e-mail and delete the information in this message that has been received in error. The sender does not give any warranty or accept liability as the content, accuracy or completeness of sent messages and accepts no responsibility for changes made after they were sent or for other risks which arise as a result of e-mail transmission, viruses, etc.

On Thu, Apr 19, 2018 at 6:45 AM, László Németh <nlaszlo1976@...84...>
wrote:

Hi Andrea,

Thank you for your answer. I did some tests.

1. Deleted all workspaces in the workspaces configuration except the
tested one.
2. Tried downloading Layer preview in KML for the problematic layer -> I
get the error.
3. Deleted the layer and recreated as new. Geoserver did figure our the
Native SRS based on DB info. If I use “compute from data” I get 0,0,-1-1,
since the table is empty, so I used “compute from SRS” and I get
-180,-90,180,90.

This seems wrong, the native bbox should be native. If your data is in
EPSG:23700 the bound coordinates should be too. I guess the UI is confused
by the "reproject native to declared" setting, but I'm not sure,
I did not work on adding the "compute from SRS" functionality.

4. Tried downloading Layer preview in KML for the problematic layer ->
SUCCESS
5. Diffed the two featuretype XML files and the only difference I see that
the one with the error has a line: <crs class="projected">EPSG:23700</crs>
in the nativeboundingbox XML section.

I attached the two XMLs. Removing the line and
inserting <crs>EPSG:4326</crs> instead solved the problem on other
problematic layers as well. Could you please clarify why?

I don't know, my guess is that it's working by accident.
Here is a sample from a working layer that I have locally, in a projected
crs (but mind the projected coordinates here):

  <nativeBoundingBox>
    <minx>-840901.150827375</minx>
    <maxx>872858.801962177</maxx>
    <miny>2966776.48464754</miny>
    <maxy>5029485.2911404</maxy>
    <crs class="projected">EPSG:32654</crs>
  </nativeBoundingBox>

Cheers
Andrea

==

GeoServer Professional Services from the experts! Visit GeoSolutions Enterprise Support Services
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://twitter.com/geosolutions_it

AVVERTENZE AI SENSI DEL D.Lgs. 196/2003

Le informazioni contenute in questo messaggio di posta elettronica e/o
nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il
loro utilizzo è consentito esclusivamente al destinatario del messaggio,
per le finalità indicate nel messaggio stesso. Qualora riceviate questo
messaggio senza esserne il destinatario, Vi preghiamo cortesemente di
darcene notizia via e-mail e di procedere alla distruzione del messaggio
stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso,
divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od
utilizzarlo per finalità diverse, costituisce comportamento contrario ai
principi dettati dal D.Lgs. 196/2003.

The information in this message and/or attachments, is intended solely for
the attention and use of the named addressee(s) and may be confidential or
proprietary in nature or covered by the provisions of privacy act
(Legislative Decree June, 30 2003, no.196 - Italy's New Data Protection
Code).Any use not in accord with its purpose, any disclosure, reproduction,
copying, distribution, or either dissemination, either whole or partial, is
strictly forbidden except previous formal approval of the named
addressee(s). If you are not the intended recipient, please contact
immediately the sender by telephone, fax or e-mail and delete the
information in this message that has been received in error. The sender
does not give any warranty or accept liability as the content, accuracy or
completeness of sent messages and accepts no responsibility for changes
made after they were sent or for other risks which arise as a result of
e-mail transmission, viruses, etc.

Thanks again. Could you please help what to look for in the code of the UI?
Is SRS bounds stored in the SRS definition? Could it be that EPSG:23700 SRS definition is not correct?

Laszlo

···

On Thu, Apr 19, 2018 at 6:45 AM, László Németh <nlaszlo1976@anonymised.com> wrote:

Hi Andrea,

Thank you for your answer. I did some tests.

  1. Deleted all workspaces in the workspaces configuration except the tested one.
  2. Tried downloading Layer preview in KML for the problematic layer → I get the error.
  3. Deleted the layer and recreated as new. Geoserver did figure our the Native SRS based on DB info. If I use “compute from data” I get 0,0,-1-1, since the table is empty, so I used “compute from SRS” and I get -180,-90,180,90.

This seems wrong, the native bbox should be native. If your data is in EPSG:23700 the bound coordinates should be too. I guess the UI is confused by the “reproject native to declared” setting, but I’m not sure,
I did not work on adding the “compute from SRS” functionality.

  1. Tried downloading Layer preview in KML for the problematic layer → SUCCESS
  2. Diffed the two featuretype XML files and the only difference I see that the one with the error has a line: EPSG:23700 in the nativeboundingbox XML section.

I attached the two XMLs. Removing the line and inserting EPSG:4326 instead solved the problem on other problematic layers as well. Could you please clarify why?

I don’t know, my guess is that it’s working by accident.
Here is a sample from a working layer that I have locally, in a projected crs (but mind the projected coordinates here):

-840901.150827375 872858.801962177 2966776.48464754 5029485.2911404 EPSG:32654

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

AVVERTENZE AI SENSI DEL D.Lgs. 196/2003
Le informazioni contenute in questo messaggio di posta elettronica e/o nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il loro utilizzo è consentito esclusivamente al destinatario del messaggio, per le finalità indicate nel messaggio stesso. Qualora riceviate questo messaggio senza esserne il destinatario, Vi preghiamo cortesemente di darcene notizia via e-mail e di procedere alla distruzione del messaggio stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso, divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od utilizzarlo per finalità diverse, costituisce comportamento contrario ai principi dettati dal D.Lgs. 196/2003.

The information in this message and/or attachments, is intended solely for the attention and use of the named addressee(s) and may be confidential or proprietary in nature or covered by the provisions of privacy act (Legislative Decree June, 30 2003, no.196 - Italy’s New Data Protection Code).Any use not in accord with its purpose, any disclosure, reproduction, copying, distribution, or either dissemination, either whole or partial, is strictly forbidden except previous formal approval of the named addressee(s). If you are not the intended recipient, please contact immediately the sender by telephone, fax or e-mail and delete the information in this message that has been received in error. The sender does not give any warranty or accept liability as the content, accuracy or completeness of sent messages and accepts no responsibility for changes made after they were sent or for other risks which arise as a result of e-mail transmission, viruses, etc.

Hi,
the code area should be this one:
https://github.com/geoserver/geoserver/blob/4d043080a8f80c76c325810d021632fdd3e9636f/src/web/core/src/main/java/org/geoserver/web/data/resource/BasicResourceConfig.java#L152

In case you want to contribute fixes here are directions and requests:
https://github.com/geoserver/geoserver/blob/master/CONTRIBUTING.md

Cheers
Andrea

···

On Thu, Apr 19, 2018 at 9:45 AM, László Németh <nlaszlo1976@anonymised.com> wrote:

Thanks again. Could you please help what to look for in the code of the UI?
Is SRS bounds stored in the SRS definition? Could it be that EPSG:23700 SRS definition is not correct?

Laszlo

On 2018. Apr 19., at 8:33, Andrea Aime <andrea.aime@anonymised.com> wrote:

On Thu, Apr 19, 2018 at 6:45 AM, László Németh <nlaszlo1976@anonymised.com> wrote:

Hi Andrea,

Thank you for your answer. I did some tests.

  1. Deleted all workspaces in the workspaces configuration except the tested one.
  2. Tried downloading Layer preview in KML for the problematic layer → I get the error.
  3. Deleted the layer and recreated as new. Geoserver did figure our the Native SRS based on DB info. If I use “compute from data” I get 0,0,-1-1, since the table is empty, so I used “compute from SRS” and I get -180,-90,180,90.

This seems wrong, the native bbox should be native. If your data is in EPSG:23700 the bound coordinates should be too. I guess the UI is confused by the “reproject native to declared” setting, but I’m not sure,
I did not work on adding the “compute from SRS” functionality.

  1. Tried downloading Layer preview in KML for the problematic layer → SUCCESS
  2. Diffed the two featuretype XML files and the only difference I see that the one with the error has a line: EPSG:23700 in the nativeboundingbox XML section.

I attached the two XMLs. Removing the line and inserting EPSG:4326 instead solved the problem on other problematic layers as well. Could you please clarify why?

I don’t know, my guess is that it’s working by accident.
Here is a sample from a working layer that I have locally, in a projected crs (but mind the projected coordinates here):

-840901.150827375 872858.801962177 2966776.48464754 5029485.2911404 EPSG:32654

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

AVVERTENZE AI SENSI DEL D.Lgs. 196/2003
Le informazioni contenute in questo messaggio di posta elettronica e/o nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il loro utilizzo è consentito esclusivamente al destinatario del messaggio, per le finalità indicate nel messaggio stesso. Qualora riceviate questo messaggio senza esserne il destinatario, Vi preghiamo cortesemente di darcene notizia via e-mail e di procedere alla distruzione del messaggio stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso, divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od utilizzarlo per finalità diverse, costituisce comportamento contrario ai principi dettati dal D.Lgs. 196/2003.

The information in this message and/or attachments, is intended solely for the attention and use of the named addressee(s) and may be confidential or proprietary in nature or covered by the provisions of privacy act (Legislative Decree June, 30 2003, no.196 - Italy’s New Data Protection Code).Any use not in accord with its purpose, any disclosure, reproduction, copying, distribution, or either dissemination, either whole or partial, is strictly forbidden except previous formal approval of the named addressee(s). If you are not the intended recipient, please contact immediately the sender by telephone, fax or e-mail and delete the information in this message that has been received in error. The sender does not give any warranty or accept liability as the content, accuracy or completeness of sent messages and accepts no responsibility for changes made after they were sent or for other risks which arise as a result of e-mail transmission, viruses, etc.

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

AVVERTENZE AI SENSI DEL D.Lgs. 196/2003

Le informazioni contenute in questo messaggio di posta elettronica e/o nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il loro utilizzo è consentito esclusivamente al destinatario del messaggio, per le finalità indicate nel messaggio stesso. Qualora riceviate questo messaggio senza esserne il destinatario, Vi preghiamo cortesemente di darcene notizia via e-mail e di procedere alla distruzione del messaggio stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso, divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od utilizzarlo per finalità diverse, costituisce comportamento contrario ai principi dettati dal D.Lgs. 196/2003.

The information in this message and/or attachments, is intended solely for the attention and use of the named addressee(s) and may be confidential or proprietary in nature or covered by the provisions of privacy act (Legislative Decree June, 30 2003, no.196 - Italy’s New Data Protection Code).Any use not in accord with its purpose, any disclosure, reproduction, copying, distribution, or either dissemination, either whole or partial, is strictly forbidden except previous formal approval of the named addressee(s). If you are not the intended recipient, please contact immediately the sender by telephone, fax or e-mail and delete the information in this message that has been received in error. The sender does not give any warranty or accept liability as the content, accuracy or completeness of sent messages and accepts no responsibility for changes made after they were sent or for other risks which arise as a result of e-mail transmission, viruses, etc.