[Geoserver-devel] GSIP 207, feature type info customization

GeoServer GeoServer Developer
1

Hi all,
please read and discuss GSIP 207, proposing to make the feature type
attribute table editable and customizable, for simple features:
https://github.com/geoserver/geoserver/wiki/GSIP-207

Feedback and votes welcomed

Cheers
Andrea

···

==
GeoServer Professional Services from the experts!

Visit http://bit.ly/gs-services-us for more information.

Ing. Andrea Aime
@geowolf
Technical Lead

GeoSolutions Group
phone: +39 0584 962313

fax: +39 0584 1660272

mob: +39 333 8128928

https://www.geosolutionsgroup.com/

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

2

All sounds good to me, only question that occurs to me is about the filter does this apply to the data coming from the datastore as now or the new data?

Ian

On Wed, 22 Dec 2021, 11:04 Andrea Aime, <andrea.aime@anonymised.com> wrote:

Hi all,
please read and discuss GSIP 207, proposing to make the feature type
attribute table editable and customizable, for simple features:
https://github.com/geoserver/geoserver/wiki/GSIP-207

Feedback and votes welcomed

Cheers
Andrea

==
GeoServer Professional Services from the experts!

Visit http://bit.ly/gs-services-us for more information.

Ing. Andrea Aime
@geowolf
Technical Lead

GeoSolutions Group
phone: +39 0584 962313

fax: +39 0584 1660272

mob: +39 333 8128928

https://www.geosolutionsgroup.com/

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-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

3

Addressed in the “interactions” section:

“With the feature type own filter attribute, which is also going to work on top of the mapping”

See more at https://github.com/geoserver/geoserver/wiki/GSIP-207#interactions

This is consistent with other forms of mapping, like app-schema, or ElasticSearch document config.

That said, I can imagine cases where the filter could be implemented on the raw data, maybe on attributes that the customization did hide.
But then it would get inconsistent with the security filters applied by GeoFence, which can only run atop the mapping (unless very significant effort is taken).
Maybe it should be configurable? If anyone has funding to make it configurable, I think that may be welcomed, but I’m not going to make it so.

Cheers
Andrea

···

Regards,

Andrea Aime

==
GeoServer Professional Services from the experts!

Visit http://bit.ly/gs-services-us for more information.

Ing. Andrea Aime
@geowolf
Technical Lead

GeoSolutions Group
phone: +39 0584 962313

fax: +39 0584 1660272

mob: +39 333 8128928

https://www.geosolutionsgroup.com/

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

4

Great, thanks! Makes sense that way.

Ian

On Wed, 22 Dec 2021, 13:25 Andrea Aime, <andrea.aime@anonymised.com> wrote:

Addressed in the “interactions” section:

“With the feature type own filter attribute, which is also going to work on top of the mapping”

See more at https://github.com/geoserver/geoserver/wiki/GSIP-207#interactions

This is consistent with other forms of mapping, like app-schema, or ElasticSearch document config.

That said, I can imagine cases where the filter could be implemented on the raw data, maybe on attributes that the customization did hide.
But then it would get inconsistent with the security filters applied by GeoFence, which can only run atop the mapping (unless very significant effort is taken).
Maybe it should be configurable? If anyone has funding to make it configurable, I think that may be welcomed, but I’m not going to make it so.

Cheers
Andrea

On Wed, Dec 22, 2021 at 2:21 PM Ian Turton <ijturton@anonymised.com> wrote:

All sounds good to me, only question that occurs to me is about the filter does this apply to the data coming from the datastore as now or the new data?

Ian

On Wed, 22 Dec 2021, 11:04 Andrea Aime, <andrea.aime@anonymised.com> wrote:

Hi all,
please read and discuss GSIP 207, proposing to make the feature type
attribute table editable and customizable, for simple features:
https://github.com/geoserver/geoserver/wiki/GSIP-207

Feedback and votes welcomed

Cheers
Andrea

==
GeoServer Professional Services from the experts!

Visit http://bit.ly/gs-services-us for more information.

Ing. Andrea Aime
@geowolf
Technical Lead

GeoSolutions Group
phone: +39 0584 962313

fax: +39 0584 1660272

mob: +39 333 8128928

https://www.geosolutionsgroup.com/

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-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

–

Regards,

Andrea Aime

==
GeoServer Professional Services from the experts!

Visit http://bit.ly/gs-services-us for more information.

Ing. Andrea Aime
@geowolf
Technical Lead

GeoSolutions Group
phone: +39 0584 962313

fax: +39 0584 1660272

