Desktop Settings Tabs
The Desktop Settings tab contains various controls used when outputting data directly from the desktop using the'Create a XML/GML file.' This tab includes options for setting a query box and compression to reduce the size of the data file.
Image of the Desktop Settings Tab in the GO Publisher Desktop
This section covers:
Output data file
The Output data file field on the Desktop Settings tab of GO Publisher Desktop lets the user specify output data file name and file path. The file path can be an absolute path or a relative path. (The path is relative to the project file).
Example of an absolute file path:
Example of a relative file path:
XML/GML data file
The Output data file field contains the path of the generated XML/GML data file.
If left blank, no data file will be generated.
Users can use thebutton to browse to an appropriate file location on their file system.
Validate output file
After generating output data, the results can be validated. This requires the schema files to be in the same directory as the data file (you can turn Copy Schemas on before publishing your data).
By pressing thebutton, a built-in validation engine validates the generated XML/GML file against the project schemas.
Results are displayed on the Execution View tab and in a pop out window.
Go to Output Folder
Thebutton opens the output folder (containing your published data) in a new window.
Query box is used to restrict the spatial extent of the GP Desktop output. Rather than publishing the entire database as a XML/GML file, the output can be restricted to a particular area of interest specified as co-ordinates.
For two-dimensional data, four space separated values are required. For three dimensions six values are needed to specify the lower left and upper right corner of the box..
Example: In the Query Box field enter X1 Y1 X2 Y2 for two dimensional data and X1 Y1 Z1 X2 Y2 Z2 for three dimensional data
where X1 Y1 (Z1) are co-ordinates for the lower left corner and X2 Y2 (Z2) are co-ordinates for the upper right corner for the area of interest.
Export a sample:
You can set a Query Box or set some SQL Filter parameters to avoid outputting all of the database data. You can also publish a sample size from the 'Create a XML/GML file' dialogue window. If none are used, the entire database will be published.
SQL Filter Parameters
When a parameter is used in the SQL Filters Tab, a value for the parameter can be specified in the Desktop Settings tab in the SQL Filter parameters field. This value can only be set in this way for publishing with GO Publisher Desktop. It is not possible to specify a value for SQL Filter parameters when using GO Publisher WFS. If you use a parameter in the SQL Filters tab for publishing with GO Publisher Workflow, you must set the value in the publishing job. For more information on using parameters with GO Publisher Workflow, see the Selection by parameter section of the Data Selection page.
For publishing with GO Publisher Desktop, if a SQL filter and SQL Filter parameters field are specified as follows:
SQL Filter (SQL Filters tab)
SQL Filter parameters value (Desktop settings tab)
The resulting SQL on execution would be:
The quotes added in the SQL Filter and in the SQL Filter parameters field will need to be specific for the SQL required for your database.
Setting the Logging Level
Set the logging level for the Execution View tab on the Preview and Execution View panel in the GO Publisher Desktop window. The following logging levels are available:
Only error messages are displayed.
Only warnings are displayed.
Standard information messages, warnings and error messages are displayed
Gives additional information for configuration and setup, e. g. database connection strings
SQL query strings are displayed and more detailed debugging information is displayed.
You can use Compression to publish output XML/GML files in compressed file format (Zip or GZip) to reduce the file size. By default, compression is set to None which results in uncompressed XML/GML files.
Currently supported compression formats are ZIP and GZIP.
Since the schema references are generated using relative path names, all schema files that the data depends on must be in the same directory structure as the schema file. If this option is enabled, all schema files will be copied to the directory where the schema is generated or the xml/gml data is stored. Subdirectories may be created as well.
Copy schemas is useful for when you want to validate the published data against the schema outside of GO Publisher, therefore having the schema files in the same location as the data is useful.
When you're ready to publish your data, see Publish and validate output files.