Autodesk MapGuide Enterprise
The fastest way to the web.
Simplicity, Speed, Freedom
Web mapping professionals demand faster innovation, more flexible development tools, and lower costs. From developing and designing web-based geographical information system (GIS) applications to accessing geospatial and engineering data, Autodesk MapGuide Enterprise helps team members make better decisions faster.

Select the Best Fit

apGuide Open Source delivers a lowM cost tool to help you quickly develop and deploy web mapping applications. You benefit from rapid release cycles and the innovation and collaboration of hundreds of software developers. MapGuide Open Source is available at mapguide.osgeo. org where the Open Source Geospatial Foundation (OSGeo) hosts this important and award-winning project. utodesk MapGuide Enterprise is the A proprietary version of MapGuide Open Source. Autodesk subjects the software to commercial-grade quality assurance testing and includes formal, dedicated support. Autodesk MapGuide Enterprise benefits from open-source innovation and adds the security and strength of Autodesks reputation for stable, highquality software. Autodesk MapGuide Software Autodesk MapGuide Enterprise helps to maximize the value of your spatial information while reducing the cost of circulating it to customers and colleagues alike. Based on MapGuide Open Source, an active open-source project, Autodesk MapGuide Enterprise builds on the rapid innovation of a large community of developers and offers formal quality assurance as well. Easy to Use Developers use Autodesk MapGuide Enterprise to publish geospatial data and applications internally, over the web, or with DWF format for offline and mobile portability. These applications give your team and your customers a faster and easier way to view and query crucial spatial information. Easy for End Users Autodesk MapGuide Enterprise delivers attractive, Web 2.0style interactive maps that give users an intuitive and helpful way to understand and analyze spatial information. The software supports Internet Explorer, Firefox, Safari, and Google Chrome web browsers and offers fast performance and a straightforward, easy-to-learn interface. Easy Installation and Deployment IT administrators appreciate the bundled Apache web server, PHP, and Java components that are included with Autodesk MapGuide Enterprise. The system automatically configures the web and application servers regardless of programming environment (.NET, PHP, Java) or web server (Internet Information Services or Apache). The Linux edition of Autodesk MapGuide Enterprise includes a precompiled RPM package manager to help you get up and running quickly. The single integrated installer for both the Windows and Linux versions makes the setup and deployment of Autodesk MapGuide Enterprise as easy as inserting a CD and clicking Install. Easy, Flexible Application Development Choose your development platform (.NET, PHP, Java) and enjoy a powerful API (application programming interface) consistent across all three platforms. The Feature Data Objects (FDO) API includes more than 150 classes exposing over 1,200 methods for publishing sophisticated GIS applications, helping developers avoid distracting data challenges. Simple Authoring and Web Design Autodesk MapGuide Studio software, the authoring tool built for Autodesk MapGuide Enterprise and MapGuide Open Source, helps you manage every aspect of preparing maps and geospatial data for your web application. Create your application with an intuitive interface, preview it as you build, upload data files, connect to databases, and stylize mapsall from the web. Flexible Web Layout Templates and application widgets accelerate the development of web mapping applications created with Autodesk MapGuide Enterprise. Since design and development tasks are separated, both nonspatial web designers and application developers can quickly build rich web mapping sites. With access to a growing number of widgets and web templates, designers can focus on site aesthetics without writing much code. And developers can freely focus on building powerful interactive AJAX (asynchronous JavaScript and XML) applications.

Flexible Layout Template design showing a map with capital cities, created using raster digital elevation map and vector data from SDF and Oracle.
Information Anytime, Anywhere
Autodesk MapGuide Enterprise delivers valuable spatial data and analysis over the web, while reducing distribution costs. Enjoy a more efficient workflow, as well as improved communication among internal teams, mobile field force, and customers.
Work Seamlessly with Multiple Data Types FDO Data Access Technology is at the heart of Autodesk Geospatial Solutions. A feature of Autodesk MapGuide Enterprise, AutoCAD Map 3D, and Autodesk Topobase software products, FDO Data Access Technology increases productivity by helping developers work on a variety of spatial and non-spatial databases and files without translation or data loss. Professionals can easily access, manage, edit, and share data stored in their GIS and make new map and design work ready for web publishing as soon as it is created. In partnership with OSGeo, Autodesk released FDO as an open source project to take advantage of developer support and the great variety of data types. As they can with MapGuide Open Source, developers all over the world can tap into this powerful technology and make their own contributions. In addition to Autodesks tested and certified FDO data providers, this active community has built many data providers that are used by organizations worldwide. Easily Move Data from Desktop to Web AutoCAD Map 3D is a leading engineering GIS platform, built to integrate GIS and computeraided design technology and help users create, edit, and manage geospatial data. AutoCAD Raster Design is a proven tool for raster data editing, manipulation, and analysis. When combined with Autodesk MapGuide Enterprise, these products deliver a powerful solution to move your organization smoothly from initial design and mapping to web deployment. You can also publish any work completed in AutoCAD Map 3D and AutoCAD Raster Design directly with Autodesk MapGuide Enterprise. Integrate, Analyze, Distribute With Autodesk MapGuide Enterprise, organizations can easily access data from AutoCAD, AutoCAD Map 3D, AutoCAD Raster Design, AutoCAD Civil 3D, and Autodesk Topobase software as well as from popular GIS sources such as Oracle Spatial,

