Download presentation
Presentation is loading. Please wait.
Published byLambert Magnus Hunter Modified over 6 years ago
1
making ogc's wfs specification mash-up friendly
Raj Singh, Open Geospatial Consortium Copyright 2006, Open Geospatial Consortium, Inc. (OGC)
2
Copyright 2006, Open Geospatial Consortium, Inc. (OGC)
OGC Today 320+ members worldwide – 31 countries & 5 continents Over 100 European members 16 approved Implementation Specifications fielded in hundreds of products 20+ candidate Implementation Specifications in work Significant interaction with ISO, W3C, IETF, OASIS and other standards organizations Copyright 2006, Open Geospatial Consortium, Inc. (OGC)
3
what’s with the mashup excitement?
unfounded “system integration” should be as sexy as “mashup” but there must be some truth to it simple things should be easy… more complex things can be harder… deployed in rich internet applications AJAX Flash Laszlo Copyright 2006, Open Geospatial Consortium, Inc. (OGC)
4
how OGC fits into the mix
WMS pretty nice way of getting maps in a mashup WFS hasn’t had the same level of uptake there’s a nice HTTP GET spec. buried in the document, and that got me thinking… Copyright 2006, Open Geospatial Consortium, Inc. (OGC)
5
Copyright 2006, Open Geospatial Consortium, Inc. (OGC)
WFS Basic — a proposal WFS Basic is a profile of Web Feature Service 1.1 intended to be easier to implement, particularly on non-geospatial platforms. The goal is to encourage mainstream Web systems, like standard PHP/MySQL setups, to participate in the geospatial Web. The primary constraints on WFS 1.1 are: There is no HTTP POST encoding of a WFS Basic request Only one Feature Type is allowed per service instance (therefore the TypeName parameter goes away) There is no <Filter> parameter supported Data may (optionally) be filtered using a regular expression All properties (i.e. columns) are always returned in a GetFeature request Copyright 2006, Open Geospatial Consortium, Inc. (OGC)
6
WFS Basic — basic data requests
&OUTPUTFORMAT=application/atom+xml &OUTPUTFORMAT=text/xml &BBOX=-71.00,42.00,-72.00,43.00&MINDATE= &MAXDATE= &OUTPUTFORMAT=text/xml Copyright 2006, Open Geospatial Consortium, Inc. (OGC)
7
but we also support filters!
regular expression queries on attributes we call them feature types well, how do you know what the attributes are? Copyright 2006, Open Geospatial Consortium, Inc. (OGC)
8
WFS Basic — DescribeFeatureType
Request: Response: <?xml version="1.0" encoding="UTF-8"?> <schema targetNamespace=" xmlns:myns=" xmlns:xsd=" xmlns=" xmlns:gml=" elementFormDefault="qualified" version="0.1"> <import namespace=" schemaLocation="../gml/3.1.1/base/gml.xsd"/> <!-- === define global elements === --> <element name="TreesA_1M" type="myns:TreesA_1M_Type" substitutionGroup="gml:_Feature"/> <!-- === define complex types (classes) === --> <complexType name="TreesA_1M_Type"> <complexContent> <extension base="gml:AbstractFeatureType"> <sequence> <element name="id" nillable="true" minOccurs="0" type="int"/> <element name="treeType" nillable="true" minOccurs="0" type="string"/> <element name="lon" type="float" nillable="false"/> <element name="lat" type="float" nillable="false"/> </sequence> </extension> </complexContent> </complexType> </schema> Copyright 2006, Open Geospatial Consortium, Inc. (OGC)
9
Copyright 2006, Open Geospatial Consortium, Inc. (OGC)
Discussion topics Uses for WFS Basic advanced use of RSS feeds simple geo-query of any database with lat/lon fields is it onerous to use XML Schema to describe the data? is regex the “right” choice for filtering content? should we keep the WFS requirement for GML output? Copyright 2006, Open Geospatial Consortium, Inc. (OGC)
10
join the discussion at: http://www.ogcnetwork.net/wfsbasic
Thank you Raj R. Singh join the discussion at: Copyright 2006, Open Geospatial Consortium, Inc. (OGC)
Similar presentations
© 2025 SlidePlayer.com. Inc.
All rights reserved.