Excellent! Thanks for taking the time to report back to the list.
Kind regards,
Ben.
On 28/11/11 16:45, TRD wrote:
> Finally It works.
> Thanks to the Geoserver team. On Friday 25th Nov I grabbed the latest
> Geoserver 2.2 Snapshot and copied my workspace files into the data_dir.
> After starting
Finally It works.
Thanks to the Geoserver team. On Friday 25th Nov I grabbed the latest
Geoserver 2.2 Snapshot and copied my workspace files into the data_dir.
After starting Geoserver and requesting the featureTypes everything worked
fine. The annoying IO.Exception is gone and adding the srsName P
I'm still struggling with this.
Any other clues? Or may I have to wait for a newer Geoserver version?
--
View this message in context:
http://osgeo-org.1803224.n2.nabble.com/Geoserver-App-Schema-WFS-getFeature-Request-with-srsName-tp6962059p6995396.html
Sent from the GeoServer - User mailing list
Network connection problems can be excluded.
Lets say my table consists of these three columns (type in brackets):
identifier (text)
geomastext (geometry in WKT format, no transformations possible on this)
geom (geometry)
Only identifier and geomastext are referenced by the current mapping. I
add
TRD,
that looks like some sort of database or network connection problem.
- Do you have a firewall between GeoServer and PostGIS?
- Please publish the table as a simple feature by creating a new PostGIS
datastore in the GUI and then publishing the feature type. Are you able
to query this featu
Hi Ben,
I downloaded the latest trunk version of Geoserver and App-Schema yesterday
(Geoserver 2.2 SNAPSHOT 11/07/2011) and gave it a shot. The error has
changed a little bit, but it's still there:
java.lang.RuntimeException: java.io.IOException
java.io.IOException
null
Eingabe/Ausgabe-Fehler {0}
TRD,
please check your database permissions. Can the user GeoServer is
connecting as select from geometry_columns?
A strongly recommend that you consider using trunk, as many bugs have
been fixed. See here for a comparison of downloads:
https://www.seegrid.csiro.au/wiki/Infosrvices/GeoserverApp
What the hell, I'm so sorry for this recent spam sent by me...
I'm using the nabble interface for replying to the mailing list and there an
error occured after submitting my response and I thought that my post was
not sent. Afer checking emails I recognized plenty of mails sent by me...
Here is th
Hi Ben
originally I had a geometry column created with AddGeometryColumn. If a
geometry column exists then a request to the feature type whose associated
table contains this column delivers a RuntimeException: java.io.IOException
This error occurs despite the fact that no mapping for this column
Hi Ben
originally I had a geometry column created with AddGeometryColumn. If a
geometry column exists then a request to the feature type whose associated
table contains this column delivers a "java.lang.RuntimeException:
java.io.IOException: java.io.IOException java.io.IOException:
java.io.IOExcep
Hi Ben
originally I had a geometry column created with AddGeometryColumn. If a
geometry column exists then a request to the feature type whose associated
table contains this column delivers a "java.lang.RuntimeException:
java.io.IOException: java.io.IOException java.io.IOException:
java.io.IOExcep
Hi Ben
originally I had a geometry column created with AddGeometryColumn. If a
geometry column exists then a request to the feature type whose associated
table contains this column delivers a "java.lang.RuntimeException:
java.io.IOException: java.io.IOException java.io.IOException:
java.io.IOExcep
Please show us the full stack trace in geoserver.log so we can see the
cause of the java.io.IOException.
The right thing to do is to diagnose and fix the cause of this
exception. Making the exception go away by using a text column will not
help you.
On 07/11/11 16:34, TRD wrote:
> Hi Ben
>
> o
Hi Ben
originally I had a geometry column created with AddGeometryColumn. If a
geometry column exists then a request to the feature type whose associated
table contains this column delivers a "java.lang.RuntimeException:
java.io.IOException: java.io.IOException java.io.IOException:
java.io.IOExcep
Hi Ben
originally I had a geometry column created with AddGeometryColumn. If a
geometry column exists then a request to the feature type whose associated
table contains this column delivers a "java.lang.RuntimeException:
java.io.IOException: java.io.IOException java.io.IOException:
java.io.IOExcep
Hi Ben
originally I had a geometry column created with AddGeometryColumn. If a
geometry column exists then a request to the feature type whose associated
table contains this column delivers a "java.lang.RuntimeException:
java.io.IOException: java.io.IOException java.io.IOException:
java.io.IOExcep
TRD,
GeoServer reprojection (coordinate transformation) will only work for a
geometry column. Your use of a text field is a great trick, but it
prevents reprojection from working.
To have reprojection you must:
- Use a geometry column, and
- Register the geometry column in the geometry_column
Hello,
I use the app-schema plugin to map data from a postgre database to a custom
feature type. The data within the database contains coordinates for records.
While storing them in a point-geometry column (type is geometry with
constraint to check if postgis type point matches) mapping this colum
18 matches
Mail list logo