Speed the design and development of your mapping sites with the new Flexible Layout Templates and drag-and-drop application widgets available with Autodesk MapGuide Studio.
Microsoft SQL Server, MySQL databases, ESRI geodatabase, ArcSDE, SHP, and popular raster formats. The software also supports the Open Geospatial Consortium (OGC) Web Mapping Services (WMS) and Web Feature Services (WFS). And because Autodesk MapGuide Enterprise supports multiple web browsers, organizations can use it to distribute data and spatial functionality to a large number of applications and people. Autodesk MapGuide Enterprise offers a mapping component to enterprise systems, such as customer relationship management and enterprise resource planning applications. Direct integration with
business applications from vendors such as Oracle and SAP gives developers more flexibility. The systems interact seamlessly, often without the need to generate and view a map. For example, the software validates location information automatically before committing data to the enterprise database, helping to streamline your organizations workflow and reduce operational costs. With its ability to integrate data from a variety of sources and business systems, Autodesk MapGuide Enterprise acts as a simple yet powerful infrastructure intelligence tool that delivers improved decision support to users across the organization.
We wanted a solution that would allow us to use the data in AutoCAD Map 3D and would be compatible with ESRI data. Autodesk MapGuide Enterprise was the ideal solution, since it responded to both criteria, and offered the possibility of sharing information over our intranet at an affordable price. In three hours, the map was online and accessible to everyone. With one server license and an unlimited number of users, the deployment was easy and implemented at minimal cost.
ean-Marie Prvost J Manager of Technical Research City of Moissy-Cramayel, France
Learn More or Purchase Access specialists worldwide who can provide product expertise, a deep understanding of your industry, and value that extends beyond your software purchase. To purchase Autodesk MapGuide Enterprise software, contact an Autodesk Premier Solutions Provider or Autodesk Authorized Reseller. Locate a reseller near you at www.autodesk.com/reseller. Autodesk Learning and Education From instructor-led or self-paced classes to online training or education resources, Autodesk offers learning solutions to fit your needs. Get expert guidance at an Autodesk Authorized Training Center (ATC) site, access learning tools online or at your local bookstore, and validate your experience with Autodesk certifications. Learn more at www.autodesk.com/learning. Autodesk Services and Support Accelerate return on investment and optimize productivity with innovative purchase methods, companion products, consulting services, and support from Autodesk and Autodesk authorized partners. Designed to get you up to speed and keep you ahead of the competition, these tools help you make the most of your software purchaseno matter what industry you are in. Learn more at www.autodesk.com/servicesandsupport. Autodesk Subscription Get the benefits of increased productivity, predictable budgeting, and simplified license management with Autodesk Subscription. You get any new upgrades of your Autodesk software and any incremental product enhancements, if these are released during your Subscription term. In addition, you get exclusive license terms available only to Subscription members. A range of community resources, including web support direct from Autodesk technical experts, self-paced training, and e-Learning, help extend your skills and make Autodesk Subscription the best way to optimize your investment. Learn more at www.autodesk.com/subscription.

*Free products are subject to the terms and conditions of the end-user license agreement that accompanies download of this software. Autodesk is committed to sustainability. This brochure is printed on 25 percent postconsumer waste recycled paper. Autodesk, AutoCAD, ATC, Autodesk MapGuide, Civil 3D, DWF, and Topobase are registered trademarks or trademarks of Autodesk, Inc., and/or its subsidiaries and/or affiliates in the USA and/or other countries. All other brand names, product names, or trademarks belong to their respective holders. Autodesk reserves the right to alter product offerings and specifications at any time without notice, and is not responsible for typographical or graphical errors that may appear in this document. 2009 Autodesk, Inc. All rights reserved. BR0A1-000000-MZ65.

