Re: [Geoserver-users] (no subject)

[Andrea Aime]

Hi Chris,
the GWC/JDBCConfig improvements just landed in nightly builds, if you want
to try them out look here:
http://ares.boundlessgeo.com/geoserver/master/
http://ares.boundlessgeo.com/geoserver/2.8.x/
http://ares.boundlessgeo.com/geoserver/2.7.x/

Let us know how that goes

Cheers
Andrea


On Thu, Oct 22, 2015 at 8:55 AM, Chris Brown  wrote:

> Hi Anrdea,
>
> Sure, I would be happy to give that a try, please let me know once it hits
> the nightlies. It might take me a few days to test, because to test that
> volume we need to clone our production server with all the data onto
> staging which is a big of an exercise.
>
> Cheers,
>
> Chris
>
> On 21 October 2015 at 02:22, Andrea Aime 
> wrote:
>
>> On Tue, Oct 20, 2015 at 6:10 PM, Chris Brown  wrote:
>>
>>> Hi,
>>>
>>> We've just installed JDBCConfig on a large GeoServer deployment with
>>> about 40,000 layers. The install web smoothly but we're seeing some very
>>> strange behaviour when we do any updates such as adding layers via the REST
>>> API.
>>>
>>> All such requests hang the server for around 25 minutes. Turning on the
>>> debugging log, it looks like some process is looping over every single
>>> layer in the catalog. The output in the log looks like this:
>>>
>>> If anyone has any ideas about what we may have done wrong or any ideas
>>> what might be causing this it would be hugely appreciated. The closest
>>> thing I could find to this issue was this:
>>> http://comments.gmane.org/gmane.comp.gis.geoserver.user/41076
>>>
>>
>> You're not doing anything wrong, it's just that the core of GeoServer
>> still has many bits of code that are written
>> with an in memory catalog in mind, JDBCConfig work included some
>> _examples_ spread out in the code
>> base that serve as examples of how things should be done to work against
>> a in dbms catalog,
>> but the migration is not complete, there are still bits of code here and
>> there that load everything
>> there is to perform some in memory check, that could be replaced with a
>> well written query
>> loading only the bits that are actually needed.
>>
>> One year ago we worked on fixing the biggest offenders in the UI and some
>> core modules,
>> leaving out the integrated GWC as the biggest outstanding offender.
>> Guess what, I'm working on a patch to address some of the issues right
>> now, which might or
>> might not address what you're seeing, it should be landing on the
>> development series
>> next week.
>>
>> I'm not saying this will remove all "linear scans" that are in the
>> codebase, but it should help in some cases.
>> Let me know if you're interested in testing that out, if so I'll ping you
>> when I commit it.
>>
>> Cheers
>> Andrea
>>
>> --
>> ==
>> GeoServer Professional Services from the experts! Visit
>> http://goo.gl/it488V for more information.
>> ==
>>
>> 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.
>>
>> 

[Geoserver-users] Possible bug rendering postgis data?

[Bernhard Kiselka]

Dear list!

I have some lines imported to postgres by osmosis and rendering the data with 
the default line style as wms in geoserver 2.7.1.1 fails for scales more zoomed 
out than 1:70K (though working zoomed more in), failing with the following 
message:

org.geotools.data.DataSourceException: An exception occurred while parsing WKB 
data
An exception occurred while parsing WKB data
Invalid number of points in LineString (found 1 - must be 0 or = 2)

WFS shows all data (just 3502 geometries) though.
I had a look at the PostgreSQL 9.4.5 database with postgis 2.1.7: ST_IsValid 
returns true for all linestrings; also is the number of points for all lines >= 
2 and the minimum length of all lines is 1.04m

That's the detail stacktrace:

2015-10-29 16:03:25,201 ERROR [ows] (http-0.0.0.0-8080-1) : 
org.geoserver.platform.ServiceException: Rendering process failed
at 
org.geoserver.wms.map.RenderedImageMapOutputFormat.produceMap(RenderedImageMapOutputFormat.java:541)
 [:2.7.1.1]
at 
org.geoserver.wms.map.RenderedImageMapOutputFormat.produceMap(RenderedImageMapOutputFormat.java:258)
 [:2.7.1.1]
at 
org.geoserver.wms.map.RenderedImageMapOutputFormat.produceMap(RenderedImageMapOutputFormat.java:130)
 [:2.7.1.1]
at org.geoserver.wms.GetMap.executeInternal(GetMap.java:504) [:2.7.1.1]
at org.geoserver.wms.GetMap.run(GetMap.java:248) [:2.7.1.1]
at org.geoserver.wms.GetMap.run(GetMap.java:119) [:2.7.1.1]
at 
org.geoserver.wms.DefaultWebMapService.getMap(DefaultWebMapService.java:369) 
[:2.7.1.1]
at sun.reflect.GeneratedMethodAccessor604.invoke(Unknown Source) 
[:1.7.0_80]
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
 [:1.7.0_80]
at java.lang.reflect.Method.invoke(Method.java:606) [:1.7.0_80]
at 
org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:319)
 [:3.1.4.RELEASE]
at 
org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:183)
 [:3.1.4.RELEASE]
at 
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150)
 [:3.1.4.RELEASE]
at 
org.geoserver.kml.WebMapServiceKmlInterceptor.invoke(WebMapServiceKmlInterceptor.java:34)
 [:2.7.1.1]
at 
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
 [:3.1.4.RELEASE]
at 
org.geoserver.gwc.wms.CacheSeedingWebMapService.invoke(CacheSeedingWebMapService.java:62)
 [:2.7.1.1]
