Hello all,
I'd like to know if there is a way to limit the supported wfs versions for
my geoserver instance (GeoServer 2.8.2).
I figured out that there is a wfs.xml in the root data dir of geoserver.
This file contains a versions-section from which I removed the part for
version 1.0.0. But that
Setting explicit output format of "GML3" then the WFS response is properly
encoded. That's what I meant when I wrote that by switching to this output
format the response is the same as requesting the WFS in version 1.1.0.
I just wanted to make sure that I'm not missing a mapping specific option.
Hello,
I'm using GeoServer's and App-Schema-Plugin's current stable version 2.8.2
for complex feature mappings. In general this is working fine. While doing
some WFS requests I noticed a difference between the output of a gml polygon
property with WFS version 1.1.0 (GML 3.1.1) and the same
Hello,
I'm using Geoserver 2.1.3 with app-schema plugin 2.7.4. I send a request to
the WFS and append the sortBy-parameter. But my resultset does not get
sorted by the given property. The geoserver.log-file shows that the sortBy
parameter is acknowledged:
But when I look at the built query,
Sorry, I forgot to append the log quotes in the mail (that happens quite
often to me):
2012-08-22 09:37:33,270 DEBUG [geoserver.requests] - Query is
net.opengis.wfs.impl.QueryTypeImpl@1cbb58c (group: [], propertyName: [],
function: null, filter: null, sortBy:
Parameter
results in transforming the coordinates.
Thanks again and best regards,
TRD
--
View this message in context:
http://osgeo-org.1803224.n2.nabble.com/Geoserver-App-Schema-WFS-getFeature-Request-with-srsName-tp6962059p7038020.html
Sent from the GeoServer - User mailing list archive
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
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
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
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:
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:
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:
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:
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:
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
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
to change my column so transformation
can made by app-schema automatically?
Thanks for reply.
Kind regards, TRD
--
View this message in context:
http://osgeo-org.1803224.n2.nabble.com/Geoserver-App-Schema-WFS-getFeature-Request-with-srsName-tp6962059p6962059.html
Sent from the GeoServer - User mailing
The file is shortened to contain only one FeatureType, in detail
Hauskoordinate which is used in the mapping. I did not edit the version in
my app-schema-cache directly. I edited the file located at my localhost and
deleted the file in the cache. This schema file does contain an element with
the
This is the schema file called dog_hk.xsd:
?xml version=1.0 encoding=UTF-8?
schema targetNamespace=http://www.lverma.nrw.de/namespaces/dog;
xmlns:dog=http://www.lverma.nrw.de/namespaces/dog;
xmlns:gml=http://www.opengis.net/gml;
xmlns:xsd=http://www.w3.org/2001/XMLSchema;
You are totally right, those - were in the original xsd-file and truly are
not wanted there. I removed them and added the missing XMLSchema namespace.
This solved the occurence of the error No top level element found in
schemas but instead I'm getting XSD type definition not found in schemas:
Finally I got it working (as no error appears anymore). The last error showed
up because a mismatch of namespaces. After correcting them everything seems
to work fine for now :D
--
View this message in context:
21 matches
Mail list logo