Building Symbol Libraries with Autodesk MapGuide Enterprise
Robert Bray Autodesk, Inc.
While not exposed to end users through Autodesk MapGuide Studio 2008, Autodesk MapGuide Enterprise 2008 includes new cartographic capabilities that can be used to build custom symbol libraries. This class will provide an introduction to MapGuides new cartographic model, show how to create custom symbols and use them to symbolize points and lines, show how to create and use compound symbols, and how to create data driven symbols. The following examples illustrate some of the capabilities of MapGuides new cartographic model.
Custom line styles and patterns.
Repeating line labels and directional arrows. Ability to offset cartographic symbols from the feature geometry.
A more consistent and accurate way to define cased-line styles.
Use of symbols on lines for labeling, e.g. highway shields, utility symbols, etc.
An Overview of the New Cartographic Model
The new cartographic model is comprised of two new XML resource types Simple Symbol Definition and Compound Symbol Definition, as well as a related set of enhancements to the Layer Definition resource type as shown in the following diagram.
The Simple Symbol Definition resource type supports the definition of a symbol based on vector geometry, an image, or text. In addition a Simple Symbol Definition can specify how it is applied when used to stylize point, line, or area geometry. Finally the Parameter Definition specifies which values in the Simple Symbol Definition can be overridden by an FDO property value or expression during stylization. The Compound Symbol Definition resource type supports combining multiple Simple Symbols to create a composite symbol. This is useful for creating cased lines or adding a repeating graphic at pre-defined intervals along a line (e.g. highway shields or directional arrows). To support the new Symbol Definition resource types, the Layer Definition resource type has been modified to include a Composite Type Style element in addition to the Point Type Style, Line Type Style, and Area Type Style elements supported in the Autodesk MapGuide 2007 release. This new Composite Type Style element supports theming rules as before, but makes use of the new Symbol Definition resource types rather than a fixed set of stylization options per geometry type.
Simple and Compound Symbol Definition resources are standalone resource types that can be shared across any number of Layer Definitions. By creating folders of these resource types it is possible to create a symbol library that is usable across and organization.Whats the Deal, Why no UI in Autodesk MapGuide Studio 2008? The implementation of the new cartographic model in Autodesk MapGuide 2008 is incomplete. The status of the implementation in Autodesk MapGuide 2008 and MapGuide Open Source 1.2.0 is as follows: Symbol definition usage with point features is fully functional. Symbol definition usage for highway shields and other linear annotation is fully functional. Complex line joins may or may not provide expected results, depending on the symbol definition. Symbol definition usage for area features is not supported.
The upcoming release of MapGuide Open Source 2.0 will have more complete support for using symbol definitions for line and area features, finer grained control over rendering passes, support for angular offsets relative to the geometry, and a bunch of bug fixes. Future releases of Autodesk MapGuide Enterprise will most likely incorporate these changes as well.
Samples Discussed in this Class
In this class well create a small symbol library and use it to update the cartography in the City of Redding sample data set. In particular well create an international hospital symbol, create a less gaudy railroad line style, and create new styles for the highways and roads (incorporating highway shields where appropriate). The images below show the map before and after:

Horizontal Line Vertical Line
Draws a horizontal line from the current point to the x coordinate.
Draws a vertical line from the current endpoint to the specified y coordinate. Draws an elliptical arc from the current endpoint to the specified point (x,y). xr defines the x radius yr defines the y radius rx defines the x-axis rotation in degrees fArc identifies the arc segment to use, a value of 1 specifies to use the large sweep 180 degrees or greater, a value of 0 specifies to use the small sweep less than 180 degrees. fSweep defines direction, if fSweep is 1, the arc is drawn clockwise. If fSweep is 0, the arc is drawn counter-clockwise. Draws a straight line from the current endpoint to the first point of the current figure and then ends the figure.
For example to draw a 5 mm square box the Geometry element would be specified as follows:
Geometry: M -2.5,2.5 H 2.5 V -2.5 H -2.5 Z
Arcs are somewhat more complex and the following table should help explain the fSweep and fArc parameters. fArc = 0, fSweep = 0 fArc = 0, fSweep = 1

fArc = 1, fSweep = 0