at 
org.geoserver.gwc.wms.CacheSeedingWebMapService.invoke(CacheSeedingWebMapService.java:36)
 [:2.7.1.1]
at 
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
 [:3.1.4.RELEASE]
at 
org.geoserver.gwc.wms.CachingWebMapService.invoke(CachingWebMapService.java:74) 
[:2.7.1.1]
at 
org.geoserver.gwc.wms.CachingWebMapService.invoke(CachingWebMapService.java:55) 
[:2.7.1.1]
at 
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
 [:3.1.4.RELEASE]
at 
org.geoserver.ows.util.RequestObjectLogger.invoke(RequestObjectLogger.java:33) 
[:2.7.1.1]
at 
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172)
 [:3.1.4.RELEASE]
at 
org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:202)
 [:3.1.4.RELEASE]
at com.sun.proxy.$Proxy274.getMap(Unknown Source)
at sun.reflect.GeneratedMethodAccessor618.invoke(Unknown Source) 
[:1.7.0_80]
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
 [:1.7.0_80]
at java.lang.reflect.Method.invoke(Method.java:606) [:1.7.0_80]
at org.geoserver.ows.Dispatcher.execute(Dispatcher.java:839) [:2.7.1.1]
at 
org.geoserver.ows.Dispatcher.handleRequestInternal(Dispatcher.java:280) 
[:2.7.1.1]
at 
org.springframework.web.servlet.mvc.AbstractController.handleRequest(AbstractController.java:153)
 [:3.1.4.RELEASE]
at 
org.springframework.web.servlet.mvc.SimpleControllerHandlerAdapter.handle(SimpleControllerHandlerAdapter.java:48)
 [:3.1.4.RELEASE]
at 
org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:923)
 [:3.1.4.RELEASE]
at 
org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:852)
 [:3.1.4.RELEASE]
at 
org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:882)
 [:3.1.4.RELEASE]
at 
org.springframework.web.servlet.FrameworkServlet.doGet(FrameworkServlet.java:778)
 [:3.1.4.RELEASE]
at javax.servlet.http.HttpServlet.service(HttpServlet.java:734) 
[:1.0.0.Final]
at javax.servlet.http.HttpServlet.service(HttpServlet.java:847) 
[:1.0.0.Final]
at 

Re: [Geoserver-users] Possible bug rendering postgis data?

[dracic]

As I'm aware, Geoserver uses ST_Simplify in WMS rendering. So you should do
se your PostgreSQL logs, and see how the query actually looks, and then do
geometry validation with that data. Perhaps small lines are collapsing to
points

https://trac.osgeo.org/postgis/ticket/2093
  



--
View this message in context: 
http://osgeo-org.1560.x6.nabble.com/Possible-bug-rendering-postgis-data-tp5233361p5233386.html
Sent from the GeoServer - User mailing list archive at Nabble.com.

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

[Geoserver-users] MapRequest filters for range of values on raster coverage stores

[Ferguson, Steve -FS]

I have a requirement to set thresholds on values to display on a map request to 
a NETCDF backed coverage store. For example, I have a layer for surface 
temperature, and they want to be able to only display areas on the map that are 
between 25 and 30 centigrade. Is there a way to achieve this with Geoserver? 
I've attempted to use CQL_FILTER but this only results in errors like "Error 
rendering coverage on the fast path" so I think that must not be the correct 
manner to produce filtered results. Any advice on how to achieve this 
requirement would be greatly appreciated.

Thanks!

Steve Ferguson


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

[Geoserver-users] Supplying GetMap dimension value to a parameterized query

[Ruff, Thomas]

I've created a layer using a parameterized query as a database view.  I see how 
I can pass in arguments for the parameters using viewparams=p1:v1;...  in the 
GetMap request.  However, I would like to pass a dimension value from the 
GetMap request into the view as the argument.  Is there any way to do this 
without forcing the client to copy the dimension value into the viewparams 
query string parameter?



Thanks,

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

Re: [Geoserver-users] REST API Feature Type Creation

[Stefano Costa]

Hi Jamal,
you should create the second feature type using the same *nativeName* (i.e.
the table name in the DB), but a different *name*.

For example, let's assume you have a my_feature table in two different
datastores, ds1 and ds2. You can publish both with these commands:

# publish my_feature table from datastore ds1

curl -v -u admin:geoserver -XPOST -H "Content-type: text/xml" -d
"*my_feature_1**my_feature*"
http://localhost:8080/geoserver/rest/workspaces/ws/datastores/ds1/featuretypes

# publish my_feature table from datastore ds2

curl -v -u admin:geoserver -XPOST -H "Content-type: text/xml" -d
"*my_feature_2**my_feature*"
http://localhost:8080/geoserver/rest/workspaces/ws/datastores/ds2/featuretypes


Hope this helps.


On Thu, Oct 29, 2015 at 3:27 AM, Murad Jamal  wrote:

> I have an workspace with multiple datastores meaning it has multiple
> database connections.so tableName can be same between the databases.
>
> So the issue is now that when i try to create a featuretype using i have
> noticed that it creates a layer automatically and in my post data
> the featureType name needs to be same as tablename.
>
> so the first featureType from one datastore gets created fine
> the second one from diffrerent datastore but same tablename get me error
> saying the resource with same name already exists.
>
> So how can i solve this?
>
> Regards
>
> Murad
>
>
> --
>
> ___
> Geoserver-users mailing list
> Geoserver-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geoserver-users
>
>


-- 

Best regards,
Stefano Costa

==
GeoServer Professional Services from the experts!
Visithttp://goo.gl/it488V for more information.
==
Dott. Stefano Costa
Senior Software Engineer

GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054  Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
http://www.geo-solutions.ithttp://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.
--
___
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users