mob: +39 333 8128928

https://www.geosolutionsgroup.com/

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

5

Thanks Andrea!

GeoServer 1.x had some very simple ability to “override” attribute information, it is nice to see that improved on. I wonder if this would allow geopackage to force the geometry of an SQLView from BigDecimal to Geometry.

I will read this more carefully tomorrow.

Jody

···

–
Jody Garnett

6

Hi Jody,
as the proposal suggests, the mapping happens above the data sources, while SQL views
are handled inside JDBCDataStore. So no, it won’t allow what you’re describing, it has to
happen somewhere inside JDBCDataStore/GeoPkgDialect.

Cheers
Andrea

···

Regards,

Andrea Aime

==
GeoServer Professional Services from the experts!

Visit http://bit.ly/gs-services-us for more information.

Ing. Andrea Aime
@geowolf
Technical Lead

GeoSolutions Group
phone: +39 0584 962313

fax: +39 0584 1660272

mob: +39 333 8128928

https://www.geosolutionsgroup.com/

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

7

This definitely looks like a useful improvement.

I do have some minor questions:

  1. There’s a couple of UI elements in Proposal > GUI who’s behavior isn’t really explained:
  • What happens if you uncheck “Customize feature type”, then later re-check it? Will any customizations you made previously be preserved?
  • What does the “reset” button do? I assume it resets to native values?1. Also, do you expect to support some form of autocompletion of “source” based on the native schema of the data? I feel like this would be a useful feature, given that GeoServer is sometimes the only window users have into a given data set.

Ultimately I’d like to verify that it’ll be easy to restore removed features, as I feel like this could cause a lot of user frustration if it isn’t.

Cheers,
Torben

On Wed, Dec 22, 2021 at 3:04 AM Andrea Aime <andrea.aime@anonymised.com.> wrote:

Hi all,
please read and discuss GSIP 207, proposing to make the feature type
attribute table editable and customizable, for simple features:
https://github.com/geoserver/geoserver/wiki/GSIP-207

Feedback and votes welcomed

Cheers
Andrea

==
GeoServer Professional Services from the experts!

Visit http://bit.ly/gs-services-us for more information.

Ing. Andrea Aime
@geowolf
Technical Lead

GeoSolutions Group
phone: +39 0584 962313

fax: +39 0584 1660272

mob: +39 333 8128928

https://www.geosolutionsgroup.com/

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-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

8

This definitely looks like a useful improvement.

I do have some minor questions:

  1. There’s a couple of UI elements in Proposal > GUI who’s behavior isn’t really explained:

As you might have noticed, the proposal has key goals, and stretch goals. Hiding attributes, type re-mapping and CQL expressions
are part of the stretch goal. Whether they are kept or not, depends also on how much burden is placed on them.
My plan was to get the base going first, and then add the extra if time allowed.

  • What happens if you uncheck “Customize feature type”, then later re-check it? Will any customizations you made previously be preserved?

That would be annoying indeed eh? If a flag is kept in FeatureTypeInfo, which indicates whether the customization is active, it should
be relatively easy to . So yes, I will implement it that way.

  • What does the “reset” button do? I assume it resets to native values?

Yep, bring the editable table back to match the native values. Would you like to suggest a better name?

  1. Also, do you expect to support some form of autocompletion of “source” based on the native schema of the data? I feel like this would be a useful feature, given that GeoServer is sometimes the only window users have into a given data set.

This is a good idea, and could be part of the stretch goals.
I believe it would require using CodeMirror for the expression editor, and writing a CQL grammar in javascript… which is definitely too much effort.
Can you think of a simpler way to get auto-complete in a text area?

Cheers
Andrea

···

GeoServer Professional Services from the experts!

Visit http://bit.ly/gs-services-us for more information.

Ing. Andrea Aime
@geowolf
Technical Lead

GeoSolutions Group
phone: +39 0584 962313

fax: +39 0584 1660272

mob: +39 333 8128928

https://www.geosolutionsgroup.com/

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

9

Based on your feedback, I’ve got no further concerns, so +1 from me.
Per-item comments inline below:

  • What does the “reset” button do? I assume it resets to native values?

Yep, bring the editable table back to match the native values. Would you like to suggest a better name?

I think the name is fine, given I guessed right. Restore or Revert may be alternatives, but I think it is mostly a matter of taste, as long as the functionality is documented

  1. Also, do you expect to support some form of autocompletion of “source” based on the native schema of the data? I feel like this would be a useful feature, given that GeoServer is sometimes the only window users have into a given data set.

