Looks good Andrea, spotted a few sentences to fix when I get to a computer.
I will clean up and publish.
Amazing release all around.
Jody
On Wed, Jan 21, 2015 at 2:11 AM Andrea Aime
wrote:
> On Tue, Jan 20, 2015 at 4:13 PM, Andrea Aime > wrote:
>
>> Hi,
>> for all those that can access wordpres
Thanks for the catch - can your please report to the issue tracker?
If you would like to patch please check for consistent use of DataUtilities
URL methods.
On Wed, Jan 21, 2015 at 6:50 PM wrote:
> HI geoserver-devel,
>
>
>
> While we are trying to fix the build error of Geoserver, we found it
HI geoserver-devel,
While we are trying to fix the build error of Geoserver, we found it broke at
the Gs-wps-core:WPSXStreamLoaderTest.java line :81(please refer the attached
building output) . We tried to debug and found the reason is because file url
path for a resources has space character
Yeah thanks for the feedback, I will keep wps-client as an unfunded dream.
No problem with the api change, added +1 to the page.
--
Jody Garnett
On 21 January 2015 at 10:12, Andrea Aime
wrote:
> On Wed, Jan 21, 2015 at 7:09 PM, Jody Garnett
> wrote:
>
>> As for the proposal I like it, any c
+0 from me. I dont think I can comment usefully on this detail and user
implications seem a little remote.
Notice: This email and any attachments are confidential.
If received in error please destroy and immediately notify us.
Do not copy or disclose the contents.
--
This is interesting Niels - it has been a trouble in each training course I
have done (communicating why security is split across service and layer).
I will read the proposal and get back to the list (I have been focused on
the beta release).
On Tue, Jan 20, 2015 at 6:53 AM, Niels Charlier wrote:
Ciao Niels,
we discussed this a little bit and there is some feedback I would like
to report fro me:
- In the motivation section you mention "It is currently possible to
accomplish this using a third party security subsystem". Well, we
contributed GeoFence to the GeoServer codebase hence is not re
On Wed, Jan 21, 2015 at 7:12 PM, Jody Garnett
wrote:
> Happy to remove it.
>
> Alternate for discussion - consider making WKT endpoint, and providing an
> attribute link inline ..
>
> http://goo.gl/NWWaa2 for more information.
==
Ing. Andrea Aime
@geowolf
Technical Lead
GeoSolutions S.A.S.
Via
Happy to remove it.
Alternate for discussion - consider making WKT endpoint, and providing an
attribute link inline ..
DATUM["World Geodetic System 1984",
> SPHEROID["WGS 84", 6378137.0, 298.257223563,
> AUTHORITY["EPSG","7030"]],
> AUTHORITY["EPSG","6326"]],
> PRIMEM["Greenwich", 0.
On Wed, Jan 21, 2015 at 7:09 PM, Jody Garnett
wrote:
> As for the proposal I like it, any chance of this interface living in
> GeoTools level? Not that I will ever get WPS client funding...
>
I don't see it happening without funding... unless someone decides to crush
a good number of weekends o
As for the proposal I like it, any chance of this interface living in
GeoTools level? Not that I will ever get WPS client funding...
Alternate suggestion is to split this up into a read interface and a write
interface (with the same method names) - and then use those as marker
interfaces.
--
Jody
+1 for removing it.
GetCap docs are already beg enough!
Regards,
Simone Giannecchini
==
GeoServer Professional Services from the experts! Visit http://goo.gl/NWWaa2
for more information.
Please, notice that GeoSolutions will be closed for seasonal holidays from
December the 24th to January the
On Wed, Jan 21, 2015 at 6:50 PM, Jody Garnett
wrote:
> It is okay Andrea, it was just a question about proposal for new extension
> points (since I have not been in day to day geoserver for a while). If we
> can handle it via email that is fine :)
>
Cool, either work for me.
If anyone has feedba
Hi,
reviewing the WMS 1.3 and WMS 1.1 capabilties documents I've noticed
that in the WMS 1.1 one we have, for each layer, a comment showing
the full WKT syntax for the native CRS of that layer, for example:
EPSG:4326
EPSG:3010
This adds quite a bit of extra text to the
It is okay Andrea, it was just a question about proposal for new extension
points (since I have not been in day to day geoserver for a while). If we
can handle it via email that is fine :)
--
Jody
--
Jody Garnett
On 21 January 2015 at 01:47, Andrea Aime
wrote:
> Hi all,
> here is a proposal f
On Wed, Jan 21, 2015 at 4:17 PM, Andrea Aime
wrote:
> void customizeRootSrsList(Set srs);
>
> void customizeFormats(String operationName, Set formats);
>
About the formats, it makes more sense to implement ExtensionFilter and
remove
the formats we don't want direclty in GeoServerExtensions.
Any
Title: Message Title
Andrea Aime reopened an issue
Hi,
I'm looking into a case where we would like to have more control over the
capabilities
document generated by GeoServer, without having to fork off its code, or to
interfere
with other plugins already customizing it (e.g. the INSPIRE one).
Now, the requirements would be, more or less, to:
* Con
On Tue, Jan 20, 2015 at 4:13 PM, Andrea Aime
wrote:
> Hi,
> for all those that can access wordpress, here is a link to the draft blog
> post for the 2.7-beta release:
>
> http://blog.geoserver.org/wp-admin/post.php?post=2070&action=edit&message=10
>
> Please integrate/review :-)
>
Following a co
Hi all,
here is a proposal for the 2.8.x series:
https://github.com/geoserver/geoserver/wiki/GSIP-126---Runtime-ProcessParameterIO-creation
The proposal implementation will be quite simple and non invasive, so we'll
want to propose
a backport to the 2.7.x series once the dust settles around the 2
20 matches
Mail list logo
