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
On Fri, Mar 23, 2018 at 3:36 PM, Jorge Gustavo Rocha
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
Yes i seperatly has that idea and have updated the proposals, now that I am
reading email I see you are ahead of me :)
On Fri, Mar 23, 2018 at 12:00 PM Andrea Aime
wrote:
> Hi Jody,
> wouldn't it be simpler to just add a default method to the existing
> interface?
-
-Alkuperäinen viesti-
Lähettäjä: Jorge Gustavo Rocha [mailto:j...@geomaster.pt]
Lähetetty: 23. maaliskuuta 2018 16:37
Vastaanottaja: geoserver-devel@lists.sourceforge.net
Aihe: Re: [Geoserver-devel] SLD from Postgis or from GeoPackage
Hi Andrea,
This proposal is backed up by myself. I
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
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
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
wrote:
> We had a chance to write up a proposal for GeoTools - to introduce
> ResourceInfo2.getStyles():
>
> -
We had a chance to write up a proposal for GeoTools - to introduce
ResourceInfo2.getStyles():
- https://github.com/geotools/geotools/wiki/ResourceInfo2-with-Style
I think allowing DataStore developers to control the presentation of their
"native" styles is worth while.
On Thu, Mar 22, 2018 at
On Thu, Mar 22, 2018 at 11:34 AM, Jody Garnett
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
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
: Andrea Aime [mailto:andrea.a...@geo-solutions.it]
Lähetetty: 22. maaliskuuta 2018 10:59
Vastaanottaja: Jorge Gustavo Rocha <j...@geomaster.pt>
Kopio: Geoserver-devel <geoserver-devel@lists.sourceforge.net>
Aihe: Re: [Geoserver-devel] SLD from Postgis or from GeoPackage
Hi Jorge,
summ
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
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
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
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
15 matches
Mail list logo