Re: [Geoserver-devel] Crazy idea... what about GeoPackage straight in core for 2.12?

2017-08-18 Thread Rahkonen Jukka (MML)
__ Lähettäjä: Brad Hards <br...@frogmouth.net> Lähetetty: 18. elokuuta 2017 1:14 Vastaanottaja: 'Jody Garnett' Kopio: 'Geoserver-devel'; 'Andrea Aime' Aihe: Re: [Geoserver-devel] Crazy idea... what about GeoPackage straight in core for 2.12? > I like the idea of makin

Re: [Geoserver-devel] Crazy idea... what about GeoPackage straight in core for 2.12?

2017-08-17 Thread Brad Hards
> I like the idea of making geopackage core - because it is a good idea. +1 > Brad when someone does have a chance to work on 1.2 is implemented it can > start off life as a community module, and move into core when ready. We > would need to support both versions right? We would, but it probably

Re: [Geoserver-devel] Crazy idea... what about GeoPackage straight in core for 2.12?

2017-08-17 Thread Jody Garnett
Hey Brad / Andrea: I like the idea of making geopackage core - because it is a good idea. Brad when someone does have a chance to work on 1.2 is implemented it can start off life as a community module, and move into core when ready. We would need to support both versions right? -- Jody Garnett

Re: [Geoserver-devel] Crazy idea... what about GeoPackage straight in core for 2.12?

2017-07-27 Thread Andrea Aime
On Thu, Jul 27, 2017 at 12:40 PM, Brad Hards wrote: > I worry about the stability of the format. GeoPackage 1.2 isn't actually > approved yet, and the changes from 1.1 are substantive (not just a patch): > https://portal.opengeospatial.org/files/?artifact_id=74224=1 for >

Re: [Geoserver-devel] Crazy idea... what about GeoPackage straight in core for 2.12?

2017-07-27 Thread Brad Hards
> Hi, > I was thinking about the current idea of splitting the geopackage > support into several > modules, one store, one WFS output (extension), one WPS output > (extension), one WMS output > (community, as written its dangerous for the server stability). > > Well,

Re: [Geoserver-devel] Crazy idea... what about GeoPackage straight in core for 2.12?

2017-07-27 Thread Andrea Aime
On Thu, Jul 27, 2017 at 1:57 AM, Ben Caradoc-Davies wrote: > Makes sense to me. Can we get it done before the freeze? > Well, the nice thing is that we really just need to add a dependency to the store in core to have a basic setup going. And maybe a custom panel (reusing

Re: [Geoserver-devel] Crazy idea... what about GeoPackage straight in core for 2.12?

2017-07-26 Thread Ben Caradoc-Davies
Makes sense to me. Can we get it done before the freeze? Kind regards, Ben. On 27/07/17 05:08, Andrea Aime wrote: Hi, I was thinking about the current idea of splitting the geopackage support into several modules, one store, one WFS output (extension), one WPS output (extension), one WMS

Re: [Geoserver-devel] Crazy idea... what about GeoPackage straight in core for 2.12?

2017-07-26 Thread Jody Garnett
I like the simplification; let's do it. -- Jody Garnett On 26 July 2017 at 10:08, Andrea Aime wrote: > Hi, > I was thinking about the current idea of splitting the geopackage support > into several > modules, one store, one WFS output (extension), one WPS output >

Re: [Geoserver-devel] Crazy idea... what about GeoPackage straight in core for 2.12?

2017-07-26 Thread Ian Turton
I saw an interesting talk at foss4ge on a proposed extension to geopackage to store sld and ows context in the package as a separate table. This would allow an easy way to migrate a set of styled data from Qgis to geoserver directly. If we were to implement this having geopackage in core would

[Geoserver-devel] Crazy idea... what about GeoPackage straight in core for 2.12?

2017-07-26 Thread Andrea Aime
Hi, I was thinking about the current idea of splitting the geopackage support into several modules, one store, one WFS output (extension), one WPS output (extension), one WMS output (community, as written its dangerous for the server stability). Well, given the importance of the format... what