[Geoserver-devel] SLD from Postgis or from GeoPackage

GeoServer GeoServer Developer
, ,
1

Hi devs,

QGIS can save the style back to the provider (to Postgis and to
GeoPackage). The style is stored on a table called layers_style. On
Postgis, the table is stored in the public schema.

The table has a column to store the native QGIS style format and another
column to store the SLD style (stylesld).

I would like to use the SLD style stored on layers_style table on
Geoserver. It would improve the interoperability between QGIS and Geoserver.

It can be done both for Postgis and for GeoPackage stores. For example,
when publishing a GeoPackahe layer, it would be nice to use the SLD
already stored in the GeoPackage. The same for Postgis.

The layers_table [1] also has a useasdefault column. It would be super
cool to immediately render the layer using that default style for the layer.

I would appreciate your feedback regarding this use case.

I've done a simple mockup [2] to improve the Publishing tab for the
layer. It adds one more list of styles. The user can choose from the
'Available styles' list and also from the 'Available style in Postgis'
(or 'Available style in GeoPackage') list.

The store (when connecting to Postgis) is always related with a schema
that might be not the public. To support this use case, we need to add
an additional connection to the database to the public schema using the
same credentials.

Regards from Bonn Code Sprint,

Jorge Gustavo

[1] CREATE TABLE public.layer_styles (
    id integer NOT NULL DEFAULT nextval('layer_styles_id_seq'::regclass),
    f_table_catalog character varying COLLATE pg_catalog."default",
    f_table_schema character varying COLLATE pg_catalog."default",
    f_table_name character varying COLLATE pg_catalog."default",
    f_geometry_column character varying COLLATE pg_catalog."default",
    stylename text COLLATE pg_catalog."default",
    styleqml xml,
    stylesld xml,
    useasdefault boolean,
    description text COLLATE pg_catalog."default",
    owner character varying(63) COLLATE pg_catalog."default",
    ui xml,
    update_time timestamp without time zone DEFAULT now(),
    CONSTRAINT layer_styles_pkey PRIMARY KEY (id)
);

[2]
https://www.dropbox.com/s/nh72i4tv21y1h0o/mockup%20with%20styles%20from%20postgis.png?dl=0

--
Geomaster, Lda
Avenida Barros e Soares, 423
Nogueira
4715-214 Braga
NIF 510906109
Tm +351 910333888
Email jgr@anonymised.com
Site geomaster.pt
GPS 41.53322,-8.41929

2

Hi,

This looks like something that could be implemented as a community module.

I see at least three major challenges here:

  1. Configure and store the extra information associated to the layer, i.e. what are the DB available styles, which one is the default etc …
  2. Plug this info into the layer when it is retrieved from the catalog at runtime
  3. Handle the calls that will be made to the catalog looking for the DB styles

The first point could be solved by storing the necessary info in the layer meta-data.
The second and third point are a bit more difficult to handle and may need to be done at the CatalogFacade level, this will need to be investigated.

Regarding the lockups, so basically the user will have two “styles selectors” available where the ones coming from the DB will be priority ?
In an ideal world only a single “styles selector” should be made available to the user …

Let’s see if anyone else has something to add :slight_smile:

Cheers,

Nuno Oliveira

···

On 03/21/2018 02:31 PM, Jorge Gustavo Rocha wrote:

Hi devs,

QGIS can save the style back to the provider (to Postgis and to
GeoPackage). The style is stored on a table called layers_style. On
Postgis, the table is stored in the public schema.

The table has a column to store the native QGIS style format and another
column to store the SLD style (stylesld).

I would like to use the SLD style stored on layers_style table on
Geoserver. It would improve the interoperability between QGIS and Geoserver.

It can be done both for Postgis and for GeoPackage stores. For example,
when publishing a GeoPackahe layer, it would be nice to use the SLD
already stored in the GeoPackage. The same for Postgis.

The layers_table [1] also has a useasdefault column. It would be super
cool to immediately render the layer using that default style for the layer.

I would appreciate your feedback regarding this use case.

I've done a simple mockup [2] to improve the Publishing tab for the
layer. It adds one more list of styles. The user can choose from the
'Available styles' list and also from the 'Available style in Postgis'
(or 'Available style in GeoPackage') list.

