Factores que intervienen

The following defines a property whose value is an XML fragment.

Chapter 10: Reference <Catalog name="foo"> ... <Property name="wms-toplayer-Title"> <Title>TopLayer</Title> </Property> ... </Catalog>

TheMultiCatalogElement

TheMultiCatalogelement defines a grouping of Express Server catalogs. It contains the fol- lowing editable attributes:

name

This is the name of the multicatalog. The name is used to specify the multicatalog in requests through the Web API. If the name begins with a "." character (period or dot), then this multicatalog is "hidden." That is, it does not appear in the list of cata- logs returned by Express Server. However, even though it is not included in that list, it is still loaded and available for queries when specified by name.

enabled

May be true or false, specifying whether the multicatalog is enabled or not. If set to false, then the multicatalog will not be loaded. The default value is true.

TheMultiCatalogelement can be treated in many ways like theCatalogelement. It can contain any of the same elements that theCatalogelement can contain (seeThe Catalog Ele- menton page 168) except theSpatialIndexelement. Specifically, these optional child ele- ments are:

LizardTech Express Server 9 User Manual l BufferMergeRule l Watermark l SizeConstraint l ThumbSpec l Property

The

SubCatalogElement

TheSubCatalogelement is a mandatory element of theMultiCatalogelement. That is, there must be at least one subcatalog in a multicatalog. If there is only one, the multicatalog essentially acts as an alias, and you will have two identical catalogs with different names. Like theCatalogelement and theMultiCatalogelement, theSubCatalogelement must have anameattribute and defaults toenabled. Thenameattribute of theSubCatalogele- ment must be the exact name of the catalog that you wish to incorporate as a subcatalog. Fur- thermore, the catalog being listed as a subcatalog:

l must be a valid catalog l must have a spatial index l must not be hidden

NOTE: Other multicatalogs can be included within the Subcatalog element.

Example: The

MultiCatalog

Element

<?xml version='1.0' encoding='utf-8' ?>  <CatalogConfig> <MultiCatalog name="multi"> <SubCatalog name="catalog1"/> <SubCatalog name="catalog2"/> <SubCatalog name="catalog3"/> </MultiCatalog> </CatalogConfig> - 180 -

Chapter 10: Reference

NOTE: When you create or update an overview for a catalog that is part of a mul- ticatalog, that multicatalog is unavailable until the overview is completed. The SubCatalog Element

The SubCatalog element is used as a subelement of the MultiCatalog element to specify the cata- logs that make up the multicatalog. The following specifies that the catalogs "Missouri_NIR" and "MODIS" make up the multicatalog "GroupOne".

<MultiCatalog name="GroupOne" enabled="true"> <SubCatalog>Missouri_NIR</SubCatalog>

<SubCatalog>MODIS</SubCatalog> </MultiCatalog>

NOTE: Multicatalogs can be included within multicatalogs. TheGlobalsElement

This section contains elements that apply to all catalogs. The elements that can be included are:

l Property

l Thumbspec l BufferMergeRule l Watermark l SizeConstraint

Example: The

Globals

Element

The following defines several properties and thumbspecs which apply to all catalogs.

<CatalogConfig>

...

LizardTech Express Server 9 User Manual

<ThumbSpec name="main" wid="80" hei="50" />

<ThumbSpec name="wide200" wid="200" hei="100" />

<Property name="infoURL" value="http://www.info.com" /> <Property name="infoName" value="John Brenner" />

</Globals>

...

</CatalogConfig>

The CatalogProps and ItemProps Elements

The CatalogProps and ItemProps elements are used as subelements of the Globals element to define the properties that will be returned in response to browse andcalcrgncommands when no props parameter is present in the URL. For example, the following will cause allbrowseand

calcrgnrequests to return the Name and Description catalog and item properties:

<Globals> ... <CatalogProps>Name,Description</CatalogProps> <ItemProps>Name,Description</ItemProps> ... </Globals>

The JPIPRoot Element

The JPIPRoot element is used as a subelement of the Globals element to alert Express Server to the presence of a JPIP server. It identifies the location of the JPIP server, making catalogued JPIP (streaming JPEG 2000) imagery visible to the browse command. Unless you choose not to install the JPIP server, this property is set by default upon installation.

Example of the JPIPRoot element:

Chapter 10: Reference

<JPIPRoot>http://STTL-DEV-GUPPY.seattle.mycompany.local:9013/</JPIP Root>

The ResponseHostPort Element

The ResponseHostPort element is used as a subelement of the Globals element to specify the host/port that Express Server will report in its XML responses. This can be useful when the Express Server is operating behind a firewall or a reverse proxy. For example, the following would return : <Globals> ... <ResponseHostPort>lizardtech.com:80</ResponseHostPort> ... </Globals>

would return the following response to a browse? request:

<ImageServer host="lizardtech.com:80" path="lizardtech/iserv" ...>

The WMSCapabilitiesMime Element

The WMSCapabilitiesMime element is used as a subelement of the Globals element to specify an alternate MIME type for the WMS capabilities document. This document is returned in Express Server'sGetCapabilitiesresponse. By default, the MIME type isapplic- ation/vnd.ogc.wms_xml. For example, the following will force Express Server to return its capabilities document with the MIME typetext/xml.

<Globals> ...

<WMSCababilitiesMime>text/xml</WMSCababilitiesMime> ...

LizardTech Express Server 9 User Manual

</Globals>