fArc = 1, fSweep = 1
A concrete example of Arc usage will be shown a little later in this document. One final important point on the path element is how fills are handled. Which portions of a figure to fill is determined using an even-odd fill algorithm. This is illustrated as follows:
The other elements within the Path element are optional. Fill Color and Line Color are specified in ARGB hexadecimal format with an alpha transparency. Like all other values in symbol
definitions Line Weight is specified in millimeters. Line Weight Scalable is a boolean value which specifies whether the line weight scales with the symbol. Line Cap specifies the cap type to use at the ends of each segment in the path outline which must evaluate to one of: None, Round (default), Triangle, or Square. Line Join specifies the join type to use at each vertex in the path outline which must evaluate to one of: None, Bevel, Round (default), or Miter. Finally the Line Miter Limit specifies the limit to use when drawing miter joins. A miter join is trimmed if the ratio of the miter length to line weight is greater than the miter limit. If specified this must be greater than zero; the default value is 5.

Graphics as an Image

The structure of the Image element for defining graphics as an image is shown at right. The image itself may either be specified in the Content element as base 64 encoded PNG or in the Reference element as a link to the image stored as Resource Data within the resource database. The Size X and Size Y elements specify the size of the symbol in millimeters. Size Scalable is a boolean value which specifies whether the image sizes scale with the symbol. The Angle element specifies the rotation angle of the image in symbol space, in degrees. The Position X and Position Y elements specify the image center within symbol space in millimeters.

Graphics as Text

The structure of the Text element for defining graphics as text is shown at right. The Content element specifies the text to render for the symbol. The FontName, Bold, Italic, and Underlined elements specify the font and attributes used to render the text. The Height element specifies the text height in millimeters. The Height Scalable element is a boolean value which specifies whether the font height scales with the symbol. Angle specifies the rotation angle of the text in symbol space, in degrees. Position X and Position Yspecify the x and y coordinate of the text within symbol space in millimeters. The alignment values are relative to this coordinate. The Horizontal Alignment element specifies the horizontal alignment of the text box relative to its position, which must evaluate to one of: Left, Center (default), or Right. The Vertical Alignment element specifies the vertical alignment of the text box relative to its position, which must evaluate to one of: Bottom, Baseline, Halfline (default), Capline, or Top. The Justification element specifies the horizontal justification of individual lines of text in a multi-line text string, which must evaluate to one of: Left, Center, Right, Justified, or
FromAlignment (default). The Line Spacing element specifies the spacing between individual lines of text in a multi-line text string, as a multiple of the font height. The Text Color and Ghost Color elements specify the color of the text and ghosting effect in ARGB hexadecimal format. The Frame element provides options for drawing a rectangular frame around the text.

Point Usage

The Point Usage element provides control over how a symbol is used to symbolize point features. The structure of the Point Usage element is shown at right. The Angle Control element specifies how the symbol angle is defined, which must evaluate to one of: FromAngle (default) or FromGeometry. The Angle element specifies the symbol angle, in degrees and only applies if AngleControl evaluates to FromAngle. The Orgin Offset X and Y elements specifies the horizontal and vertical offset to apply to the symbol origin, in mm. This offset is applied before the symbol is scaled and rotated.
Defining the International Hospital Symbol
Now that the basics of symbol definition and point usage have been explained, lets look at how to define an international hospital sign to replace the basic cross used on the Hospital layer.
<?xml version="1.0" encoding="UTF-8"?> <SimpleSymbolDefinition xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="SymbolDefinition-1.0.0.xsd" version="1.0.0"> <Name>Hospital</Name> <Description>International Hospital Symbol</Description> <Graphics> <Path> <Geometry>M -2.5,2.5 H 2.5 V -2.5 H -2.5 Z</Geometry> <FillColor>FF0000FF</FillColor> <LineColor>FFFFFFFF</LineColor> <LineWeight>0.75</LineWeight> <LineWeightScalable>false</LineWeightScalable> </Path> <Path> <Geometry>M -1.0,1.25 V -1.25 Z M 1.0,1.25 V -1.25 Z M -1.0,0.0 H 1.0 Z</Geometry> <LineColor>FFFFFFFF</LineColor> <LineWeight>0.75</LineWeight> <LineWeightScalable>false</LineWeightScalable> </Path> </Graphics> <PointUsage/> <ParameterDefinition/> </SimpleSymbolDefinition>
This symbol uses two Geometry elements, one to draw the blue box with a white border and one to draw the H. The Point Usage element is empty since we do not want the symbol rotated and well use the center of the symbol as the insertion point.
Layer Definition Updates to Support Symbol Definitions
The structure of the new Composite Type Style element of Layer Definition is shown in the following diagram. In this document well ignore Composite Type Style and Composite Rule as they are functionally equivalent to the Point, Line, and Area equivalents in previous versions of Layer Definition.