The store (when connecting to Postgis) is always related with a schema
that might be not the public. To support this use case, we need to add
an additional connection to the database to the public schema using the
same credentials.

Regards from Bonn Code Sprint,

Jorge Gustavo

[1] CREATE TABLE public.layer_styles (
    id integer NOT NULL DEFAULT nextval('layer_styles_id_seq'::regclass),
    f_table_catalog character varying COLLATE pg_catalog."default",
    f_table_schema character varying COLLATE pg_catalog."default",
    f_table_name character varying COLLATE pg_catalog."default",
    f_geometry_column character varying COLLATE pg_catalog."default",
    stylename text COLLATE pg_catalog."default",
    styleqml xml,
    stylesld xml,
    useasdefault boolean,
    description text COLLATE pg_catalog."default",
    owner character varying(63) COLLATE pg_catalog."default",
    ui xml,
    update_time timestamp without time zone DEFAULT now(),
    CONSTRAINT layer_styles_pkey PRIMARY KEY (id)
);

[2]
[https://www.dropbox.com/s/nh72i4tv21y1h0o/mockup%20with%20styles%20from%20postgis.png?dl=0](https://www.dropbox.com/s/nh72i4tv21y1h0o/mockup%20with%20styles%20from%20postgis.png?dl=0)


-- 
Regards,
Nuno Oliveira
==
GeoServer Professional Services from the experts! Visit [http://goo.gl/it488V](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://www.geo-solutions.it)
[http://twitter.com/geosolutions_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.
3

We have a similar need with shape files, the presence of a sidecar SLD file is great way to pass styling around.

At a GeoTools level I would love a way to “discover” a built-in style for a layer so we could make it available for either a) GeoServer Data Import (sadly that would just be a one time solution), or see we could make a placeholder in the LayerInfo (maybe with a special default style placeholder.

GeoTools does have a per layer “info” data structure used to pass meta information on to the application, we could see about making the style available in this manner.

···

On 21 March 2018 at 15:31, Jorge Gustavo Rocha <jgr@anonymised.com> wrote:

Hi devs,

QGIS can save the style back to the provider (to Postgis and to
GeoPackage). The style is stored on a table called layers_style. On
Postgis, the table is stored in the public schema.

The table has a column to store the native QGIS style format and another
column to store the SLD style (stylesld).

I would like to use the SLD style stored on layers_style table on
Geoserver. It would improve the interoperability between QGIS and Geoserver.

It can be done both for Postgis and for GeoPackage stores. For example,
when publishing a GeoPackahe layer, it would be nice to use the SLD
already stored in the GeoPackage. The same for Postgis.

The layers_table [1] also has a useasdefault column. It would be super
cool to immediately render the layer using that default style for the layer.

I would appreciate your feedback regarding this use case.

I’ve done a simple mockup [2] to improve the Publishing tab for the
layer. It adds one more list of styles. The user can choose from the
‘Available styles’ list and also from the ‘Available style in Postgis’
(or ‘Available style in GeoPackage’) list.

The store (when connecting to Postgis) is always related with a schema
that might be not the public. To support this use case, we need to add
an additional connection to the database to the public schema using the
same credentials.

Regards from Bonn Code Sprint,

Jorge Gustavo

[1] CREATE TABLE public.layer_styles (
id integer NOT NULL DEFAULT nextval(‘layer_styles_id_seq’::regclass),
f_table_catalog character varying COLLATE pg_catalog.“default”,
f_table_schema character varying COLLATE pg_catalog.“default”,
f_table_name character varying COLLATE pg_catalog.“default”,
f_geometry_column character varying COLLATE pg_catalog.“default”,
stylename text COLLATE pg_catalog.“default”,
styleqml xml,
stylesld xml,
useasdefault boolean,
description text COLLATE pg_catalog.“default”,
owner character varying(63) COLLATE pg_catalog.“default”,
ui xml,
update_time timestamp without time zone DEFAULT now(),
CONSTRAINT layer_styles_pkey PRIMARY KEY (id)
);

[2]
https://www.dropbox.com/s/nh72i4tv21y1h0o/mockup%20with%20styles%20from%20postgis.png?dl=0

–
Geomaster, Lda
Avenida Barros e Soares, 423
Nogueira
4715-214 Braga
NIF 510906109
Tm +351 910333888
Email jgr@anonymised.com
Site geomaster.pt
GPS 41.53322,-8.41929

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

Geoserver-devel mailing list
Geoserver-devel@anonymised.com.366…sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

–
Jody Garnett

4

On 22-03-18 02:59, Jody Garnett wrote:

We have a similar need with shape files, the presence of a sidecar SLD
file is great way to pass styling around.

At a GeoTools level I would love a way to "discover" a built-in style
for a layer so we could make it available for either a) GeoServer Data
Import (sadly that would just be a one time solution), or see we could
make a placeholder in the LayerInfo (maybe with a special default style
placeholder.

GeoTools does have a per layer "info" data structure used to pass meta
information on to the application, we could see about making the style
available in this manner.

Hi Jody,

about sidecar SLD: if I'm correct esri products used a lyr file next to
a shapefile automatically if it had the exact same name.
QGIS is doing the same when you have a .qml (QGIS stylefile) with the
same name.
Unfortunatly that does not work (yet) with sld files (in QGIS), but it
could be a usable model... if you want to keep working with shapefiles :wink:

In case of Geopackage/Spatialite I would think a 'packaged' style could
be favoured over sld styles in Geoserver? Indeed it would be best if
GeoTools could serve this information.

Regards,

Richard Duivenvoorde

5

Hi Jorge,
summarizing what others said and adding a few bits of my own. You’d need (top to bottom):

  • A notion of “layer local style” in the configuration, right now styles are global and are just linked to the layer. Basically, what Nuno said. And add UI for it, what you said, but without “postgis” in the title, it should be generic (native styles or something like that)
  • Change all style using bits (GetCapabilties, GetMap, GetFeatureInfo, GetLegendGraphic, GetStyles) to recognize this new type of style (GetCapabilities) and make a call to the ResourcePool that would look something like getStyle(LayerInfo, styleName)
  • Have a generic way for datastores to publish a local style, basically what Jody said, using the Info data structure, that would have to be extended
  • Implementation wise, GeoPackage and Postgis are actually two dialects of JDBCDataStore (one class for all JDBC based stores), the SQLDialect woudl have to be extended to locate native styles if present
  • There is the issue of name conflicts, a native style name could overlap a configured one… in this case, if the native one is configured to be published, I guess it would have to take precedence on the other
    GeoServer wise there is a core API change, so a improvement proposal + vote is needed, GeoTools wise, meh… it’s more or less the same (ResourceInfo interface is public API that would need to be extended). Personally the GeoTools change looks smaller to me and I’d be content with just a mail discussion on geotools-devel, but it’s just my feeling about it, writing a proposal is indeed just a little effort more.

Hope this helps!

Cheers
Andrea

···

On Wed, Mar 21, 2018 at 3:31 PM, Jorge Gustavo Rocha <jgr@anonymised.com> wrote:

Hi devs,

QGIS can save the style back to the provider (to Postgis and to
GeoPackage). The style is stored on a table called layers_style. On
Postgis, the table is stored in the public schema.

The table has a column to store the native QGIS style format and another
column to store the SLD style (stylesld).

I would like to use the SLD style stored on layers_style table on
Geoserver. It would improve the interoperability between QGIS and Geoserver.

It can be done both for Postgis and for GeoPackage stores. For example,
when publishing a GeoPackahe layer, it would be nice to use the SLD
already stored in the GeoPackage. The same for Postgis.

The layers_table [1] also has a useasdefault column. It would be super
cool to immediately render the layer using that default style for the layer.

I would appreciate your feedback regarding this use case.

I’ve done a simple mockup [2] to improve the Publishing tab for the
layer. It adds one more list of styles. The user can choose from the
‘Available styles’ list and also from the ‘Available style in Postgis’
(or ‘Available style in GeoPackage’) list.

The store (when connecting to Postgis) is always related with a schema
that might be not the public. To support this use case, we need to add
an additional connection to the database to the public schema using the
same credentials.

Regards from Bonn Code Sprint,

Jorge Gustavo

[1] CREATE TABLE public.layer_styles (
id integer NOT NULL DEFAULT nextval(‘layer_styles_id_seq’::regclass),
f_table_catalog character varying COLLATE pg_catalog.“default”,
f_table_schema character varying COLLATE pg_catalog.“default”,
f_table_name character varying COLLATE pg_catalog.“default”,
f_geometry_column character varying COLLATE pg_catalog.“default”,
stylename text COLLATE pg_catalog.“default”,
styleqml xml,
stylesld xml,
useasdefault boolean,
description text COLLATE pg_catalog.“default”,
owner character varying(63) COLLATE pg_catalog.“default”,
ui xml,
update_time timestamp without time zone DEFAULT now(),
CONSTRAINT layer_styles_pkey PRIMARY KEY (id)
);

[2]
https://www.dropbox.com/s/nh72i4tv21y1h0o/mockup%20with%20styles%20from%20postgis.png?dl=0

–
Geomaster, Lda
Avenida Barros e Soares, 423
Nogueira
4715-214 Braga
NIF 510906109
Tm +351 910333888
Email jgr@anonymised.com
Site geomaster.pt
GPS 41.53322,-8.41929

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

Geoserver-devel mailing list
Geoserver-devel@anonymised.com.366…sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

–

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.

6

So the next step would be to make a proposal on what we want to do. Sounds like there is a requirement, and a UI idea, and we need to fill in the middle.

One interesting one is the ability to ask for an SLD for a layer via GetStyles - this is done by layer name so it would work to retrieve the style from PostGIS or GeoPackage. The style would not be available from GeoServer REST API … and I am fine with that because it is part of the PostGIS or GeoPackage configuration and not part of the GeoServer configuration.

On Thu, Mar 22, 2018 at 9:44 AM Richard Duivenvoorde <rdmailings@anonymised.com> wrote:

On 22-03-18 02:59, Jody Garnett wrote:

We have a similar need with shape files, the presence of a sidecar SLD
file is great way to pass styling around.

At a GeoTools level I would love a way to “discover” a built-in style
for a layer so we could make it available for either a) GeoServer Data
Import (sadly that would just be a one time solution), or see we could
make a placeholder in the LayerInfo (maybe with a special default style
placeholder.

GeoTools does have a per layer “info” data structure used to pass meta
information on to the application, we could see about making the style
available in this manner.

Hi Jody,

about sidecar SLD: if I’m correct esri products used a lyr file next to
a shapefile automatically if it had the exact same name.
QGIS is doing the same when you have a .qml (QGIS stylefile) with the
same name.
Unfortunatly that does not work (yet) with sld files (in QGIS), but it
could be a usable model… if you want to keep working with shapefiles :wink:

In case of Geopackage/Spatialite I would think a ‘packaged’ style could
be favoured over sld styles in Geoserver? Indeed it would be best if
GeoTools could serve this information.

Regards,

Richard Duivenvoorde

7

On Thu, Mar 22, 2018 at 11:34 AM, Jody Garnett <jody.garnett@anonymised.com>
wrote:

So the next step would be to make a proposal on what we want to do. Sounds
like there is a requirement, and a UI idea, and we need to fill in the
middle.

One interesting one is the ability to ask for an SLD for a layer via
GetStyles - this is done by layer name so it would work to retrieve the
style from PostGIS or GeoPackage. The style would not be available from
GeoServer REST API ... and I am fine with that because it is part of the
PostGIS or GeoPackage configuration and not part of the GeoServer
configuration.

I think this is debatable, I don't see a strict need to expose the native
styles on first round, but it's not impossible, they could be placed at
workspace/<store>/featuretypes/<featureType>/styles/<style>, read only.
And well, nothing eventually denies the notion of eventually updating them
too, provided the underlying API is designed to allow such thing

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.

8

We had a chance to write up a proposal for GeoTools - to introduce ResourceInfo2.getStyles():

I think allowing DataStore developers to control the presentation of their “native” styles is worth while.

On Thu, Mar 22, 2018 at 9:44 AM Richard Duivenvoorde <rdmailings@anonymised.com> wrote:

On 22-03-18 02:59, Jody Garnett wrote:

We have a similar need with shape files, the presence of a sidecar SLD
file is great way to pass styling around.

At a GeoTools level I would love a way to “discover” a built-in style
for a layer so we could make it available for either a) GeoServer Data
Import (sadly that would just be a one time solution), or see we could
make a placeholder in the LayerInfo (maybe with a special default style
placeholder.

GeoTools does have a per layer “info” data structure used to pass meta
information on to the application, we could see about making the style
available in this manner.

Hi Jody,

about sidecar SLD: if I’m correct esri products used a lyr file next to
a shapefile automatically if it had the exact same name.
QGIS is doing the same when you have a .qml (QGIS stylefile) with the
same name.
Unfortunatly that does not work (yet) with sld files (in QGIS), but it
could be a usable model… if you want to keep working with shapefiles :wink:

In case of Geopackage/Spatialite I would think a ‘packaged’ style could
be favoured over sld styles in Geoserver? Indeed it would be best if
GeoTools could serve this information.

Regards,

Richard Duivenvoorde

9

Hi Jody,
wouldn’t it be simpler to just add a default method to the existing interface?

Cheers
Andrea

···

On Fri, Mar 23, 2018 at 11:40 AM, Jody Garnett <jody.garnett@anonymised.com.403…> wrote:

We had a chance to write up a proposal for GeoTools - to introduce ResourceInfo2.getStyles():

I think allowing DataStore developers to control the presentation of their “native” styles is worth while.

On Thu, Mar 22, 2018 at 9:44 AM Richard Duivenvoorde <rdmailings@anonymised.com> wrote:

On 22-03-18 02:59, Jody Garnett wrote:

We have a similar need with shape files, the presence of a sidecar SLD
file is great way to pass styling around.

At a GeoTools level I would love a way to “discover” a built-in style
for a layer so we could make it available for either a) GeoServer Data
Import (sadly that would just be a one time solution), or see we could
make a placeholder in the LayerInfo (maybe with a special default style
placeholder.

GeoTools does have a per layer “info” data structure used to pass meta
information on to the application, we could see about making the style
available in this manner.

Hi Jody,

about sidecar SLD: if I’m correct esri products used a lyr file next to
a shapefile automatically if it had the exact same name.
QGIS is doing the same when you have a .qml (QGIS stylefile) with the
same name.
Unfortunatly that does not work (yet) with sld files (in QGIS), but it
could be a usable model… if you want to keep working with shapefiles :wink:

In case of Geopackage/Spatialite I would think a ‘packaged’ style could
be favoured over sld styles in Geoserver? Indeed it would be best if
GeoTools could serve this information.

Regards,

Richard Duivenvoorde

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

Geoserver-devel mailing list
Geoserver-devel@anonymised.com.366…sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

–

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.

10

Hi all,
just a reminder, the original motivation for proposal was first introduced to avoid people
going and starting changes without having the resourcing to actually finish the work.
The people making the proposals are the same that need to fund it (with their own time,
typically, but nothing prevents others from chiming in and helping of course).

This is something obvious for those that have contributed to the project for a long time,
but maybe not so for others. So… this activity is funded/resourced already right?

Cheers
Andrea

···

On Fri, Mar 23, 2018 at 11:40 AM, Jody Garnett <jody.garnett@anonymised.com> wrote:

We had a chance to write up a proposal for GeoTools - to introduce ResourceInfo2.getStyles():

I think allowing DataStore developers to control the presentation of their “native” styles is worth while.

On Thu, Mar 22, 2018 at 9:44 AM Richard Duivenvoorde <rdmailings@anonymised.com> wrote:

On 22-03-18 02:59, Jody Garnett wrote:

We have a similar need with shape files, the presence of a sidecar SLD
file is great way to pass styling around.

At a GeoTools level I would love a way to “discover” a built-in style
for a layer so we could make it available for either a) GeoServer Data
Import (sadly that would just be a one time solution), or see we could
make a placeholder in the LayerInfo (maybe with a special default style
placeholder.

GeoTools does have a per layer “info” data structure used to pass meta
information on to the application, we could see about making the style
available in this manner.

Hi Jody,

about sidecar SLD: if I’m correct esri products used a lyr file next to
a shapefile automatically if it had the exact same name.
QGIS is doing the same when you have a .qml (QGIS stylefile) with the
same name.
Unfortunatly that does not work (yet) with sld files (in QGIS), but it
could be a usable model… if you want to keep working with shapefiles :wink:

In case of Geopackage/Spatialite I would think a ‘packaged’ style could
be favoured over sld styles in Geoserver? Indeed it would be best if
GeoTools could serve this information.

Regards,

Richard Duivenvoorde

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

Geoserver-devel mailing list
Geoserver-devel@anonymised.com.366…sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

–

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.

11

Hi Andrea,

This proposal is backed up by myself. I want to support the
interoperability between QGIS and GeoTools/GeoServer. I'm also
interested in improving GeoPackage.

Jeff Yutzler (OGC GeoPackage editor) confirms that there are no
interoperable approaches to handle styling in GeoPackage for now, but he
is committed to find a standard approach.

If we go forward with a sound proposal, we can get some more open source
projects adopting our approach regarding "native" styles that can be
delivered with the data. I can contribute with this approach to both
GeoTools and QGIS. It will be even easier to support this in uDig.

If you or the PSC can help me to find additional resources to support
this proposal, that would be very welcome. You comments are already a
valuable contribution. Thanks!

Regards,

Jorge Gustavo

On 23-03-2018 13:04, Andrea Aime wrote:

Hi all,
just a reminder, the original motivation for proposal was first
introduced to avoid people
going and starting changes without having the resourcing to actually
finish the work.
The people making the proposals are the same that need to fund it (with
their own time,
typically, but nothing prevents others from chiming in and helping of
course).

This is something obvious for those that have contributed to the project
for a long time,
but maybe not so for others. So... this activity is funded/resourced
already right?

Cheers
Andrea

On Fri, Mar 23, 2018 at 11:40 AM, Jody Garnett <jody.garnett@anonymised.com
<mailto:jody.garnett@anonymised.com>> wrote:

    We had a chance to write up a proposal for GeoTools - to introduce
    ResourceInfo2.getStyles():

    - https://github.com/geotools/geotools/wiki/ResourceInfo2-with-Style
    <https://github.com/geotools/geotools/wiki/ResourceInfo2-with-Style&gt;

    I think allowing DataStore developers to control the presentation of
    their "native" styles is worth while.

    On Thu, Mar 22, 2018 at 9:44 AM Richard Duivenvoorde
    <rdmailings@anonymised.com <mailto:rdmailings@anonymised.com>> wrote:

        On 22-03-18 02:59, Jody Garnett wrote:
        > We have a similar need with shape files, the presence of a sidecar SLD
        > file is great way to pass styling around.
        >
        > At a GeoTools level I would love a way to "discover" a built-in style
        > for a layer so we could make it available for either a) GeoServer Data
        > Import (sadly that would just be a one time solution), or see we could
        > make a placeholder in the LayerInfo (maybe with a special default style
        > placeholder.
        >
        >
        > GeoTools does have a per layer "info" data structure used to pass meta
        > information on to the application, we could see about making the style
        > available in this manner.

        Hi Jody,

        about sidecar SLD: if I'm correct esri products used a lyr file
        next to
        a shapefile automatically if it had the exact same name.
        QGIS is doing the same when you have a .qml (QGIS stylefile)
        with the
        same name.
        Unfortunatly that does not work (yet) with sld files (in QGIS),
        but it
        could be a usable model... if you want to keep working with
        shapefiles :wink:

        In case of Geopackage/Spatialite I would think a 'packaged'
        style could
        be favoured over sld styles in Geoserver? Indeed it would be best if
        GeoTools could serve this information.

        Regards,

        Richard Duivenvoorde

    ------------------------------------------------------------------------------
    Check out the vibrant tech community on one of the world's most
    engaging tech sites, Slashdot.org! http://sdm.link/slashdot
    _______________________________________________
    Geoserver-devel mailing list
    Geoserver-devel@lists.sourceforge.net
    <mailto:Geoserver-devel@lists.sourceforge.net>
    https://lists.sourceforge.net/lists/listinfo/geoserver-devel
    <https://lists.sourceforge.net/lists/listinfo/geoserver-devel&gt;

--

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.

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

_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

--
Geomaster, Lda
Avenida Barros e Soares, 423
Nogueira
4715-214 Braga
NIF 510906109
Tm +351 910333888
Email jgr@anonymised.com
Site geomaster.pt
GPS 41.53322,-8.41929

12

Yes i seperatly has that idea and have updated the proposals, now that I am reading email I see you are ahead of me :slight_smile:

···

On Fri, Mar 23, 2018 at 11:40 AM, Jody Garnett <jody.garnett@anonymised.com> wrote:

We had a chance to write up a proposal for GeoTools - to introduce ResourceInfo2.getStyles():

I think allowing DataStore developers to control the presentation of their “native” styles is worth while.

On Thu, Mar 22, 2018 at 9:44 AM Richard Duivenvoorde <rdmailings@anonymised.com> wrote:

On 22-03-18 02:59, Jody Garnett wrote:

We have a similar need with shape files, the presence of a sidecar SLD
file is great way to pass styling around.

At a GeoTools level I would love a way to “discover” a built-in style
for a layer so we could make it available for either a) GeoServer Data
Import (sadly that would just be a one time solution), or see we could
make a placeholder in the LayerInfo (maybe with a special default style
placeholder.

GeoTools does have a per layer “info” data structure used to pass meta
information on to the application, we could see about making the style
available in this manner.

Hi Jody,

about sidecar SLD: if I’m correct esri products used a lyr file next to
a shapefile automatically if it had the exact same name.
QGIS is doing the same when you have a .qml (QGIS stylefile) with the
same name.
Unfortunatly that does not work (yet) with sld files (in QGIS), but it
could be a usable model… if you want to keep working with shapefiles :wink:

In case of Geopackage/Spatialite I would think a ‘packaged’ style could
be favoured over sld styles in Geoserver? Indeed it would be best if
GeoTools could serve this information.

Regards,

Richard Duivenvoorde

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

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://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.

–
Jody Garnett

13

On Fri, Mar 23, 2018 at 3:36 PM, Jorge Gustavo Rocha <jgr@anonymised.com>
wrote:

Hi Andrea,

If you or the PSC can help me to find additional resources to support
this proposal, that would be very welcome. You comments are already a
valuable contribution. Thanks!

Hi,
I'll keep it in mind during conversations, but I have not much
confidence... even with the
obvious "let's make QGIS export correct and complete SLD" speech that we
gave to many
potential interested parties the return has been somewhat slim... which
saddens me quite
a bit, I've spent a mountain of spare time to get that thing started...
and many thanks to those that sponsored the existing bits, of course! :slight_smile:

Anyways, if you have questions or get stuck, just ask.

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.

14

Hi devs,

Thank you for the feedback received so far.

I've been working on this proposal. I've update the wiki [1] and made
the first PR [2]. It is tagged WIP, so we can have time to discuss it
and improve before going forward.

I've made a very simple screencast, using the ResourceInfo class with
these new methods. It takes has 4 minutes [3].

Boundless GeoServer Explorer plugin (developed by Victor Olaya) is no
longer maintained. With this proposal, users will be able to share
styles between QGIS and GeoServer much easier.

I'll be around to improve the proposal.

Regards,

Jorge Gustavo

[1] https://github.com/geotools/geotools/wiki/ResourceInfo-with-native-style
[2] https://github.com/geotools/geotools/pull/1851
[3]
https://www.dropbox.com/s/6u41jjx2gsqix76/Screencast%202018-04-03%2019%3A24%3A02.mp4?dl=0

On 24-03-2018 13:19, Andrea Aime wrote:

On Fri, Mar 23, 2018 at 3:36 PM, Jorge Gustavo Rocha <jgr@anonymised.com
<mailto:jgr@anonymised.com>> wrote:

    Hi Andrea,

    If you or the PSC can help me to find additional resources to support
    this proposal, that would be very welcome. You comments are already a
    valuable contribution. Thanks!

Hi,
I'll keep it in mind during conversations, but I have not much
confidence... even with the
obvious "let's make QGIS export correct and complete SLD" speech that we
gave to many
potential interested parties the return has been somewhat slim... which
saddens me quite
a bit, I've spent a mountain of spare time to get that thing started...
and many thanks to those that sponsored the existing bits, of course! :slight_smile:

Anyways, if you have questions or get stuck, just ask.

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.

--
Geomaster, Lda
Avenida Barros e Soares, 423
Nogueira
4715-214 Braga
NIF 510906109
Tm +351 910333888
Email jgr@anonymised.com
Site geomaster.pt
GPS 41.53322,-8.41929