Getting Started: Autodesk Mapguide Enterprise 2010
Getting Started: Autodesk Mapguide Enterprise 2010
Getting Started
Certain materials included in this publication are reprinted with the permission of the copyright holder.
Trademarks
The following are registered trademarks or trademarks of Autodesk, Inc., in the USA and other countries: 3DEC (design/logo), 3December,
3December.com, 3ds Max, ADI, Alias, Alias (swirl design/logo), AliasStudio, Alias|Wavefront (design/logo), ATC, AUGI, AutoCAD, AutoCAD
Learning Assistance, AutoCAD LT, AutoCAD Simulator, AutoCAD SQL Extension, AutoCAD SQL Interface, Autodesk, Autodesk Envision, Autodesk
Insight, Autodesk Intent, Autodesk Inventor, Autodesk Map, Autodesk MapGuide, Autodesk Streamline, AutoLISP, AutoSnap, AutoSketch,
AutoTrack, Backdraft, Built with ObjectARX (logo), Burn, Buzzsaw, CAiCE, Can You Imagine, Character Studio, Cinestream, Civil 3D, Cleaner,
Cleaner Central, ClearScale, Colour Warper, Combustion, Communication Specification, Constructware, Content Explorer, Create>what's>Next>
(design/logo), Dancing Baby (image), DesignCenter, Design Doctor, Designer's Toolkit, DesignKids, DesignProf, DesignServer, DesignStudio,
Design|Studio (design/logo), Design Web Format, Discreet, DWF, DWG, DWG (logo), DWG Extreme, DWG TrueConvert, DWG TrueView, DXF,
Ecotect, Exposure, Extending the Design Team, Face Robot, FBX, Filmbox, Fire, Flame, Flint, FMDesktop, Freewheel, Frost, GDX Driver, Gmax,
Green Building Studio, Heads-up Design, Heidi, HumanIK, IDEA Server, i-drop, ImageModeler, iMOUT, Incinerator, Inferno, Inventor, Inventor
LT, Kaydara, Kaydara (design/logo), Kynapse, Kynogon, LandXplorer, LocationLogic, Lustre, Matchmover, Maya, Mechanical Desktop, Moonbox,
MotionBuilder, Movimento, Mudbox, NavisWorks, ObjectARX, ObjectDBX, Open Reality, Opticore, Opticore Opus, PolarSnap, PortfolioWall,
Powered with Autodesk Technology, Productstream, ProjectPoint, ProMaterials, RasterDWG, Reactor, RealDWG, Real-time Roto, REALVIZ,
Recognize, Render Queue, Retimer,Reveal, Revit, Showcase, ShowMotion, SketchBook, Smoke, Softimage, Softimage|XSI (design/logo),
SteeringWheels, Stitcher, Stone, StudioTools, Topobase, Toxik, TrustedDWG, ViewCube, Visual, Visual Construction, Visual Drainage, Visual
Landscape, Visual Survey, Visual Toolbox, Visual LISP, Voice Reality, Volo, Vtour, Wire, Wiretap, WiretapCentral, XSI, and XSI (design/logo).
The following are registered trademarks or trademarks of Autodesk Canada Co. in the USA and/or Canada and other countries:
Backburner,Multi-Master Editing, River, and Sparks.
The following are registered trademarks or trademarks of MoldflowCorp. in the USA and/or other countries: Moldflow, MPA, MPA
(design/logo),Moldflow Plastics Advisers, MPI, MPI (design/logo), Moldflow Plastics Insight,MPX, MPX (design/logo), Moldflow Plastics Xpert.
All other brand names, product names or trademarks belong to their respective holders.
Disclaimer
THIS PUBLICATION AND THE INFORMATION CONTAINED HEREIN IS MADE AVAILABLE BY AUTODESK, INC. "AS IS." AUTODESK, INC. DISCLAIMS
ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR
FITNESS FOR A PARTICULAR PURPOSE REGARDING THESE MATERIALS.
Published by:
Autodesk, Inc.
111 Mclnnis Parkway
San Rafael, CA 94903, USA
Contents
Chapter 1 Fundamentals . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
What’s New in Autodesk MapGuide Enterprise 2010? . . . . . . . . . . . 2
Information About Licensing and Upgrading . . . . . . . . . . . . . . . 3
PDF Tips . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
The Development Process . . . . . . . . . . . . . . . . . . . . . . . . . 5
Sites and Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Component Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Autodesk MapGuide Studio . . . . . . . . . . . . . . . . . . . . . . . . 13
MapGuide Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
MapGuide Web Extensions . . . . . . . . . . . . . . . . . . . . . . . . 17
MapGuide Viewer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Load and Configure . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Feature Sources and Drawing Sources . . . . . . . . . . . . . . . . . . . 23
Load Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Resource Repository . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Feature Joins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Learning MapGuide . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Chapter 3 Exercises . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
About the Exercises . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
iii
Create a Folder Structure . . . . . . . . . . . . . . . . . . . . . . . . . 42
Load Shapefiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Load SDF Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Load Geometry from a DWG File . . . . . . . . . . . . . . . . . . . . . 48
Load Raster Images . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Connect to an Access Database . . . . . . . . . . . . . . . . . . . . . . 52
Set the Style for a Polygon Layer . . . . . . . . . . . . . . . . . . . . . 54
Make Composite Lines . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Define Scale Ranges . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Create a New Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Add Layers to a Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Create a New Layer . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Theme from a Database Table . . . . . . . . . . . . . . . . . . . . . . . 66
Organize the Layers in a Map . . . . . . . . . . . . . . . . . . . . . . . 68
Edit Layers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Create a Symbol Library . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Use Symbols for Points . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Generate Labels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
Add Tooltips . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Set Up the Map Legend . . . . . . . . . . . . . . . . . . . . . . . . . . 80
View the Map in a Web Browser . . . . . . . . . . . . . . . . . . . . . 82
Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
iv | Contents
Fundamentals
1
MapGuide is a software platform for distributing spatial data over the Internet or on an
intranet. There are two versions of MapGuide: MapGuide Open Source, and Autodesk
MapGuide Enterprise. The concepts in this first chapter of the Getting Started Guide will help
you understand and use either version. The second chapter summarizes the development
process in the form of a flow diagram. The final chapter provides examples of authoring tasks,
which will give you some initial hands-on experience, using the sample data included on the
Autodesk MapGuide Enterprise product CD.
1
What’s New in Autodesk MapGuide Enterprise
2010?
Welcome to Autodesk MapGuide Enterprise 2010. The following list describes
what's new in this release.
Performance Improvements
Autodesk MapGuide Enterprise 2010 includes a number of performance
enhancements:
■ Improved connection time for Oracle feature sources and faster authoring
in Studio
Raster Re-projection
Autodesk MapGuide Enterprise 2010 now includes an efficient raster
re-projection algorithm that is based on tessellating an image into smaller
triangles and re-projecting the triangles.
2 | Chapter 1 Fundamentals
Information About Licensing and Upgrading
Licensing
For information about licensing MapGuide Enterprise, refer to the Network
Licensing Guide. The Network Licensing Guideis available from the Media Browser
of your Autodesk MapGuide Enterprise 2010 installation CD.
Upgrading
For information about upgrading from the previous version of MapGuide
Enterprise, refer to one of the following documents:
The document appropriate for your operating system is available from the
Media Browser of your Autodesk MapGuide Enterprise 2010 installation CD.
PDF Tips
NOTE This book is in PDF format, which is optimized for viewing on a
high-resolution monitor (preferably set to 1280x1024), and for printing. To read
this guide online, follow these suggestions for the best viewing experience:
■ Close the bookmarks tab (you can easily open it when you need it).
■ Click the Fit Page icon (this gives you two full pages on most monitors).
■ Use the Dynamic Zoom tool to adjust the view so that you can see as much
of the double-page spread as possible without straining your eyes to read
the text.
■ Use the Hand tool to move the page left and right.
■ Use the Page Up and Page Down keys to go forward and back.
Bookmarks tab
4 | Chapter 1 Fundamentals
The Development Process
The diagram on the facing page shows the process of developing a Web-based
application using MapGuide. In the diagram, the rectangles represent tasks,
the oval shapes represent entities that are created by the tasks or used by them,
and the arrows indicate the flow of data. You can break down the development
process into five phases (you may also have a Planning and Preparation phase,
not included in this diagram):
Place the map on the Internet or intranet using layouts for generating
4 web pages and for plotting.
Develop the web application, using the MapGuide APIs to add func-
5 tionality.
See also Chapter 2, “Flow Diagram” for a more detailed diagram of these
phases.
Extend
2
Tasks
Build layers
Resources managed
by the site server
3
Make map
Application elements
(PHP/ASP/JSP) and
HTML
4
Place on internet
Web application
Test
6 | Chapter 1 Fundamentals
Sites and Servers
The collection of servers that process requests in MapGuide is called a site.
You can divide the processing load between two or more servers within the
site. Each site shares a single resource repository among its servers. The resource
repository stores the resources that map authors use to create maps, for example,
pre-defined layers for features such as roads or land parcels.
In the diagram on the facing page, the site contains two servers, one of which
is designated as the site server. The site server contains the resource repository.
It also connects to any database server or servers.
MapGuide Server provides seven services: Site, Resource, Drawing, Feature,
Mapping, Rendering, and Tile. If you are using a single server, that server
performs all of these services. In any case, the site server always runs the first
two services, because they handle data access and manage the resources for
the site. However, if you have two or more servers, you can split off the other
services and allocate them to another server or servers. For example, the
Mapping and Rendering services are the most processor-intensive operations
and can benefit from having a dedicated server to handle them.
■ The Rendering service creates the final map image for the AJAX viewer
from input provided by the Mapping service.
Site
8 | Chapter 1 Fundamentals
Installation
MapGuide consists of four separate components, which should be installed
in the following order:
■ MapGuide Server
■ MapGuide Viewer
You can access detailed information about hardware and software requirements
for installation from the Installation HTML page of the CD browser that
appears when you insert the Autodesk MapGuide Enterprise product CD. Here
is a short summary:
■ MapGuide Server and MapGuide Web Extensions run on both Linux and
Windows.
■ MapGuide Web Extensions run on IIS and Apache (Windows) and Apache
(Windows and Linux).
■ The MapGuide Viewers work with Microsoft Internet Explorer and Firefox
browsers.
The diagram on the facing page shows where to install the different
components of the software.
Installation | 9
Download
AJAX Viewer
Download
Autodesk DWF Vewer Install Studio
10 | Chapter 1 Fundamentals
Component Overview
The diagram on the facing page provides a high-level overview of how the
four components work together after installation. Each component is described
in more detail in the next four topics of this chapter.
Autodesk MapGuide Studio and the MapGuide Viewer are client applications
of MapGuide Server. Requests coming from these clients, and from the other
client applications that you develop using the API, go to the Web Extensions
by means of HTTP protocol. The WebAgent component of the Web Extensions
processes the requests and forwards them on to MapGuide Server. When you
start Autodesk MapGuide Studio, you enter the name or the IP address of the
web server that is hosting the Web Extensions. For example,
http://144.111.19.94/mapguide2010
When it receives a request, MapGuide Server accesses the resources stored in
the resource repository, builds and renders the map in DWF format or as a
static image for the AJAX viewer, and returns it to the Web Extensions, which
in turn send it back to the client.
Autodesk MapGuide Studio has the MapGuide Viewer built into it. The Viewer
displays the rendered data onscreen and manages the layers and other
properties of the data returned from the server.
Component Overview | 11
Viewer
Viewer
Viewers Studio
Web Extensions
Services to build
and render map
12 | Chapter 1 Fundamentals
Autodesk MapGuide Studio
Autodesk MapGuide Studio is an authoring environment that handles all
aspects of collecting and preparing geospatial data for distribution on the
Internet (except custom coding). When you use Autodesk MapGuide Studio,
you will generally follow these steps:
1 Create resources from your source data, either by loading file-based data
or by connecting directly to external databases.
After you have a web layout, you can customize the appearance and functions
of the web application by adding your own programming code. The final step
is to publish the completed web application to the Internet or intranet for
viewing and interaction.
The Autodesk MapGuide Studio interface is divided into three parts:
■ The Editor
When you open Autodesk MapGuide Studio and connect to your site server
(via the WebAgent), the Site Explorer shows you the resources stored in the
resource repository, as shown in the upper image on the facing page.
Double-clicking any resource in the Site Explorer opens the appropriate editor
for that resource. If the resource is a layer or a map, the Viewer also opens and
displays a preview of the data.
Preview of map
Preview of layer
Layer Editor with theme
Two views of Autodesk MapGuide Studio
14 | Chapter 1 Fundamentals
MapGuide Server
The MapGuide Server component hosts the MapGuide services and responds
to requests from client applications through TCP/IP protocol.
You can manage your site and its servers with the Site Administrator program.
This program is installed with the Web Extensions. It has a Web-based interface
that you can access from any web browser. To start the program, you open a
browser and enter: http://servername/mapguide/mapadmin/login.php, using
the name or IP address of the server on which you installed the Web
Extensions.
When you log onto the Site Administrator program, you can:
■ Manage your site. For example, you can add and remove servers, or take
them offline for maintenance.
■ Assign services to the servers. For example, one server can process mapping
requests while another handles rendering tasks.
■ Define users and groups and assign roles and access permissions to them.
The illustration on the facing page shows two views of the Site Administrator
program. The upper image shows the home page, which lists the servers in
the site. The lower image shows a typical list of users and the groups that they
belong to.
MapGuide Server | 15
List of servers in the site
Manage Servers selected
16 | Chapter 1 Fundamentals
MapGuide Web Extensions
The MapGuide Web Extensions are internal components which can be accessed
through the Web Extensions API. (There is also a forms-based interface which
you can access: http://servername/mapguide/mapagent/index.html). The Web
Extensions expose the services offered by the MapGuide Server to client
applications over the Internet or an intranet using HTTP protocol. The diagram
on the facing page shows the main sub-components of the MapGuide Web
Extensions.
The WebAgent processes requests coming from clients and passes them to the
MapGuide Server. Two of the clients are Autodesk MapGuide Studio and the
MapGuide Viewer. The WebAgent implements the MapGuide services HTTP
Protocol, which it uses when directing requests to the server. The WebAgent
processes incoming request parameters, establishes a connection to the
appropriate server, and calls the service API(s) required to process the request.
When the service API responds, any data returned from the API is streamed
back to the client.
The OpenGIS Agent implements a number of the OpenGIS web-mapping
protocols to expose the services offered by the MapGuide Server to
standards-based OpenGIS clients.
The MapGuide Web Extensions provide a platform for application
development, based on the services offered by the MapGuide Server. The Web
Extensions API supports three languages/environments: ASP, JSP, and PHP.
For more information, see the Developer’s Guide.
Web Server
Server
18 | Chapter 1 Fundamentals
MapGuide Viewer
The MapGuide Viewer provides a means of viewing a map in a web browser.
After you have made your spatial data available on the Internet or on your
intranet, users can use the viewer to display the data and interact with it.
There are three flavors of the MapGuide Viewer:
■ The AJAX viewer (or “zero-client viewer”) does not need a download. It
works with Microsoft Internet Explorer, running on Windows, or with
Internet Explorer or Firefox on other operating systems, such as MacOS or
Linux.
■ The Fusion-based AJAX Viewer uses the popular Open Layers project for
both non-tiled and tiled maps.
You can customize the appearance of the MapGuide Viewer and select which
toolbar commands you want to use with a template called a web layout. Of
course, you can also add features and functions to the basic layout using your
own program code.
MapGuide Viewer | 19
Legend showing layers
Toolbar buttons
Task pane
20 | Chapter 1 Fundamentals
Load and Configure
Before you can build maps in MapGuide, you must make your source data
available. There are three ways to make source data available:
■ Load any file-based data, such as DWG, SHP, or SDF, onto the MapGuide
site. You can also load raster files.
■ Connect to SDF, SHP, and raster files not loaded into the MapGuide
resource repository.
Load data by converting all, or part of, the source file into a format that
MapGuide can use, and storing it as a resource. For example, you can load all
the layers in a DWG file and create a separate resource for each one.
Connect to SDF, SHP, or raster files without loading them into the MapGuide
resource repository. The files can be located on the same server as MapGuide
or on a different server.
Data stored in a database does not need to be loaded. You simply connect to
it by configuring a data source for it. In this case, the information necessary
to connect to the database is stored as the resource.
If the database is a simple file (Microsoft Access MDB or Microsoft Excel XLS),
Autodesk MapGuide Studio uploads it when you connect to the server. It is
stored on the server as source data for the resource.
MapGuide uses Autodesk and OSGeo FDO providers. An FDO provider is an
implementation of the FDO (Feature Data Objects) API that provides access
to data in a particular DataStore. (For more information about FDO, see the
Open Source Geospatial website at
https://mapguide.osgeo.org/gettingstarted.html.)
Connections to databases are stored as resources in the resource repository
and can be edited just like any other resource.
DWG files
Raster files
Points database
Database tables
Loading files and configuring connections to databases
22 | Chapter 1 Fundamentals
Feature Sources and Drawing Sources
During the load process, MapGuide transforms source data into formats that
are optimal for serving over the Web. Some formats are already optimal for
use on the Web, including: Autodesk SDF, Autodesk DWF, and ESRI SHP.
These formats are loaded directly without transformation. Other formats are
converted into either SDF or DWF, which are the two native file-formats in
MapGuide. SDF is used for feature sources and DWF is used for drawing sources.
■ Feature sources are the best choice when you simply want to load the raw
geometry and then style or theme it in Autodesk MapGuide Studio.
■ Drawing sources are best when you want to retain any styles or themes
already applied to the source data.
For example, the diagram on the facing page shows four views of a DWG file
in Autodesk Map. The layer containing unstylized polygons (screenshot 1 at
top) is converted to a feature source, because it contains simple geometry. The
Display Manager styles and themes (3 and 4) already have some stylization,
and so they are converted to drawing sources. There is also a polygon layer
that has some stylization (2). In this case, you can choose to convert the layer
either to a feature source (and lose the stylization) or to a drawing source (and
keep it).
Layers containing
1 colored and hatched
polygons:
drawing source or
feature source
2
Display Manager:
drawing source
Views of a DWG file in Autodesk Map, showing options for converting to feature sources or drawing
sources
24 | Chapter 1 Fundamentals
Load Procedures
When you drag a file or a set of files of the same format to the Site Explorer
in Autodesk MapGuide Studio, you get a new load procedure. Load procedures
are essentially saved scripts for reloading data. You can use load procedures
to automate the updating of resources on the server. They capture the location
of the source files, the conversion rules, and where to put the resulting data
on the server.
You can execute these conversion rules (either interactively in Autodesk
MapGuide Studio or through a script) to refresh file-based spatial data on your
site. Scripts can be run overnight or at regular intervals to keep the data
up-to-date.
Load procedures are themselves stored as resources in the repository. Open
them in Autodesk MapGuide Studio whenever you need to add or delete files,
change the destination, or update any of the other parameters.
The illustration on the facing page shows two load procedures open in
Autodesk MapGuide Studio. Both procedures load multiple files at the same
time. One loads SDF files, and the other loads raster files.
Load Procedures | 25
Drag files to the Site Explorer
SDF files
Raster files
Load procedures for SDF files (top) and raster files (bottom)
26 | Chapter 1 Fundamentals
Resource Repository
The resource repository is an XML database that stores the resources created
by loading file-based data or by connecting to databases. There is one repository
per site and it resides on the site server. The diagram on the facing page shows
how the resources are stored in the repository.
Resources are designed to be reused and shared. Some resources reference
other resources. For example, maps and layers are stored as separate resources,
and the map references the layers that are included in the map. Layers reference
feature or drawing sources. When you update the original feature source, the
layer is automatically updated as well.
Other resources, such as print layouts, are self-sufficient and do not reference
any other resources or files. Some resources use associated resource data. For
example, an ArcSDE feature source uses a file which holds the database
credentials. Resource data can be stored as files, streams, or strings.
■ Files are used when the amount of data is large, such as DWF or SDF files.
■ Streams are used for faster access to smaller pieces of binary data, such as
symbols.
■ Strings are used for small pieces of text data, such as database access
credentials.
For information on backing up and restoring the resource repository, see the
document RepositoryAdmin.pdf, installed with MapGuide.
Resource Repository | 27
Resources
Web layout
Print layout
Resource Data
Layer
Feature sources
Oracle credentials
ArcSDE credentials
file
ODBC credentials
config file
Feature join
Procedure
28 | Chapter 1 Fundamentals
Feature Joins
After you have loaded your data or connected to it, you can establish
relationships between any two feature sources. These relationships are called
feature joins. A feature join is saved as a new resource in the repository. When
you join feature sources, you create a feature-join resource, which is similar
to a relational join in a database, except that you are “extending” a feature
resource to create a new one.
The example on the facing page shows how a feature source containing county
boundaries is joined to another feature source containing census population
data, using the following general steps:
■ Enter a name for the extender property (serves as the prefix for the joined
properties, for example, Population).
Feature Joins | 29
Primary feature source Secondary feature source
Population
Counties - CountyID
- ID - CountyName
- Name - LandArea
- State - WaterArea
- Area - CountyPopulation
Counties
- ID
- Name
- State
- Area
- Population.CountyID
- Population.CountyName
- Population.LandArea
- Population.WaterArea
- Population.CountyPopulation
Joining two feature sources
30 | Chapter 1 Fundamentals
Learning MapGuide
MapGuide provides learning materials to get you started using the software,
and complete documentation to serve as a reference.
The Autodesk MapGuide Enterprise Getting Started Guide introduces the most
important concepts in MapGuide. After reading through it, and perhaps doing
some of the suggested exercises using the sample files provided, you should
feel comfortable enough to start working with your own data.
The Autodesk MapGuide Studio User’s Guide is a Help file in CHM format with
a table of contents, an index, and keyword search. You can print out the Help
topics that interest you.
MapGuide Server Site Adminstrator Help is a set of HTML pages that you can
access from the Site Administrator program.
The MapGuide Developer’s Guide is a book in PDF format that covers all topics
related to developing Web-based applications using the APIs provided with
MapGuide. It includes many practical examples with sample code that you
can copy and use.
The MapGuide Web API Reference and Studio API Reference are HTML pages.
They contain detailed information about all the APIs and include many code
samples.
The MapGuide Sample Application is a web application, written in PHP, that
demonstrates many of the features and services provided by the MapGuide
Server APIs.
Learning MapGuide | 31
The phrase you searched for is highlighted.
List of classes
MapGuide Studio API Reference (bottom) and Studio User’s Guide (top)
32 | Chapter 1 Fundamentals
Learning MapGuide | 33
34
Flow Diagram
2
The detailed flow diagram in this chapter summarizes the process of developing a Web
application using MapGuide. The numbers of the phases in this flowchart correspond to the
numbered steps in The Development Process topic at the beginning of Chapter 1,
“Fundamentals.” Some of the tasks in the flow diagram are marked with an asterisk icon (*).
Step-by-step tutorials for these tasks are included in Chapter 3, “Examples.”
35
36 | Chapter 2 Flow Diagram
P H A S E 0: P L A N N I N G
Set up site
Install software
Configure services
| 37
P H A S E 1: L O A D A N D C O N F I G U R E
Load files
SHP files
SDF files
DWF files
DWG layers
DWG elements
Raster files
Connect to databases
ODBC
Oracle
ArcSDE
1 Style layers
Generate labels
P H A S E 3: M A K E A M A P
Organize layers
Generate a legend
| 39
P H A S E 4: P L A C E O N I N T E R N E T
View in browser 5
41
About the Exercises
The following exercises are laid out on facing pages. The steps are on the
left-hand page with matching illustrations on the right-hand page. The
illustrations provide a summary of the task while the text includes the detailed
steps for the exercise. The large red numbers relate the two pages.
It is recommended that you read the text carefully the first time you do these
exercises and use the illustrations to confirm that your results are correct.
Later, you may find it useful to print out this chapter and use the illustration
pages as a quick reference to common tasks.
42 | Chapter 3 Exercises
Creating the Recommended Folder Structure
1
Create a root folder
Create a subfolder
3
Repeat to create structure
44 | Chapter 3 Exercises
Loading Shapefiles
Drag files
to folder
Specify load
procedure
3
Load resources
Load Shapefiles | 45
Load SDF Files
In this exercise, you add more data source files to the site. Like SHP files, you
load SDF files by dragging them directly into a folder in the Site Explorer.
46 | Chapter 3 Exercises
Loading SDF files
Drag files
to folder
Specify load
procedure
3
Load Resources
48 | Chapter 3 Exercises
Loading Geometry From a DWG File
Drag file
to folder
3
Load Resources
2 Select the four TIF files in the folder. Drag the files to
the Sheboygan Public folder in the Site Explorer.
50 | Chapter 3 Exercises
Loading Raster Files
Drag files
to folder
Specify load
procedure
3
Load Resources
52 | Chapter 3 Exercises
Connecting to a Microsoft Access Database
Select ODBC
provider
2
Specify connection
string and upload file
3
Save, then
test connection
3 Click OK.
54 | Chapter 3 Exercises
Setting a Style for Polygons
2
Set the style
3
Save the layer
56 | Chapter 3 Exercises
Making Composite Lines
2
Set the style
3
Save the layer
58 | Chapter 3 Exercises
Defining Scale Ranges
2
Define scale ranges
3
Test scale ranges
and save the layer
60 | Chapter 3 Exercises
Starting a New Map
2
Specify the
properties
of the map
3
Save the map
62 | Chapter 3 Exercises
Adding Layers to a Map
2
Drag layers
3
Preview and
then save
the map
3 Click Open.
Click Refresh to see the parcel polygons in the Preview
panel.
64 | Chapter 3 Exercises
Reference Data in a New Layer
2
Select the data
resource and preview
3
Save the layer
5 For Style Ramp, click the Browse button and then, for
Foreground Color, select yellow and red for the start
and finish colors. Click OK.
66 | Chapter 3 Exercises
Theming from a Database Table
2
Select the property and
set up the theme
3
Test and then save
the layer
1 Click the Drawing Order tab, then use the arrow but-
3 tons to move the layers into the order shown in the
illustration, with the layer Images at the bottom and
treepoints at the top.
68 | Chapter 3 Exercises
Organizing the Layers in a Map
2
Drag layers to
layers list
3
Set draw order and
make layer groups
70 | Chapter 3 Exercises
Editing the Style of the Layers
Edit Hydrographic
Polygons
and save. Scale range = 0-30000
2
Scale range = 0-10000
Edit buildingsNEW
and save.
3
Edit treepoints and save.
Result in
Map Editor:
Styled layers
Edit Layers | 71
Create a Symbol Library
In this exercise, you create a new symbol library. You will use one of the
symbols from it in the next exercise.
2 Click New.
72 | Chapter 3 Exercises
Creating a Symbol Library
2
Select the files to
include
in the library
3
Save the symbol
library
74 | Chapter 3 Exercises
Using Symbols for Points
2
Select the symbol
3
Save the layer
76 | Chapter 3 Exercises
Generating Labels
2
Select the property to use
as a label
3
Test and then save
the layer
Generate Labels | 77
Add Tooltips
In this exercise, you select properties to display in Tooltips. Tooltips are pop-up
boxes that contain information about the features in the map. You will be
able to view the tooltips in the Web browser in the final exercise.
5 Click OK.
The completed expression is displayed in the Settings
panel.
78 | Chapter 3 Exercises
Adding Tooltips
2
Select the properties
to display
3
Test and then
save the layer
Add Tooltips | 79
Set Up the Map Legend
In this exercise, you specify how you want the legend to appear. Some layers
are initially turned on while others are turned off. You will be able to view
the legend in the Web browser in the next exercise.
3 Click the Layers By Group tab and make sure that the
Parcels (Area) layer is still selected. Clear the check-
boxes for Layer Is Initially Displayed In The Map and
Layer (If Themed) Is Initially Expanded In The Legend.
The layer will be turned off when the map is displayed
in the viewer and the color-key for the theme will not
be expanded.
80 | Chapter 3 Exercises
Setting Up the Legend for the Map
Double-click Sheboygan
City Map
2
Specify which layers
are visible
3
Preview and then
save the map
1 Click File ➤ Save and save the Web layout in the Web
3 Layout folder with the name City Map.
You must save the Web layout before you can test it
in the browser.
82 | Chapter 3 Exercises
Viewing the Map in a Web Browser
2
Select the map
to use
3
Save the web layout
and then test
blocks In AutoCAD or Autodesk Map, compound objects that have been saved
for reuse in the drawing or in multiple drawings, for example, a North arrow.
In MapGuide, blocks are converted into symbols when they are loaded. See
also symbol.
CD Browser The program that appears when you insert the product CD, and
which provides access to installation instructions and other information.
Display Manager In Autodesk Map, the component that handles the styling
and theming of features in a DWG file.
Display Manager element A set of features that has been assigned a specific
style or theme in Display Manager and which can be selected individually for
loading into Autodesk MapGuide Studio.
Drawing service The service that allows low level access to DWF data stored
in a resource repository as part of a drawing source.
Glossary | 85
drawing source One of the two types of resources created by loading file-based
data. Drawing sources are stored in the repository in DWF format and retain
any styles or themes already applied to the source data. Compare with feature
source.
drive alias In Autodesk Map, the mechanism that points to the folder where
attached DWG files are stored.
DWF Design Web Format. An Autodesk file format for sharing 2D, 3D, and
spatially-enabled design data.
DWF Viewer The free viewer for the DWF file format. The DWF Viewer can
be used to preview layers and maps in Autodesk MapGuide Studio and to
display the completed map in MapGuide Viewer.
DWG The Autodesk file format for storing 2D, 3D, and spatially-enabled
design data.
FDO Feature Data Objects. An Autodesk software standard and general purpose
API for accessing features and geospatial data regardless of the underlying data
store. See also feature, feature class.
FDO provider An implementation of the FDO API that provides access to data
in a particular data store, such as an Oracle or ArcSDE database, or to a
file-based data store, such as SDF or SHP.
feature join A relationship that joins one feature source to another, similar
to a relational join in a database.
86 | Glossary
Feature service The service that allows low level access to SDF 3 data stored
in a resource repository as part of a feature source.
feature source One of the two types of resources created by loading file-based
data or by connecting to a spatial database. Feature sources are stored in the
repository in SDF 3 format or as database connections and contain raw
geometry only. Compare with drawing source.
layer A resource that references a feature source or a drawing source. The layer
contains styling and theming information, and a collection of scale ranges.
Load procedure A saved script for reloading file-based data. You can use load
procedures to automate the updating of resources on the server. They capture
the location of the source files, the conversion rules, and where to put the
resulting data on the server.
map A resource that references a collection of layers and displays them within
a consistent coordinate system and extents.
MapGuide A software platform for distributing spatial data over the Internet
or on an intranet. Exists in two versions: Open Source (supported by the
community) and Enterprise (supported by Autodesk). (www.osgeo.org)
Mapping service The service that creates the view of a map in response to
requests from the clients.
Glossary | 87
OpenGIS Agent The component of the MapGuide Web Extensions that
implements a number of the OpenGIS web-mapping protocols to expose the
services offered by the MapGuide Server to standards-based OpenGIS clients.
package A compressed file that can speed up the process of loading data onto
the server. Large source-data files can be zipped up in this file format and
saved to a network location or copied to a CD.
raster catalog A list of image files and their lower-left and upper-right
coordinates. MapGuide scans the catalog file to find the images that correspond
to the area being viewed, and then sends only the data for that area.
reference point For a symbol, the point that controls the position of a symbol
over a feature in a map. The default reference point is the center of the symbol.
Rendering service The service that creates the final map image for the HTML
viewer from input provided by the Mapping service.
SDF (SDF 3) Spatial Database Format. The current version of the SDF format.
It is the native format for MapGuide Enterprise and MapGuide Open Source
and is new in Autodesk Map 3D 2007. Each SDF 3 file can contain multiple
feature classes or types of data stored in tables with attributes and geometry.
88 | Glossary
SDF 2 The previous version of the SDF file format. It was the native file format
for Autodesk MapGuide (the last release was Autodesk MapGuide 6.5). Each
SDF 2 file generally contained one feature or type of data, for example points,
lines, polygons, or text.
services The software modules that reside on the MapGuide Server and which
implement its core functions. See also Site service, Resource service, Drawing
service, Feature service, Mapping service, Rendering service, and Tile service.
sheet In a DWF file, a plot layout containing a specific view of the original
data.
Site Explorer The tree view in Autodesk MapGuide Studio that shows you
the resources stored in the resource repository.
Site service The service that provides basic site-related functionality, such as
enumerating users and creating user sessions.
styling The process of assigning display characteristics (such as line color, line
pattern, fill color, fill pattern, and so on) to a feature (points, polylines,
polygons). See also theming.
symbol lbrary A collection of related symbols. Image files are converted into
symbols when they are brought into the symbol library. The symbol library
is stored in the resource repository.
task bar In MapGuide Viewer, a pane that contains tools and controls for
specific tasks, such as searching or buffering.
Glossary | 89
Tile service The service that supports smooth pans and zooms in the AJAX
viewer.
tooltips Pop-up boxes that contain information about the features in the map.
web surround The extra functionality that is automatically built for a web
layout, which resides outside of the map itself.
90 | Glossary
Index
A
Access database, connecting to D
(exercise) 52 data conversion during load 23
add layers to a map (exercise) 62 databases
add tooltips (exercise) 78 configure connections 21
API Reference, description of 31 relationships 29
authoring maps 13 supported by providers 21
Autodesk Map theming from (exercise) 66
styles and themes 23 upload file 21
automating update of source data 25 define scale ranges (exercise) 58
Developer’s Guide, description of 31
B development process
flow diagram 35
backing up the resource repository 27 overview 6
building maps, steps for 13 phases of 5
summary diagram 5
Display Manager 23
C documentation, list of 31
CD browser 9 drawing sources, definition of 23
client applications 11, 17 DWF Viewer
components used by Studio and Viewer 11
diagram of 12 used for preview 13
overview of 11 DWF, as rendered map 11
Server 15 DWG file, styles and themes in 23
Studio 13 DWG geometry, loading (exercise) 48
Viewer 19
Web Extensions 17 E
where to install 9
composite lines, making (exercise) 56 edit layers (exercise) 70
concepts exercises
learning 31 add layers to a map 62
configure connections to databases 21 add tooltips 78
connect Access database (exercise) 52 connect to an Access database 52
connecting to databases 21 create a folder structure 42
connections to databases 21 create a new layer 64
create a folder structure (exercise) 42 create a new map 60
create a new layer (exercise) 64 create a symbol library 72
create a new map (exercise) 60 define scale ranges 58
create symbol library (exercise) 72 edit layers 70
generate labels 76
Index | 91
load DWG geometry 48 HTML viewer
load raster files 50 compatibility 19
load SDF files 46 static image for 11
load SHP files 44 HTTP protocol 17
make composite lines 56
organize layers 68
overview of 41 I
set style for a layer 54 installation, where to find steps 9
set up the legend 80 interface, Autodesk MapGuide Studio 13
theme from a database 66 Internet Explorer browser 19
use symbols for points 74 IP address, log into Studio 11
view in Web browser 82
L
F
labels, generating (exercise) 76
FDO (Feature Data Objects) layer style, setting (exercise) 54
definition of 21 layers
providers 21 adding (exercise) 62
FDO providers 21 as resources 27
feature join create new (exercise) 64
definition of 29 editing (exercise) 70
diagram of 30 organizing (exercise) 68
feature sources learning MapGuide 31
definition of 23 legend, setting up (exercise) 80
joining 29 Linux
files components that run on 9
conversion process 23 supported browser 19
database 21 load
in resource repository 27 conversion process 23
Firefox browser 19 data from files 21
flow diagram 35 load and configure, diagram 22
folder structure, creating (exercise) 42 load DWG geometry (exercise) 48
formats, optimized for Web 23 load procedures
definition of 25
G screenshots of 26
load raster files (exercise) 50
generate labels (exercise) 76 load SDF files (exercise) 46
Getting Started Guide load SHP files (exercise) 44
overview of contents 1 log in
suggested use 31 to Site Adminstrator 15
to Studio 11
H
M
Help system, introduction to 31
MacOS 19
92 | Index
making composite lines (exercise) 56 resources
map authoring and site server 7
tutorials for 41 database connection 21
MapGuide relationships between 29
components of 9 reuse and sharing of 27
introduction to 1 view of 13
learning 31 restoring the resource repository 27
sample application 31
Mapping service, definition of 7
maps S
authoring 13 sample application 31
creating (exercise) 60 scale ranges, defining (exercise) 58
rendered in DWF format 11 screenshots
load procedures 26
O Site Administrator 16
Studio 14
OpenGIS Agent 17 Viewer 20
organize layers (exercise) 68 scripts for reloading data 25
SDF files, loading (exercise) 46
Server
P and client requests 11, 17
PDF tips 3 and Site Adminstrator 15
phases of development 6 and Web Extensions 17
flow diagram 35 overview of 15
summary diagram 5 servers
programming managing 15
adding to Web layout 13 services
languages supported 17 and Web Extensions 17
providers, FDO 21 assigning to servers 7, 15
providers, for database support 21 list of 7
set layer style (exercise) 54
set up the legend (exercise) 80
R sharing resources 27
SHP files, loading (exercise) 44
raster files, loading (exercise) 50 site
refreshing source data 25 definition of 7
relationships, database 29 diagram of 8
Rendering service, definition of 7 managing 15
requests from clients to server 11, 17 Site Administrator
resource repository documentation for 31
and Site Explorer 13 purpose of 15
and site server 7 screenshots of 16
backing up 27 Site Explorer, purpose of 13
definition of 27 site server
diagram of 28 and resource repository 27
connecting to 11
Index | 93
definition of 7 compatibility 19
source data flavors of 19
conversion during load 23 overview of 19
refreshing 25 screenshots of 20
static image, HTML viewer 11
streams, in resource repository 27
strings, in resource repository 27 W
Studio Web browser
as client application 11, 17 and Site Administrator 15
overview of 13 and viewer compatibility 9
parts of 13 and Viewer component 19
screenshots of 14 Firefox 19
styles and themes, retain from DWG Internet Explorer 19
file 23 viewing in (exercise) 82
symbol library Web Extensions
creating (exercise) 72 and client requests 11, 17
using (exercise) 74 diagram of 18
languages supported by 9
T overview of 17
Web layout
template for Web layout 19 and programming 13
theme from a database (exercise) 66 for customizing Viewer 19
tooltips, adding (exercise) 78 steps to build 13
tutorial exercises 41 WebAgent
purpose of 11, 17
Windows, components that run on 9
U
use symbols for points (exercise) 74 X
User’s Guide, description of 31
users and groups 15 XML database, for resource repository 27
V Z
view in Web browser (exercise) 82 zero-client viewer 19
Viewer
as client application 11, 17
94 | Index