Construire un site avec MapGuide Open Source Gwenaël Bachelot

Déroulement Installation du serveur déjà réalisée Comment construire un site utilisant différentes données ? Comment diffuser ces données ?

Serveur Web (IIS/Apache) Outils de publication Serveur Applicatif Serveur Web Client Serveur base de données MapGuide Open Source Fichiers de données Services Web WMS / WFS Serveur Web (IIS/Apache) + Web Server Extensions de MapGuide MapGuide Web Studio Google Earth Client Ajax Client DWF MapStudio Open Source Autodesk Studio Now let’s look more closely at the Autodesk MapGuide® Enterprise web services architecture, which is composed of server, web, and client tiers. Each of these fulfills a separate function. The server tier contains the data sources—including files, databases, and web services—that can be accessed by the Autodesk MapGuide Enterprise default application through the services residing on the server. These services include the core software components that access data (FDO Data Access Technology), perform analysis, handle client queries, and prepare data for display to the end user’s client. The Autodesk MapGuide Enterprise platform is compatible with either Microsoft® Windows® or Linux® server environments. [Build 1] The web tier contains the web extensions that developers use to build applications on the web services. Unlike many other web mapping systems, Autodesk MapGuide Enterprise supports the three main web development environments: PHP, Microsoft .NET, and Java. This provides the developer with the flexibility to choose the one that best suits the application and the customer’s deployment environment. The web application contains the business logic: what the end user sees and does. [Build 2] The client tier contains the different mechanisms for delivering the user interface of the application to the end user. Autodesk MapGuide Enterprise supports five basic client types, which can be loosely divided into thin clients that don’t require anything to be downloaded to the end user’s local machine or browser and thick clients that do require some type of installation or download. The main thin client is the AJAX Java mapping client, and the Autodesk® DWF™ viewer provides an ActiveX component that works within the browser. Both give flexibility to the developer for creating applications that meet different user needs. One of the interesting capability in Autodesk MapGuide Enterprise is that Google Earth™ is directly supported as a client. Some of you may be familiar with the idea of being able to publish static files by KML to Google Earth, but the direct support of KML/KMZ within Autodesk MapGuide Enterprise actually allows for interactive applications to be built for Google Earth. Some of the examples that have been built so far involve using extrusion support to model buildings and then thematically shade them based on data values, all extracted from the Autodesk MapGuide Enterprise server. We think this is a very exciting capability. There are also the Autodesk MapGuide® Studio and open source Web Studio clients. Autodesk MapGuide Studio provides a powerful desktop tool for authoring and administering applications and web sites. Web Studio, available through open source, is a thin client application that provides a basic set of administrative tools. [Build 3] In summary, the server tier provides the core components of the system, the web tier contains the application and business logic, and the client provides the user interface. Services Rendering KML Mapping Tile Feature Drawing Resource FDO Site PHP .NET® Java® 3

MapStudio Open Source Développé par Kenneth Skovhede Une alternative au produit propriétaire Autodesk MapGuide Studio. Actuellement hébergé par Google Code Développé en .Net 1.1 (C#) Devrait fonctionner sous Linux, avec Mono Avec WebStudio, permet de créer un site.

Téléchargement

MapStudio Open Source - Installation Framework .Net 1.1 : http://www.microsoft.com/downloads/details.aspx?FamilyID=262d25e3-f589-4842-8157-034d1e7cf3a3&displaylang=fr Décompresser l’archive MapStudio Open Source

Préambule - Ressources MGOS stocke toutes les informations de paramétrage dans une base de données XML (BerkeleyDB) Ressources de différents types : - Source de données (Feature Source-DataConnection ) - FDO - Couche (Layer) – lié à une source de données - Carte (Map) – empile des ressources couches - Présentation Web (Layout) – Paramétrage du client et fonctions mises à disposition des utilisateurs – Référence une carte - Présentation Web Flexible (application Fusion) - Référence une carte - Bibliothèque de symboles - Définition de mise en page pour impression

Etapes Outil Action MapStudio Open Source Créer un répertoire dans le référentiel MapGuide Créer une connexion vers un fichier SHP WebStudio Créer une couche (layer) et modifier sa symbologie Créer une carte (map) MapStudio Créer un Layout à partir d’un Layout existant http://mgos:8008/mapguide/mapviewerajax/?WEBLAYOUT=Library://Demo/Layout.WebLayout Changer option d’affichage de propriétés Filtre NOM_COM like 'MEUDON‘ URL : concat('http://www.google.fr/search?hl=fr&q=',NOM_COM) Info bulles concat(NUMERO,concat('\n',NOM_COM)) MapStudio et WebStudio Ajouter une seconde couche – SDF Couleur : FF880F0F

Diffusion Google Earth http://trac.osgeo.org/mapguide/wiki/MapGuideRfc16 Library://Boulogne/Boulogne_3D.MapDefinition

Evolutions MapGuide Open Source à venir Changement de moteur de système de projection - Proj4 actuellement - CS Map dès que ce sera un projet OSGeo

Où trouver plus d’informations ?

Documentation MapGuide

Documentation MapGuide

Documentation MapGuide