Hi,
the current output of WFS capabilities only lists the DescribeFeatureType format
that is mandated by the spec, that is, for example, "XMLSCHEMA" for
wfs 1.0 and "text/xml; subtype=gml/3.1.1" for WFS 1.1
I'm wondering, theoretically this is pluggable and in fact I can make a WFS 1.1
DTF asking for XMLSCHEMA, and it will work, e.g.:
http://localhost:8080/geoserver/ows?service=wfs&version=1.1.0&request=DescribeFeatureType&typeName=topp:states
(-> gml3 schema)
http://localhost:8080/geoserver/ows?service=wfs&version=1.1.0&request=DescribeFeatureType&typeName=topp:states&outputFormat=XMLSCHEMA
(-> gml2 schema)
Wondering, shall we make the capabilities document look into the
extension points and report
all possible outputs for DescribeFeatureType instead?
Cheers
Andrea
--
-------------------------------------------------------
Ing. Andrea Aime
GeoSolutions S.A.S.
Tech lead
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 962313
mob: +39 339 8844549
http://www.geo-solutions.it
http://geo-solutions.blogspot.com/
http://www.youtube.com/user/GeoSolutionsIT
http://www.linkedin.com/in/andreaaime
http://twitter.com/geowolf
-------------------------------------------------------
Pretty sure there are TODO’s sprinkled throughout the capabilies transformer for doing this… so yeah +1 for sure. You may want to check the cite compliance flag first though… i believe i may have tried that previously and the cite tests complained. I could be wrong though and getting confused with something else.
On Fri, Mar 16, 2012 at 5:29 AM, Andrea Aime <andrea.aime@anonymised.com> wrote:
Hi,
the current output of WFS capabilities only lists the DescribeFeatureType format
that is mandated by the spec, that is, for example, “XMLSCHEMA” for
wfs 1.0 and “text/xml; subtype=gml/3.1.1” for WFS 1.1
I’m wondering, theoretically this is pluggable and in fact I can make a WFS 1.1
DTF asking for XMLSCHEMA, and it will work, e.g.:
http://localhost:8080/geoserver/ows?service=wfs&version=1.1.0&request=DescribeFeatureType&typeName=topp:states
(-> gml3 schema)
http://localhost:8080/geoserver/ows?service=wfs&version=1.1.0&request=DescribeFeatureType&typeName=topp:states&outputFormat=XMLSCHEMA
(-> gml2 schema)
Wondering, shall we make the capabilities document look into the
extension points and report
all possible outputs for DescribeFeatureType instead?
Cheers
Andrea
–
Ing. Andrea Aime
GeoSolutions S.A.S.
Tech lead
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 962313
mob: +39 339 8844549
http://www.geo-solutions.it
http://geo-solutions.blogspot.com/
http://www.youtube.com/user/GeoSolutionsIT
http://www.linkedin.com/in/andreaaime
http://twitter.com/geowolf
This SF email is sponsosred by:
Try Windows Azure free for 90 days Click Here
http://p.sf.net/sfu/sfd2d-msazure
Geoserver-devel mailing list
Geoserver-devel@anonymised.comsts.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
–
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.
FWIW, I double CITE's WFS 1.1 tests check the advertised format is a
valid MIME Type, although the spec may state that's what has to be
advertised, and the literal "XMLSCHEMA" wouldn't be valid. Although
"text/xml; subtype=gml/2.1.2" would be.
2c/
Gabriel
On Fri, Mar 16, 2012 at 11:03 AM, Justin Deoliveira
<jdeolive@anonymised.com> wrote:
Pretty sure there are TODO's sprinkled throughout the capabilies transformer
for doing this... so yeah +1 for sure. You may want to check the cite
compliance flag first though... i believe i may have tried that previously
and the cite tests complained. I could be wrong though and getting confused
with something else.
On Fri, Mar 16, 2012 at 5:29 AM, Andrea Aime <andrea.aime@anonymised.com>
wrote:
Hi,
the current output of WFS capabilities only lists the DescribeFeatureType
format
that is mandated by the spec, that is, for example, "XMLSCHEMA" for
wfs 1.0 and "text/xml; subtype=gml/3.1.1" for WFS 1.1
I'm wondering, theoretically this is pluggable and in fact I can make a
WFS 1.1
DTF asking for XMLSCHEMA, and it will work, e.g.:
http://localhost:8080/geoserver/ows?service=wfs&version=1.1.0&request=DescribeFeatureType&typeName=topp:states
(-> gml3 schema)
http://localhost:8080/geoserver/ows?service=wfs&version=1.1.0&request=DescribeFeatureType&typeName=topp:states&outputFormat=XMLSCHEMA
(-> gml2 schema)
Wondering, shall we make the capabilities document look into the
extension points and report
all possible outputs for DescribeFeatureType instead?
Cheers
Andrea
--
-------------------------------------------------------
Ing. Andrea Aime
GeoSolutions S.A.S.
Tech lead
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 962313
mob: +39 339 8844549
http://www.geo-solutions.it
http://geo-solutions.blogspot.com/
http://www.youtube.com/user/GeoSolutionsIT
http://www.linkedin.com/in/andreaaime
http://twitter.com/geowolf
-------------------------------------------------------
------------------------------------------------------------------------------
This SF email is sponsosred by:
Try Windows Azure free for 90 days Click Here
http://p.sf.net/sfu/sfd2d-msazure
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
--
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.
------------------------------------------------------------------------------
This SF email is sponsosred by:
Try Windows Azure free for 90 days Click Here
http://p.sf.net/sfu/sfd2d-msazure
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
--
Gabriel Roldan
OpenGeo - http://opengeo.org
Expert service straight from the developers.