However the Symbol Instance element is new and interesting. Symbol Instance specifies the symbol(s) to use for a particular Composite Rule and provides control over how each symbol is rendered. First note that a Symbol Definition can either be referenced by the Symbol Instance via the Resource Id element or the definition of the symbol may be embedded within the Symbol Instance itself. The Parameter Overrides element will be covered later in the document, so well skip over that for now. Scale X and Y specify the additional amount to scale the symbol horizontally and vertically. Insertion Offset X and Y applies only to point symbols and specifies the additional amount to offset the symbol horizontally, in mm in device units, after scaling and rotation have been applied. Size Context specifies whether the symbol sizes are with respect to the map or the user's display device. Draw Last is a boolean value which specifies whether the symbol is drawn as part of a final rendering pass (e.g. for labeling). Check Exclusion Region is a boolean value which specifies whether to render this symbol only if its graphical extent does not overlap the exclusion region. If the positioning algorithm generates multiple candidate symbol positions and this setting is true, then only the first non-overlapping candidate is rendered. Similarly Add To Exclusion Region is a boolean value which specifies whether the graphical extent for this symbol instance should be added to the exclusion region (if it is rendered). Finally the Positioning Algorithm element specifies the algorithm used to generate candidate positions for the symbol. If specified this must evaluate to one of: Default or EightSurrounding. Default means generate one position using the feature geometry (used for normal rendering). EightSurrounding means generate eight positions surrounding the feature geometry (used when labeling point features).
The Updated Hospital Layer
Now lets take a look at our updated Hospital Layer Definition.
<?xml version="1.0" encoding="UTF-8"?> <LayerDefinition xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="LayerDefinition-1.1.0.xsd" version="1.1.0"> <VectorLayerDefinition> <ResourceId>Library://MapsWithStyle/Redding/Basemap/Data/Hospital.FeatureSource</ResourceId> <FeatureName>Default:Hospital</FeatureName> <FeatureNameType>FeatureClass</FeatureNameType> <PropertyMapping> <Name>NAME</Name> <Value>NAME</Value> </PropertyMapping> <Geometry>Geometry</Geometry> <VectorScaleRange> <CompositeTypeStyle> <CompositeRule> <LegendLabel>Hospital</LegendLabel> <CompositeSymbolization> <SymbolInstance> <ResourceId>Library://MapsWithStyle/CartoSymbols/Hospital.SymbolDefinition</ResourceId> <ParameterOverrides> </ParameterOverrides> </SymbolInstance> </CompositeSymbolization> </CompositeRule> </CompositeTypeStyle> </VectorScaleRange> </VectorLayerDefinition> </LayerDefinition>

Note that because there is no theming there is a single Composite Rule and within that a single Composite Symbolization and Symbol Instance referring to the Hospital Symbol Definition.
Simple Symbols and Line Usage
The Line Usage element of Simple Symbol Definition provides control over how a symbol is used to symbolize line features. The structure of the Line Usage element is shown at right. Within the Line Usage element the Angle Control element specifies how the symbol angle is defined, which must evaluate to one of: FromAngle or FromGeometry (default). The Units Control element specifies whether the distribution parameters are interpreted as Absolute (default) values (in mm) or Parametric values. The Vertex Control element specifies the symbol behavior at vertices and must evaluate to one of: OverlapNone (default), OverlapDirect, OverlapNoWrap, or OverlapWrap. The Angle element only applies if AngleControl evaluates to FromAngle and it specifies the symbol angle in degrees. The Start Offset and End Offset element specifies where the symbol distribution begins, relative to the start or end of the feature. The Repeat element allows you to repeat the rendering of a symbol along the line and specifies the separation between them in millimeters. The Vertex Angle Limit, Vertex Join, Vertex Miter Limit, and Default Path elements are not yet supported in Autodesk MapGuide 2008 and hence will not be discussed here.

Defining Line Patterns

Dashed line patterns can be defined by specifying the geometry for a single complete sequence of dashing and then specifying a Repeat value within the Line Usage element. For example: Geometry: M 0,0 H 4 Z M 6,0 H 2 Z Repeat: 10 Results in:
Defining Lines with Decorations
Crossing decorations can be added to line patterns by simply adding the additional geometry and repeating the pattern as before. For example: Geometry: M -2.5,0.0 H 2.5 Z M 0.0,0.5 V -0.5 Z

