Re: [Geoserver-devel] Reminder: GeoTools / GeoServer Meeting at 15:30 UTC on Tuesday

[Jody Garnett]

Are we adjusted for time zones here?
On Mon, Nov 14, 2016 at 10:22 AM Ben Caradoc-Davies 
wrote:

> GeoTools / GeoServer committee meeting on Skype at 15:30 UTC on Tuesday:
>
> http://www.timeanddate.com/worldclock/fixedtime.html?msg=GeoTools+%2F+GeoServer+Meeting&year=2016&month=11&day=15&hour=15&min=30&sec=0&ah=1
>
> --
> Ben Caradoc-Davies 
> Director
> Transient Software Limited 
> New Zealand
>
>
> --
> ___
> Geoserver-devel mailing list
> Geoserver-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>
-- 
--
Jody Garnett
--
___
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

[Geoserver-devel] OSGeo Live 10.5: upgrade GeoServer to 2.10.1, move to Transifex

[Ben Caradoc-Davies]

OSGeo Live is a live image based on Lubuntu that contains a variety of 
open source geospatial software:
https://live.osgeo.org/en/index.html

The current release of OSGeo Live (10.0) contains GeoServer 2.8.3, which 
is no longer supported. I have volunteered to upgrade GeoServer to 
2.10.1 for OSGeo Live 10.5. This upgrade presents an opportunity to add 
more content to match recent GeoServer developments.

I am considering adding more plugins. The current image contains the 
INSPIRE and CSS extensions and the entire HTML docs (yay!). Nice things 
to demonstrate might include the NetCDF plugin which is newly in 
GeoServer supported-land. There was also interest in GeoGig.

OSGeo Live 10.5 release schedule:

Feature freeze: 20 January 2017
Final ISO release: 10 March 2017

Questions:

(1) What things could be upgraded or added to the OSGeo Live image to 
make it more useful to members of the GeoServer community? Would 
additional plugins enhance OSGeo Live?

(2) Is anyone interested in contributing a small amount of tutorial 
material? A subset of the multidimensional coverage tutorial might be a 
useful demonstration of the NetCDF and NetCDF-out plugins.

(3) The OSGeo Live developers are also moving translations to Transifex 
and are soliciting contributions of translations. If anyone wants to 
contribute translations to OSGeo Live, please let me know.

IRC log of today's meeting:
http://irclogs.geoapt.com/osgeolive/%23osgeolive.2016-11-14.log

Kind regards,

-- 
Ben Caradoc-Davies 
Director
Transient Software Limited 
New Zealand

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

[Geoserver-devel] Build failed in Jenkins: GeoServer-Master-OpenJDK8 #1135

[jenkins]

See 


Changes:

[tbarsballe] [GEOS-7826] Add check for no layers when instantiating Style Editor

