gml7.1 KB

Kestrel Bay Territory — GML 3.2 Twin (latitude-first)

The territory as GML 3.2 with an EPSG URN srsName — which means latitude comes first, the opposite of GeoJSON. This is the single most common cause of features landing in the wrong hemisphere, so the file is built to catch it.

Geospatial Conversion testing Error handling

Preview — first 50 linesgml

<?xml version="1.0" encoding="UTF-8"?>
<kb:FeatureCollection xmlns:kb="https://examples.novusstreamsolutions.com/ns/kestrel-bay" xmlns:gml="http://www.opengis.net/gml/3.2" gml:id="fc-kestrel-bay">
  <gml:boundedBy>
    <gml:Envelope srsName="urn:ogc:def:crs:EPSG::4326">
      <gml:lowerCorner>46.95 -12.64</gml:lowerCorner>
      <gml:upperCorner>47.14 -12.36</gml:upperCorner>
    </gml:Envelope>
  </gml:boundedBy>
  <kb:featureMember>
    <kb:Feature gml:id="town-KB">
      <kb:name>Kestrel Bay</kb:name>
      <kb:code>KB</kb:code>
      <kb:kind>town</kb:kind>
      <kb:geometry>
        <gml:Point gml:id="g-town-KB" srsName="urn:ogc:def:crs:EPSG::4326"><gml:pos>47.064 -12.482</gml:pos></gml:Point>
      </kb:geometry>
    </kb:Feature>
  </kb:featureMember>
  <kb:featureMember>
    <kb:Feature gml:id="town-MR">
      <kb:name>Marram</kb:name>
      <kb:code>MR</kb:code>
      <kb:kind>town</kb:kind>
      <kb:geometry>
        <gml:Point gml:id="g-town-MR" srsName="urn:ogc:def:crs:EPSG::4326"><gml:pos>47.112 -12.3915</gml:pos></gml:Point>
      </kb:geometry>
    </kb:Feature>
  </kb:featureMember>
  <kb:featureMember>
    <kb:Feature gml:id="town-HW">
      <kb:name>Holloway</kb:name>
      <kb:code>HW</kb:code>
      <kb:kind>town</kb:kind>
      <kb:geometry>
        <gml:Point gml:id="g-town-HW" srsName="urn:ogc:def:crs:EPSG::4326"><gml:pos>47.018 -12.551</gml:pos></gml:Point>
      </kb:geometry>
    </kb:Feature>
  </kb:featureMember>
  <kb:featureMember>
    <kb:Feature gml:id="town-NP">
      <kb:name>Ninepin</kb:name>
      <kb:code>NP</kb:code>
      <kb:kind>town</kb:kind>
      <kb:geometry>
        <gml:Point gml:id="g-town-NP" srsName="urn:ogc:def:crs:EPSG::4326"><gml:pos>46.9725 -12.4402</gml:pos></gml:Point>
      </kb:geometry>
    </kb:Feature>
  </kb:featureMember>
  <kb:featureMember>
    <kb:Feature gml:id="town-QC">

… 166 lines total — download for the full file.

Specifications

Territory: Kestrel Bay County (invented)
Crs: WGS 84 (EPSG:4326), longitude/latitude order
Features: 14
Geometry Types: Point, MultiPoint, LineString, Polygon
Bbox: -12.64,46.95,-12.36,47.14
Encoding: UTF-8
Format: GML 3.2
Srs Name: urn:ogc:def:crs:EPSG::4326
Coordinate Order: latitude longitude (URN axis order)
Pos List: true
Line Endings: LF

Testing contract

Expected to pass

Scenario: Convert to GeoJSON honouring the URN axis order declared by srsName.
Expected result: Towns land near 47 N, 12.5 W; a reader that ignores axis order puts them near 12 N, 47 E instead.

What is a .gml file?

GML (Geography Markup Language) is the OGC's XML grammar for geographic features. Features carry typed properties and geometry elements such as gml:Point, gml:LineString, gml:Polygon, and their aggregates, with coordinates in gml:posList or gml:coordinates and the coordinate reference system named by an srsName attribute. It is the payload format of WFS services and the base of several national and INSPIRE data standards.

How to use this file

Use an example .gml file to test GML parsers and XML-based GIS pipelines, checking namespace handling, srsName resolution including the axis-order rules that differ between GML versions, and conversion to GeoJSON or shapefile.

How to use this file for testing

“Kestrel Bay Territory — GML 3.2 Twin (latitude-first)” is a deterministic Novus Examples fixture for Geospatial, Conversion testing, Error handling. GeoJSON, GPX, and KML files with points, lines, polygons, and tracks — for testing map tools, route parsers, and geo importers.

Documented properties for this file: UTF-8 · LF · GML 3.2. Compare results against paired or grouped companions on this page when present (clean↔damaged, searchable↔scanned, or format twins) so scores stay reproducible across runs.

Download the file once, keep the path stable in CI or local scripts, and treat the spec table as the contract: dimensions, seeds, field lists, and roles are intentional. Corrupt or invalid samples are labelled as such — expect parsers to fail loudly rather than silently accept them.

Geospatial fixtures publish one invented territory across formats, with the coordinate reference system and feature counts documented in specs. Convert or reproject and diff against the twin in the same group; edge-case geometries state exactly which assumption they are built to break.