Prev | Next |
Generate GML Application Schema
An Application schema is typically created by geographic informaticians in an organization, industry or community of modelers. The collaboration facilities in Enterprise Architect allow you and your colleagues to develop the model collaboratively. Once you have created a model using the GML diagram and Diagram Toolbox, and have created the required elements and connectors, you can automatically generate a GML-compliant Application Schema directly from the model. This Application Schema describes the Feature Types that a community of users is interested in. For example, an application for the travel industry might define Features including churches, lookouts, coastlines, camping grounds, monuments, places of interest, museums, and road exit ramps. These Feature Types in turn reference the primitive object types defined in the GML standard.
After you have created a GML model you can generate GML Application Schema from the model Package.
Access
Ribbon |
Specialize > Technologies > GML > Generate GML Application Schema |
Context Menu |
Right-click on the Package | Specialize | GML | Generate GML Application Schema |
Generate GML Application Schema
Option |
Action |
See also |
---|---|---|
Source Package |
Displays the name of the selected «Application Schema» stereotyped Package. |
|
Directory |
Type in or browse for the directory into which the application schema file is to be generated. |
|
GML Version |
Click on the drop-down arrow and select the appropriate GML version for the GML Application Schema. Currently versions 3.3 and 3.2.1 are supported. |
|
XML Encoding |
Click on the drop-down arrow and select the XML encoding scheme to be used. |
|
Ignore Element and Property Visibility |
Click on this option to include all Classes, Attributes and Association End roles in the GML Application Schema, irrespective of their visibility (or Scope). Otherwise, only those with Public visibility will be considered for generation. |
Details Create and Manage Attributes Source and Target Role |
Stylesheet |
(Optional) Select an XSL stylesheet to post-process the Schema before saving it to file. Import the required stylesheet into the project through the 'Resources' tab of the Browser window before selecting it in this field. |
Browser - Resources |
Application Schema(s) |
Lists all the Application Schema Packages under the selected source Package. Click on a Package to display its details, as well as any of its child «Leaf» stereotyped Package details, in the Package Details panel. GML Application Schema will not be generated for any Package in the list that is unchecked. |
|
Package Details |
Against each of the child «Application Schema» and (optionally) «Leaf» stereotyped Packages (if any), enter a filename. To do this, double-click on the Package name in the list and, on the 'Package Details' dialog, review or complete these fields:
Note that:
|
|
Generate |
Click on this button to generate the GML Application Schema for each of the checked Packages in the 'Package Details' panel. |
|
View Schema |
Click on this button to display the generated GML Application Schema for the selected Package in the 'Package Details' panel. |
|
Close |
Click on this button to close the 'Generate GML Application Schema' dialog. |
|
Help |
Click on this button to display this Help topic. |
Notes
- GML is available in the Professional, Corporate, Unified and Ultimate Editions of Enterprise Architect
- A «CodeList» stereotyped Class with the tag 'asDictionary' set to True will be exported as a separate XML file to the directory specified in the 'Directory' field, with the filename CodeList_<classname>.xml (where <classname> is the name of the «CodeList» stereotyped Class)
- Using the configurable file GMLStereotypes.xml in the Sparx Systems > EA > Config > GML folder, you can specify aliases for the standard GML stereotypes; the GML Application Schema Generator will also consider these aliases during Schema generation
- Association Class is specific to GML 3.3; when generating GML 3.2.1 Application Schema, the Association and Class of an Association Class are treated as separate entities
Learn more
- The Open Geospatial Consortium GML Specification (Online Resource)