GO Loader Aviation 1.2 is here! Take a look at what's new.
Skip to end of metadata
Go to start of metadata

Introduction

This section tells you how to create a new project. You will need to have existing schema files for your data.

Mapping the database to a target schema is an involved process and will require use of functionality described later to help map from the database to target schema.

This section covers:

Create a New Project

Click the Create a New Project button () or go to File > New Project to access the GO Publisher Project Wizard.

In the Project Name field, choose a name for your project.

 

Select the Schema Repository

The Schema Repository is the ROOT location (highest directory level) at which the computer can derive referenced schema files. Schema files can be stored anywhere further down the file directory tree, even if this is not in the same physical folder. Absolute file paths are not needed using this repository method.

 

Click on the Select Repository button to open up the Open folder dialog window and navigate to the ROOT folder containing the relevant schemas. In the example below, the 'Schema' folder contains the schemas used in this GO Publisher project.

Select the folder and click Select Repository to select the folder.

 

If you are only working with web schemas, then simply point your Schema Repository to 'C:\'. This will enable the 'Add Local Schema' and 'Add Web Schema' buttons to allow you to add your web schemas.

The Schema Repository now displays the file location of the selected folder holding the schemas used within the GO Publisher project.

Adding Schemas

Once you have selected the Schema Repository folder, you can now add a schema to the project. This can be a locally saved schema file or web schema.

 

Tip!

Schemas will not load if they are invalid. Users will get the following message:

Add a Local Schema

Click Add a Local Schema button to open up an 'open file' dialog window.

Select a local schema file and click Open to add it to your project.

 

The local schema has now been added to the GO Publisher project and is displayed in a table shown in the image below. 

Namespace

The namespace helps to distinguish between different schemas and also clearly separate outs the ownership of the schemas. The namespace does not have to be an existing page on your website or the location of any actual files. Since website URL's are unique it is easy to use these as a namespace. They are not actually references to any websites. The namespace prefix is used within the XML file as shorthand for the namespace URL.

Location

This is the name of the schema document. If you hover over the Location field, the full directory path is displayed.

Status

The display will be either  (the schema exists at the specified location) or  (the schema doesn't exist at the specified location).

Add a Web Schema

Click Add a Web Schema button to open up a 'Load Schema from URL' dialog window.

Type in (or copy and paste) the URL of the web schema you wish to include in your project then click OK.

The web schema has now been added to the GO Publisher project and is displayed in a table shown in the image below. 

Include WFS 2.0 Schema

The introduction of the GML3.2.1 specification requires application specific Feature Collections to be defined by the user. However, the WFS 2.0 schema support the generic wfs:featurecollection and wfs:member which are pre-defined and ready to use, but a user could also define their own WFS feature collection if required.

 

Tip!

The Include WFS 2.0 Schema check box becomes enabled once a valid schema has been included in the project.

 

 

Information

Include WFS schemas checkbox includes the WFS 2.0 schemas. These are particularly useful if you are going to deploy a WFS (Web Feature Service) and would like to use wfs:FeatureCollection as the root element for your GML. 

Up until GML 3.1.1 the gml:FeatureCollection element was the default feature collection element. With GML 3.2.1 there is no default feature collection element defined. The application schemas that extend GML 3.2.1 now need to define a feature collection element. Including the WFS 2.0 schemas makes the wfs:FeatureCollection available to the user.

 

If you wish to include the WFS 2.0 schema tick the Include WFS 2.0 Schema check box, below, to automatically include the WFS 2.0 schema into your GO Publisher project:

Tip!

To remove the WFS 2.0 schema, untick the Include WFS 2.0 Schema check box.

The WFS 2.0 schema is now listed in the table and is included in the GO Publisher project.

Image displaying the WFS 2.0 Schema included in the project.

Remove a Schema

Highlight the schema you wish to remove, and the Remove Selected Schema button will become enabled.

Click Remove Selected Schema to remove the selected schema.

Click OK to confirm you wish to remove the schema.

The schema will be removed from the table display and from the GO Publisher project.

 

If you remove the last schema, a dialog window will appear to warn you that a project requires at least one schema is required.

Continue

Click  to continue...

Dive Deeper!

Navigate around the product documentation using the tree structure below or on the left hand side panel.

You can also search this documentation space using the search box below:


  • No labels