[postgis-users] 回复: Postgis 2.0 and geoserver 2.1 rc4
龙龙
463487397 at qq.com
Mon Apr 18 05:06:14 PDT 2011
Thanks for your kind-hearted answer. The data from the table is the same.
There is a sample data in geoserver's user documentation named nyc_buildings.sql.
When we use PostgreSQL9.0ãpostgis 1.5 and geoserver 2.1 rc4 to publish this data, everything goes all right.
But when we change postgis1.5 to postgis2.0, the problem comes....
There are two bouding boxes to fill. When we clicked Compute from data or Compute from Native bounds, the error happened...
Someone says that postgis API has changed in 2.0 for bounding boxes. So the error happens. Do you agree with him? And if it is true, does it mean that we can't use postgis2.0 to publish the layer or there is a need of other tools to solve it? I'm looking forword to your reply. Thank you very much.
------------------ åå§é®ä»¶ ------------------
å件人: "Maria Arias de Reyna"<marias at emergya.es>;
åéæ¶é´: 2011å¹´4æ18æ¥(ææä¸) ä¸å3:18
æ¶ä»¶äºº: "PostGIS Users Discussion"<postgis-users at postgis.refractions.net>;
主é¢: Re: [postgis-users] Postgis 2.0 and geoserver 2.1 rc4
El Monday 18 April 2011, é¾é¾ escribió:
> Hi, I am getting the following error when trying to add a layer from a
> postgis 2.0 database: java.lang.RuntimeException: java.io.IOException:
> Error occured calculating bounds at
> org.geotools.jdbc.JDBCFeatureSource.getBoundsInternal(JDBCFeatureSource.ja
> va:476) at
> org.geotools.jdbc.JDBCFeatureStore.getBoundsInternal(JDBCFeatureStore.java
> :178) at
> org.geotools.data.store.ContentFeatureSource.getBounds(ContentFeatureSourc
> e.java:369) at
> org.geotools.data.store.ContentFeatureSource.getBounds(ContentFeatureSourc
> e.java:341) at
> org.geotools.data.SimpleFeatureSourceBridge.getBounds(SimpleFeatureSourceB
> ridge.java:49) at
> org.vfny.geoserver.global.GeoServerFeatureSource.getBounds(GeoServerFeatur
> eSource.java:529) at
> org.geoserver.catalog.CatalogBuilder.getNativeBounds(CatalogBuilder.java:4
> 63) at
> org.geoserver.web.data.resource.BasicResourceConfig$1.onSubmit(BasicResour
> ceConfig.java:115) at
> org.apache.wicket.ajax.markup.html.form.AjaxSubmitLink$1.onSubmit(AjaxSubm
> itLink.java:68) at
> org.apache.wicket.ajax.form.AjaxFormSubmitBehavior.onEvent(AjaxFormSubmitB
> ehavior.java:143) at
> org.apache.wicket.ajax.AjaxEventBehavior.respond(AjaxEventBehavior.java:17
> 7) at
> org.apache.wicket.ajax.AbstractDefaultAjaxBehavior.onRequest(AbstractDefau
> ltAjaxBehavior.java:300) at
> org.apache.wicket.request.target.component.listener.BehaviorRequestTarget.
> processEvents(BehaviorRequestTarget.java:119) at
> org.apache.wicket.request.AbstractRequestCycleProcessor.processEvents(Abst
> ractRequestCycleProcessor.java:92) at
> org.apache.wicket.RequestCycle.processEventsAndRespond(RequestCycle.java:1
> 250) 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.doPost(WicketServlet.java:16
> 0) at javax.servlet.http.HttpServlet.service(HttpServlet.java:727) at
> javax.servlet.http.HttpServlet.service(HttpServlet.java:820) at
> org.springframework.web.servlet.mvc.ServletWrappingController.handleReques
> tInternal(ServletWrappingController.java:158) at
> org.springframework.web.servlet.mvc.AbstractController.handleRequest(Abstr
> actController.java:153) at
> org.springframework.web.servlet.mvc.SimpleControllerHandlerAdapter.handle(
> SimpleControllerHandlerAdapter.java:48) at
> org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherSer
> vlet.java:875) at
> org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServ
> let.java:809) at ....
>
> But this problem doesn't exist when I use postgis 1.5. So, is this a
> postgis problem or a geoserver problem. How shall I deal with it?
The data from the table is the same?
I had this error once when the geometry column wasn't correctly defined. Are
you sure the table is defined on the geometry_columns table?
Can you look inside geoserver to see which is the exact sql sentence that is
used there?
--
MarÃa Arias de Reyna DomÃnguez
Área de Operaciones
Emergya ConsultorÃa
Tfno: +34 954 51 75 77 / +34 607 43 74 27
Fax: +34 954 51 64 73
www.emergya.es
_______________________________________________
postgis-users mailing list
postgis-users at postgis.refractions.net
http://postgis.refractions.net/mailman/listinfo/postgis-users
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/postgis-users/attachments/20110418/9c079c59/attachment.html>
More information about the postgis-users
mailing list