[Geoserver-devel] Getting Store source files from a FeatureTypeInfo(Impl)?

I'm trying to extend Daniele's work on DirectDownload to handle non-Coverage cases. I understand that this isn't going to work for every case (e.g. if it is a database Store), but the case I'm interested in should be a file. The web part seems OK, and I'm up to the part where I need to handle bu

[Geoserver-devel] Build failed in Jenkins: 2.8-cite-wms-1.1 #37

See -- [...truncated 9003 lines...] [exec] at net.sf.saxon.instruct.Block.processLeavingTail(Block.java:409) [exec] at net.sf.saxon.expr.LetExpression.processLeavingTail(LetExpres

[Geoserver-devel] Build failed in Jenkins: 2.8-cite-wcs-1.1 #37

See -- [...truncated 1314 lines...] all: build.script: build.script: data: webapp.scripts: [mkdir] Created dir:

[Geoserver-devel] Build failed in Jenkins: 2.8-cite-wcs-1.0 #37

See -- [...truncated 1385 lines...] war: [zip] Building zip: jar.realm: compile: [mkdir] Creat

[Geoserver-devel] Build failed in Jenkins: 2.8-cite-wfs-1.0 #37

See -- [...truncated 3250 lines...] [exec] at net.sf.saxon.instruct.Block.processLeavingTail(Block.java:409) [exec] at net.sf.saxon.instruct.Block.processLeavingTail(Block.java:40

[Geoserver-devel] Build failed in Jenkins: cite-wms-1.3 #743

See -- [...truncated 1830 lines...] + (( i++ )) + (( i <= 100 )) + sleep 2 + echo 'Pinging GeoServer at http://localhost:11010/geoserver' Pinging GeoServer at http://localhost:11010/geoserver + curl -G

[Geoserver-devel] Build failed in Jenkins: cite-wfs-1.0 #749

See -- [...truncated 1944 lines...] + (( i++ )) + (( i <= 100 )) + sleep 2 + echo 'Pinging GeoServer at http://localhost:11010/geoserver' Pinging GeoServer at http://localhost:11010/geoserver + curl -G

Re: [Geoserver-devel] LayergroupInfo changes

+0. No objection. On 06/11/15 23:46, Niels Charlier wrote: > https://github.com/geoserver/geoserver/wiki/GSIP-135 > > Let me know what you think. > > Kind Regards > Niels > > On 27-10-15 19:09, Jody Garnett wrote: >> Yeah okay I like that. >> >> I had a proposal a while back to organize our pages

[Geoserver-devel] Build failed in Jenkins: cite-wcs-1.1 #746

See -- [...truncated 1848 lines...] + (( i++ )) + (( i <= 100 )) + sleep 2 + echo 'Pinging GeoServer at http://localhost:11010/geoserver' Pinging GeoServer at http://localhost:11010/geoserver + curl -G

[Geoserver-devel] Build failed in Jenkins: cite-wcs-1.0 #747

See -- [...truncated 1829 lines...] + (( i++ )) + (( i <= 100 )) + sleep 2 + echo 'Pinging GeoServer at http://localhost:11010/geoserver' Pinging GeoServer at http://localhost:11010/geoserver + curl -G

[Geoserver-devel] Build failed in Jenkins: cite-wms-1.1 #746

See -- [...truncated 1818 lines...] + (( i++ )) + (( i <= 100 )) + sleep 2 + echo 'Pinging GeoServer at http://localhost:11010/geoserver' Pinging GeoServer at http://localhost:11010/geoserver + curl -G

Re: [Geoserver-devel] FW: geoserver 2.8.x branch build error on htmlvalidator-1.2.pom - how to resolve?

I uploaded 1.2 (which was what the original bug report called for). However we may need to change the pom.xml boundless Boundless Maven Repository https://boundless.artifactoryonline.com/boundless/main/ true Can you try uncommenting (so the 1.2 jar can be found)

Re: [Geoserver-devel] LayergroupInfo changes

I updated the page with +1, but your proposal may of used the old template? -- Jody Garnett On 6 November 2015 at 11:46, Niels Charlier wrote: > https://github.com/geoserver/geoserver/wiki/GSIP-135 > > Let me know what you think. > > Kind Regards > Niels > > > On 27-10-15 19:09, Jody Garnett wr

Re: [Geoserver-devel] [NEW FEATURE] New configuration and memory caching of features in WFS GetFeature requests.

Hi Andrea, On 6 November 2015 at 12:03, Andrea Aime wrote: > Say someone sets the cache limit to 1000, and also sets the global max > features to 1000... or that the GetFeature > is a paged one (has a maxFeatures/count parameter), and we know in advance > only 100 features are going to be loaded

Re: [Geoserver-devel] [NEW FEATURE] New configuration and memory caching of features in WFS GetFeature requests.

Hi, I moved the cache to other point (ContentFeatureCollection), it seems me better, and that would help with all data sources, not just shapefiles.:-) https://github.com/geotools/geotools/compare/master...ahuarte47:GEOS-7301_CachedFeatureCollection Whay do tou think ? De: Andrea Aime Par

[Geoserver-devel] [JIRA] (GEOS-7301) Speed up GetFeature queries for datasources with slow count queries

Title: Message Title Sampo Savolainen created an issue

Re: [Geoserver-devel] [NEW FEATURE] New configuration and memory caching of features in WFS GetFeature requests.

Hi Robert, your mail made me consider another option... assuming that we have a caching memory limit configured somewhere, what if we know in advance that we cannot possibly go beyond it, because the current request or the global max features is bigger than the cached size? Say someone sets the ca

Re: [Geoserver-devel] LayergroupInfo changes

+1 -Jukka Rahkonen- Niels Charlier wrote: https://github.com/geoserver/geoserver/wiki/GSIP-135 Let me know what you think. Kind Regards Niels On 27-10-15 19:09, Jody Garnett wrote: Yeah okay I like that. I had a proposal a while back to organize our pages with consistent headings (like GetC

Re: [Geoserver-devel] LayergroupInfo changes

+0 Regards, Simone Giannecchini == GeoServer Professional Services from the experts! Visit http://goo.gl/it488V for more information. == Ing. Simone Giannecchini @simogeo Founder/Director GeoSolutions S.A.S. Via Poggio alle Viti 1187 55054 Massarosa (LU) Italy phone: +39 0584 962313 fax: +3

Re: [Geoserver-devel] LayergroupInfo changes

Hi Niels, had a quick read, all seems perfectly reasonable, +1 Cheers Andrea On Fri, Nov 6, 2015 at 11:46 AM, Niels Charlier wrote: > https://github.com/geoserver/geoserver/wiki/GSIP-135 > > Let me know what you think. > > Kind Regards > Niels > > > On 27-10-15 19:09, Jody Garnett wrote: > > Y

Re: [Geoserver-devel] LayergroupInfo changes

https://github.com/geoserver/geoserver/wiki/GSIP-135 Let me know what you think. Kind Regards Niels On 27-10-15 19:09, Jody Garnett wrote: Yeah okay I like that. I had a proposal a while back to organize our pages with consistent headings (like GetCapabilities for all the title, abstract, m

Re: [Geoserver-devel] [NEW FEATURE] New configuration and memory caching of features in WFS GetFeature requests.

On 6 November 2015 at 08:04, A Huarte wrote: > Hi Andrea, you are right, I verified same behavior in postgis layers. Each > WFS GetFeature request (v1.1/2.0) executes two SQL requests to the database > similar to shapefile: > > - size = features.size() sentence: > First request using "JDBCFeatu

Re: [Geoserver-devel] [NEW FEATURE] New configuration and memory caching of features in WFS GetFeature requests.

On Fri, Nov 6, 2015 at 9:56 AM, A Huarte wrote: > > Hi, I see a problem in my proposal. For long GetFeature requests, two > "JDBCFeatureSource::getReaderInternal()" > calls are executed, much worse than "JDBCFeatureSource::getCountInternal()" > + "JDBCFeatureSource::getReaderInternal()" calls. >

Re: [Geoserver-devel] [NEW FEATURE] New configuration and memory caching of features in WFS GetFeature requests.

Hi, I see a problem in my proposal. For long GetFeature requests, two  "JDBCFeatureSource::getReaderInternal()" calls are executed, much worse than "JDBCFeatureSource::getCountInternal()" + "JDBCFeatureSource::getReaderInternal()" calls. The best, preserve the cache directly in the shapefile pro

Re: [Geoserver-devel] [NEW FEATURE] New configuration and memory caching of features in WFS GetFeature requests.

To try clarify my comments, better a little of code: https://github.com/geoserver/geoserver/compare/master...ahuarte47:GEOS-7296_fix_read_twice :-) Alvaro De: A Huarte Para: Andrea Aime CC: "geoserver-devel@lists.sourceforge.net" Enviado: Viernes 6 de noviembre de 2015 9:04 Asunto:

Re: [Geoserver-devel] [NEW FEATURE] New configuration and memory caching of features in WFS GetFeature requests.

On Thu, Nov 5, 2015 at 11:52 AM, A Huarte  wrote: Hi, I would propose this new feature to solve the issue  https://osgeo-org.atlassian.net/browse/GEOS-7296 Now, the WFS requests of 1.1/2.0 versions force to read the features from the data source (and also filter evaluation) twice. Or each time a