18
Copyright © 2013 Open Geospatial Consortium.
Therefore, the encoding rule includes a statement in the application schema requirements that each feature should not have more than one geometry property. ShapeChange reports
a warning, if a feature type has multiple geometry properties.
This is not considered a limitation for the mobile web mapping use case that is a driver for the JSON work in OWS-9 mobile in the sense that the application is mobile and
can be run on a wide range of devices, not limited to smartphones and other mobile devices.
6.2.3.11 Types without geometry properties
Instances of these types will simply lack the geometry property.
6.2.3.12 Support for ISO 19100 types used in application schemas
As the encoding rule does not aim at defining JSON schemas for base types specified in the ISO 19100 series, the encoding rule will only support types from the ISO 19100
standards for which a JSON encoding exists as part of GeoServices JSON and GeoJSON, or where a conversion has been defined above.
The encoding rule includes a list of all supported ISO 19100 types in the application schema requirements. For properties with other types a warning is issued and the type is
mapped to object in the extended encoding rule or string in the simple encoding rule.
Other types include the types, for example, from ISO 19108 e.g. TM_Instant, ISO 19115 e.g. LI_Lineage, CI_ResponsibleParty, DQ_Result and ISO 19123 e.g.
CV_RectifiedGrid as well as those from ISO 19107 that go beyond the spatial geometries supported by ISO 19125 e.g. GM_Solid, TP_Edge.
6.3 Implementation and test application schema
6.3.1 Implementation in ShapeChange
Support for the simple and extended JSON Schema encoding rules has been added to ShapeChange
2
. Details can be found at http:shapechange.nettargetsjson
. NOTE The webpages are not yet complete. Content from this chapter will be transferred
once the Engineering Report is final.
2
OCL constraints on classifiers are currently not supported by the implementation.
Copyright © 2013 Open Geospatial Consortium.
19
6.3.2 The test application schema
A test application schema has been set up in Enterprise Architect that includes the different aspects discussed in the previous sub-clause.
The application schema is part of the ShapeChange distribution and unit tests. In the unit test, the schema documents are compared against the JSON Schema documents included
in the next sub-clauses.
NOTE This test application schema uses the stereotype voidable on properties to indicate that the property value may be nil including optional metadata for the nil value
see 6.2.3.3. ShapeChange supports this as a shorthand notation, the explicit NilUnion type also included in the application schema models this more explicitly.
Figure 3 - Test application schema
6.3.3 Simple GeoServices JSON encoding rule
The conversion results in the following schemas. FeatureType1:
{ schema:http:json-schema.orgdraft-03schema,
id:http:portele.deows9testFeatureType1.json,
