#PAGE LAYERS IN MICROSOFT PUBLISHER FULL#
#PAGE LAYERS IN MICROSOFT PUBLISHER CODE#

Is a shapefile, as the PRJ files lack all the extra information provided by the EPSG database (it will for example break WFS 1.1 and 2.0 SRS declarations in GML output). This is particularly problematic if the source Using the native CRS in all otherrequests (with no reprojection in between, unless explicitly requested from client).

Keeping native means using the declared one in the capabilities documents, but then Keep native: this is a setting that should be used in very rare cases.

#PAGE LAYERS IN MICROSOFT PUBLISHER CODE#

OGC protocols need to advertiseĪ EPSG code for the layers, with this setting the declared one will be advertised, and reprojection from native will happen on the fly as needed (in case a thirdĬRS is requested, the reprojection will go directly from native to declared) Reproject from native: This setting should be used when the native data set has a CRS that is not matching any official EPSG.

#PAGE LAYERS IN MICROSOFT PUBLISHER FULL#

Native CRS, has a wrong one, or has one matching the EPSG code (in order to get full metadata in the CRS used by GeoServer). The declared code comes from the EPSG database and has a wealth of extra information in it, starting from a valid EPSG code, an area of validity, a link back in theĭatabase to find the best transformation steps to other coordinate reference systems should reprojection be required. This is the default option and normally the best course of action, Possible values are:įorce declared (default): the declared SRS is forced upon the data, overwriting the native one. SRS Handling-Determines how GeoServer should handle projection when the two SRSes differ. Clicking the projection link displays a description of the SRS.ĭeclared SRS-Specifies the coordinate system GeoServer publishes to clients

Native SRS-Specifies the coordinate system the layer is stored in. Finally, “URL” points to the actual metadata, while “Format” provides its mime type. The optional “About” entry can be used to point to the definition of the metadata standard, or any other side information about it. The “type” input provides a few example types, like FGDC or ISO19115:2003, but allows any other type to be declared. Metadata Links-Allows linking to external documents that describe the data layer. Keywords-List of short words associated with the layer to assist catalog searching Title-Human-readable description to briefly identify the layer to clients (required)

A non-advertised layer will be available in all data access requests (for example, WMS GetMap, WMS GetFeature) but won’t appear in any capabilities document or in the layer preview. (Note that for a new layer for an already-published resource, the name must be changed to avoid conflict.)Įnabled-A layer that is not enabled won’t be available to any kind of request, it will just show up in the configuration (and in REST config)Īdvertised-A layer is advertised by default. Name-Identifier used to reference the layer in WMS requests. The metadata information will appear in the capabilities documents which refer to the layer. These sections provide “data about the data,” specifically textual information that make the layer data easier to understand and work with. The beginning sections-Basic Resource Info, Keywords and Metadata link-are analogous to the Service Metadata section for WCS, WFS, and WMS.

Page layers in microsoft publisher