Re: [Geoserver-devel] Pull request #841 / CQL concatenation

[Sampo Savolainen]

Hi,

Interesting. To clarify, would this mean the expression [ foo + ',' + bar ]
in my current branch would be replaced by [ foo ',' bar ] (brackets are
there only to separate expressions from text)? And this would mean the
value of foo concatenated to ',' concatenated to the valut of bar?

If so, this definitely is a workable solution in my case as well. It's
definitely best if we can avoid having slightly different CQL syntax in
different places.


 Sampo

On Thu, Dec 11, 2014 at 8:19 PM, Jody Garnett 
wrote:
>
> Thanks for taking discussion to the email list.
>
> For your question: "should I remove the overridden + operator and go with
> the standard concatenation function?"
>
> We have a similar requirement in a few places in our code (handling of
> labels in SLD, and handling of embedded CQL expressions in external
> graphics). In these cases rather than use "+" we use whitespace - resulting
> in a list of expressions that can be evaluated).
>
> I think ECQL has a method that takes a lis of expressions separated by ";"
> as well.
>
> Would you be with using white space to produce your Concatenate
> expression? This would make the codebase a bit more consistent (and one
> less opportunity for confusion).
> --
> Jody
>
> --
> Jody Garnett
>
> On 11 December 2014 at 00:44, Sampo Savolainen <
> sampo.savolai...@spatineo.com> wrote:
>
>> Hi,
>>
>> Jody and I have been discussing my pull request on cascaded stored
>> requests and we'd like to open another point to wider debate.
>>
>> This is regarding Jody's notes on this test case:
>> https://github.com/geoserver/geoserver/pull/841#discussion-diff-21495146
>>
>> Some background: my implementation of cascaded stored query passes stored
>> query parameters to the backend via two mechanisms:
>>
>>1. The original request to the feature type backed by a cascaded
>>stored query may include view parameters, just like with Virtual Table
>>backed feature types.
>>2. Feature type configuration may specify mappings to the parameters.
>>
>> There are a two types of mappings possible in the implementation. You can
>> either specify a default value (two flavours: one you can override with a
>> view parameter and another you can't), or the parameter value can be
>> evaluated from an expression. The discussion here is regarding these
>> expressions.
>>
>> The expressions are written in CQL and are executed within a context
>> where the query filter, basic feature type information and the query bounds
>> are accessible. A stored query that my work specifically targets has a
>> bounding box parameter that needs to be derived from this context. I used
>> expressions instead of a hard-coded bounding box type parameter mapping to
>> make the implementation more general.
>>
>> When I wrote the CQL expression parts, I was only aware of a single
>> concatenation function in CQL, strConCat. This function only takes two
>> parameters and both must be strings. So as you can see in the test
>> referenced by the diff, the expression to build a bounding box becomes
>> quite a mess. To avoid this, I overrode the + operator for these
>> expressions so it does string concatenation if either the left hand side or
>> right hand side values were strings.
>>
>>
>> https://github.com/geotools/geotools/blob/master/modules/unsupported/wfs-ng/src/main/java/org/geotools/data/wfs/internal/v2_0/storedquery/ParameterCQLExpressionFilterFactoryImpl.java#L104
>>
>> However, Jody led me on to the fact that there is a multi-parameter
>> concatenation function in CQL.
>>
>> Now the question is: should I remove the overridden + operator and go
>> with the standard concatenation function?
>>
>>
>> Also: I was unable to find reference documentation on this concatenation
>> function. Maybe someone knows where it is so I can check it? Especially
>> whether it allows combining numbers and strings is of interest.
>>
>>
>>   Sampo
>>
>>
>>
>> --
>> Sampo Savolainen
>> R&D Director, Spatineo Oy
>> sampo.savolai...@spatineo.com
>> +358-407555649
>> Linnankoskenkatu 16 A 17, 00250 Helsinki, Finland
>> www.spatineo.com, twitter.com/#!/spatineo
>> www.linkedin.com/company/spatineo-inc
>>
>> This message may contain privileged and/or confidential information. If
>> you
>> have received this e-mail in error or are not the intended recipient, you
>> may not use, copy, disseminate, or distribute it; do not open any
>> attachments, delete it immediately from your system and notify the sender
>> promptly by e-mail that you have done so.
>>
>>
>> --
>> Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
>> from Actuate! Instantly Supercharge Your Business Reports and Dashboards
>> with Interactivity, Sharing, Native Excel Exports, App Integration & more
>> Get technology previously reserved for billion-dollar corporations, FREE
>>
>> http://pubads.g.doubleclick.net/gampad/clk?id=164703151&iu=/4140/ostg.clktrk
>> _

Re: [Geoserver-devel] Uploading CSS styles via REST

[Justin Deoliveira]

If I remember correctly the way it was done was that if you specify the
"raw=true" parameter, then it doesn't attempt any conversion.


http://docs.geoserver.org/stable/en/user/rest/api/styles.html#rest-api-styles-raw

This was I believe a result of developer feedback when the feature of
supporting different languages was implemented. I'm not tied to it any way.

On Thu, Dec 11, 2014 at 10:31 AM, Jody Garnett 
wrote:

> Yep, looks like a bug. I also found some issues when copying a style
> (either via the UI or via REST) and being unable to correct (the now
> incorrect) format via the UI (which is a read-only field).
>
> --
> Jody Garnett
>
> On 11 December 2014 at 10:21, Andrea Aime 
> wrote:
>
>> Hi,
>> one of the new features in the 2.6.0 release is the ability to handle
>> styles
>> in more than one language.
>>
>> I've seen it work with CSS on the web UI, but I've just tried with REST
>> and
>> I cannot seem to make it work, from what I can see it looks lilke a bug.
>>
>> Here is what I've done. First, create the style xml, telling GeoServer
>> I'm going
>> to upload a css:
>>
>> > curl -v -u admin:geoserver -XPOST -H "Content-type: text/xml" -d
>> "test_csstest_css.csscss"
>>  http://localhost:8080/geoserver/rest/styles
>> * Hostname was NOT found in DNS cache
>> *   Trying 127.0.0.1...
>> * Connected to localhost (127.0.0.1) port 8080 (#0)
>> * Server auth using Basic with user 'admin'
>> > POST /geoserver/rest/styles HTTP/1.1
>> > Authorization: Basic YWRtaW46Z2Vvc2VydmVy
>> > User-Agent: curl/7.35.0
>> > Host: localhost:8080
>> > Accept: */*
>> > Content-type: text/xml
>> > Content-Length: 89
>> >
>> * upload completely sent off: 89 out of 89 bytes
>> < HTTP/1.1 *201 Created*
>> < Date: Thu, 11 Dec 2014 18:07:58 GMT
>> < Location: http://localhost:8080/geoserver/rest/styles/test_css
>> * Server Noelios-Restlet-Engine/1.0..8 is not blacklisted
>> < Server: Noelios-Restlet-Engine/1.0..8
>> < Transfer-Encoding: chunked
>>
>> And then I'm going to upload the css file itself:
>>
>> > curl -v -u admin:geoserver -XPUT -H "Content-type:
>> application/vnd.geoserver.geocss+css" -d @test_css.css
>> http://localhost:8080/geoserver/rest/styles/test_css
>>
>> The upload works at least up to a certain point, but then fails with the
>> following stack trace:
>>
>> org.geoserver.rest.RestletException:
>> java.lang.UnsupportedOperationException
>> at
>> org.geoserver.rest.ReflectiveResource.handleException(ReflectiveResource.java:326)
>> at
>> org.geoserver.rest.ReflectiveResource.handlePut(ReflectiveResource.java:197)
>> at org.restlet.Finder.handle(Finder.java:298)
>> at
>> org.geoserver.rest.BeanDelegatingRestlet.handle(BeanDelegatingRestlet.java:38)
>> at org.restlet.Filter.doHandle(Filter.java:105)
>> at org.restlet.Filter.handle(Filter.java:134)
>> at org.restlet.Router.handle(Router.java:444)
>> at org.geoserver.rest.RESTDispatcher$1.handle(RESTDispatcher.java:205)
>> at
>> com.noelios.restlet.ext.servlet.ServletConverter.service(ServletConverter.java:129)
>> at
>> org.geoserver.rest.RESTDispatcher.handleRequestInternal(RESTDispatcher.java:87)
>> at
>> org.springframework.web.servlet.mvc.AbstractController.handleRequest(AbstractController.java:153)
>> at
>> org.springframework.web.servlet.mvc.SimpleControllerHandlerAdapter.handle(SimpleControllerHandlerAdapter.java:48)
>> at
>> org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:923)
>> at
>> org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:852)
>> at
>> org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:882)
>> at
>> org.springframework.web.servlet.FrameworkServlet.doPut(FrameworkServlet.java:800)
>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:730)
>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
>> at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:487)
>> at
>> org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1093)
>> at
>> org.geoserver.filters.ThreadLocalsCleanupFilter.doFilter(ThreadLocalsCleanupFilter.java:28)
>> at
>> org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1084)
>> at
>> org.geoserver.filters.SpringDelegatingFilter$Chain.doFilter(SpringDelegatingFilter.java:75)
>> at
>> org.geoserver.wms.animate.AnimatorFilter.doFilter(AnimatorFilter.java:71)
>> at
>> org.geoserver.filters.SpringDelegatingFilter$Chain.doFilter(SpringDelegatingFilter.java:71)
>> at
>> org.geoserver.filters.SpringDelegatingFilter.doFilter(SpringDelegatingFilter.java:46)
>> at
>> org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1084)
>> at
>> org.geoserver.platform.AdvancedDispatchFilter.doFilter(AdvancedDispatchFilter.java:50)
>> at
>> org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1084)
>> at
>> org.springframework.security.web.FilterChainProx

Re: [Geoserver-devel] Pull request (#841) / GeoServerFeatureSource constructor

[Jody Garnett]

Thanks Andrea, that is all we need. The new metadata thing was part of the
pull request from Sampo (hopefully with a parameter object we can get a
good javadoc explaining what it is for).

Jody

--
Jody Garnett

On 11 December 2014 at 10:24, Andrea Aime 
wrote:

> On Thu, Dec 11, 2014 at 6:59 PM, Jody Garnett 
> wrote:
>
>> I don't want to hold up the pull request on this one, should be a 5 mins
>> conversation.
>>
>
> Sorry, I'm busy enough that I don't know what day it is anymore these days
>
>
>> Andrea are these constructor arguments holding up?
>>
>
> You mean you want to introduce a parameter object to avoid growing the
> constructor?
> Sure, pretty standard refactoring I'd say.
>
> I have no idea what these new metadata things are though
>
> Cheers
> Andrea
>
> --
> ==
> 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 6th
> ==
>
> Ing. Andrea Aime
> @geowolf
> Technical Lead
>
> GeoSolutions S.A.S.
> Via Poggio alle Viti 1187
> 55054  Massarosa (LU)
> Italy
> phone: +39 0584 962313
> fax: +39 0584 1660272
> mob: +39  339 8844549
>
> http://www.geo-solutions.it
> http://twitter.com/geosolutions_it
>
> *AVVERTENZE AI SENSI DEL D.Lgs. 196/2003*
>
> Le informazioni contenute in questo messaggio di posta elettronica e/o
> nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il
> loro utilizzo è consentito esclusivamente al destinatario del messaggio,
> per le finalità indicate nel messaggio stesso. Qualora riceviate questo
> messaggio senza esserne il destinatario, Vi preghiamo cortesemente di
> darcene notizia via e-mail e di procedere alla distruzione del messaggio
> stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso,
> divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od
> utilizzarlo per finalità diverse, costituisce comportamento contrario ai
> principi dettati dal D.Lgs. 196/2003.
>
>
>
> The information in this message and/or attachments, is intended solely for
> the attention and use of the named addressee(s) and may be confidential or
> proprietary in nature or covered by the provisions of privacy act
> (Legislative Decree June, 30 2003, no.196 - Italy's New Data Protection
> Code).Any use not in accord with its purpose, any disclosure, reproduction,
> copying, distribution, or either dissemination, either whole or partial, is
> strictly forbidden except previous formal approval of the named
> addressee(s). If you are not the intended recipient, please contact
> immediately the sender by telephone, fax or e-mail and delete the
> information in this message that has been received in error. The sender
> does not give any warranty or accept liability as the content, accuracy or
> completeness of sent messages and accepts no responsibility  for changes
> made after they were sent or for other risks which arise as a result of
> e-mail transmission, viruses, etc.
>
> ---
>
--
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration & more
Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=164703151&iu=/4140/ostg.clktrk___
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

Re: [Geoserver-devel] Uploading CSS styles via REST

[Jody Garnett]

Yep, looks like a bug. I also found some issues when copying a style
(either via the UI or via REST) and being unable to correct (the now
incorrect) format via the UI (which is a read-only field).

--
Jody Garnett

On 11 December 2014 at 10:21, Andrea Aime 
wrote:

> Hi,
> one of the new features in the 2.6.0 release is the ability to handle
> styles
> in more than one language.
>
> I've seen it work with CSS on the web UI, but I've just tried with REST
> and
> I cannot seem to make it work, from what I can see it looks lilke a bug.
>
> Here is what I've done. First, create the style xml, telling GeoServer I'm
> going
> to upload a css:
>
> > curl -v -u admin:geoserver -XPOST -H "Content-type: text/xml" -d
> "test_csstest_css.csscss"
>  http://localhost:8080/geoserver/rest/styles
> * Hostname was NOT found in DNS cache
> *   Trying 127.0.0.1...
> * Connected to localhost (127.0.0.1) port 8080 (#0)
> * Server auth using Basic with user 'admin'
> > POST /geoserver/rest/styles HTTP/1.1
> > Authorization: Basic YWRtaW46Z2Vvc2VydmVy
> > User-Agent: curl/7.35.0
> > Host: localhost:8080
> > Accept: */*
> > Content-type: text/xml
> > Content-Length: 89
> >
> * upload completely sent off: 89 out of 89 bytes
> < HTTP/1.1 *201 Created*
> < Date: Thu, 11 Dec 2014 18:07:58 GMT
> < Location: http://localhost:8080/geoserver/rest/styles/test_css
> * Server Noelios-Restlet-Engine/1.0..8 is not blacklisted
> < Server: Noelios-Restlet-Engine/1.0..8
> < Transfer-Encoding: chunked
>
> And then I'm going to upload the css file itself:
>
> > curl -v -u admin:geoserver -XPUT -H "Content-type:
> application/vnd.geoserver.geocss+css" -d @test_css.css
> http://localhost:8080/geoserver/rest/styles/test_css
>
> The upload works at least up to a certain point, but then fails with the
> following stack trace:
>
> org.geoserver.rest.RestletException:
> java.lang.UnsupportedOperationException
> at
> org.geoserver.rest.ReflectiveResource.handleException(ReflectiveResource.java:326)
> at
> org.geoserver.rest.ReflectiveResource.handlePut(ReflectiveResource.java:197)
> at org.restlet.Finder.handle(Finder.java:298)
> at
> org.geoserver.rest.BeanDelegatingRestlet.handle(BeanDelegatingRestlet.java:38)
> at org.restlet.Filter.doHandle(Filter.java:105)
> at org.restlet.Filter.handle(Filter.java:134)
> at org.restlet.Router.handle(Router.java:444)
> at org.geoserver.rest.RESTDispatcher$1.handle(RESTDispatcher.java:205)
> at
> com.noelios.restlet.ext.servlet.ServletConverter.service(ServletConverter.java:129)
> at
> org.geoserver.rest.RESTDispatcher.handleRequestInternal(RESTDispatcher.java:87)
> at
> org.springframework.web.servlet.mvc.AbstractController.handleRequest(AbstractController.java:153)
> at
> org.springframework.web.servlet.mvc.SimpleControllerHandlerAdapter.handle(SimpleControllerHandlerAdapter.java:48)
> at
> org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:923)
> at
> org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:852)
> at
> org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:882)
> at
> org.springframework.web.servlet.FrameworkServlet.doPut(FrameworkServlet.java:800)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:730)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
> at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:487)
> at
> org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1093)
> at
> org.geoserver.filters.ThreadLocalsCleanupFilter.doFilter(ThreadLocalsCleanupFilter.java:28)
> at
> org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1084)
> at
> org.geoserver.filters.SpringDelegatingFilter$Chain.doFilter(SpringDelegatingFilter.java:75)
> at
> org.geoserver.wms.animate.AnimatorFilter.doFilter(AnimatorFilter.java:71)
> at
> org.geoserver.filters.SpringDelegatingFilter$Chain.doFilter(SpringDelegatingFilter.java:71)
> at
> org.geoserver.filters.SpringDelegatingFilter.doFilter(SpringDelegatingFilter.java:46)
> at
> org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1084)
> at
> org.geoserver.platform.AdvancedDispatchFilter.doFilter(AdvancedDispatchFilter.java:50)
> at
> org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1084)
> at
> org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:311)
> at
> org.geoserver.security.filter.GeoServerCompositeFilter$NestedFilterChain.doFilter(GeoServerCompositeFilter.java:69)
> at
> org.springframework.security.web.access.intercept.FilterSecurityInterceptor.invoke(FilterSecurityInterceptor.java:116)
> at
> org.springframework.security.web.access.intercept.FilterSecurityInterceptor.doFilter(FilterSecurityInterceptor.java:83)
> at
> org.geoserver.security.filter.GeoServerCompositeFilter$NestedFilterChain.doFilter(GeoServerComposi

Re: [Geoserver-devel] Pull request (#841) / GeoServerFeatureSource constructor

[Andrea Aime]

On Thu, Dec 11, 2014 at 6:59 PM, Jody Garnett 
wrote:

> I don't want to hold up the pull request on this one, should be a 5 mins
> conversation.
>

Sorry, I'm busy enough that I don't know what day it is anymore these days


> Andrea are these constructor arguments holding up?
>

You mean you want to introduce a parameter object to avoid growing the
constructor?
Sure, pretty standard refactoring I'd say.

I have no idea what these new metadata things are though

Cheers
Andrea

-- 
==
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 6th
==

Ing. Andrea Aime
@geowolf
Technical Lead

GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054  Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39  339 8844549

http://www.geo-solutions.it
http://twitter.com/geosolutions_it

*AVVERTENZE AI SENSI DEL D.Lgs. 196/2003*

Le informazioni contenute in questo messaggio di posta elettronica e/o
nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il
loro utilizzo è consentito esclusivamente al destinatario del messaggio,
per le finalità indicate nel messaggio stesso. Qualora riceviate questo
messaggio senza esserne il destinatario, Vi preghiamo cortesemente di
darcene notizia via e-mail e di procedere alla distruzione del messaggio
stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso,
divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od
utilizzarlo per finalità diverse, costituisce comportamento contrario ai
principi dettati dal D.Lgs. 196/2003.



The information in this message and/or attachments, is intended solely for
the attention and use of the named addressee(s) and may be confidential or
proprietary in nature or covered by the provisions of privacy act
(Legislative Decree June, 30 2003, no.196 - Italy's New Data Protection
Code).Any use not in accord with its purpose, any disclosure, reproduction,
copying, distribution, or either dissemination, either whole or partial, is
strictly forbidden except previous formal approval of the named
addressee(s). If you are not the intended recipient, please contact
immediately the sender by telephone, fax or e-mail and delete the
information in this message that has been received in error. The sender
does not give any warranty or accept liability as the content, accuracy or
completeness of sent messages and accepts no responsibility  for changes
made after they were sent or for other risks which arise as a result of
e-mail transmission, viruses, etc.

---
--
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration & more
Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=164703151&iu=/4140/ostg.clktrk___
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

[Geoserver-devel] Uploading CSS styles via REST

[Andrea Aime]

Hi,
one of the new features in the 2.6.0 release is the ability to handle styles
in more than one language.

I've seen it work with CSS on the web UI, but I've just tried with REST and
I cannot seem to make it work, from what I can see it looks lilke a bug.

Here is what I've done. First, create the style xml, telling GeoServer I'm
going
to upload a css:

> curl -v -u admin:geoserver -XPOST -H "Content-type: text/xml" -d
"test_csstest_css.csscss"
 http://localhost:8080/geoserver/rest/styles
* Hostname was NOT found in DNS cache
*   Trying 127.0.0.1...
* Connected to localhost (127.0.0.1) port 8080 (#0)
* Server auth using Basic with user 'admin'
> POST /geoserver/rest/styles HTTP/1.1
> Authorization: Basic YWRtaW46Z2Vvc2VydmVy
> User-Agent: curl/7.35.0
> Host: localhost:8080
> Accept: */*
> Content-type: text/xml
> Content-Length: 89
>
* upload completely sent off: 89 out of 89 bytes
< HTTP/1.1 *201 Created*
< Date: Thu, 11 Dec 2014 18:07:58 GMT
< Location: http://localhost:8080/geoserver/rest/styles/test_css
* Server Noelios-Restlet-Engine/1.0..8 is not blacklisted
< Server: Noelios-Restlet-Engine/1.0..8
< Transfer-Encoding: chunked

And then I'm going to upload the css file itself:

> curl -v -u admin:geoserver -XPUT -H "Content-type:
application/vnd.geoserver.geocss+css" -d @test_css.css
http://localhost:8080/geoserver/rest/styles/test_css

The upload works at least up to a certain point, but then fails with the
following stack trace:

org.geoserver.rest.RestletException: java.lang.UnsupportedOperationException
at
org.geoserver.rest.ReflectiveResource.handleException(ReflectiveResource.java:326)
at
org.geoserver.rest.ReflectiveResource.handlePut(ReflectiveResource.java:197)
at org.restlet.Finder.handle(Finder.java:298)
at
org.geoserver.rest.BeanDelegatingRestlet.handle(BeanDelegatingRestlet.java:38)
at org.restlet.Filter.doHandle(Filter.java:105)
at org.restlet.Filter.handle(Filter.java:134)
at org.restlet.Router.handle(Router.java:444)
at org.geoserver.rest.RESTDispatcher$1.handle(RESTDispatcher.java:205)
at
com.noelios.restlet.ext.servlet.ServletConverter.service(ServletConverter.java:129)
at
org.geoserver.rest.RESTDispatcher.handleRequestInternal(RESTDispatcher.java:87)
at
org.springframework.web.servlet.mvc.AbstractController.handleRequest(AbstractController.java:153)
at
org.springframework.web.servlet.mvc.SimpleControllerHandlerAdapter.handle(SimpleControllerHandlerAdapter.java:48)
at
org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:923)
at
org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:852)
at
org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:882)
at
org.springframework.web.servlet.FrameworkServlet.doPut(FrameworkServlet.java:800)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:730)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:487)
at
org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1093)
at
org.geoserver.filters.ThreadLocalsCleanupFilter.doFilter(ThreadLocalsCleanupFilter.java:28)
at
org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1084)
at
org.geoserver.filters.SpringDelegatingFilter$Chain.doFilter(SpringDelegatingFilter.java:75)
at org.geoserver.wms.animate.AnimatorFilter.doFilter(AnimatorFilter.java:71)
at
org.geoserver.filters.SpringDelegatingFilter$Chain.doFilter(SpringDelegatingFilter.java:71)
at
org.geoserver.filters.SpringDelegatingFilter.doFilter(SpringDelegatingFilter.java:46)
at
org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1084)
at
org.geoserver.platform.AdvancedDispatchFilter.doFilter(AdvancedDispatchFilter.java:50)
at
org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1084)
at
org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:311)
at
org.geoserver.security.filter.GeoServerCompositeFilter$NestedFilterChain.doFilter(GeoServerCompositeFilter.java:69)
at
org.springframework.security.web.access.intercept.FilterSecurityInterceptor.invoke(FilterSecurityInterceptor.java:116)
at
org.springframework.security.web.access.intercept.FilterSecurityInterceptor.doFilter(FilterSecurityInterceptor.java:83)
at
org.geoserver.security.filter.GeoServerCompositeFilter$NestedFilterChain.doFilter(GeoServerCompositeFilter.java:73)
at
org.geoserver.security.filter.GeoServerCompositeFilter.doFilter(GeoServerCompositeFilter.java:92)
at
org.springframework.security.web.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:323)
at
org.geoserver.security.filter.GeoServerCompositeFilter$NestedFilterChain.doFilter(GeoServerCompositeFilter.java:69)
at
org.springframework.security.web.access.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:113)
at
org.geos

Re: [Geoserver-devel] Pull request #841 / CQL concatenation

[Jody Garnett]

Thanks for taking discussion to the email list.

For your question: "should I remove the overridden + operator and go with
the standard concatenation function?"

We have a similar requirement in a few places in our code (handling of
labels in SLD, and handling of embedded CQL expressions in external
graphics). In these cases rather than use "+" we use whitespace - resulting
in a list of expressions that can be evaluated).

I think ECQL has a method that takes a lis of expressions separated by ";"
as well.

Would you be with using white space to produce your Concatenate expression?
This would make the codebase a bit more consistent (and one less
opportunity for confusion).
--
Jody

--
Jody Garnett

On 11 December 2014 at 00:44, Sampo Savolainen <
sampo.savolai...@spatineo.com> wrote:

> Hi,
>
> Jody and I have been discussing my pull request on cascaded stored
> requests and we'd like to open another point to wider debate.
>
> This is regarding Jody's notes on this test case:
> https://github.com/geoserver/geoserver/pull/841#discussion-diff-21495146
>
> Some background: my implementation of cascaded stored query passes stored
> query parameters to the backend via two mechanisms:
>
>1. The original request to the feature type backed by a cascaded
>stored query may include view parameters, just like with Virtual Table
>backed feature types.
>2. Feature type configuration may specify mappings to the parameters.
>
> There are a two types of mappings possible in the implementation. You can
> either specify a default value (two flavours: one you can override with a
> view parameter and another you can't), or the parameter value can be
> evaluated from an expression. The discussion here is regarding these
> expressions.
>
> The expressions are written in CQL and are executed within a context where
> the query filter, basic feature type information and the query bounds are
> accessible. A stored query that my work specifically targets has a bounding
> box parameter that needs to be derived from this context. I used
> expressions instead of a hard-coded bounding box type parameter mapping to
> make the implementation more general.
>
> When I wrote the CQL expression parts, I was only aware of a single
> concatenation function in CQL, strConCat. This function only takes two
> parameters and both must be strings. So as you can see in the test
> referenced by the diff, the expression to build a bounding box becomes
> quite a mess. To avoid this, I overrode the + operator for these
> expressions so it does string concatenation if either the left hand side or
> right hand side values were strings.
>
>
> https://github.com/geotools/geotools/blob/master/modules/unsupported/wfs-ng/src/main/java/org/geotools/data/wfs/internal/v2_0/storedquery/ParameterCQLExpressionFilterFactoryImpl.java#L104
>
> However, Jody led me on to the fact that there is a multi-parameter
> concatenation function in CQL.
>
> Now the question is: should I remove the overridden + operator and go with
> the standard concatenation function?
>
>
> Also: I was unable to find reference documentation on this concatenation
> function. Maybe someone knows where it is so I can check it? Especially
> whether it allows combining numbers and strings is of interest.
>
>
>   Sampo
>
>
>
> --
> Sampo Savolainen
> R&D Director, Spatineo Oy
> sampo.savolai...@spatineo.com
> +358-407555649
> Linnankoskenkatu 16 A 17, 00250 Helsinki, Finland
> www.spatineo.com, twitter.com/#!/spatineo
> www.linkedin.com/company/spatineo-inc
>
> This message may contain privileged and/or confidential information. If you
> have received this e-mail in error or are not the intended recipient, you
> may not use, copy, disseminate, or distribute it; do not open any
> attachments, delete it immediately from your system and notify the sender
> promptly by e-mail that you have done so.
>
>
> --
> Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
> from Actuate! Instantly Supercharge Your Business Reports and Dashboards
> with Interactivity, Sharing, Native Excel Exports, App Integration & more
> Get technology previously reserved for billion-dollar corporations, FREE
>
> http://pubads.g.doubleclick.net/gampad/clk?id=164703151&iu=/4140/ostg.clktrk
> ___
> Geoserver-devel mailing list
> Geoserver-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>
>
--
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration & more
Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=164703151&iu=/4140/ostg.clktrk___

Re: [Geoserver-devel] Pull request (#841) / GeoServerFeatureSource constructor

[Jody Garnett]

I don't want to hold up the pull request on this one, should be a 5 mins
conversation.
Andrea are these constructor arguments holding up?

Quick fix:

public GeoServerFeatureSource(source, schema, definitionQuery, declaredCRS,
srsHandling, linearizationTolerance){
this( source, schema, definitionQuery, declaredCRS, srsHandling,
linearizationTolerance, null );
}

Longer term:

// for backwards compatibility (deprecate or remove to force compile
failure)
GeoServerFeatureSource(source, schema, definitionQuery, declaredCRS,
srsHandling, linearizationTolerance){
   this( source, new Settings( schema, definitionQuery, declaredCRS,
srsHandling, linearizationTolerance) );
}
GeoServerFeatureSource(source, schema, Settings settings ){
  ...
}

Where "GeoServerFeatureSource.Settings" is a parameter object we can add
fields to over time:

static class Settings {
  SimpleFeatureType schema = null;
  Filter definitionQuery = null;
  CoordinateReferenceSystem declaredCRS = null;
  int srsHandling = null;
  Double linearizationTolerance  = null;
  Map metadata = null;
}




--
Jody Garnett

On 11 December 2014 at 00:16, Sampo Savolainen <
sampo.savolai...@spatineo.com> wrote:

> Hi,
>
> Jody and I have been discussing an API change in GeoServerFeatureSource
> that is in my pull request for cascaded stored query support.
>
> https://github.com/geoserver/geoserver/pull/841#discussion-diff-21494311
>
> The reasoning behind the change is to pass all metadata supplied for a
> feature type to the FeatureSource. This allows GeoServer to pass the
> configuration required for cascaded stored queries to the actual data
> store. The pattern is generic so it should be usable in other cases as well.
>
> Jody was looking for more feedback, especially from Andrea, regarding this.
>
>
>  Thanks,
>   Sampo
>
>
> --
> Sampo Savolainen
> R&D Director, Spatineo Oy
> sampo.savolai...@spatineo.com
> +358-407555649
> Linnankoskenkatu 16 A 17, 00250 Helsinki, Finland
> www.spatineo.com, twitter.com/#!/spatineo
> www.linkedin.com/company/spatineo-inc
>
> This message may contain privileged and/or confidential information. If you
> have received this e-mail in error or are not the intended recipient, you
> may not use, copy, disseminate, or distribute it; do not open any
> attachments, delete it immediately from your system and notify the sender
> promptly by e-mail that you have done so.
>
>
> --
> Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
> from Actuate! Instantly Supercharge Your Business Reports and Dashboards
> with Interactivity, Sharing, Native Excel Exports, App Integration & more
> Get technology previously reserved for billion-dollar corporations, FREE
>
> http://pubads.g.doubleclick.net/gampad/clk?id=164703151&iu=/4140/ostg.clktrk
> ___
> Geoserver-devel mailing list
> Geoserver-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>
>
--
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration & more
Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=164703151&iu=/4140/ostg.clktrk___
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

Re: [Geoserver-devel] Feedback on GeoPackage plugin

[Justin Deoliveira]

Thanks for the great feedback Evan. Raster support in the
GeoTools/GeoServer geopackage driver was done with much less certainty than
the vector stuff. I am not even 100% sure it is compliant with the latest
spec as it was implemented before the spec got to final 1.0. Going to wade
through this list and start filing bug reports in our JIRA.

On Wed, Dec 10, 2014 at 2:41 PM, Even Rouault 
wrote:

> Hi,
>
> I've recently added read/write support in GDAL for GeoPackage rasters and
> did
> try it a bit with the GeoPackage plugin of GeoServer.
>
> I found several issues in the GeoServer plugin:
>
> - it refuses to add some geopackages as raster datasources. For example
> http://download.osgeo.org/gdal/data/geopackage/utm_jpeg_one_band.gpkg or
>
> http://download.osgeo.org/gdal/data/geopackage/small_world_googlemapscompatible.gpkg
> .
> An exception is generated when trying to publish the datasource ( see (1)
> at
> bottom of this email). After a bit of trying, it seems that the issue is
> encountered when the SRS of the GeoPackage is not EPSG:4326 as I could
> import
> all my GeoPackage datasets with SRS=EPSG:4326 and none in other SRS.
>
> - when previewing the
> http://download.osgeo.org/gdal/data/geopackage/small_world_png.gpkg in the
> OpenLayers previewer, I get strange artifacts on the tile of the eastern
> hemisphere that go beyon longitude +180 (the actual data stops at longitude
> +180 but the extent of the tile goes beyond with padding).
>
> - a bit similar issue with
>
> http://download.osgeo.org/gdal/data/geopackage/small_world_googlecrs84quad.gpkg
> ,
> still using OpenLayers previewer, only northern hemisphere can be
> displayed.
> This is likely due to the WMTS googlecrs84quad tiling scheme used where the
> extent of latitudes at zoom level 0 is [-180,180].
>
> - when downloading that layer with format=geopackage in WMS, with
>
> http://localhost:8080/geoserver/test/wms?service=WMS&version=1.1.0&request=GetMap&layers=test:small_world_png&styles=&bbox=-180.0,-90.0,180.0,90.0&width=660&height=330&srs=EPSG:4326&format=geopackage
> I found the following issues:
>* typo in the gpkg_metadata table. The column "md_standard_uri"
> mandated by
> the specification (see http://www.geopackage.org/spec/#_metadata_table) is
> labelled "metadata_standard_URI" in the geopackage generated by GeoServer.
> In
> the changelog of the specification, one can see :
> "2013-11-21 R10 Paul Daisey Annex C, G Change metadata_standard_uri column
> name to md_standard_uri"
>* more annoying: it seems that GeoServer uses the bottom left corner of
> the
> tiling scheme as the origin for tile_row numbering, instead of the top left
> corner.
>* not really an issue, but generated that output file is extremely slow,
> like 30 seconds, and lot of noise done by harddisk ;-)
>
> * actually when trying to display
>
> http://download.osgeo.org/gdal/data/geopackage/small_world_googlecrs84quad_bigger.gpkg
> with OpenLayers previewer, I get also the issue with the inverted tile_row
> numbering. So the issue seems to exist on both reading and writing side.
>
> Best regards,
>
> Even
>
>
> (1) :
> java.lang.RuntimeException: Error occurred while building the resources for
> the configuration page at
>
> org.geoserver.web.data.layer.NewLayerPage.buildLayerInfo(NewLayerPage.java:330)
> at
> org.geoserver.web.data.layer.NewLayerPage$7.onClick(NewLayerPage.java:261)
> at
> org.geoserver.web.wicket.SimpleAjaxLink$1.onClick(SimpleAjaxLink.java:46)
> at org.apache.wicket.ajax.markup.html.AjaxLink$1.onEvent(AjaxLink.java:68)
> at
>
> org.apache.wicket.ajax.AjaxEventBehavior.respond(AjaxEventBehavior.java:177)
> at
>
> org.apache.wicket.ajax.AbstractDefaultAjaxBehavior.onRequest(AbstractDefaultAjaxBehavior.java:300)
> at
>
> org.apache.wicket.request.target.component.listener.BehaviorRequestTarget.processEvents(BehaviorRequestTarget.java:119)
> at
>
> org.apache.wicket.request.AbstractRequestCycleProcessor.processEvents(AbstractRequestCycleProcessor.java:92)
> at
>
> org.apache.wicket.RequestCycle.processEventsAndRespond(RequestCycle.java:1250)
> at org.apache.wicket.RequestCycle.step(RequestCycle.java:1329) at
> org.apache.wicket.RequestCycle.steps(RequestCycle.java:1436) at
> org.apache.wicket.RequestCycle.request(RequestCycle.java:545) at
> org.apache.wicket.protocol.http.WicketFilter.doGet(WicketFilter.java:484)
> at
> org.apache.wicket.protocol.http.WicketServlet.doGet(WicketServlet.java:138)
> at
> javax.servlet.http.HttpServlet.service(HttpServlet.java:707) at
> javax.servlet.http.HttpServlet.service(HttpServlet.java:820) at
>
> org.springframework.web.servlet.mvc.ServletWrappingController.handleRequestInternal(ServletWrappingController.java:159)
> at
>
> org.springframework.web.servlet.mvc.AbstractController.handleRequest(AbstractController.java:153)
> at
>
> org.springframework.web.servlet.mvc.SimpleControllerHandlerAdapter.handle(SimpleControllerHandlerAdapter.java:48)
> at
>
> org.springframework.web.servlet.DispatcherServlet.do

[Geoserver-devel] [jira] (GEOS-6798) Saving layer after an SQL view edit causes WicketRuntimeException

[Lorenzo Pini (JIRA)]

Title: Message Title










 

 Lorenzo Pini created an issue











 






 GeoServer /  GEOS-6798



  Saving layer after an SQL view edit causes WicketRuntimeException 










Issue Type:

  Bug




Affects Versions:


 2.4.8




Assignee:

 Andrea Aime




Components:


 Wicket UI




Created:


 11/Dec/14 10:07 AM




Environment:


 CentOS 6  GeoServer 2.4.8  JAVA: Oracle Corporation: 1.7.0_65 (OpenJDK 64-Bit Server VM)




Priority:

  Minor




Reporter:

 Lorenzo Pini










I had an SQL view without an identifier, so I edited the "SQL statement" to include another field and setted it as "Identifier". The "Edit SQL view" page save when fine. The "Edit Layer" page save returned this stack trace.
Reopening the layer showed no problem, the data was updated correcly.
org.apache.wicket.WicketRuntimeException: Method onFormSubmitted of interface org.apache.wicket.markup.html.form.IFormSubmitListener targeted at component [MarkupContainer [Component id = resource]] threw an exception at org.apache.wicket.RequestListenerInterface.invoke(RequestListenerInterface.java:193) at org.apache.wicket.request.target.component.listener.ListenerInterfaceRequestTarge

Re: [Geoserver-devel] [GEOS-6688] Addition to better support more interpolation types.

[Alex van den Hoogen | Geodan]

Hi,

Unfortunately, I'm still having issues with this issue, even after my own
fix. I'm suspecting it just has to do with the spelling of neighbor, which
is inconsistent at places. So locally I have changed all the definitions in
the relevant Java code to neighbor and it seems to work a bit beter.

Some of the improvements I saw:
 - Web interface shows nearest neighbor immediatly, instead of after a save
like it was before
 - More consistent language approach (neighbor everywhere)
 - Less error prone in the future.

However, I'm not currently foreseeing in what way this could break existing
configurations of GeoServer. I'm not sure how GeoServer approaches
interpolation methods when suddenly switching to nearest neighbor instead
of neighbour.

I am wondering what you guys think of this? And I will supply a pull
request with a better test for interpolation methods in the forthcoming
days.

Kind regards,
Alex van den Hoogen

-
*Geodan*
Buitenhaven 27-A
5211 TP 's-Hertogenbosch (NL)

E alex.van.den.hoo...@geodan.nl

www.geodan.nl | disclaimer 
-

2014-12-08 12:03 GMT+01:00 Alex van den Hoogen | Geodan <
alex.van.den.hoo...@geodan.nl>:

> Hi,
>
> During some internal tests it seems that the committed code for GEOS-6688
> wasn't working correctly all of the time. There are some issues regarding
> the nearest neighbor/neighbour interpolation method.
>
> Appearently some code is still using the word neighbor, while some other
> code is using the word neighbour. Differences between US or UK style
> spelling. When evaluating the code I came to the conclusion that when
> enforcing either way of spelling you potentially break a lot of existing,
> and good working, configurations.
>
> That's why I submitted a pull request (
> https://github.com/geoserver/geoserver/pull/846) that checks for the
> interpolation type of a WCS GetCoverage with a startsWith instead of an
> equalsIgnoreCase(), This should be less error prone and cause either UK or
> US style nearest neighbor interpolation to work.
>
> But I would still like the opinion of the community about this issue.
>
> Thanks!
>
> Kind regards,
> Alex van den Hoogen
>
> -
> *Geodan*
> Buitenhaven 27-A
> 5211 TP 's-Hertogenbosch (NL)
>
> E alex.van.den.hoo...@geodan.nl
>
> www.geodan.nl | disclaimer 
> -
>
--
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration & more
Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=164703151&iu=/4140/ostg.clktrk___
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

Re: [Geoserver-devel] Feedback on GeoPackage plugin

[Stadin, Benjamin]

Hi Jukka,

I didn’t do any concrete timings this time, but I use these settings for a
mobile project since years where I once did concrete timings (differential
database updates on Android and iOS). It of course varies with the
particular database, indices etc.

See also some performance measurements of different journal and
synchronization modes here:
http://stackoverflow.com/questions/1711631/improve-insert-per-second-perfor
mance-of-sqlite

Cheers
Ben

Am 11.12.14 07:04 schrieb "Rahkonen Jukka (Tike)" unter
:

>Hi Benjamin,
>
>Your estimate about 100x - 1000x speedup makes me suspicious but I will
>be happily surprised if it happens to be true.
>
>I would like to get some sample data and exact timings from your test for
>repeating them. I mean from what you wrote " I¹ve played with Geopackage
>in GDAL and creating a geopackage db via ogr2ogr was slow as well." Did
>you compare the speed with creating a SpatiaLite db with ogr2ogr instead?
>
>-Jukka Rahkonen-
>
>
>
>
>Stadin, Benjamin wrote:
>
>Hi,
>
>I didn¹t try GeoPackage plugin in GeoServer, I¹ve played with Geopackage
>in GDAL and creating a geopackage db via ogr2ogr was slow as well.
>
>In my opinion it would be save for both GDAL as well as the GeoPackage
>plugin to change the SQLite journaling mode to WAL and turn file
>synchronization off (at least when creating databases). C Example:
>
>sqlite3_exec(db, "PRAGMA synchronous = OFF", NULL, NULL, NULL);
>sqlite3_exec(db, "PRAGMA journal_mode = WAL", NULL, NULL, NULL);
>
>This must be done right after opening the database. The the insert /
>delete performance difference is enorm (several orders of magnitude
>compared to non-transactional inserts and also twice or three times faster
>for transactions).
>
>A speedup between 100x - 1000x is not unlikely. This comes of course at
>the slightly increased cost of db corruption (see also [1,2]). But even
>then, it¹s debatable whether for the db utilization of both GeoServer and
>GDAL this can be configuration enabled globally for all operations: rare
>updates, still journaling enabled though with backup point from last disk
>write time compared to constant disk sync journaling for each op.
>
>Cheers
>Ben
>
>[1] https://www.sqlite.org/wal.html
>[2] http://www.sqlite.org/pragma.html#pragma_journal_mode
>
>
>
>
>Am 10.12.14 23:41 schrieb "Even Rouault" unter
>:
>
>>   * not really an issue, but generated that output file is extremely
>>slow,
>>like 30 seconds, and lot of noise done by harddisk ;-)
>
>
>--
>
>Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
>from Actuate! Instantly Supercharge Your Business Reports and Dashboards
>with Interactivity, Sharing, Native Excel Exports, App Integration & more
>Get technology previously reserved for billion-dollar corporations, FREE
>http://pubads.g.doubleclick.net/gampad/clk?id=164703151&iu=/4140/ostg.clkt
>rk
>___
>Geoserver-devel mailing list
>Geoserver-devel@lists.sourceforge.net
>https://lists.sourceforge.net/lists/listinfo/geoserver-devel

--
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration & more
Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=164703151&iu=/4140/ostg.clktrk
___
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

Re: [Geoserver-devel] Feedback on GeoPackage plugin

[Stadin, Benjamin]

Those must be very ancient (> 5 years or so). But if so, it¹s post
performance speedup comes indeed from synchronous = off.


Am 11.12.14 09:40 schrieb "Even Rouault" unter
:

>> sqlite3_exec(db, "PRAGMA journal_mode = WAL", NULL, NULL, NULL);
>
>AFAIR using WAL uses a slightly different storage that makes it
>incompatible
>with ancient sqlite3 versions.
>In my tests synchronous = off gives enough performance boost.


--
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration & more
Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=164703151&iu=/4140/ostg.clktrk
___
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

Re: [Geoserver-devel] Feedback on GeoPackage plugin

[Andrea Aime]

On Wed, Dec 10, 2014 at 11:41 PM, Even Rouault 
wrote:

> Hi,
>
> I've recently added read/write support in GDAL for GeoPackage rasters and
> did
> try it a bit with the GeoPackage plugin of GeoServer.
>

Thanks for the feedback.
I do hope that the people that worked on it will follow up, but mind, the
module
is in unsupported land, so there is no guarantee it will happen, the modules
in the "community" section are either new or without an official maintaner,
sometimes a bit
of both at the same time.


> - when previewing the
> http://download.osgeo.org/gdal/data/geopackage/small_world_png.gpkg in the
> OpenLayers previewer, I get strange artifacts on the tile of the eastern
> hemisphere that go beyon longitude +180 (the actual data stops at longitude
> +180 but the extent of the tile goes beyond with padding).
>

In version 1.6.0 we added map wrapping to raster data as well, to follow
suit with
the already available vector one, so it's normal that the data gets
replicated on
the other side of the dateline.

However, by your description it seems that it's not working as it should in
your case.
When I use one of natural earth tiffs and zoom out, I get the following,
which is the
expected behavior:

Cheers
Andrea
​

-- 
==
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 6th
==

Ing. Andrea Aime
@geowolf
Technical Lead

GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054  Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39  339 8844549

http://www.geo-solutions.it
http://twitter.com/geosolutions_it

*AVVERTENZE AI SENSI DEL D.Lgs. 196/2003*

Le informazioni contenute in questo messaggio di posta elettronica e/o
nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il
loro utilizzo è consentito esclusivamente al destinatario del messaggio,
per le finalità indicate nel messaggio stesso. Qualora riceviate questo
messaggio senza esserne il destinatario, Vi preghiamo cortesemente di
darcene notizia via e-mail e di procedere alla distruzione del messaggio
stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso,
divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od
utilizzarlo per finalità diverse, costituisce comportamento contrario ai
principi dettati dal D.Lgs. 196/2003.



The information in this message and/or attachments, is intended solely for
the attention and use of the named addressee(s) and may be confidential or
proprietary in nature or covered by the provisions of privacy act
(Legislative Decree June, 30 2003, no.196 - Italy's New Data Protection
Code).Any use not in accord with its purpose, any disclosure, reproduction,
copying, distribution, or either dissemination, either whole or partial, is
strictly forbidden except previous formal approval of the named
addressee(s). If you are not the intended recipient, please contact
immediately the sender by telephone, fax or e-mail and delete the
information in this message that has been received in error. The sender
does not give any warranty or accept liability as the content, accuracy or
completeness of sent messages and accepts no responsibility  for changes
made after they were sent or for other risks which arise as a result of
e-mail transmission, viruses, etc.

---
--
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration & more
Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=164703151&iu=/4140/ostg.clktrk___
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

[Geoserver-devel] Pull request #841 / CQL concatenation

[Sampo Savolainen]

Hi,

Jody and I have been discussing my pull request on cascaded stored requests
and we'd like to open another point to wider debate.

This is regarding Jody's notes on this test case:
https://github.com/geoserver/geoserver/pull/841#discussion-diff-21495146

Some background: my implementation of cascaded stored query passes stored
query parameters to the backend via two mechanisms:

   1. The original request to the feature type backed by a cascaded stored
   query may include view parameters, just like with Virtual Table backed
   feature types.
   2. Feature type configuration may specify mappings to the parameters.

There are a two types of mappings possible in the implementation. You can
either specify a default value (two flavours: one you can override with a
view parameter and another you can't), or the parameter value can be
evaluated from an expression. The discussion here is regarding these
expressions.

The expressions are written in CQL and are executed within a context where
the query filter, basic feature type information and the query bounds are
accessible. A stored query that my work specifically targets has a bounding
box parameter that needs to be derived from this context. I used
expressions instead of a hard-coded bounding box type parameter mapping to
make the implementation more general.

When I wrote the CQL expression parts, I was only aware of a single
concatenation function in CQL, strConCat. This function only takes two
parameters and both must be strings. So as you can see in the test
referenced by the diff, the expression to build a bounding box becomes
quite a mess. To avoid this, I overrode the + operator for these
expressions so it does string concatenation if either the left hand side or
right hand side values were strings.

https://github.com/geotools/geotools/blob/master/modules/unsupported/wfs-ng/src/main/java/org/geotools/data/wfs/internal/v2_0/storedquery/ParameterCQLExpressionFilterFactoryImpl.java#L104

However, Jody led me on to the fact that there is a multi-parameter
concatenation function in CQL.

Now the question is: should I remove the overridden + operator and go with
the standard concatenation function?


Also: I was unable to find reference documentation on this concatenation
function. Maybe someone knows where it is so I can check it? Especially
whether it allows combining numbers and strings is of interest.


  Sampo



-- 
Sampo Savolainen
R&D Director, Spatineo Oy
sampo.savolai...@spatineo.com
+358-407555649
Linnankoskenkatu 16 A 17, 00250 Helsinki, Finland
www.spatineo.com, twitter.com/#!/spatineo
www.linkedin.com/company/spatineo-inc

This message may contain privileged and/or confidential information. If you
have received this e-mail in error or are not the intended recipient, you
may not use, copy, disseminate, or distribute it; do not open any
attachments, delete it immediately from your system and notify the sender
promptly by e-mail that you have done so.
--
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration & more
Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=164703151&iu=/4140/ostg.clktrk___
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

Re: [Geoserver-devel] Feedback on GeoPackage plugin

[Even Rouault]

Le jeudi 11 décembre 2014 00:40:56, Stadin, Benjamin a écrit :
> Hi,
> 
> I didn¹t try GeoPackage plugin in GeoServer, I¹ve played with Geopackage
> in GDAL and creating a geopackage db via ogr2ogr was slow as well.
> 
> In my opinion it would be save for both GDAL as well as the GeoPackage
> plugin to change the SQLite journaling mode to WAL and turn file
> synchronization off (at least when creating databases). C Example:
> 
> sqlite3_exec(db, "PRAGMA synchronous = OFF", NULL, NULL, NULL);

This can actually be done by adding "--config OGR_SQLITE_SYNCHRONOUS OFF" to 
the gdal_translate/ogr2ogr command line (see "Performance hints" section of 
http://gdal.org/drv_sqlite.html), and is what I practice regularly, and yes it 
gives a huge performance boost.

> sqlite3_exec(db, "PRAGMA journal_mode = WAL", NULL, NULL, NULL);

AFAIR using WAL uses a slightly different storage that makes it incompatible 
with ancient sqlite3 versions.  
In my tests synchronous = off gives enough performance boost.

> 
> This must be done right after opening the database. The the insert /
> delete performance difference is enorm (several orders of magnitude
> compared to non-transactional inserts and also twice or three times faster
> for transactions).
> 
> A speedup between 100x - 1000x is not unlikely. This comes of course at
> the slightly increased cost of db corruption (see also [1,2]). But even
> then, it¹s debatable whether for the db utilization of both GeoServer and
> GDAL this can be configuration enabled globally for all operations: rare
> updates, still journaling enabled though with backup point from last disk
> write time compared to constant disk sync journaling for each op.

Yes perhaps I should consider turning synchronous = off by default.

> 
> Cheers
> Ben
> 
> [1] https://www.sqlite.org/wal.html
> [2] http://www.sqlite.org/pragma.html#pragma_journal_mode
> 
> 
> 
> 
> Am 10.12.14 23:41 schrieb "Even Rouault" unter
> 
> :
> >   * not really an issue, but generated that output file is extremely
> >
> >slow,
> >like 30 seconds, and lot of noise done by harddisk ;-)

-- 
Spatialys - Geospatial professional services
http://www.spatialys.com

--
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration & more
Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=164703151&iu=/4140/ostg.clktrk
___
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

[Geoserver-devel] Jenkins build is back to normal : geoserver-master-nightly #472

[monitor]

See 


--
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration & more
Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=164703151&iu=/4140/ostg.clktrk
___
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

[Geoserver-devel] Pull request (#841) / GeoServerFeatureSource constructor

[Sampo Savolainen]

Hi,

Jody and I have been discussing an API change in GeoServerFeatureSource
that is in my pull request for cascaded stored query support.

https://github.com/geoserver/geoserver/pull/841#discussion-diff-21494311

The reasoning behind the change is to pass all metadata supplied for a
feature type to the FeatureSource. This allows GeoServer to pass the
configuration required for cascaded stored queries to the actual data
store. The pattern is generic so it should be usable in other cases as well.

Jody was looking for more feedback, especially from Andrea, regarding this.


 Thanks,
  Sampo


-- 
Sampo Savolainen
R&D Director, Spatineo Oy
sampo.savolai...@spatineo.com
+358-407555649
Linnankoskenkatu 16 A 17, 00250 Helsinki, Finland
www.spatineo.com, twitter.com/#!/spatineo
www.linkedin.com/company/spatineo-inc

This message may contain privileged and/or confidential information. If you
have received this e-mail in error or are not the intended recipient, you
may not use, copy, disseminate, or distribute it; do not open any
attachments, delete it immediately from your system and notify the sender
promptly by e-mail that you have done so.
--
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration & more
Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=164703151&iu=/4140/ostg.clktrk___
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel