[Geoserver-devel] [JIRA] (GEOS-8172) Store UI inconsistent about file location format

Title: Message Title Kevin Smith

[Geoserver-devel] [JIRA] (GEOS-8171) ExternalGraphicFactory does not have a general way to reset caches

Title: Message Title David Vick created

Re: [Geoserver-devel] [Geotools-devel] upgrade postgresql JDBC driver to 42.1.1 (full binary xfer)

Hi, I have no particular object, but not going to take responsibility for it. Merge as you see fit (and handle whatever side effect). Cheers Andrea On Tue, Jun 6, 2017 at 6:54 PM, Dave Blasby wrote: > Hi, > > I was hoping we could merge Ben's PR, which updates the

Re: [Geoserver-devel] [Geotools-devel] upgrade postgresql JDBC driver to 42.1.1 (full binary xfer)

Hi, I was hoping we could merge Ben's PR, which updates the driver version. https://github.com/geotools/geotools/pull/1605 Thanks, Dave On Wed, May 31, 2017 at 4:08 AM, Ben Caradoc-Davies wrote: > CentOS 6 has 8.4.20: >

[Geoserver-devel] [JIRA] (GEOS-8170) Allow CatalogBuilder to setup a new CoverageInfo even if the test read return null

Title: Message Title aaime created an

Re: [Geoserver-devel] geofence: invalidating rules cache

Ouch. So do you reckon there is possible method to determine whether a cache entry is affected by a specific rule? Could we say that my method works as long as priority doesn't change? Or are there other concerns apart from priority? And in case the priority changes, could we perhaps repeat

Re: [Geoserver-devel] geofence: invalidating rules cache

> Could we say that my method works as long as priority doesn't change? Or > are there other concerns apart from priority? As said, the Rules behaviour is quite contextual, as the Rules work as a whole and not singularly; the priority example is just one way to make this clear. Let me show

Re: [Geoserver-devel] geofence: invalidating rules cache

Hello Emanuele, Thanks for your email. You say "a change in a single Rule may reflect in changes in many items in the cache, that are quite difficult to track down." Would a RuleFilter.match(Rule) not be able to track this down? The cache is indexed on rule filters... All rule filters that

[Geoserver-devel] Jenkins build is back to normal : geoserver-2.9.x #433

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

[Geoserver-devel] [JIRA] (GEOS-8169) CQL filter in layer preview disabled for ImageMosaics

Title: Message Title Alessandro Parma

[Geoserver-devel] Backporting legend graphics with count functionality

Hi, a month ago the new ability to add feature counts in the legend output: https://github.com/geoserver/geoserver/pull/2296 e.g: https://github.com/aaime/geoserver/blob/89723950a199cf90b12dcd92c5b0f8ddf0b794f2/doc/en/user/source/services/wms/get_legend_graphic/img/states-all.png I'd like to

Re: [Geoserver-devel] geofence: invalidating rules cache

Hi Niels, the access info that GeoServer receives from GeoFence may come from more than one Rule. The Rule engine looks for all matching rules: constraints contained in Rules of LIMIT type will be merged so to restrict the constraints found in the ALLOW rule. Furthermore, if a user belongs to

Re: [Geoserver-devel] WFS 2.0 DescribeType opertation: typeName or typeNames

However: http://docs.opengeospatial.org/is/09-025r2/09-025r2.html#88 Quoting: For KVP-encoded ad hoc query expressions the typeNames parameter shall be encoded using the TYPENAMES keyword (see Table 8). The TYPENAMES parameter is mandatory in all cases except when the RESOURCEID parameter is