Document:
gml_subset.xsd

Draft (A preliminary unapproved sketch, outline, or version.)

Details

Submitted By Toby Considine on 2011-09-14 9:59 pm UTC

Publication Type

None at this time.

Group / Folder

OASIS Energy Interoperation TC / Contributions

Modified by

Not modified.

Copy

This document is not a copy.

Technical Contact

None at this time.

Download Count

400

Download Agreement

None at this time.

Description

Some have complained of the enormous size of GML. I have been meditiating on schema subsets. Clearly we do not need vegeation coverage, and annual rainfall, and architectural featurees to defien an affected area.

The attached is an attempt at defining a GML subset. Some notes:

It is considered good practice to include a bounding envelope in a feature collection--the idea being that any two points define the diagonal line of a rectangle, and if you are not in that rectangle, you don't need to compute all the icky stuff inside.

We may want to sub-class multi-curve, perhaps to create a circuit, perhaps with a margin of [50 ft] on either side that is also covered.

Point collections. Should each poitn have a radius? Is this another ssub-classing issue?