--
[...truncated 79448 lines...]
Started calculate disk usage of workspace
Finished Calculation of disk usage of workspace in 0 seconds
[INFO] 
[INFO] Reactor Summary:
[INFO] 
[INFO] GeoServer .. SUCCESS [  4.378 s]
[INFO] Core Platform Module ... SUCCESS [ 14.348 s]
[INFO] Open Web Service Module  SUCCESS [  8.497 s]
[INFO] Main Module  SUCCESS [01:36 min]
[INFO] GeoServer Security Modules . SUCCESS [  2.703 s]
[INFO] GeoServer JDBC Security Module . SUCCESS [ 16.727 s]
[INFO] GeoServer LDAP Security Module . SUCCESS [ 17.290 s]
[INFO] Web Coverage Service Module  SUCCESS [  4.283 s]
[INFO] Web Coverage Service 1.0 Module  SUCCESS [ 15.322 s]
[INFO] Web Coverage Service 1.1 Module  SUCCESS [ 17.726 s]
[INFO] Web Coverage Service 2.0 Module  SUCCESS [ 37.359 s]
[INFO] Web Feature Service Module . SUCCESS [ 59.802 s]
[INFO] Web Map Service Module . FAILURE [02:29 min]
[INFO] KML support for GeoServer .. SKIPPED
[INFO] GeoWebCache (GWC) Module ... SKIPPED
[INFO] REST Support Module  SKIPPED
[INFO] REST Configuration Service Module .. SKIPPED
[INFO] GeoServer Web Modules .. SKIPPED
[INFO] Core UI Module . SKIPPED
[INFO] WMS UI Module .. SKIPPED
[INFO] GWC UI Module .. SKIPPED
[INFO] WFS UI Module .. SKIPPED
[INFO] Demos Module ... SKIPPED
[INFO] WCS UI Module .. SKIPPED
[INFO] Security UI Modules  SKIPPED
[INFO] Security UI Core Module  SKIPPED
[INFO] Security UI JDBC Module  SKIPPED
[INFO] Security UI LDAP Module  SKIPPED
[INFO] REST UI Module . SKIPPED
[INFO] GeoServer Web Application .. SKIPPED
[INFO] Community Space  SKIPPED
[INFO] GeoServer Extensions ... SKIPPED
[INFO] Application Schema Support . SKIPPED
[INFO] Application Schema Integration Test  SKIPPED
[INFO] Sample DataAccess Integration Test . SKIPPED
[INFO] ArcSDE DataStore Extension . SKIPPED
[INFO] H2 DataStore Extension . SKIPPED
[INFO] SQL Server DataStore Extension . SKIPPED
[INFO] Oracle DataStore Extension . SKIPPED
[INFO] MySQL DataStore Extension .. SKIPPED
[INFO] DB2 DataStore Extension  SKIPPED
[INFO] ImageMap Output Format . SKIPPED
[INFO] ImageI/O-Ext GDAL Coverage Extension ... SKIPPED
[INFO] JP2K Coverage Extension  SKIPPED
[INFO] OGR parent . SKIPPED
[INFO] OGR CORE ... SKIPPED
[INFO] OGR WFS  SKIPPED
[INFO] Web Processing Service parent .. SKIPPED
[INFO] Web Processing Service Module .. SKIPPED
[INFO] OGR WPS  SKIPPED
[INFO] Excel Output Format  SKIPPED
[INFO] Chart external graphics support  SKIPPED
[INFO] Feature Generalization Extension ... SKIPPED
[INFO] Image Mosaic JDBC Extension  SKIPPED
[INFO] OWS request flow controller  SKIPPED
[INFO] Web process status sharing with Hazelcast .. SKIPPED
[INFO] Web Processing Service GUI . SKIPPED
[INFO] GeoServer Layer Querying filter functions .. SKIPPED
[INFO] Teradata DataStore Extension ... SKIPPED
[INFO] GeoServer Monitor Extensions ... SKIPPED
[INFO] Core Monitor Extension . SKIPPED
[INFO] Monitor Hibernate Extension  SKIPPED
[INFO] GeoServer Security Extension Modules ... SKIPPED
[INFO] GeoServer CAS Security Module .. SKIPPED
[INFO] GeoServer Secur

[Geoserver-devel] [GEOS-7852] - GoeServer CatalogFacade API violation

[Torben Barsballe]

I found an interesting behavior in the GeoServer REST API today. Details
described here: here https://osgeo-org.atlassian.net/browse/GEOS-7852

While it does not impact functionality of core GeoServer, it could be
construed as a violation of the CatalodFacade interface / api.

Unless there was a good reason for this implementation, I think it should
be fixed.
PR here: https://github.com/geoserver/geoserver/pull/1966
Opinions welcome.
--
___
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

[Geoserver-devel] readthedocs

[Jody Garnett]

So the robots.txt is cutting down web searches finding old docs, but
http://geoserver.readthedocs.io is holding on to an old version.

Anyone know who set this up, can we update or kill it?
--
Jody Garnett
--
___
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

[Geoserver-devel] [JIRA] (GEOS-7852) REST API implementation for setting defaults violates Catalog API

