The Application page in Geocortex Essentials Manager has settings that apply to the viewer as a whole, such as the proxy page.
You can configure additional application-wide settings in the configuration files. In particular, you can configure datum transformations to apply whenever the viewer performs an operation that requires projection, such as geocoding, measurement, or buffering.
To open the Application page for an HTML5 viewer:
In beside the viewer.
In the side panel, click Application.
The Application page has the following settings:
Proxy URI: The URI to the proxy page, if you are using one. By default, the proxy URI is set to the ASP.NET proxy page that ships with the HTML5 Viewer, proxy.ashx?
. The default URI is terminated with a question mark because the viewer attaches parameters to the URI. The question mark is optional—the viewer will add the question mark if necessary. For instructions on setting up a proxy page, see Set Up a Proxy Page for the HTML5 Viewer.
If you do not want to use a proxy page, remove proxy.ashx?
from the Proxy URI box.
Allow Unsafe Content: If this checkbox is selected, content from a KML or GeoRSS layer that contains HTML markup is interpreted by the viewer. If you want the viewer to display the actual markup rather than what it represents, clear the checkbox. By default, unsafe content is not allowed.
If you have not added any KML or GeoRSS layers to your site, this setting has no effect.
Geometry Service URI: (deprecated) The URI of the geometry service to use for projection and other geometry operations. The HTML5 Viewer's Geolocation feature uses the geometry service specified here to project the user's location from latitude/longitude coordinates to map coordinates.
As of version 2.5, the Geometry Service URI property of the HTML5 Viewer has been deprecated. To configure a geometry service, edit the site instead. If the geometry service in the site is configured, it overrides the geometry service that is configured here. For more information, see Geometry Services.
See also...
Application-Wide Settings in the Configuration Files