Autodesk 15606-011408-9330 - MAPGUIDE R6.3 SITE LIC-UPG R6 Developer's Manual
  1. Manuals
  2. Brands
  3. Autodesk Manuals
  4. Software
  5. 15606-011408-9330 - MAPGUIDE R6.3 SITE LIC-UPG...
  6. Developer's manual
Autodesk 15606-011408-9330 - MAPGUIDE R6.3 SITE LIC-UPG R6 Developer's Manual

Autodesk 15606-011408-9330 - MAPGUIDE R6.3 SITE LIC-UPG R6 Developer's Manual

User manual
Hide thumbs Also See for 15606-011408-9330 - MAPGUIDE R6.3 SITE LIC-UPG R6:
Table of Contents

Advertisement

Quick Links

Download this manual See also: User Manual, Developer's Manual
Autodesk MapGuide® LiteView
Developer's Guide
April 2004

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the 15606-011408-9330 - MAPGUIDE R6.3 SITE LIC-UPG R6 and is the answer not in the manual?

Questions and answers

Related Manuals for Autodesk 15606-011408-9330 - MAPGUIDE R6.3 SITE LIC-UPG R6

Summary of Contents for Autodesk 15606-011408-9330 - MAPGUIDE R6.3 SITE LIC-UPG R6

  • Page 1 Autodesk MapGuide® LiteView Developer’s Guide April 2004...
  • Page 2 MATERIALS DESCRIBED HEREIN. Autodesk, Inc., reserves the right to revise and improve its products as it sees fit. This publication describes the state of this product at the time of its publication, and may not reflect the product at all times in the future.

  • Page 3: Table Of Contents

    What You Need to Know . Conventions . Copying Text from This Document . Overview of Autodesk MapGuide LiteView Features . Creating an Autodesk MapGuide LiteView Application. Understanding Application Architecture . Chapter 2 Understanding Requests Overview of Requests and Responses OpenGIS WMS 1.1.1 Compliance...
  • Page 4 GetFeatureInfo Request Parameters . Chapter 4 Configuring and Using the Sample Applications . . 49 The Sample Applications . The WMS Viewer Sample Application . Starting WMS Viewer Extending WMS Viewer . Configuring WMS Viewer . The ColdFusion Sample Application. ColdFusion Sample Application Files ColdFusion Sample Application Requirements ColdFusion Sample Application Client Platforms.

  • Page 5: Introduction

    In this chapter About this document ® dent viewing solution for Autodesk MapGuide maps. Overview of Autodesk Deployed as a Java servlet, Autodesk MapGuide LiteView MapGuide LiteView Creating an Autodesk serves interactive maps to most browsers—map users MapGuide LiteView application don’t have to download or install a viewer.

  • Page 6: About This Document

    Servlet technology Web-application architecture You don’t need to know the Autodesk MapGuide Viewer API because you do not call its methods to create an Autodesk MapGuide LiteView application. If you want to use the ColdFusion sample application that’s included with...

  • Page 7: Conventions

    This document assumes that you know how to create maps with Autodesk MapGuide Author and have read the Autodesk MapGuide User’s Guide and Autodesk MapGuide Help. Conventions The following syntax-diagram conventions are used in the of Web Map Service (WMS) requests:...

  • Page 8: Overview Of Autodesk Mapguide Liteview

    LiteView installation program prompts you for the most important Autodesk MapGuide LiteView configuration parameters, configures Apache Tomcat, and sets up Autodesk MapGuide LiteView so it is ready to use. The ColdFusion and WMS Viewer sample application files are copied Chapter 1 Introduction...
  • Page 9 SampleApp and WmsViewer subfolders in the Autodesk MapGuide LiteView installation folder on your hard drive. Fast map viewing—For first-time users or occasional users, it’s faster to use a Autodesk MapGuide LiteView application to download and display a raster image than it is to download and install a specialized viewer for image display.

  • Page 10: Creating An Autodesk Mapguide Liteview Application

    Creating an Autodesk MapGuide LiteView Application You can use the sample applications provided with Autodesk MapGuide Lite- View as starting points for creating your own Autodesk MapGuide LiteView applications. This section describes the general steps to create an Autodesk MapGuide LiteView application.

  • Page 11: Understanding Application Architecture

    Application LiteView Servlet Data Sources The Autodesk MapGuide LiteView servlet requires a Web application server that functions as a Java servlet container. To fulfill a request for a raster image. Autodesk MapGuide LiteView: Accepts an HTTP request for a raster image of a portion of an MWF file...
  • Page 12 Chapter 1 Introduction...

  • Page 13: Understanding Requests

    This chapter gives an overview of requests and responses In this chapter Overview of requests and ® using Autodesk MapGuide LiteView, and describes how responses to create requests for a map image and its feature informa- Creating a map request...

  • Page 14: Overview Of Requests And Responses

    068r3.pdf. As an active and Principal Member of the Open GIS Consortium (OGC) Autodesk works with OGC staff and members to create industry-stan- dard mapping specifications for the Web. The OGC Web site is at www.opengis.org.

  • Page 15: Formatting A Map Request

    Autodesk MapGuide Lite- View returns a PNG or JPEG image of the map in response. Formatting a map Request A map request consists of a URL, required parameters, variable and constant parameter values, and delimiters—ampersand (&), equal sign (=), and comma (,).

  • Page 16: Example Of A Minimal Map Request

    &WIDTH=<integer> &HEIGHT=<integer> &LAYERS=<filename.mwf> &FORMAT=<PNG|JPEG|JPG> Syntax of Optional Parameters The map request can include the following optional parameters, each having its own syntax: SELECT parameter syntax: &SELECT=<MWFName>/[MWFLayerName|MWFLayerGroupName], featureID (,<MWFName>/[MWFLayerName|MWFlayerGroupName], [featureID])* SRS parameter syntax: &SRS=ADSK:LL84 HLS parameter syntax &HLS=<n> SYMBOLS Parameter Syntax &SYMBOLS=<SymbolName>,<X>,<Y>,<Width>,<Height>, [(rotationDegrees)],[<labelString>] (,[<SymbolName>],<X>,<Y>,[<Width>],[<Height>],...

  • Page 17: Overview Of Map Request Parameters

    Examples of Optional Parameters The following example shows how to use the optional SELECT parameter to display US, CA, and UK features on the Countries layer of Sample_World.mwf: &SELECT=Sample_World.mwf/Countries,US,,CA,,UK Repeated delimiters Null values between comma delimiters imply the repeated use of Sample_World.mwf/Countries as the MWF and the layer that has CA and UK features.
  • Page 18 ID of the map feature that should be drawn in the selected state. The map-layer name is the MWF file name followed by a forward slash and the name of an Autodesk MapGuide layer within the MWF file. For more information, see “SELECT Parameter,”...

  • Page 19: Understanding Map Request Parameters

    13. LAYERS Parameter To locate an MWF file, Autodesk MapGuide LiteView concatenates the MWF name specified in the map request and the value of that MWFSearchPath parameter specified in config.ini. MWFSearchPath can contain multiple path names, each of which Autodesk MapGuide LiteView prefixes onto the LAYERS value and uses to search for the MWF file.
  • Page 20 Relative path names starting with .\ or ./ are not allowed Autodesk MapGuide Autodesk MapGuide LiteView assumes that MWF names are relative to the MWFSearchPath pathnames. Below are some exam- ples of valid MWF names, assuming that MyMap.mwf exists in the appro- priate folder: MyMap.mwf...
  • Page 21 ID of a map feature to be drawn in the selected state. You use the MWF file name followed by a forward slash (/) and the name of an Autodesk MapGuide layer or group within the MWF, followed by a comma and the feature ID, as follows: <MwfName>/<LayerNameInMWF>, <feature ID>...
  • Page 22 Selecting Multiple Features To select multiple features from a layer or a layer group, use the following syntax: SELECT=<MWFName>/[MWFLayerName|MWFLayerGroupName], featureID (,<MWFName>/[MWFLayerName|MWFlayerGroupName], [featureID])* Restricted Characters in the SELECT Parameter You must enclose the layer-name portion of the SELECT parameter (MWFName/MWFLayerName) in quotation marks if the name contains a space, a forward slash, or a comma.
  • Page 23 Select And Identify Implementation,” on page 75. SRS Parameter If the SRS parameter appears in the map request, Autodesk MapGuide Lite- View interprets coordinates as latitude/longitude. If SRS is absent, Autodesk MapGuide LiteView interprets the BBOX and SYMBOLS parameters as coor- dinates of the Map Coordinate System (MCS).
  • Page 24 Autodesk MapGuide LiteView Servlet Administrator’s Guide. You can use PPIY used to increase the vertical pixel resolution of the returned PNG or JPEG image. When you want to print a Autodesk MapGuide LiteView map in large scale, increase PPIY to prevent degradation of printed-image quality.
  • Page 25 The following table specifies the SYMBOLS parameter: Specification Description Name The name of an Autodesk MapGuide API symbol. If a symbol with the specified name is not found, the default symbol (a black square) is displayed. X, Y The insertion point, usually the center, defined by the symbol.

  • Page 26: Tips For Creating Map Requests

    Tips for Creating Map Requests Some important things to remember when creating a map request are: Maps must reside on the same local area network (LAN) as the Autodesk MapGuide LiteView servlet. You must set the MWFSearchPath parameter in the config.ini file to list the location of the MWF files.

  • Page 27: Example Of A Feature_Info Request

    & "&LAYERS=" & Form.mapName & "&BBOX=" & Form.bbox & "&X=" & Form.MAP.X & "&Y=" & Form.MAP.Y> Note The Form.server variable must include the web-server name and context path. For a default Autodesk MapGuide LiteView installation, Form.server is Creating a feature_info Request...

  • Page 28: Understanding Feature_Info Request Parameters

    Sample_World.mwf found in the search path specified by the A file name without any MWFSearchPath parameter in config.ini leading drive, folder, or (see Chapter 3, “Configuring Autodesk relative path informa- MapGuide LiteView,” in the Autodesk tion. MapGuide LiteView Servlet Administrator’s Guide).
  • Page 29 Feature_info Request Parameters (continued) Parameter Description Content Required. The pixel offset in the X direc- integer tion that identifies the feature of interest. The upper-left corner of map image is at 0,0. Increase the value of X to move the right.

  • Page 30: Interpreting Responses To A Feature_Info Request

    “feature_info Response DTDs” on page 28 contains a portions of gmlfeature.dtd and gmlgeometry.dtd. Both DTDs (document type definitions) have been simplified for use in this document. Autodesk MapGuide LiteView formats its responses according to these DTDs. The response to a feature_info request should be set to the MIME type text/xml.

  • Page 31: Sample Response

    Sample Response A Autodesk MapGuide LiteView sample response to a feature_info request is: <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE FeatureCollection SYSTEM "gmlfeature.dtd"> <FeatureCollection typeName="FeatureInfo"> <boundedBy> <Box srsName=""> <coordinates>0.0,0.0 4.0,4.0</coordinates> </Box> </boundedBy> <featureMember typeName="FeatureInfoMember"> <Feature typeName="USA.MWF/Streets" identifier="F045"> <name>Main Street</name> <property typeName="hyperlink" type="string"> http://www.mysite.com/scripts/info.cgi?fid=01 </property>...

  • Page 32: Feature_Info Response Dtds

    Response DTDs This section presents the DTDs that are used to format responses to feature_info requests. Use these DTDs to interpret XML responses returned by an Autodesk MapGuide LiteView application. gmlfeature.dtd <?xml version="1.0" encoding="UTF-8"?> <!--======================================================== --> <!-- G e o g r a p h y -->...
  • Page 33 gmlfeature.dtd (continued) <!ATTLIST FeatureCollection typeName CDATA #REQUIRED identifier CDATA #IMPLIED > <!-- A featureMember can be a Feature or a FeatureCollection. The name of the relationship between the containing FeatureCollection and contained Features is specified by the typeName attribute. --> <!ELEMENT featureMember ( Feature | FeatureCollection )>...
  • Page 34 gmlgeometry.dtd <!-- ======================================================== --> <!-- G e o g r a p h y --> <!-- M a r k u p --> <!-- L a n g u a g e --> <!-- --> <!-- ( G M L ) -->...
  • Page 35 gmlgeometry.dtd (continued) <!-- a Polygon is defined by an outer boundary and zero or more inner boundaries. These boundaries are themselves defined by LinerRings. --> <!ELEMENT Polygon (outerBoundaryIs, innerBoundaryIs*) > <!ATTLIST Polygon CDATA #IMPLIED srsName CDATA #IMPLIED > <!ELEMENT outerBoundaryIs (LinearRing) > <!ELEMENT innerBoundaryIs (LinearRing) >...
  • Page 36 gmlgeometry.dtd (continued) <!ELEMENT GeometryCollection (geometryMember+) > <!ATTLIST GeometryCollection CDATA #IMPLIED srsName CDATA #IMPLIED > <!ELEMENT geometryMember %GeometryClasses; > <!-- ======================================================== --> <!-- G E O M E T R Y P R O P E R T Y D e f i n i t i o n s -->...
  • Page 37 gmlgeometry.dtd (continued) <!-- the multiLineStringProperty has two descriptive names: multiCenterLineOf and multiEdgeOf. --> <!ELEMENT multiLineStringProperty (MultiLineString) > <!ELEMENT multiCenterLineOf (MultiLineString) > <!ELEMENT multiEdgeOf (MultiLineString) > <!-- the multiPolygonProperty has two descriptive names: multiCoverage and multiExtentOf. --> <!ELEMENT multiPolygonProperty (MultiPolygon) > <!ELEMENT multiCoverage (MultiPolygon) >...
  • Page 38 Chapter 2 Understanding Requests...

  • Page 39: Making Getcapabilities, Getmap, And Getfeatureinfo Requests

    Making GetCapabilities, GetMap, and GetFeatureInfo Requests ® This chapter describes Autodesk MapGuide LiteView’s In this chapter Overview support for OpenGIS Web Map Service (WMS) 1.1.1 GetCapabilities requests GetCapabilities, GetMap, and GetFeatureInfo operations. GetMap requests GetFeatureInfo requests WMS specifies a URL syntax for producing maps on the Web from georeferenced data.

  • Page 40: Overview

    MWF files and some from the administrator who registers MWF files by using WMS Admin- istrator. For the default Autodesk MapGuide LiteView installation, the following example shows the URL for a typical GetCapabilities request from a WMS- compliant Web client: http://localhost:8080/liteview6.5/servlet/MapGuideLiteView?

  • Page 41: Getcapabilities Request Parameters

    CDT (capabilities document template)—from which Autodesk MapGuide LiteView takes the value. For those values that come from an MWF file, the table identifies the value’s location in the MWF.
  • Page 42 Keyword Editable list of zero or more values. /KeywordList OnLineResource Editable value. Must be a valid URL. ContactInformation ContactPersonPrimary ContactPerson Editable value. ContactOrganization Editable value. /ContactPersonPrimary ContactPosition Editable value. ContactAddress AddressType Fixed value. Must be “postal”. Address Editable value. City Editable value.
  • Page 43 Fees Editable value. “none” is the default. AccessConstraints Editable value. “none” is the default. /Service Capability Request GetCapabilities Format Fixed value. Must be “application/ vnd.ogc.wms_xml”. DCPType Fixed DCPType element content declaring support for both HTTP GET and POST. For POST, the body must be the same URL- encoded key-value pairs that can appear in GET requests.
  • Page 44 Format Must be “application/vnd.ogc.gml.1”, “text/ xml”, or “text/html“. “application/vnd.ogc.gml.1” is appropriate only for viewers that support GML 1.0 parsing. MIME types XML and HTML are more widely supported by browsers (with HTML supported by all browsers). DCPType Fixed DCPType element content declaring support for both HTTP GET and POST.
  • Page 45 MWF is selected by default, but an administrator can override this parameter. For more information, see Chapter 3, “Configuring Autodesk MapGuide LiteView,” in the Autodesk MapGuide LiteView Servlet Administrator’s Guide. LatLonBoundingBox Latitude/longitude bounding box calculated from the map’s latitude/longitude center point and width/height, expressed in meters, specified in the MWF file.
  • Page 46 AuthorityURL — Not supported or included in the capabilities response. Identifier — Not supported or included in the capabilities response. MetadataURL Editable value. DataURL — Not supported or included in the capabilities response. FeatureListURL — Not supported or included in the capabilities response for top-level layers (MWF files, for example).
  • Page 47 — The spatial reference system of the individual layer. This value usually is inherited from the parent layer (MWF). The SRS parameter on a nested layer is supported only if the parent MWF can’t be published in EPSG:4326 but some of its vector layers can be published in EPSG:4326.

  • Page 48: Getmap Requests

    Style — Not supported or included in the capabilities response. ScaleHint Scale range at which the layer is visible (from the layer attributes). An administrator can mention any gaps in the scale range in the Abstract field of the MWF file metadata section.

  • Page 49: Getmap Request Parameters

    STYLES Must be empty. (STYLES also can be a comma-separated list with the same number of elements as the LAYERS list. Autodesk MapGuide LiteView will validate this list but not apply the styles.) Identifier for the spatial reference system. This value must match one of the values for the respective layer in the GetCapabilities response.
  • Page 50 Handling Transparency In Internet Explorer (but not Netscape Navigator), a transparent PNG image appears with a gray background color, so Autodesk MapGuide LiteView- generated transparent images can’t be overlaid unless the Web page loads the images by using an AlphaImageLoader filter. Therefore, on web pages that...

  • Page 51: Getfeatureinfo Requests

    GetFeatureInfo Requests The response to a GetFeatureInfo request is an XML or HTML document that provides clients with information about a feature in the map image returned by a GetMap request. GetFeatureInfo is supported for only those layers for which the queryable attribute is one (true). When a user sees the response (a map image) of a GetMap request and chooses (clicks) a point on that map, a WMS-compliant Web client sends a GetFeatureInfo request such as:...
  • Page 52 “text/html“. FEATURE_COUNT Optional parameter that is not supported in this release. GetFeatureInfo in Autodesk MapGuide LiteView always returns information about a single feature. X coordinate of the point of interest, measured in pixels from the top left corner of the image.

  • Page 53: Configuring And Using The Sample Applications

    This chapter explains how the sample applica- application The ColdFusion sample tions are designed, describes how to configure and run application Troubleshooting and other them, and describes how to use them as models for writ- resources ing your own Autodesk MapGuide LiteView applications.

  • Page 54: The Sample Applications

    Autodesk MapGuide LiteView comes with two sample applications: A simple browser-based client, called WMS Viewer, displays maps pub- lished by Autodesk MapGuide LiteView and by other servers that comply with the WMS 1.1.1 specification. This application supports WMS 1.1.1 GetCapabilities, GetMap, and GetFeatureInfo requests. For more informa- tion, see “The WMS Viewer Sample Application”...

  • Page 55: Extending Wms Viewer

    WMS Viewer Extending WMS Viewer You can use WMS Viewer as a model for writing your own Autodesk MapGuide LiteView applications. In general, it’s better to start with a copy of WMS Viewer and modify it to suit your needs. This section describes WMS Viewer’s architecture and gives an example of how to add a new feature to it.
  • Page 56 code processes a capabilities document and the result is used by the JSP code to create JavaScript data structures dynamically in the resulting HTML page. These data structures are used to populate the WMS Viewer page’s SRS list, layer list, image-format list, and other elements. The HTML and JavaScript code is available via your browser’s View Source command.
  • Page 57 var contactOrganization = '<%= svi != null? svi.getContactOrganization(): "" %>' var contactAddress = '<%= svi != null? svi.getContactAddress(): "" %>' var contactCity = '<%= svi != null? svi.getContactCity(): "" %>' var contactState = '<%= svi != null? svi.getContactState(): "" %>' var contactTelephone = '<%= svi != null? svi.getContactTelephone(): ""...
  • Page 58 function initContactInfo() //Get the information from the main Viewer script //by using the opener property of this pop-up window document.ContactInfo.name.value = window.opener.contactName document.ContactInfo.organization.value = window.opener.contactOrganization document.ContactInfo.address.value = window.opener.contactAddress document.ContactInfo.city.value = window.opener.contactCity document.ContactInfo.state.value = window.opener.contactState document.ContactInfo.telephone.value = window.opener.contactTelephone document.ContactInfo.email.value = window.opener.contactEmail </script>...

  • Page 59: Configuring Wms Viewer

    Configuring WMS Viewer The Autodesk MapGuide LiteView installation comes with Apache Tomcat 3.3.1a and, at your option, Autodesk MapGuide LiteView Setup will install and configure Tomcat automatically to run with the WMS Viewer. To set up Tomcat or a different application server manually, see Chapter 5, “Config- uring Application Servers,”...

  • Page 60: Coldfusion Sample Application Files

    Displaying online help Zooming The ColdFusion sample application demonstrates the minimal components and techniques that are needed to create an Autodesk MapGuide LiteView application. Although not implemented in this sample application, you can create an application that: Displays symbols on the image by using the SYMBOLS parameter in a map request to mark, say, points of interest or a route’s start and end points.

  • Page 61: Coldfusion Sample Application Requirements

    ColdFusion Sample Application Client Platforms User who want to view images created by an Autodesk MapGuide LiteView application must have a Web browser that can display PNG or JPEG images and supports the XML 1.0 specification. The browser also must support frames.

  • Page 62: Configuring The Coldfusion Sample Application

    Configure the ColdFusion Application Server to run ColdFusion under a user account Check that Autodesk MapGuide Server is running, and start it if necessary Configuring the Java Settings You set the JVM and CFX Jar paths for your installation of Java by using the ColdFusion Administrator.
  • Page 63 To configure Java settings 1 Launch ColdFusion Administrator. The ColdFusion Server Administrator screen is displayed. JVM and Java Settings The ColdFusion Sample Application...
  • Page 64 2 Under the Extensions category, click JVM and Java Settings. The JVM and Java Settings page is displayed. 3 Set the Java Virtual Machine path to the jvm.dll pathname. 4 Set the Class Path variable. Include the pathnames for the parseXml class and the Xalan and Xerces JAR files: <InstallFolder>\SampleApp\classes <InstallFolder>\SampleApp\classes\parseXml.class...
  • Page 65 Registering parseXml You use ColdFusion Administrator to register and manage ColdFusion custom tags. To use a CFX tag, you first must register it with ColdFusion, so ColdFusion can find the required DLL for processing the CFX tag in an appli- cation page.
  • Page 66 2 On line 9, replace the <your-server-name> tag with the name of the server on which Autodesk MapGuide LiteView is running, for example: <cfset server = "MYSERVER"> 3 Save and close map.cfm. 4 Open the following file in a text editor: <InstallFolder>\SampleApp\featureInfo.cfm...

  • Page 67: Starting The Coldfusion Sample Application

    6 Save and close featureInfo.cfm. Starting the ColdFusion Sample Application To start the ColdFusion sample application 1 Create a virtual directory named TestSample that maps to the <InstallFolder>\SampleApp folder on your hard drive. 2 Set the access properties of the virtual directory to permit all access modes except write access.

  • Page 68: Removing The Coldfusion Sample Application Files

    Using the ColdFusion Sample Application This section describes how to use the ColdFusion sample application as a model for your own Autodesk MapGuide LiteView applications. The HTTP response to a request to start the sample application is an HTML form. The form has three frames that contain JavaScript functions and ColdFusion application pages.
  • Page 69 Organizing the Image into Frames Organizing an Autodesk MapGuide LiteView application into frames, as the ColdFusion sample application demonstrates, simplifies development. The following diagram shows the frames contained by the ColdFusion sample application form. Frame 2: Toolbar Frame 1: Map image...
  • Page 70 The initial view that appears in the browser is from the Sample_World data set. Setting the Default Bounding Box Autodesk MapGuide LiteView uses the default bounding box specified in map.cfm to frame returned images: <cfset defaultbbox = "-150.0,0.0,-54.0,92.0"> At start up, and when the user unzooms, the ColdFusion sample application sets the mode and bounding box to default values as follows: <cfset mode = "identify">...
  • Page 71 Sets the bounding-box parameter of the map request. To build your own Autodesk MapGuide LiteView application, you can modify the ColdFusion templates that are part of the sample application. The templates encode the map and feature_info requests to Autodesk MapGuide LiteView.
  • Page 72 "&Y = " & Form.MAP.Y> Note The variable Form.server must include the web-server name and context path. For a default Autodesk MapGuide LiteView installation, Form.server is “localhost:8080/liteview6.5”. For general information about request syntax, see “Formatting a map Request” on page 11.
  • Page 73 Key Parameter Description Content MAP.Y Required. Y coordinate, expressed in pixels, of integer mouse click on the map image. MODE Required. Current mode of the application as string determined by the toolbar button that the user clicks. SELECT Optional. The key of the feature that you want string the user to perceive as being selected on the map.
  • Page 74 5 The ColdFusion sample application reads the image tag and sends the request to Autodesk MapGuide LiteView. 6 Autodesk MapGuide LiteView embeds a PNG or JPEG image in a Web page and returns the page. Examining the Map Form in map.cfm The ColdFusion sample application starts in Identify mode.
  • Page 75 The ColdFusion sample application sends a request to the page featureInfo.cfm in the Feature Info frame. As this page is parsed, the map is cleared, a feature_info request is sent to Autodesk MapGuide LiteView, and the XML result is captured.
  • Page 76 2 The user clicks the map. 3 The sample application sends a post request to featureInfo.cfm. 4 The sample application builds the feature_info request for Autodesk MapGuide LiteView. 5 The sample application sends the request. 6 The sample application captures and stores XML.
  • Page 77 Understanding the XML Parser The parseXml class uses Xerces and Xalan parsers to format the XML into a style sheet to return to the browser as HTML. The file parseXml.java contains the following class definition: parseXml.java class import com.allaire.cfx.*; import org.apache.xalan.*; import org.apache.xerces.*;...
  • Page 78 CFM. Then, it sets the mode parameter in the post request to the same value as the mode in the get request. The active mode determines how a new bounding box is calculated and used in the request to Autodesk MapGuide LiteView.
  • Page 79 JavaScript function showMapSelected(). 7 The function showMapSelected() sends a request to the ColdFusion map page. 8 The ColdFusion map page formulates the correct request to Autodesk MapGuide LiteView to show the selected feature on the map. Understanding the Recenter Implementation...
  • Page 80 1 When the user clicks the map, the sample application sends a request to Autodesk MapGuide LiteView with a new bounding box that is shifted, and decreased by the default zoom factor of two.

  • Page 81: Troubleshooting And Other Resources

    You can implement the Recenter function as described in “Designing the Recenter Feature,” on page 78 to solve this problem. Autodesk MapGuide LiteView can’t read the GML DTD while offline or behind a firewall. You can use the FeatureInfoDTD parameter in the config.ini file to point to the local GML DTD that Autodesk MapGuide LiteView Setup installs;...

  • Page 82: Designing The Recenter Feature

    Designing the Recenter Feature The width and height parameters in a map request specify a rectangle of pixels into which Autodesk MapGuide LiteView should draw the resulting map. The Recenter feature centers the bounding box within the image width and height. To recenter correctly, the ratio of the X to Y bounding box coor-...
  • Page 83 The ColdFusion sample application recenters the map correctly when the user invokes the Recenter function, because the ratio of the width to height matches the ratio of bounding-box coordinates: ratio of image width to height = 500 / 480 = 1.04 ratio of bounding box X to Y coordinates = ((–150) –...

  • Page 84: Accessing The Gml Dtd While Offline

    XML processor used by a sample application might not be able to access the DTD file (and trigger a timeout error). Note For information about FeatureInfoDTD, see Chapter 3, “Configuring Autodesk MapGuide LiteView,” in the Autodesk MapGuide LiteView Servlet Admin- istrator’s Guide. Chapter 4 Configuring and Using the Sample Applications...

  • Page 85: Srs-To-Wkt Mapping

    This file contains a mapping from ADSK:xxxx to well- known toolkit (WKT) strings. You can extract these WKT strings and use them in your Autodesk MapGuide LiteView client applications to display WKT strings instead of ADSK:xxxx codes. The following example entry from CsToEpsgMap.xml shows the mapping from ADSK:UTM-49S to a WKT.

  • Page 86: Where To Get More Information

    This site provides many examples of demo and actual customer applications that were developed with MapGuide. You also will find links to other resources, such as Autodesk MapGuide Viewer API Help, API examples, general product documentation, and discus- sion groups.
  • Page 87 In, Zoom Out, and Recenter controls are implemented as radio buttons. As a user, you select the Identify radio button, and then click a room on the map. Autodesk MapGuide LiteView returns feature information for the room, and the Facilities Management application displays it in the browser.
  • Page 88 To use the application builder 1 Download the template files from the Autodesk MapGuide Web site. 2 Map a virtual directory of your Web server to the template folder. 3 In a browser, navigate to the virtual directory and open start.cfm.
  • Page 89 4 Follow the onscreen instructions. The application builder modifies the file application.cfm and launches your custom application. The following screen shows the default application and a sample world map. Alternatively, you can customize the application by modifying the file application.cfm directly. To customize the application manually 1 Using an HTML editor, modify the application.cfm file.
  • Page 90 Chapter 4 Configuring and Using the Sample Applications...

  • Page 91: Index

    7 toolbar implementation 74 sample 50 toolbar, Help 76 template for creating 83 toolbar, Re-center 75 Autodesk Web site 82 toolbar, Select And Identify 75 toolbar, UnZoom 76 use of JavaScript 74 using 64 building an application 84 XML 73...
  • Page 92 example applications 82 application 74 JPEG 5 converting MWFs to 4 JVM (Java Virtual Machine) path, setting 58–60 feature information, positioning 23 feature_info requests ColdFusion sample application 70 ColdFusion sample application layers implementation 70 displaying data by 77 creating 22 for symbols 21 DTD for responses 28 formatting names as request parameters 18...
  • Page 93 parser, XML 73 in the LAYERS parameter 16 parseXml 61 in the SELECT parameter 18 registering 61–62 Perl, use with LiteView 2 platforms, client (ColdFusion sample application) sample applications PNG 5 ColdFusion 50 PNG (Portable Network Graphics) others available 82 converting MWFs to 4 WMS Viewer 50 positioning feature information 23...
  • Page 94 extending 51 XML 61, 72 getting help 51 XML parser 73 modifying 51 Java class 56 overview 50 starting 50 WMS. See Web Map Service (WMS) Zoom In implementation 76 Zoom Out implementation 76 Xalan and Xerces 2, 56, 72 90 | Index...

This manual is also suitable for:

Mapguide liteview

Table of Contents