Repeat: 5 Results in:

Defining the New Railroad Symbol
Now that the line usage has been explained, lets look at how to define the new railroad symbol to replace the MapGuides standard Railroad line style.
<?xml version="1.0" encoding="UTF-8"?> <SimpleSymbolDefinition version="1.0.0" xsi:noNamespaceSchemaLocation="SymbolDefinition1.0.0.xsd" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <Name>Railroad</Name> <Description> Railroad (single track)</Description> <Graphics> <Path> <Geometry> M -2.5,0.0 H 2.5 Z M 0.0,0.5 V -0.5 Z </Geometry> <LineColor>FF000000</LineColor> <LineWeight>0.125</LineWeight> </Path> </Graphics> <LineUsage> <VertexControl>'OverlapWrap'</VertexControl> <StartOffset>0</StartOffset> <Repeat>5.0</Repeat> </LineUsage> <ParameterDefinition/> </SimpleSymbolDefinition>

Compound Symbols

Compound symbols can be used to create cased lines and to add decorative symbols at the start, end, or at repeating intervals along a line. The structure of the Compound Symbol Definition element is shown below.
Note that Compound Symbol Definitions simply allow you to aggregate multiple Simple Symbol Definitions to create a more complex symbol. The simple symbols may either be referenced by a resource identifier or may be embedded within the Compound Symbol Definition. For simplicity well use that approach throughout the remainder of this document, however if you are defining libraries of reusable symbols you may wish to define them independently and use references. The Rendering Pass element gives the symbol author fine grained control over the draw order of each Simple Symbol within a Compound Symbol Definition.
Defining a Freeway with a Compound Symbol
To define a cased freeway symbol well use a Compound Symbol Definition with two Simple Symbol Definitions embedded within it as follows:
<?xml version="1.0" encoding="UTF-8"?> <CompoundSymbolDefinition xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="SymbolDefinition-1.0.0.xsd" version="1.0.0"> <Name>Freeway</Name> <SimpleSymbol> <SimpleSymbolDefinition> <Name>Outline</Name> <Graphics> <Path> <Geometry>M 0.0,0.0 H 5.0 Z</Geometry> <LineColor>FF000000</LineColor> <LineWeight>1.4</LineWeight> </Path> </Graphics> <LineUsage> <VertexControl>'OverlapWrap'</VertexControl> <StartOffset>0</StartOffset> <Repeat>5.0</Repeat> </LineUsage> <ParameterDefinition/> </SimpleSymbolDefinition> <RenderingPass>0</RenderingPass> </SimpleSymbol> <SimpleSymbol> <SimpleSymbolDefinition> <Name>Inner</Name> <Graphics> <Path> <Geometry>M 0.0,0.0 H 5.0 Z</Geometry> <LineColor>FFFF6464</LineColor> <LineWeight>0.8</LineWeight> </Path> </Graphics> <LineUsage> <VertexControl>'OverlapWrap'</VertexControl> <StartOffset>0</StartOffset> <Repeat>5.0</Repeat> </LineUsage> <ParameterDefinition/> </SimpleSymbolDefinition> <RenderingPass>1</RenderingPass> </SimpleSymbol> </CompoundSymbolDefinition>

Note the RenderingPass elements clearly establish that the Outline is drawn first followed by the Inner line. This ensures that the Freeway geometry intersections render correctly.

Adding a Shield Symbol

To add a shield to our Freeway definition well add another Simple Symbol Definition to our Freeway Composite Symbol Definition. The shield will be composed of both a Path element to define the outline and a Text element to contain the route number. The Arc geometry for the Shield is shown to the right. The Simple Symbol XML fragment that defines our Shield is as follows:
<SimpleSymbol> <SimpleSymbolDefinition> <Name>Shield</Name> <Graphics> <Path> <ResizeControl>'AdjustToResizeBox'</ResizeControl> <Geometry> M -2.0,2.5 A 1.0,0.0.0,2.5 A 1.0,0.2.0,2.5 A 3.0,3.0.0,-2.5 A 3.0,3.-2.0,2.5 Z </Geometry> <FillColor>FFFFFFFF</FillColor> <LineColor>FF0000FF</LineColor> <LineWeight>0.7</LineWeight> <LineWeightScalable>false</LineWeightScalable> </Path> <Text> <ResizeControl>'AddToResizeBox'</ResizeControl> <Content>'#'</Content> <FontName>'Arial'</FontName> <Height>4</Height> <PositionX>0</PositionX> <PositionY>0</PositionY> <HorizontalAlignment>'Center'</HorizontalAlignment> <VerticalAlignment>'Halfline'</VerticalAlignment> </Text> </Graphics> <ResizeBox> <SizeX>6</SizeX> <SizeY>6</SizeY> <PositionX>0</PositionX> <PositionY>0</PositionY> <GrowControl>'GrowInX'</GrowControl> </ResizeBox> <LineUsage> <AngleControl>'FromAngle'</AngleControl> <VertexControl>'OverlapNoWrap'</VertexControl> <Angle>0</Angle> <StartOffset>50</StartOffset> <EndOffset>50</EndOffset> <Repeat>200</Repeat> </LineUsage> <ParameterDefinition> </ParameterDefinition> </SimpleSymbolDefinition> <RenderingPass>2</RenderingPass> </SimpleSymbol>