[Torben Barsballe (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Torben Barsballe created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 GeoServer /  GEOS-7852  
 
 
  REST API implementation for setting defaults violates Catalog API   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Unassigned  
 
 
Components: 
 REST  
 
 
Created: 
 15/Nov/16 1:32 AM  
 
 
Priority: 
  Medium  
 
 
Reporter: 
 Torben Barsballe  
 

  
 
 
 
 

 
 The REST API implementation of handleObjectPut for NamespaceResource and WorkspaceResource has an odd implementation for case of setting the default value. It passes a partial (name / prefix set, everything else null, including Id) Info object to catalog.setDefault[Workspace/Namespace]: https://github.com/geoserver/geoserver/blob/master/src/restconfig/src/main/java/org/geoserver/catalog/rest/NamespaceResource.java#L88 https://github.com/geoserver/geoserver/blob/master/src/restconfig/src/main/java/org/geoserver/catalog/rest/WorkspaceResource.java#L121 Just looking at the CatalogInfo / CatalogFacade interfaces, the behaviour for this is undefined, but the implication is that you should be passing valid Catalig objects to the CatalogFacade method. Looking at the implementation, it appears this only works because there is a special case hardcoded in to handle it: https://github.com/geoserver/geoserver/blob/master/src/main/src/main/java/org/geoserver/catalog/impl/DefaultCatalogFacade.java#L645 https://github.com/geoserver/geoserver/blob/master/src/main/src/main/java/org/geoserver/catalog/impl/DefaultCatalogFacade.java#L744 The REST API implementation should be fixed.  
 

  
 
 
  
 

 
 
 

Re: [Geoserver-devel] Does the scripting extension still work?

[Jody Garnett]

It is included in opengeo suite ... focused on the python flavour.

--
Jody Garnett

On 14 November 2016 at 09:55, Ian Turton  wrote:

> Before I dive into a debugging marathon, does any one know if the
> scripting extension (http://docs.geoserver.org/stable/en/user/community/
> scripting/installation.html) currently work? I can find people
> complaining since 2.7 (https://gis.stackexchange.com/questions/158006/
> geoserver-2-7-1-fails-to-start-after-installing-11-aug-
> 2015-scripting-extension) and it doesn't seem to work for me with 2.11.x
> on Ubuntu and Java8.
>
> Cheers
>
> Ian
>
> --
> Ian Turton
>
> 
> --
>
> ___
> Geoserver-devel mailing list
> Geoserver-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>
>
--
___
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

Re: [Geoserver-devel] Documentation - Translating the Geoserver Web Interface (geoserver-users crosspost)

[Jody Garnett]

It should be added, some of the translations have not been touched in some
time.

--
Jody Garnett

On 14 November 2016 at 10:24, P O'Toole  wrote:

> >Message: 3
>
> >Date: Sun, 13 Nov 2016 08:07:21 +1300
>
> >From: Ben Caradoc-Davies 
>
> >Subject: Re: [Geoserver-users] Translating the Geoserver Web Interface
>
> >To: Ammar 
>
> >Cc: "geoserver-us...@lists.sourceforge.net"
>
> >
>
> >Message-ID: 
>
> >Content-Type: text/plain; charset=utf-8; format=flowed
>
>
>
> >Ammar,
>
> >
>
> >welcome! Do you have particular languages of interest?
>
> >
>
> >Because web interface translations are merged into to GeoServer source
>
> >code, translation discussions occur on the geoserver-devel mailing list.
>
> >
>
> >Frank is the Transifex project maintainer:
>
> >https://www.transifex.com/GeoServer/geoserver/
>
> >
>
> >Frank has written an updated translation guide that describes how to use
>
> >Transifex:
>
> >https://github.com/fgdrf/geoserver/blob/406b761bf64a4bf345db2402efc9dd
> 4d04ae3cc0/doc/en/developer/source/translation.rst
>
> >
>
> >Here is a mailing list discussion about Transifex from earlier this year:
>
> >http://osgeo-org.1560.x6.nabble.com/How-translating-
> Geoserver-through-Transifex-works-td5248325.html
>
> >
>
> >( The translation guide from the developer manual is out of date and
>
> >does not mention Transifex:
>
> >http://docs.geoserver.org/latest/en/developer/translation.html )
>
> >
>
> >Kind regards,
>
> >Ben.
>
>
>
> I looked briefly at the tracker, but I didn't see any issues stating that
> the contributed-translations part of the docs are out-of-date.
>
>
>
> Am I just not finding it, or should this be added?
>
>
>
> While I'm at it, is there a clean way to find **ALL** the
> documentation-related issues in JIRA? (Like a documentation-type issue as
> opposed to Bug/Improvement/New Feature/etc.?) I'll eventually be putting in
> a PR to get some of the WPS/Script-plugin docs more up-to-date, and I'd be
> happy to at least provide some basic pointers to users in other sections of
> the documentation where the current presentation has gotten stale (even if
> a more expert eye would be needed to make said sections fully exhaustive).
> That'll be easier if there's a good way to determine where current
> docs-deficiencies are.
>
>
>
> Thanks,
>
> - Patrick O'Toole
>
>
>
> Application Developer
>
> Wyoming Natural Diversity Database 
>
> UW Berry Biodiversity Conservation Center
>
> Department 3381, 1000 E. University Av.
>
> Laramie, WY 82071
>
> P: 307-766-3018
>
>
>
> 
> --
>
> ___
> Geoserver-devel mailing list
> Geoserver-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>
>
--
___
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

[Geoserver-devel] Documentation - Translating the Geoserver Web Interface (geoserver-users crosspost)

[P O'Toole]

>Message: 3
>Date: Sun, 13 Nov 2016 08:07:21 +1300
>From: Ben Caradoc-Davies 
>Subject: Re: [Geoserver-users] Translating the Geoserver Web Interface
>To: Ammar 
>Cc: "geoserver-us...@lists.sourceforge.net"
>
>Message-ID: 
>Content-Type: text/plain; charset=utf-8; format=flowed

>Ammar,
>
>welcome! Do you have particular languages of interest?
>
>Because web interface translations are merged into to GeoServer source
>code, translation discussions occur on the geoserver-devel mailing list.
>
>Frank is the Transifex project maintainer:
>https://www.transifex.com/GeoServer/geoserver/
>
>Frank has written an updated translation guide that describes how to use
>Transifex:
>https://github.com/fgdrf/geoserver/blob/406b761bf64a4bf345db2402efc9dd4d04ae3cc0/doc/en/developer/source/translation.rst
>
>Here is a mailing list discussion about Transifex from earlier this year:
>http://osgeo-org.1560.x6.nabble.com/How-translating-Geoserver-through-Transifex-works-td5248325.html
>
>( The translation guide from the developer manual is out of date and
>does not mention Transifex:
>http://docs.geoserver.org/latest/en/developer/translation.html )
>
>Kind regards,
>Ben.

I looked briefly at the tracker, but I didn't see any issues stating that the 
contributed-translations part of the docs are out-of-date.

Am I just not finding it, or should this be added?

While I'm at it, is there a clean way to find *ALL* the documentation-related 
issues in JIRA? (Like a documentation-type issue as opposed to 
Bug/Improvement/New Feature/etc.?) I'll eventually be putting in a PR to get 
some of the WPS/Script-plugin docs more up-to-date, and I'd be happy to at 
least provide some basic pointers to users in other sections of the 
documentation where the current presentation has gotten stale (even if a more 
expert eye would be needed to make said sections fully exhaustive). That'll be 
easier if there's a good way to determine where current docs-deficiencies are.

Thanks,
- Patrick O'Toole

Application Developer
Wyoming Natural Diversity Database
UW Berry Biodiversity Conservation Center
Department 3381, 1000 E. University Av.
Laramie, WY 82071
P: 307-766-3018

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

[Geoserver-devel] Reminder: GeoTools / GeoServer Meeting at 15:30 UTC on Tuesday

[Ben Caradoc-Davies]

GeoTools / GeoServer committee meeting on Skype at 15:30 UTC on Tuesday:
http://www.timeanddate.com/worldclock/fixedtime.html?msg=GeoTools+%2F+GeoServer+Meeting&year=2016&month=11&day=15&hour=15&min=30&sec=0&ah=1

-- 
Ben Caradoc-Davies 
Director
Transient Software Limited 
New Zealand

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

[Geoserver-devel] Does the scripting extension still work?

[Ian Turton]

Before I dive into a debugging marathon, does any one know if the scripting
extension (
http://docs.geoserver.org/stable/en/user/community/scripting/installation.html)
currently
work? I can find people complaining since 2.7 (
https://gis.stackexchange.com/questions/158006/geoserver-2-7-1-fails-to-start-after-installing-11-aug-2015-scripting-extension)
and it doesn't seem to work for me with 2.11.x on Ubuntu and Java8.

Cheers

Ian

-- 
Ian Turton
--
___
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

[Geoserver-devel] [JIRA] (GEOS-7851) Backup and Restore may fail if java.io.tmpdir is not defined

[Alessio Fabiani (JIRA)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Alessio Fabiani created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 GeoServer /  GEOS-7851  
 
 
  Backup and Restore may fail if java.io.tmpdir is not defined   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Alessio Fabiani  
 
 
Components: 
 Backup and Restore, Community modules  
 
 
Created: 
 14/Nov/16 12:25 PM  
 
 
Priority: 
  Medium  
 
 
Reporter: 
 Alessio Fabiani  
 

  
 
 
 
 

 
 BackupUtils class needs to store temporary files in a temp folder. In order to do this it is now trying to do Resource root = Resources.fromPath(System.getProperty("java.io.tmpdir", ".")); This causes an exception if the property "java.io.tmpdir" is null falling back to "." java.lang.IllegalArgumentException: Contains invalid . path:  at org.geoserver.platform.resource.Paths.toPath(Paths.java:168) at org.geoserver.platform.resource.Paths.path(Paths.java:114) at org.geoserver.platform.resource.Paths.path(Paths.java:96) at org.geoserver.platform.resource.FileSystemResourceStore$FileSystemResource.get(FileSystemResourceStore.java:422) The proposed solution would be to make use of the GeoServer data dir temp folder if the System variable is not available. GeoServer will WARNING the user about this since the GEOSERVER Data Dir temp folder may considerably increase in size.  
 

  
 
 
  
 

 
 
 

 
 
 Add Comment