[Geoserver-users] Reprojection of ArcSDE rasters is extremly slow.
We have tested on several servers GEOSERVER 2.x with ArcSDE 9.3.1 rasters reprojection of WMS service. It's extremly slow. Can you help? Testing url: http://geo.enviroportal.sk/geoserver/sazp/zakladna_mapa_1/wms - slow http://geo.enviroportal.sk/geoserver/sazp/dmr3/wms - timeout http://geo.enviroportal.sk/geoserver/sazp/IMA_2000/wms - mostly timeout Same data in WMS - ArcGis server works for reprojection fast. Thank you -- Miloslav Kmeť -- Sell apps to millions through the Intel(R) Atom(Tm) Developer Program Be part of this innovative community and reach millions of netbook users worldwide. Take advantage of special opportunities to increase revenue and speed time-to-market. Join now, and jumpstart your future. http://p.sf.net/sfu/intel-atom-d2d ___ Geoserver-users mailing list Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users
Re: [Geoserver-users] wfs getfeature: geometry filter with polygon doesn't work with version 2
Hi, Try to catch the exact WFS query that your application is sending. -Jukka Rahkonen- Lähettäjä: Jean-Baptiste RAYNAUD [mailto:jb.rayn...@gingergroupe.com] Lähetetty: 24. elokuuta 2010 10:26 Vastaanottaja: geoserver-users@lists.sourceforge.net Aihe: [Geoserver-users] wfs getfeature: geometry filter with polygon doesn't work with version 2 Hello, I think there is a bug in the version 2 of GeoServer with wfs getfeature request. I developed a function for a web mapping interface that use a wfs getfeature request with a geometry intersects filter with a polygon. The polygon is actually a little square made with 4 coordinates based on a mouse click in the map area. I choose this method because the accuracy with a bbox is not good and if I choose a point intersects filter it doesn't work with a point layer or a linestring layer because the user have to click exactly on the point or the line in the map. With Geoserver 1.7.7 it worked fine but with the version 2.02 the request returns an empty set of records. The requested output format is JSON and my data are stored in Postgres/PostGis database. I tested the request in PGAdmin and I obtained the attempted result, so, maybe the filter function changed in the new version of Geoserver? Is there a solution? It is for me a real problem because I use to work with the latest version of Geoserver, and it should be a waste of time to go back to the previous version. Regards, Jean-Baptiste Raynaud -- Sell apps to millions through the Intel(R) Atom(Tm) Developer Program Be part of this innovative community and reach millions of netbook users worldwide. Take advantage of special opportunities to increase revenue and speed time-to-market. Join now, and jumpstart your future. http://p.sf.net/sfu/intel-atom-d2d___ Geoserver-users mailing list Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users
Re: [Geoserver-users] wfs getfeature: geometry filter with polygon doesn't work with version 2
Here the post with WFS query parameters catched with firebug:
Filter : Filter xmlns=http://www.opengis.net/ogc;
xmlns:gml=http://www.opengis.net/gml;IntersectsPropertyNamewkb_geometry/PropertyNamegml:Polygongml:outerBoundaryIsgml:LinearRinggml:coordinates912119.35162095,6312937.3566085
912139.35162095,6312937.3566085 912139.35162095,6312957.3566085
912119.35162095,6312957.3566085
912119.35162095,6312937.3566085/gml:coordinates/gml:LinearRing/gml:outerBoundaryIs/gml:Polygon/Intersects/Filter
OutputFormat : JSON
Request : GetFeature
Service : wfs
typeName : topp:communes
version : 1.1.0
I do not have error from geoserver but an empty result :
{type:FeatureCollection,features:[]}
The projection is EPSG:2154 (Lambert 93 France)
I tried with a DWithin filter and it worked fine so I think I will use this
method. But I would like to understand why the intersects filter didn't work
with polygon geometry but worked with a point.
Thanks,
Jean-Baptiste Raynaud
De : Rahkonen Jukka [mailto:jukka.rahko...@mmmtike.fi]
Envoyé : mardi 24 août 2010 10:01
À : Jean-Baptiste RAYNAUD; geoserver-users@lists.sourceforge.net
Objet : VS: [Geoserver-users] wfs getfeature: geometry filter with polygon
doesn't work with version 2
Hi,
Try to catch the exact WFS query that your application is sending.
-Jukka Rahkonen-
Lähettäjä: Jean-Baptiste RAYNAUD [mailto:jb.rayn...@gingergroupe.com]
Lähetetty: 24. elokuuta 2010 10:26
Vastaanottaja: geoserver-users@lists.sourceforge.net
Aihe: [Geoserver-users] wfs getfeature: geometry filter with polygon doesn't
work with version 2
Hello,
I think there is a bug in the version 2 of GeoServer with wfs getfeature
request.
I developed a function for a web mapping interface that use a wfs getfeature
request with a geometry intersects filter with a polygon.
The polygon is actually a little square made with 4 coordinates based on a
mouse click in the map area. I choose this method because the accuracy with a
bbox is not good and if I choose a point intersects filter it doesn't work with
a point layer or a linestring layer because the user have to click exactly on
the point or the line in the map.
With Geoserver 1.7.7 it worked fine but with the version 2.02 the request
returns an empty set of records. The requested output format is JSON and my
data are stored in Postgres/PostGis database. I tested the request in PGAdmin
and I obtained the attempted result, so, maybe the filter function changed in
the new version of Geoserver?
Is there a solution? It is for me a real problem because I use to work with
the latest version of Geoserver, and it should be a waste of time to go back to
the previous version.
Regards,
Jean-Baptiste Raynaud
--
Sell apps to millions through the Intel(R) Atom(Tm) Developer Program
Be part of this innovative community and reach millions of netbook users
worldwide. Take advantage of special opportunities to increase revenue and
speed time-to-market. Join now, and jumpstart your future.
http://p.sf.net/sfu/intel-atom-d2d___
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users
Re: [Geoserver-users] wfs getfeature: geometry filter with polygon doesn't work with version 2
Hi,
In a hurry I just believe this is not a valid WFS 1.1.0 request. Try 1.0.0
instead, or rewrite the polygon in gml3.
-Jukka-
Lähettäjä: Jean-Baptiste RAYNAUD [mailto:jb.rayn...@gingergroupe.com]
Lähetetty: 24. elokuuta 2010 11:24
Vastaanottaja: Rahkonen Jukka; geoserver-users@lists.sourceforge.net
Aihe: RE: [Geoserver-users] wfs getfeature: geometry filter with
polygon doesn't work with version 2
Here the post with WFS query parameters catched with firebug:
Filter : Filter xmlns=http://www.opengis.net/ogc;
xmlns:gml=http://www.opengis.net/gml;IntersectsPropertyNamewkb_geometry/PropertyNamegml:Polygongml:outerBoundaryIsgml:LinearRinggml:coordinates912119.35162095,6312937.3566085
912139.35162095,6312937.3566085 912139.35162095,6312957.3566085
912119.35162095,6312957.3566085
912119.35162095,6312937.3566085/gml:coordinates/gml:LinearRing/gml:outerBoundaryIs/gml:Polygon/Intersects/Filter
OutputFormat : JSON
Request : GetFeature
Service : wfs
typeName : topp:communes
version : 1.1.0
I do not have error from geoserver but an empty result :
{type:FeatureCollection,features:[]}
The projection is EPSG:2154 (Lambert 93 France)
I tried with a DWithin filter and it worked fine so I think I will use
this method. But I would like to understand why the intersects filter didn't
work with polygon geometry but worked with a point.
Thanks,
Jean-Baptiste Raynaud
De : Rahkonen Jukka [mailto:jukka.rahko...@mmmtike.fi]
Envoyé : mardi 24 août 2010 10:01
À : Jean-Baptiste RAYNAUD; geoserver-users@lists.sourceforge.net
Objet : VS: [Geoserver-users] wfs getfeature: geometry filter with
polygon doesn't work with version 2
Hi,
Try to catch the exact WFS query that your application is sending.
-Jukka Rahkonen-
Lähettäjä: Jean-Baptiste RAYNAUD
[mailto:jb.rayn...@gingergroupe.com]
Lähetetty: 24. elokuuta 2010 10:26
Vastaanottaja: geoserver-users@lists.sourceforge.net
Aihe: [Geoserver-users] wfs getfeature: geometry filter with
polygon doesn't work with version 2
Hello,
I think there is a bug in the version 2 of GeoServer with wfs
getfeature request.
I developed a function for a web mapping interface that use a
wfs getfeature request with a geometry intersects filter with a polygon.
The polygon is actually a little square made with 4
coordinates based on a mouse click in the map area. I choose this method
because the accuracy with a bbox is not good and if I choose a point intersects
filter it doesn't work with a point layer or a linestring layer because the
user have to click exactly on the point or the line in the map.
With Geoserver 1.7.7 it worked fine but with the version 2.02
the request returns an empty set of records. The requested output format is
JSON and my data are stored in Postgres/PostGis database. I tested the request
in PGAdmin and I obtained the attempted result, so, maybe the filter function
changed in the new version of Geoserver?
Is there a solution? It is for me a real problem because I use
to work with the latest version of Geoserver, and it should be a waste of time
to go back to the previous version.
Regards,
Jean-Baptiste Raynaud
--
Sell apps to millions through the Intel(R) Atom(Tm) Developer Program
Be part of this innovative community and reach millions of netbook users
worldwide. Take advantage of special opportunities to increase revenue and
speed time-to-market. Join now, and jumpstart your future.
http://p.sf.net/sfu/intel-atom-d2d___
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users
[Geoserver-users] GML3 namespace error
Hi I'm running into a strange issue. I get this error when trying to receive a gml3 wfs output: 24 Aug 11:14:48 ERROR [geoserver.ows] - java.lang.NoSuchMethodError: org.apache.xml.serialize.XMLSerializer.setNamespaces(Z)V at org.geotools.xml.Encoder.encode(Encoder.java:559) at org.geoserver.wfs.xml.GML3OutputFormat.write(GML3OutputFormat.java:197) at org.geoserver.wfs.WFSGetFeatureOutputFormat.write(WFSGetFeatureOutputFormat.java:137) at org.geoserver.ows.Dispatcher.response(Dispatcher.java:726) at org.geoserver.ows.Dispatcher.handleRequestInternal(Dispatcher.java:234) 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:875) at org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:809) at org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:571) at org.springframework.web.servlet.FrameworkServlet.doGet(FrameworkServlet.java:501) at javax.servlet.http.HttpServlet.service(HttpServlet.java:617) at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.vfny.geoserver.filters.SetCharacterEncodingFilter.doFilter(SetCharacterEncodingFilter.java:108) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.acegisecurity.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:265) at org.acegisecurity.intercept.web.FilterSecurityInterceptor.invoke(FilterSecurityInterceptor.java:107) at org.acegisecurity.intercept.web.FilterSecurityInterceptor.doFilter(FilterSecurityInterceptor.java:72) at org.acegisecurity.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:275) at org.acegisecurity.ui.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:124) at org.acegisecurity.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:275) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at org.acegisecurity.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:275) at org.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:174) at org.acegisecurity.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:275) at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) at org.acegisecurity.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:275) at org.acegisecurity.util.FilterChainProxy.doFilter(FilterChainProxy.java:149) at org.acegisecurity.util.FilterToBeanProxy.doFilter(FilterToBeanProxy.java:98) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.geoserver.filters.LoggingFilter.doFilter(LoggingFilter.java:73) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.geoserver.filters.ReverseProxyFilter.doFilter(ReverseProxyFilter.java:183) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.geoserver.filters.GZIPFilter.doFilter(GZIPFilter.java:41) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) at
Re: [Geoserver-users] GML3 namespace error
Hi Justin The error makes me think you have xerces or another xml jar in the servlet container common libs folder? Any chance that is true? The content of tomcats lib directory looks like this: annotations-api.jar el-api.jar postgresql-8.4-701.jdbc3.jar tomcat-i18n-fr.jar catalina-ant.jar jasper-el.jar servlet-api.jar tomcat-i18n-ja.jar catalina-ha.jar jasper.jar tomcat-coyote.jar catalina.jar jasper-jdt.jar tomcat-dbcp.jar catalina-tribes.jar jsp-api.jar tomcat-i18n-es.jar regards Stefan On Tue, Aug 24, 2010 at 6:07 AM, Ziegler Stefan stefan.zieg...@bd.so.ch wrote: Hi I'm running into a strange issue. I get this error when trying to receive a gml3 wfs output: 24 Aug 11:14:48 ERROR [geoserver.ows] - java.lang.NoSuchMethodError: org.apache.xml.serialize.XMLSerializer.setNamespaces(Z)V at org.geotools.xml.Encoder.encode(Encoder.java:559) at org.geoserver.wfs.xml.GML3OutputFormat.write(GML3OutputFormat.java:197) at org.geoserver.wfs.WFSGetFeatureOutputFormat.write(WFSGetFeatureOutputFormat.java:137) at org.geoserver.ows.Dispatcher.response(Dispatcher.java:726) at org.geoserver.ows.Dispatcher.handleRequestInternal(Dispatcher.java:234) 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:875) at org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:809) at org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:571) at org.springframework.web.servlet.FrameworkServlet.doGet(FrameworkServlet.java:501) at javax.servlet.http.HttpServlet.service(HttpServlet.java:617) at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.vfny.geoserver.filters.SetCharacterEncodingFilter.doFilter(SetCharacterEncodingFilter.java:108) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.acegisecurity.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:265) at org.acegisecurity.intercept.web.FilterSecurityInterceptor.invoke(FilterSecurityInterceptor.java:107) at org.acegisecurity.intercept.web.FilterSecurityInterceptor.doFilter(FilterSecurityInterceptor.java:72) at org.acegisecurity.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:275) at org.acegisecurity.ui.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:124) at org.acegisecurity.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:275) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at org.acegisecurity.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:275) at org.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:174) at org.acegisecurity.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:275) at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) at org.acegisecurity.util.FilterChainProxy$VirtualFilterChain.doFilter(FilterChainProxy.java:275) at org.acegisecurity.util.FilterChainProxy.doFilter(FilterChainProxy.java:149) at org.acegisecurity.util.FilterToBeanProxy.doFilter(FilterToBeanProxy.java:98) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.geoserver.filters.LoggingFilter.doFilter(LoggingFilter.java:73) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.geoserver.filters.ReverseProxyFilter.doFilter(ReverseProxyFilter.java:183) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at
[Geoserver-users] SLD doesnt work exactly for GoogleEarth-Plugin
Hi @ all! I have a problem with my SLD and the GoogleEarth-Plugin in my application. I made a SLD with PointSymbolizers which have a dynamic size. PointSymbolizer Graphic Mark WellKnownNamecircle/WellKnownName Fill CssParameter name=fill-opacity1.0/CssParameter CssParameter name=fill#D4/CssParameter /Fill /Mark Sizeogc:PropertyNamemagnitude/ogc:PropertyName/Size /Graphic /PointSymbolizer The size is defined by the field magnitude coming from GeoServer (at the end from PostGIS). In my OpenLayers-application everything works fine. The points have a different size. However the GoogleEarth-plugin styles the points with the default point style of GoogleEarth and the color I defined for different rules. The problem is, that the size is the same for every point. Does anyone have a solution for this problem? I appreciate any help. Thanks in advance Martin -- View this message in context: http://old.nabble.com/SLD-doesnt-work-exactly-for-GoogleEarth-Plugin-tp29523761p29523761.html Sent from the GeoServer - User mailing list archive at Nabble.com. -- Sell apps to millions through the Intel(R) Atom(Tm) Developer Program Be part of this innovative community and reach millions of netbook users worldwide. Take advantage of special opportunities to increase revenue and speed time-to-market. Join now, and jumpstart your future. http://p.sf.net/sfu/intel-atom-d2d ___ Geoserver-users mailing list Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users
Re: [Geoserver-users] Appschema: Circular feature-chaining
Thanks Rini - This worked perfectly. I'm curious, could this kind of configuration help to get around another GeoSciML problem? Specifically, MappedFeatures cross geometry type boundaries. A MappedFeature might be a polygon, a line or a point. While this is sensible from the perspective of an XML document, I'm not sure its viable in the framework of a WFS response coming from Geoserver. Certainly at the least, the data source for a multi-geometry MappedFeature type would have to come from different PostGIS tables. This is just another example of a situation where I previously had to use two services, one to provide linear MappedFeatures, and one for polygon MappedFeatures. Thanks again, and I'm glad to hear the CRS bug has been worked out. Ryan -Original Message- From: Rini Angreani [mailto:rini.angre...@csiro.au] Sent: Monday, August 23, 2010 10:51 PM To: geoserver-users@lists.sourceforge.net Subject: Re: [Geoserver-users] Appschema: Circular feature-chaining Hello Ryan, You can have multiple mappings of a feature type in one service, as long as they're not in the same location where its featuretype.xml is defined. E.g. you can't have 2 GeologicUnit mappings in GeologicUnit configuration location, as the featuretype.xml would not know which mapping to use. However, you can have a second GeologicUnit mapping file in MappedFeature folder. That means, only one mapping is used to serve the type as a top level feature (where featuretype.xml exists), and the other mappings are only used inside another feature type in a different location/folder. To achieve this, you can use mappingName (http://docs.geoserver.org/trunk/en/user/data/app-schema/mapping-file.html#t ypemappings-and-featuretypemapping). Sorry the documentation is not clear.. an improvement is long overdue. So in MappedFeature mapping file, you'd have something like: AttributeMapping targetAttributegsml:specification/targetAttribute sourceExpression OCQLGEOLOGIC_UNIT_ID/OCQL linkElementgeologicUnit_no_Occurrence/linkElement linkFieldFEATURE_LINK/linkField /sourceExpression /AttributeMapping Where geologicUnit_no_occurrence would have no specified attribute mapping for gsml:occurrence. To make this mapping unique from the top level GeologicUnit mapping, you must specify mappingName in its FeatureTypeMapping tag. In this case, mappingName would be geologicUnit_no_occurrence. You'd then include the location of geologicUnit_no_occurrence mapping, or define the FeatureTypeMapping in the same file (and would only exist for this MappedFeature). Same deal with GeologicUnit mapping, where you define it separately as a top level feature, and link occurrences to a separate MappedFeature mapping (with a different mappingName). Your second MappedFeature would have specification mapped as xlink:href. To sum up, to avoid having errors for multiple mappings per type: - mappingName has to override existing mapping with the same targetElement. - mappingName to be used instead of targetElement in linkElement tag on the chaining side. - there should only be 1 mapping file for the type where it is configured as top level feature (otherwise you'll get an error about feature type already exists or something to that effect). I hope it's not too confusing, and it works for you. Let me know otherwise. By the way, my colleague Victor Tey is close to fixing the problem you reported a long time ago: http://jira.codehaus.org/browse/GEOT-2843. Cheers Rini Ryan Clark wrote: Hello - I've ran into the old circular feature-chaining problem in a GeoSciML WFS service again. Basically it is exactly the problem outlined at http://docs.geoserver.org/stable/en/user/data/app-schema/feature-chain ing.ht ml#multi-valued-properties-by-reference-xlink-href The approach outlined there requires that one or the other, GeologicUnit.occurence or MappedFeature.specification, be by xlink:href all of the time. If I make my occurrences by xlink:href, then whether I make a WFS query for gsml:GeologicUnit or gsml:MappedFeature, the occurrences will always be by xlink:href, and the value may or may not be resolvable, depending on how I construct the string and what exactly is in the WFS response document. What you'd really like is a service which followed these rules: 1) GeologicUnits that are being returned as MappedFeature.specifications would simply not include the optional gsml:occurrence property. 2) MappedFeature.specifications would only be by xlink:href if those MappedFeatures are being returned as GeologicUnit.occurrences. 3) In any other situation, occurrences or specifications would not be by xlink:href, unless they were being repeated within a single WFS response document. Is there any tricky way to
[Geoserver-users] Appschema: NullPointerException
Okay - hopefully my last app-schema issue for a while. I certainly appreciate the help! My MappedFeature mapping file works perfectly until I add the targetAttribute gsmlcore:metadata. Here's the mapping: AttributeMapping targetAttributegsmlcore:metadata/targetAttribute sourceExpression OCQLdatasourceid/OCQL linkElementisp:MD_Metadata/linkElement linkFieldFEATURE_LINK[1]/linkField /sourceExpression isMultiplefalse/isMultiple /AttributeMapping Exactly the same mapping works fine within my GeologicUnit mapping file, which also has a gsmlcore:metadata property. Therefore, I don't think that the problem has anything to do with the mapping for the isp:MD_Metadata element. When I add this targetAttribute to the MappedFeature file, Geoserver gags on boot, throwing the error shown below. The error goes away if I rename the targetAttribute to something that doesn't exist (e.g. gsmlcore:moustache), but then as you'd expect there's an error when making a feature request. Thanks! Ryan 24 Aug 12:56:37 INFO [org.geoserver] - java.io.IOException at org.geoserver.catalog.ResourcePool.getDataStore(ResourcePool.java:362) at org.geoserver.catalog.impl.DataStoreInfoImpl.getDataStore(DataStoreInfoImpl. java:37) at org.geoserver.config.GeoServerLoader.readCatalog(GeoServerLoader.java:572) at org.geoserver.config.GeoServerLoader.loadCatalog(GeoServerLoader.java:152) at org.geoserver.config.GeoServerLoader.postProcessBeforeInitialization(GeoServ erLoader.java:123) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory .applyBeanPostProcessorsBeforeInitialization(AbstractAutowireCapableBeanFact ory.java:350) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory .initializeBean(AbstractAutowireCapableBeanFactory.java:1330) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory .doCreateBean(AbstractAutowireCapableBeanFactory.java:473) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory $1.run(AbstractAutowireCapableBeanFactory.java:409) at java.security.AccessController.doPrivileged(Native Method) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory .createBean(AbstractAutowireCapableBeanFactory.java:380) at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(Ab stractBeanFactory.java:264) at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSi ngleton(DefaultSingletonBeanRegistry.java:221) at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(Abst ractBeanFactory.java:261) at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(Abstra ctBeanFactory.java:185) at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(Abstra ctBeanFactory.java:164) at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolv eReference(BeanDefinitionValueResolver.java:269) at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolv eValueIfNecessary(BeanDefinitionValueResolver.java:104) at org.springframework.beans.factory.support.ConstructorResolver.resolveConstru ctorArguments(ConstructorResolver.java:495) at org.springframework.beans.factory.support.ConstructorResolver.autowireConstr uctor(ConstructorResolver.java:162) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory .autowireConstructor(AbstractAutowireCapableBeanFactory.java:925) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory .createBeanInstance(AbstractAutowireCapableBeanFactory.java:835) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory .doCreateBean(AbstractAutowireCapableBeanFactory.java:440) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory $1.run(AbstractAutowireCapableBeanFactory.java:409) at java.security.AccessController.doPrivileged(Native Method) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory .createBean(AbstractAutowireCapableBeanFactory.java:380) at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(Ab stractBeanFactory.java:264) at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSi ngleton(DefaultSingletonBeanRegistry.java:221) at
Re: [Geoserver-users] SLD doesnt work exactly for GoogleEarth-Plugin
Google Earth is a toy that basically renders any symbol as a 32 pixel image and then resizes that as it pleases to make everything fit. One way to achieve the effect you are after is to create a polygon for each of these points and send these polygons as KML to Google Earth. Those are not clickable, so if you want popups you'll also have to add a transparent PNG or something something similar as a point symbolizer. -Arne On 8/24/10 9:23 PM, Martin.L wrote: Hi @ all! I have a problem with my SLD and the GoogleEarth-Plugin in my application. I made a SLD with PointSymbolizers which have a dynamic size. PointSymbolizer Graphic Mark WellKnownNamecircle/WellKnownName Fill CssParameter name=fill-opacity1.0/CssParameter CssParameter name=fill#D4/CssParameter /Fill /Mark Sizeogc:PropertyNamemagnitude/ogc:PropertyName/Size /Graphic /PointSymbolizer The size is defined by the field magnitude coming from GeoServer (at the end from PostGIS). In my OpenLayers-application everything works fine. The points have a different size. However the GoogleEarth-plugin styles the points with the default point style of GoogleEarth and the color I defined for different rules. The problem is, that the size is the same for every point. Does anyone have a solution for this problem? I appreciate any help. Thanks in advance Martin -- Sell apps to millions through the Intel(R) Atom(Tm) Developer Program Be part of this innovative community and reach millions of netbook users worldwide. Take advantage of special opportunities to increase revenue and speed time-to-market. Join now, and jumpstart your future. http://p.sf.net/sfu/intel-atom-d2d ___ Geoserver-users mailing list Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users