Within this fragment there are several noteworthy things. First is the use of the Resize Box and Resize Control elements. The Shields Path element sets the Resize Control value to AdjustToResizeBox while the Text element sets the Resize Control value to AddToResizeBox. Finally the Grow Control element in the ResizeBox is set to GrowInX. This allows the symbol to grow in width to adapt to longer route numbers. Second note the Start Offset, End Offset, and Repeat elements. Collectively these indicate that the shields should start 50 millimeters from the beginning of the feature geometry, repeat every 200 millimeters, and the final shield should appear 50 millimeters from the end of the feature geometry.

Data Driven Symbols

Every aspect of a Simple Symbol Definition whether standalone or as part of a Compound Symbol Definition can be driven by FDO expressions. Symbol Definitions advertize this via the
Parameter Definition element. Symbol Instances in the Layer Definition supply values for parameters via the Parameter Overrides element. The structure of the Parameter Definition element is shown at right. Each Parameter Definition element can contain zero or more Parameter elements. Each Parameter element must supply an Identifier and a Default Value. Optionally values for Display Name, Description, and Data Type elements can be supplied. Again if you are building reusable symbol libraries this metadata can be extremely useful. The following XML fragment shows a completed Parameter Definition element:
<ParameterDefinition> <Parameter> <Identifier>MY_PARAMETER</Identifie r> <DefaultValue>0</DefaultValue> <DisplayName>Some Parameter</DisplayName> <Description>A useful description goes here.</Description> <DataType>Integer</DataType> </Parameter> </ParameterDefinition>
Once the parameter is defined, replace the constant element values in the Symbol Definition that you want to be specified dynamically with %MY_PARAMETER% (e.g. the parameter identifier delimited by percent signs). Going back to the Freeway symbol, we can now use a parameter to specify the route number displayed in the shield. The updated XML fragment defining the Shield symbol now looks as follows:
<SimpleSymbol> <SimpleSymbolDefinition> <Name>Shield</Name> <Graphics> <Path> <ResizeControl>'AdjustToResizeBox'</ResizeControl> <Geometry> M -2.0,2.5 A 1.0,0.0.0,2.5 A 1.0,0.2.0,2.5 A 3.0,3.0.0,-2.5 A 3.0,3.-2.0,2.5 Z </Geometry> <FillColor>FFFFFFFF</FillColor> <LineColor>FF0000FF</LineColor> <LineWeight>0.7</LineWeight> <LineWeightScalable>false</LineWeightScalable> </Path> <Text> <ResizeControl>'AddToResizeBox'</ResizeControl> <Content>%ROUTE_NUMBER%</Content> <FontName>'Arial'</FontName> <Height>4</Height> <PositionX>0</PositionX>

