86
Copyright © 2015 Open Geospatial Consortium.
}.setView[37.82053680, -122.36481177], 11; script
body html
Recommendation 29: Consider to include tileJSON in a non normative example for the WMTS Simple profile.
Target: WMS.SWG
10.3.2 JSON encoding for a TileMatrixSet
One of the elements that makes singular the WMTS is capability to completely describe a tile matrix set. Being able to provide the description of a tile matrix set as in JSON could
simplify the way WMTS clients deal with tile space descriptions. In particular it could be useful to have a json description of the fixed tile matrix sets provided by the new WMTS
simple profile.
{ tileMatrixSet: [ {
id: wmtss:WorldWebMercatorQuad, type: wmts:TileMatrixSet,
title: Google Maps Compatible for the World, CRSbbox:
{ crs: http:www.opengis.netdefcrsEPSG03857,
lowerCorner: POINT-20037508.3427892, - 20037508.3427892,
upperCorner: POINT20037508.3427892, 20037508.3427892
}, crs: http:www.opengis.netdefcrsEPSG03857,
wellKnownScaleSet: http:www.opengis.netdefwkssOGC1.0GoogleMapsCompatible,
tileMatrix: [ { id: wmtss:WorldWebMercatorQuad0,
type: wmts:TileMatrix, scaleDenominator: 559082264.0287178,
topLeftCorner: POINT-20037508.3427892, 20037508.3427892,
tileWidth: 256, tileHeight: 256,
matrixWidth: 1, matrixHeight: 1
},{ id: wmtss:WorldWebMercatorQuad1,
type: wmts:TileMatrix, scaleDenominator: 279541132.0143589,
Copyright © 2015 Open Geospatial Consortium.
87
topLeftCorner: POINT-20037508.3427892, 20037508.3427892,
tileWidth: 256, tileHeight: 256,
matrixWidth: 2, matrixHeight: 2
},{ id: wmtss:WorldWebMercatorQuad18,
type: wmts:TileMatrix, scaleDenominator: 2132.729583849784,
topLeftCorner: POINT-20037508.3427892, 20037508.3427892,
tileWidth: 256, tileHeight: 256,
matrixWidth: 262272, matrixHeight: 262272
} ] }]
}
Recommendation 30: Include in the WMTS Simple profile the JSON description of the WMTS simple two tile matrix sets.
Target: WMS.SWG
10.4 Serving GeoJSON with a Web Feature Service
Some people believe that WFS can only serve GML features but even if this is a common case nothing in the standard prevents from using other geospatial formats and encodings.
In particular, it is possible to server GeoJSON as a result of a WFS GetFeature request. In fact, GeoServer has been doing this for a quite a while. A more profound question is if it
possible to have a WFS without GML support. WFS is deeply related with the idea of the GML application schema and the definition of feature types. We already have mentioned
that GeoJSON does not provide this concept directly. Reintroducing this concept in GeoJSON as an extension is easy by means of adding to each GeoJSON feature a
property called “type”. This will allow a WFS server to group the features in feature types and to provide a list of available feature types in the GetCapabilities.
Recommendation 31: For a WFS serving GeoJSON, force the features to have a property that contains the feature type.
Target: WFS.SWG
A fundamental question could be the format that a DescribeFeatureType operation has to return when asking the characteristics of a feature type. Having to return a GML
encoding seems unnecessary. One possibility explored is to return a encoding neutral representation for describing feature types as described in ISO19110. Following the new
ISO19115-3 encoding for metadata a river object can be encoded like this:
gfc:FC_FeatureCatalogue gfc:featureType
gfc:FC_FeatureType gfc:typeNameriverTypegfc:typeName