This is a good idea, and could be part of the stretch goals.
I believe it would require using CodeMirror for the expression editor, and writing a CQL grammar in javascript… which is definitely too much effort.
Can you think of a simpler way to get auto-complete in a text area?

I was thinking something a little less sophisticated (basically disregarding more complicated expressions entirely, and only autocompleting individual names) - so just a text overlay listing the attribute names in the data source, filtered by whatever characters have already been typed. Definitely a stretch goal though.

Cheers,
Torben

10

Hi all, Andrea,
looks good to me, just a couple of comments:

  • Is the identifier (ID attribute) of the feature type fixed? I’m assuming it is.
  • If we define a new attribute that uses a complex CQL expression (for example a concatenation) I’m assuming that someone can send a filter that targets the value of that attribute, and GeoServer will take care of translating it properly behind the scenes: delegate it to the underlying data source if supported or execute it in memory as a last resort.
    If my assumptions above are correct, you have my +1.

Kind regards,
Nuno Oliveira

···

Regards,

Nuno Oliveira

==
GeoServer Professional Services from the experts!

Visit http://bit.ly/gs-services-us for more information.

Nuno Miguel Carvalho Oliveira
@nmcoliveira
Technical Lead / Project Manager

GeoSolutions Group
phone: +39 0584 962313
fax: +39 0584 1660272

https://www.geosolutionsgroup.com/
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.

11

Hi all, Andrea,
looks good to me, just a couple of comments:

  • Is the identifier (ID attribute) of the feature type fixed? I’m assuming it is.

Yes, it is.

  • If we define a new attribute that uses a complex CQL expression (for example a concatenation) I’m assuming that someone can send a filter that targets the value of that attribute, and GeoServer will take care of translating it properly behind the scenes: delegate it to the underlying data source if supported or execute it in memory as a last resort.

In practice, that’s what happens. In detail, if you have “myatt = concatenate(a1, 12)” and a filter like “myatt = ‘test123’” comes in,
the machinery will rewrite the filter as “concatenate(a1, 12) = ‘test123’” and pass it to the underlying store, which will then decide
how to process it (either in memory, or native execution).

Cheers
Andrea

···

GeoServer Professional Services from the experts!

Visit http://bit.ly/gs-services-us for more information.

Ing. Andrea Aime
@geowolf
Technical Lead

GeoSolutions Group
phone: +39 0584 962313

fax: +39 0584 1660272

mob: +39 333 8128928

https://www.geosolutionsgroup.com/

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

12

+1 here

···

Regards,

Alessio Fabiani

==
GeoServer Professional Services from the experts!

Visit http://bit.ly/gs-services-us for more information.

Ing. Alessio Fabiani

@alfa7691
Founder/Technical Lead

GeoSolutions Group
phone: +39 0584 962313

fax: +39 0584 1660272

mob: +39 333 8128928

https://www.geosolutionsgroup.com/

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.

13

Great, thank you for the clarification, +1.

···

Regards,

Nuno Oliveira

==
GeoServer Professional Services from the experts!

Visit http://bit.ly/gs-services-us for more information.

Nuno Miguel Carvalho Oliveira
@nmcoliveira
Technical Lead / Project Manager

GeoSolutions Group
phone: +39 0584 962313
fax: +39 0584 1660272

https://www.geosolutionsgroup.com/
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.

14

Aaaaaand PR here: https://github.com/geoserver/geoserver/pull/5587
(with a small demo video)

Cheers
Andrea

···

Regards,

Andrea Aime

==
GeoServer Professional Services from the experts!

Visit http://bit.ly/gs-services-us for more information.

Ing. Andrea Aime
@geowolf
Technical Lead

GeoSolutions Group
phone: +39 0584 962313

fax: +39 0584 1660272

mob: +39 333 8128928

https://www.geosolutionsgroup.com/

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

15

The video demo did not work me; but I appreciate the effort!

···

–
Jody Garnett

16

Doh, works fine in Chrome but Firefox complains.
Try with this one maybe?

https://drive.google.com/u/0/uc?id=16c4etMcgUJPST8GIduzYJnB_Lw6N0HJG&export=download

Cheers
Andrea

···

Regards,

Andrea Aime

==
GeoServer Professional Services from the experts!

Visit http://bit.ly/gs-services-us for more information.

Ing. Andrea Aime
@geowolf
Technical Lead

GeoSolutions Group
phone: +39 0584 962313

fax: +39 0584 1660272

mob: +39 333 8128928

https://www.geosolutionsgroup.com/

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