<PositionY>0</PositionY> <HorizontalAlignment>'Center'</HorizontalAlignment> <VerticalAlignment>'Halfline'</VerticalAlignment> </Text> </Graphics> <ResizeBox> <SizeX>6</SizeX> <SizeY>6</SizeY> <PositionX>0</PositionX> <PositionY>0</PositionY> <GrowControl>'GrowInX'</GrowControl> </ResizeBox> <LineUsage> <AngleControl>'FromAngle'</AngleControl> <VertexControl>'OverlapNoWrap'</VertexControl> <Angle>0</Angle> <StartOffset>50</StartOffset> <EndOffset>50</EndOffset> <Repeat>200</Repeat> </LineUsage> <ParameterDefinition> <Parameter> <Identifier>ROUTE_NUMBER</Identifier> <DefaultValue>0</DefaultValue> <DisplayName>Route Number</DisplayName> <Description>The interstate number.</Description> <DataType>Integer</DataType> </Parameter> </ParameterDefinition> </SimpleSymbolDefinition> <RenderingPass>2</RenderingPass> </SimpleSymbol>
Note the ROUTE_NUMBER parameter is defined and the Content element of the Text Geometry is now set to %ROUTE_NUMBER%. Now to set the value of the expression a Parameter Override needs to be specified within the Symbol Instance element in the Layer Definition. The structure of the Parameter Overrides element is shown at right. Note that the Parameter Overrides element contains zero or more Override element. Each Override element specifies an expression to use for a single parameter of a specific symbol. The following XML fragment shows a completed Parameter Overrides element:
<ParameterOverrides> <Override> <SymbolName>MySymbol</SymbolName> <ParameterIdentifier> MY_PARAMETER </ParameterIdentifier> <ParameterValue>MY_VALUE_FIELD"< /ParameterValue> </Override> </ParameterOverrides>
This fragment will replace the %MY_PARAMETER% values in a symbol called MySymbol with the value from the MY_VALUE_FIELD property of the layers FDO feature class. To

make full use of the Freeway Symbol Definition, the completed Roads Layer Definition looks as follows:
<?xml version="1.0" encoding="UTF-8"?> <LayerDefinition xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="LayerDefinition-1.1.0.xsd" version="1.1.0"> <VectorLayerDefinition> <ResourceId>Library://MapsWithStyle/Redding/Basemap/Roads.FeatureSource</ResourceId> <FeatureName>Default:Roads</FeatureName> <FeatureNameType>FeatureClass</FeatureNameType> <Geometry>Geometry</Geometry> <VectorScaleRange> <MaxScale>15000</MaxScale> <CompositeTypeStyle> <CompositeRule> <LegendLabel>'ART'</LegendLabel> <Filter>"ST_TYPE" = 'ART' OR "ST_TYPE" = 'COL'</Filter> <CompositeSymbolization> <SymbolInstance> <ResourceId>Library://MapsWithStyle/CartoSymbols/ArterialCollector.SymbolDefinition</ResourceId> <ParameterOverrides> </ParameterOverrides> </SymbolInstance> </CompositeSymbolization> </CompositeRule> <CompositeRule> <LegendLabel>'FWY'</LegendLabel> <Filter>"ST_TYPE" = 'FWY'</Filter> <CompositeSymbolization> <SymbolInstance> <ResourceId>Library://MapsWithStyle/CartoSymbols/Freeway.SymbolDefinition</ResourceId> <ParameterOverrides> <Override> <SymbolName>Shield</SymbolName> <ParameterIdentifier>ROUTE_NUMBER</ParameterIdentifier> <ParameterValue>"RTNUM"</ParameterValue> </Override> </ParameterOverrides> </SymbolInstance> </CompositeSymbolization> </CompositeRule> <CompositeRule> <LegendLabel>'HWY'</LegendLabel> <Filter>"ST_TYPE" = 'HWY'</Filter> <CompositeSymbolization> <SymbolInstance> <ResourceId>Library://MapsWithStyle/CartoSymbols/Highway.SymbolDefinition</ResourceId> <ParameterOverrides> <Override> <SymbolName>Shield</SymbolName> <ParameterIdentifier>ROUTE_NUMBER</ParameterIdentifier> <ParameterValue>"RTNUM"</ParameterValue> </Override> </ParameterOverrides> </SymbolInstance> </CompositeSymbolization> </CompositeRule> <CompositeRule> <LegendLabel></LegendLabel> <CompositeSymbolization> <SymbolInstance> <ResourceId>Library://MapsWithStyle/CartoSymbols/Street.SymbolDefinition</ResourceId> <ParameterOverrides> </ParameterOverrides> </SymbolInstance> </CompositeSymbolization> </CompositeRule> </CompositeTypeStyle> </VectorScaleRange> </VectorLayerDefinition>

</LayerDefinition>

The roads layer is themed based upon the ST_TYPE property of the Roads feature class. Note that both ST_TYPE = FWY and ST_TYPE = HWY use parameterized Symbol Definitions that display the route number.

Summary

This course has provided an overview of the new cartographic model in Autodesk MapGuide Enterprise 2008. While no support exists in the user interface of Autodesk MapGuide Studio 2008, you can use the techniques shown here to create a library of custom symbols and use those in your MapGuide applications.