Hello,
I'm about to try to cascade a WFS, but I don't really know where to start. I've browsed through the archives and docs and found obscure references to some WFSDataStoreFactory:GET_CAPABILITIES_URL and "same datastore that uDig uses". I'm using udig, but found no datastore. (Is this an xml file like geoserver uses?)
So, has anyone out there a snippet to spare, that shows me how to cascade a WFS? Or am I missing something? (I'm using geoserver 1.5.2.)
Has anyone tried to cascade a deegree wfs? (They currently use version 1.1.0. Is it possible to handle that with geoserver/geotools?)
(I've tried some code, but I'm currently bound to a geotools 2.1 version.)
Thanx,
Ugo
--
Ugo Taddei
Fraunhofer Institut Intelligente Analyse- und Informationssysteme (FhG IAIS)
http://www.iais.fraunhofer.de
Department Knowledge Discovery - IAIS.KD -
Working Group Spatial Decision Support
http://www.iais.fraunhofer.de/kd.html
phone (+49)2241-14-2184 fax (+49)2241-14-2072
Schloss Birlinghoven, D-53754 Sankt Augustin, Germany
------------------------------------------------------
Visit our thematic mapping tool CommonGIS: http://www.commongis.de
Hi Ugo,
Currently you cant really cascade one GeoServer to another ... :(. I know its kind of silly. Here is the issue report for it.
http://jira.codehaus.org/browse/GEOS-4
As you can see from the issue number its been one of the longest standing GeoServer issues but one we just have not gotten around to fixing.
However if you are just looking for some code to connect to any wfs server using the geotools wfs client / datastore. This should help.
http://geotools.codehaus.org/How+to+use+a+WFS+DataStore
-Justin
Ugo Taddei wrote:
Hello,
I'm about to try to cascade a WFS, but I don't really know where to start. I've browsed through the archives and docs and found obscure references to some WFSDataStoreFactory:GET_CAPABILITIES_URL and "same datastore that uDig uses". I'm using udig, but found no datastore. (Is this an xml file like geoserver uses?)
So, has anyone out there a snippet to spare, that shows me how to cascade a WFS? Or am I missing something? (I'm using geoserver 1.5.2.)
Has anyone tried to cascade a deegree wfs? (They currently use version 1.1.0. Is it possible to handle that with geoserver/geotools?)
(I've tried some code, but I'm currently bound to a geotools 2.1 version.)
Thanx,
Ugo
--
Justin Deoliveira
The Open Planning Project
http://topp.openplans.org
Hi Justin,
Justin Deoliveira wrote:
Hi Ugo,
Currently you cant really cascade one GeoServer to another ... :(. I know its kind of silly. Here is the issue report for it.
http://jira.codehaus.org/browse/GEOS-4
As you can see from the issue number its been one of the longest standing GeoServer issues but one we just have not gotten around to fixing.
However if you are just looking for some code to connect to any wfs server using the geotools wfs client / datastore. This should help.
http://geotools.codehaus.org/How+to+use+a+WFS+DataStore
Yeah, I found and tried this out yesterday, but the geotools parser says
INFO: END: wfs:Operations
25.07.2007 15:19:47 org.geotools.xml.XMLSAXHandler endElement
WARNUNG: Too few children
25.07.2007 15:19:47 org.geotools.xml.XMLSAXHandler endElement
WARNUNG: Line 1 Col 5061
org.xml.sax.SAXException: Too few children
at org.geotools.xml.XMLSAXHandler.endElement(XMLSAXHandler.java:229)
at org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown Source)
(Sorry, folks, if this is off-topic here. Consider it an interoperability experiment 
If someone is willing to have a go with the current geotools code on this WFS
http://demo.deegree.org/deegree-wfs/services?REQUEST=GetCapabilities&version=1.1.0&service=WFS
please let me know. Meanwhile I'll tackle the geotools docs.
Anyway, thanks for the answer, Justin.
Cheers,
Ugo
-Justin
Ugo Taddei wrote:
Hello,
I'm about to try to cascade a WFS, but I don't really know where to start. I've browsed through the archives and docs and found obscure references to some WFSDataStoreFactory:GET_CAPABILITIES_URL and "same datastore that uDig uses". I'm using udig, but found no datastore. (Is this an xml file like geoserver uses?)
So, has anyone out there a snippet to spare, that shows me how to cascade a WFS? Or am I missing something? (I'm using geoserver 1.5.2.)
Has anyone tried to cascade a deegree wfs? (They currently use version 1.1.0. Is it possible to handle that with geoserver/geotools?)
(I've tried some code, but I'm currently bound to a geotools 2.1 version.)
Thanx,
Ugo
--
Ugo Taddei
Fraunhofer Institut Intelligente Analyse- und Informationssysteme (FhG IAIS)
http://www.iais.fraunhofer.de
Department Knowledge Discovery - IAIS.KD -
Working Group Spatial Decision Support
http://www.iais.fraunhofer.de/kd.html
phone (+49)2241-14-2184 fax (+49)2241-14-2072
Schloss Birlinghoven, D-53754 Sankt Augustin, Germany
------------------------------------------------------
Visit our thematic mapping tool CommonGIS: http://www.commongis.de
Ahh... seems that you are trying to parse wfs 1.1... Unfortunately the geotools code only does wfs 1.0.
Ugo Taddei wrote:
Hi Justin,
Justin Deoliveira wrote:
Hi Ugo,
Currently you cant really cascade one GeoServer to another ... :(. I know its kind of silly. Here is the issue report for it.
http://jira.codehaus.org/browse/GEOS-4
As you can see from the issue number its been one of the longest standing GeoServer issues but one we just have not gotten around to fixing.
However if you are just looking for some code to connect to any wfs server using the geotools wfs client / datastore. This should help.
http://geotools.codehaus.org/How+to+use+a+WFS+DataStore
Yeah, I found and tried this out yesterday, but the geotools parser says
INFO: END: wfs:Operations
25.07.2007 15:19:47 org.geotools.xml.XMLSAXHandler endElement
WARNUNG: Too few children
25.07.2007 15:19:47 org.geotools.xml.XMLSAXHandler endElement
WARNUNG: Line 1 Col 5061
org.xml.sax.SAXException: Too few children
at org.geotools.xml.XMLSAXHandler.endElement(XMLSAXHandler.java:229)
at org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown Source)
(Sorry, folks, if this is off-topic here. Consider it an interoperability experiment 
If someone is willing to have a go with the current geotools code on this WFS
http://demo.deegree.org/deegree-wfs/services?REQUEST=GetCapabilities&version=1.1.0&service=WFS
please let me know. Meanwhile I'll tackle the geotools docs.
Anyway, thanks for the answer, Justin.
Cheers,
Ugo
-Justin
Ugo Taddei wrote:
Hello,
I'm about to try to cascade a WFS, but I don't really know where to start. I've browsed through the archives and docs and found obscure references to some WFSDataStoreFactory:GET_CAPABILITIES_URL and "same datastore that uDig uses". I'm using udig, but found no datastore. (Is this an xml file like geoserver uses?)
So, has anyone out there a snippet to spare, that shows me how to cascade a WFS? Or am I missing something? (I'm using geoserver 1.5.2.)
Has anyone tried to cascade a deegree wfs? (They currently use version 1.1.0. Is it possible to handle that with geoserver/geotools?)
(I've tried some code, but I'm currently bound to a geotools 2.1 version.)
Thanx,
Ugo
--
Justin Deoliveira
The Open Planning Project
http://topp.openplans.org
hi,
Justin Deoliveira wrote:
Ahh... seems that you are trying to parse wfs 1.1...
True.
Unfortunately the
geotools code only does wfs 1.0.
This is a shame. I *assumed* geotools (and geoserver) would accept 1.1, because I read on their (geotools) site, they had experimental support for GML 3.1 (That is, way too optimistic of me.)
BTW, I saved the WFS response to a file and tried to parse it with geotools; there were yet more incompatibilites, though the GML had the complexity of GML 2. But that's yet another matter, and for another mailing list 
Cheers,
Ugo
Ugo Taddei wrote:
Hi Justin,
Justin Deoliveira wrote:
Hi Ugo,
Currently you cant really cascade one GeoServer to another ... :(. I know its kind of silly. Here is the issue report for it.
http://jira.codehaus.org/browse/GEOS-4
As you can see from the issue number its been one of the longest standing GeoServer issues but one we just have not gotten around to fixing.
However if you are just looking for some code to connect to any wfs server using the geotools wfs client / datastore. This should help.
http://geotools.codehaus.org/How+to+use+a+WFS+DataStore
Yeah, I found and tried this out yesterday, but the geotools parser says
INFO: END: wfs:Operations
25.07.2007 15:19:47 org.geotools.xml.XMLSAXHandler endElement
WARNUNG: Too few children
25.07.2007 15:19:47 org.geotools.xml.XMLSAXHandler endElement
WARNUNG: Line 1 Col 5061
org.xml.sax.SAXException: Too few children
at org.geotools.xml.XMLSAXHandler.endElement(XMLSAXHandler.java:229)
at org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown Source)
(Sorry, folks, if this is off-topic here. Consider it an interoperability experiment 
If someone is willing to have a go with the current geotools code on this WFS
http://demo.deegree.org/deegree-wfs/services?REQUEST=GetCapabilities&version=1.1.0&service=WFS
please let me know. Meanwhile I'll tackle the geotools docs.
Anyway, thanks for the answer, Justin.
Cheers,
Ugo
-Justin
Ugo Taddei wrote:
Hello,
I'm about to try to cascade a WFS, but I don't really know where to start. I've browsed through the archives and docs and found obscure references to some WFSDataStoreFactory:GET_CAPABILITIES_URL and "same datastore that uDig uses". I'm using udig, but found no datastore. (Is this an xml file like geoserver uses?)
So, has anyone out there a snippet to spare, that shows me how to cascade a WFS? Or am I missing something? (I'm using geoserver 1.5.2.)
Has anyone tried to cascade a deegree wfs? (They currently use version 1.1.0. Is it possible to handle that with geoserver/geotools?)
(I've tried some code, but I'm currently bound to a geotools 2.1 version.)
Thanx,
Ugo
--
Ugo Taddei
Fraunhofer Institut Intelligente Analyse- und Informationssysteme (FhG IAIS)
http://www.iais.fraunhofer.de
Department Knowledge Discovery - IAIS.KD -
Working Group Spatial Decision Support
http://www.iais.fraunhofer.de/kd.html
phone (+49)2241-14-2184 fax (+49)2241-14-2072
Schloss Birlinghoven, D-53754 Sankt Augustin, Germany
------------------------------------------------------
Visit our thematic mapping tool CommonGIS: http://www.commongis.de
Ugo Taddei wrote:
hi,
Justin Deoliveira wrote:
Ahh... seems that you are trying to parse wfs 1.1...
True.
Unfortunately the
geotools code only does wfs 1.0.
This is a shame. I *assumed* geotools (and geoserver) would accept 1.1, because I read on their (geotools) site, they had experimental support for GML 3.1 (That is, way too optimistic of me.)
Well its coming... a project just recently started in which a wfs 1.1 datastore is in scope so stay tuned. We do gml 3.1 so parsing a getfeature request is doable... but none of the other operations from the wfs schema.
BTW, I saved the WFS response to a file and tried to parse it with geotools; there were yet more incompatibilites, though the GML had the complexity of GML 2. But that's yet another matter, and for another mailing list 
Cheers,
Ugo
Ugo Taddei wrote:
Hi Justin,
Justin Deoliveira wrote:
Hi Ugo,
Currently you cant really cascade one GeoServer to another ... :(. I know its kind of silly. Here is the issue report for it.
http://jira.codehaus.org/browse/GEOS-4
As you can see from the issue number its been one of the longest standing GeoServer issues but one we just have not gotten around to fixing.
However if you are just looking for some code to connect to any wfs server using the geotools wfs client / datastore. This should help.
http://geotools.codehaus.org/How+to+use+a+WFS+DataStore
Yeah, I found and tried this out yesterday, but the geotools parser says
INFO: END: wfs:Operations
25.07.2007 15:19:47 org.geotools.xml.XMLSAXHandler endElement
WARNUNG: Too few children
25.07.2007 15:19:47 org.geotools.xml.XMLSAXHandler endElement
WARNUNG: Line 1 Col 5061
org.xml.sax.SAXException: Too few children
at org.geotools.xml.XMLSAXHandler.endElement(XMLSAXHandler.java:229)
at org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown Source)
(Sorry, folks, if this is off-topic here. Consider it an interoperability experiment 
If someone is willing to have a go with the current geotools code on this WFS
http://demo.deegree.org/deegree-wfs/services?REQUEST=GetCapabilities&version=1.1.0&service=WFS
please let me know. Meanwhile I'll tackle the geotools docs.
Anyway, thanks for the answer, Justin.
Cheers,
Ugo
-Justin
Ugo Taddei wrote:
Hello,
I'm about to try to cascade a WFS, but I don't really know where to start. I've browsed through the archives and docs and found obscure references to some WFSDataStoreFactory:GET_CAPABILITIES_URL and "same datastore that uDig uses". I'm using udig, but found no datastore. (Is this an xml file like geoserver uses?)
So, has anyone out there a snippet to spare, that shows me how to cascade a WFS? Or am I missing something? (I'm using geoserver 1.5.2.)
Has anyone tried to cascade a deegree wfs? (They currently use version 1.1.0. Is it possible to handle that with geoserver/geotools?)
(I've tried some code, but I'm currently bound to a geotools 2.1 version.)
Thanx,
Ugo
--
Justin Deoliveira
The Open Planning Project
http://topp.openplans.org
Hi evrybody,
I've looked sld spec 1.0 and I see we can specify a Color Map to a raster
and my question is where we specify which dimension is concerned by the colormap?
Here there is ane example basic of sld using ColorMap but no dimension specify:
<?xml version="1.0" encoding="UTF-8"?>
<StyledLayerDescriptor xmlns="http://www.opengis.net/sld" xmlns:ogc="http://www.opengis.net/ogc" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.opengis.net/sld
http://schemas.opengis.net/sld/1.0.0/StyledLayerDescriptor.xsd" version="1.0.0">
<UserLayer>
<Name>raster_layer</Name>
<LayerFeatureConstraints>
<FeatureTypeConstraint/>
</LayerFeatureConstraints>
<UserStyle>
<Name>raster</Name>
<Title>A boring default style</Title>
<Abstract>A sample style for rasters</Abstract>
<FeatureTypeStyle>
<FeatureTypeName>Feature</FeatureTypeName>
<Rule>
<RasterSymbolizer>
<Opacity>1.0</Opacity>
<OverlapBehavior>
<AVERAGE/>
</OverlapBehavior>
<ColorMap>
<ColorMapEntry color="#000000" quantity="-500" label="nodata" opacity="0.0"/>
<ColorMapEntry color="#00ff00" quantity="-500" label="values"/>
<ColorMapEntry color="#00fa00" quantity="-417" label="values"/>
<ColorMapEntry color="#14f500" quantity="-333" label="values"/>
<ColorMapEntry color="#28f502" quantity="-250" label="values"/>
<ColorMapEntry color="#3cf505" quantity="-167" label="values"/>
<ColorMapEntry color="#50f50a" quantity="-83" label="values"/>
<ColorMapEntry color="#64f014" quantity="-1" label="values"/>
<ColorMapEntry color="#7deb32" quantity="0" label="values"/>
<ColorMapEntry color="#78c818" quantity="30" label="values"/>
<ColorMapEntry color="#38840c" quantity="105" label="values"/>
<ColorMapEntry color="#2c4b04" quantity="300" label="values"/>
<ColorMapEntry color="#ffff00" quantity="400" label="values"/>
<ColorMapEntry color="#dcdc00" quantity="700" label="values"/>
<ColorMapEntry color="#b47800" quantity="1200" label="values"/>
<ColorMapEntry color="#c85000" quantity="1400" label="values"/>
<ColorMapEntry color="#be4100" quantity="1600" label="values"/>
<ColorMapEntry color="#963000" quantity="2000" label="values"/>
<ColorMapEntry color="#3c0200" quantity="3000" label="values"/>
<ColorMapEntry color="#ffffff" quantity="5000" label="values"/>
<ColorMapEntry color="#ffffff" quantity="13000" label="values"/>
</ColorMap>
<ShadedRelief/>
</RasterSymbolizer>
</Rule>
</FeatureTypeStyle>
</UserStyle>
</UserLayer>
</StyledLayerDescriptor>
I hope you can help me.
Bye
Ugo Taddei ha scritto:
hi,
Justin Deoliveira wrote:
Ahh... seems that you are trying to parse wfs 1.1...
True.
Unfortunately the
geotools code only does wfs 1.0.
This is a shame. I *assumed* geotools (and geoserver) would accept 1.1, because I read on their (geotools) site, they had experimental support for GML 3.1 (That is, way too optimistic of me.)
Unfortunately to support GML3 we had to roll a new parser, with a different interface. The WFS datastore, used to cascade WFS, is using
the old GML parser, and there haven't been port tentatives, since
that would not only mean upgrading the parser, but also the protocol:
the WFS datastore can only deal with WFS 1.0.
Cheers
Andrea