[Geoserver-users] Repaired geometries still producing WKB errors for WFS on PostGIS store
Hi all, I've just started using PostGIS as a datastore, importing shapefiles using shp2pgsql. I've attached the shapefiles I use to reproduce this issue: http://osgeo-org.1560.n6.nabble.com/file/n560/example.zip example.zip If there is a problem with the geometry neither WMS nor WFS will work with WFS requests reporting: An exception occurred while parsing WKB data Points of LinearRing do not form a closed linestring This can be verified in PostGIS with the query: SELECT gid, st_isvalidreason(geom), st_summary(geom) FROM c1t3desertpavement WHERE st_isclosed(geom) is FALSE; After repairing the geometry in ArcMap, and importing into PostGIS, the above query no longer returns any rows. When the repaired data is published in GeoServer, WMS requests will work but WFS requests still report the same error. Any help is or suggestions are appreciated. Context: Centralising thousands of shapefiles for client use over WFS in ArcMap I've tried: Reloading the GeoServer cache and restarting GeoServer Cleaning up the data using GRASS (with minor damage to the polygons) which will fix WMS and WFS but Arc fails to show the features and just says No Geometry (no errors in the GeoServer logs) Additional notes: I can load the invalid geometry directly from PostGIS using QuantumGIS I am using: GeoServer 2.1.4 Postgres: 9.1.5.1 with PostGIS 2.0.1 using a 2.0 template. Windows Server 2008 -- View this message in context: http://osgeo-org.1560.n6.nabble.com/Repaired-geometries-still-producing-WKB-errors-for-WFS-on-PostGIS-store-tp560.html Sent from the GeoServer - User mailing list archive at Nabble.com. -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ Geoserver-users mailing list Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users
Re: [Geoserver-users] 2.1.2 REST create featuretype with app-schema datastore
Hi Ben, thanks, I spent some time creating a script to reproduce the problem for you. I'm not sure what has happened because the issue is now a NullPointerException, even when the requests are made from the original script. I've included both stack traces and responses. http://osgeo-org.1803224.n2.nabble.com/file/n6960237/rest_script.php rest_script.php http://osgeo-org.1803224.n2.nabble.com/file/n6960237/classCast_geoserver.log classCast_geoserver.log http://osgeo-org.1803224.n2.nabble.com/file/n6960237/classCast_requestLog.txt classCast_requestLog.txt http://osgeo-org.1803224.n2.nabble.com/file/n6960237/nullPointer_geoserver.log nullPointer_geoserver.log http://osgeo-org.1803224.n2.nabble.com/file/n6960237/nullPointer_requestLog.txt nullPointer_requestLog.txt -- View this message in context: http://osgeo-org.1803224.n2.nabble.com/2-1-2-REST-create-featuretype-with-app-schema-datastore-tp6950658p6960237.html Sent from the GeoServer - User mailing list archive at Nabble.com.-- RSA(R) Conference 2012 Save $700 by Nov 18 Register now http://p.sf.net/sfu/rsa-sfdev2dev1___ Geoserver-users mailing list Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users
Re: [Geoserver-users] 2.1.2 REST create featuretype with app-schema datastore
I just extended the POST example in the link below to create an app-schema datastore given a predefined workspace and then used the name of the new datastore to create a new featuretype http://docs.geoserver.org/stable/en/user/restconfig/rest-config-examples/rest-config-examples-php.html We've been using this process to create temporary features to mediate WFS results with respect to an ontology. -- View this message in context: http://osgeo-org.1803224.n2.nabble.com/2-1-2-REST-create-featuretype-with-app-schema-datastore-tp6950658p6950754.html Sent from the GeoServer - User mailing list archive at Nabble.com. -- RSAreg; Conference 2012 Save #36;700 by Nov 18 Register now http://p.sf.net/sfu/rsa-sfdev2dev1 ___ Geoserver-users mailing list Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users
[Geoserver-users] 2.1.2 REST create featuretype with app-schema datastore
Hi there, I've just upgraded from 2.0.2 to 2.1.2 and am having some trouble integrating some datastore and featuretype generation scripts via php-curl. The scripts worked fine previously but now only the datastore is successfully created via REST. When creating the featuretype based on an app-schema datastore I get the following error in the curl response: org.geotools.data.complex.AppSchemaDataAccess cannot be cast to org.geotools.DataStore Any ideas? Cheers Sina -- View this message in context: http://osgeo-org.1803224.n2.nabble.com/2-1-2-REST-create-featuretype-with-app-schema-datastore-tp6950658p6950658.html Sent from the GeoServer - User mailing list archive at Nabble.com. -- RSAreg; Conference 2012 Save #36;700 by Nov 18 Register now http://p.sf.net/sfu/rsa-sfdev2dev1 ___ Geoserver-users mailing list Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users
Re: [Geoserver-users] WFS getFeature on custon featuretype
I should mention I am using GeoServer 2.0.2 on Windows -- View this message in context: http://osgeo-org.1803224.n2.nabble.com/WFS-getFeature-on-custon-featuretype-tp6470169p6472644.html Sent from the GeoServer - User mailing list archive at Nabble.com. -- EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. http://p.sf.net/sfu/ephox-dev2dev ___ Geoserver-users mailing list Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users
Re: [Geoserver-users] WFS getFeature on custon featuretype
Thanks Ben, I have included the parameter as you suggested but the result is still the same http://127.0.0.1:8082/geoserver/wfs?service=WFSversion=1.1.0request=GetFeaturetypeName=LCDB2:lcdb2_testbbox=19567068.48958,-4695788.62634,19567393.34695,-4695454.21434,EPSG:900913SRSNAME=EPSG:900913maxfeatures=10 I also tried adding CRS=EPSG:900913 with no luck. If I change the typeName to the GeoServer generated featuretype it will work though, they both reference the same shapefile. Cheers Sina On Tue, Jun 14, 2011 at 3:56 PM, Ben Caradoc-Davies ben.caradoc-dav...@csiro.au wrote: Sina, for WFS, I think this option should be SRSNAME=EPSG:900913 I have not used the five-component version of BBOX. Please try SRSNAME to see if it works. Kind regards, Ben. On 13/06/11 21:29, Sina Masoud-Ansari wrote: If I inlcude SRS=EPSG:900913 in the requests the results are the same. -- Ben Caradoc-Davies ben.caradoc-dav...@csiro.au Software Engineering Team Leader CSIRO Earth Science and Resource Engineering Australian Resources Research Centre -- EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. http://p.sf.net/sfu/ephox-dev2dev___ Geoserver-users mailing list Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users
Re: [Geoserver-users] WFS getFeature on custon featuretype
Will do, thanks ; ) On Tue, Jun 14, 2011 at 4:45 PM, Ben Caradoc-Davies ben.caradoc-dav...@csiro.au wrote: Sina, GeoServer 2.0.2 is quite old. Many app-schema bugs have been fixed in more recent versions. Are you able to try 2.1.0 or a trunk nightly build? Here is an example of a BBOX handling bug that should be fixed in more recent versions of GeoServer app-schema: http://jira.codehaus.org/browse/GEOT-3174 There are more! Kind regards, Ben. On 14/06/11 11:38, Sina wrote: I should mention I am using GeoServer 2.0.2 on Windows -- View this message in context: http://osgeo-org.1803224.n2.nabble.com/WFS-getFeature-on-custon-featuretype-tp6470169p6472644.html Sent from the GeoServer - User mailing list archive at Nabble.com. -- EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. http://p.sf.net/sfu/ephox-dev2dev ___ Geoserver-users mailing list Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users -- Ben Caradoc-Davies ben.caradoc-dav...@csiro.au Software Engineering Team Leader CSIRO Earth Science and Resource Engineering Australian Resources Research Centre -- EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. http://p.sf.net/sfu/ephox-dev2dev___ Geoserver-users mailing list Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users
Re: [Geoserver-users] [ExternalEmail] Re: Deleting a *.properties file when GeoServer has an open handle
Thanks Ben, I would like to run the updated app-schema in a production environment if possible, do recommend just using a recent nightly build of Geoserver? Cheers Sina On Tue, Sep 28, 2010 at 9:10 PM, Ben Caradoc-Davies ben.caradoc-dav...@csiro.au wrote: Sina, your second error also results from using plugins from a different build to the main geoserver. This is always dangerous. Kind regards, Ben. On 25/09/10 09:22, Sina Masoud-Ansari wrote: I was previously using app-schema 2.6.4with Geoserver 2.0.2 and it processed the following WFS GetFeature request fine: [...] Using the nightly build from the 24/9/2010 , app-schema 2.6 SNAPSHOT produces the next error (see far below) -- Ben Caradoc-Davies ben.caradoc-dav...@csiro.au Software Engineering Team Leader CSIRO Earth Science and Resource Engineering Australian Resources Research Centre -- Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing. http://p.sf.net/sfu/novell-sfdev2dev___ Geoserver-users mailing list Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users
Re: [Geoserver-users] [ExternalEmail] Re: Deleting a *.properties file when GeoServer has an open handle
Hi again Ben, I was previously using app-schema 2.6.4with Geoserver 2.0.2 and it processed the following WFS GetFeature request fine: http://localhost:8082/geoserver/wfs?request=GetFeatureversion=1.1.0typeName=LCDB1:ni_lc_1020maxfeatures=1 but with app-schema 2.7 M4 I get the following error (see below) Using the nightly build from the 24/9/2010 , app-schema 2.6 SNAPSHOT produces the next error (see far below) I could not find 2.6.6, the stable release is currently 2.6.4. Am I to include any additional jars with these builds eg the appropriate version of the gt-api-*.jar ? I reinstalled 2.6.4 and the request works again Cheers Sina 2010-09-25 12:46:49,078 INFO [layer.TileLayerDispatcher] - ConfigurationLoader completed 2010-09-25 12:47:47,781 INFO [geoserver.wfs] - Request: getServiceInfo 2010-09-25 12:47:47,968 ERROR [geoserver.ows] - java.lang.IncompatibleClassChangeError: Found interface org.geotools.data.Query, but class was expected at org.geotools.data.complex.MappingFeatureSource.namedQuery(MappingFeatureSource.java:100) at org.geotools.data.complex.MappingFeatureSource.getFeatures(MappingFeatureSource.java:150) at org.geoserver.wfs.GetFeature.getFeatures(GetFeature.java:462) at org.geoserver.wfs.GetFeature.run(GetFeature.java:363) at org.geoserver.wfs.DefaultWebFeatureService.getFeature(DefaultWebFeatureService.java:115) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:310) at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:182) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:149) at org.geoserver.ows.util.EMFLogger.invoke(EMFLogger.java:51) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171) at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204) at $Proxy19.getFeature(Unknown Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.geoserver.ows.Dispatcher.execute(Dispatcher.java:599) at org.geoserver.ows.Dispatcher.handleRequestInternal(Dispatcher.java:230) 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:707) 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.vfny.geoserver.filters.SetCharacterEncodingFilter.doFilter(SetCharacterEncodingFilter.java:108) at org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1084) at org.acegisecurity.util.FilterChainProxy$VirtualFilterChai1:03 p.m. 25/09/2010n.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
