Experiences in GML

Thanks & Questions Experiences in GML Ian Painter

Our experience with GML GO Loader – GML2.2, 3.1.1 and 3.2.1 From local government to central government, primarily in UK, Netherlands and Germany but deployment worldwide GO Publisher – GML2.2, 3.1.1, 3.2.1, XML and KML Large data providers ~ national mapping agencies, geological survey, metrological surveys, Air Traffic Management (primarily complex models in GML3.2.1) GML Viewer (GML 2.2, 3.1.1, 3.2.1) 50,000+ download over the last 9 1/2 years GML Training GML Fundamentals GML Hands On GML LinkedIn Group

What we support GML2.2, 3.1.1 and 3.2.1 Geometry: Envelopes, Point, LineString, LinearRing, Curve (single / multiple), Polygon, Surface (single / multiple patches), PolyhedralSurface, Triangulated Surface, Tin, Composite Curves, Rings, CompositeSurface, CompositeSolid, Multi*, Arc, ArcString, Circle, ArcByCenterPoint, Geodesic, OffsetCurve, Polygon Patch, Triangle, Rectangle Time, CRS, UoM, xlinks in local feature associations Some O&M No Spatial Topology, No Coverages

What we like … Simplicity of GML 2 The GML Wikipedia page The GeoRSS Documentation Simplicity

What we dislike Profiles as an answer to simplicity Mandatory ids on geometry Geometry by reference Remote resolving of xlink Clemens I need a GML profile Holey, adoption tangles. To the Enterprise Architect install

The early years of GML … GML 2.2 simple schemas, simple models Emphasis on adoption Plenty of complaints and moaning GIS vendors Plenty of adoption problem (transition from NTF) Made extensive use of GML2.2 TOID ~ gml:id 5 feature types, feature associations Simple geometry: points, linestrings and polygons From no GML to 450 million features in every UK wide dataset That’s billions of GML features loaded on a weekly basis: local government, utilities, fire and rescue, police you name them they loaded it … a success story for GML! It all started here ….

And then we started adding more … One more wafer thin geometry type Mr GML 3

The OGC collective … is made of : Specialists; Early adopters; Domain experts; Data modelers; Software architects, and Mathematicians Who are passionate about their domains of expertise But very few are end users

What if …. We hadn’t developed GML 3 and stuck with GML2? OGC TC’s would be a very different place OGC would have less membership but … Would GML be more widespread Would KML have extended from GML? Would there be more tool support? Would we have more people using GML?

My wish list Widespread adoption will only ever come from simplicity Follow the KML example, follow the Geoserver example It may not work for you but it works for 99% of other people There are companies like ourselves who cater for the specialists Design GML for the membership AND for the consumers No additions, just restructuring Make the entry level a single schema file: Features, point, lines and polygons With optional gml:ids One single page of documentation (just a wiki page) Let people pick and mix easily and work up to the fine dining experience of the full blown spec

Image Breakfast: Clothoid, Geodesic, Orientable Surfaces Lunch: Cones, Cylinders, Spheres Snacks: Shells, Polyhedrals, Geodesics Dinner: Quasi Uniform Knots BSpline, Cubic Spline Drinks: ArcByBulge OffsetCurve

Thanks & Questions Me: [email_address] Twitter: iapainter LinkedIn GML Group: http://www.linkedin.com/groups?home=&gid=1503247

Experiences in GML

More Related Content

Similar to Experiences in GML (20)

Recently uploaded (20)

Experiences in GML

Editor's Notes