Comparación de clientes web de servicios web geográficos v.6

Esta comparación tiene como objetivo servir de base a las personas que buscan un primer acercamiento a las tecnologías web para SIG del lado del cliente. En la sexta versión se agregan doce (12) nuevos proyectos y se establece una categorización de los clientes con el fin de distinguirlos mejor, dado que actualmente hay cuarenta y cuatro (44) en la comparación.

For English click here.

INTRODUCCIÓN

Los clientes web de servicios web geográficos desempeñan un rol fundamental en los geoportales de Infraestructuras de Datos Espaciales (IDE) permitiendo la visualización de datos espaciales de diversas fuentes. Así mismo, dichos clientes hacen parte de aplicaciones de Sistemas de Información Geográfica (SIG) en la web, en las que los usuarios pueden interactuar directamente con los servicios ofrecidos por IDEs, visualizarlos, consultarlos e integrarlos con datos locales y herramientas SIG.

Existen varios proyectos de software libre y de código abierto que facilitan el desarrollo y la personalización de clientes web de servicios geográficos estándar. El presente estudio busca caracterizarlos y compararlos con el fin de brindar elementos de decisión a los arquitectos de proyectos SIG en la web, para elegir una u otra tecnología del lado del cliente según los requerimientos que se tengan.

En el estudio se presenta un amplio compendio de clientes web con capacidad para acceder a servicios web regulados por el Open Geospatial Consortium (OGC) y se examinan algunas de sus propiedades más relevantes, por lo que no se realiza un estudio exhaustivo de sus características técnicas. Además, se propone una definición del término “cliente web de servicios web geográficos” y se examina la relación que existe entre ellos.

CLIENTES WEB DE SERVICIOS WEB GEOGRÁFICOS

Los clientes web de servicios geográficos son piezas de software (aplicaciones, librerías, frameworks, entre otros) que proveen o extienden un componente interactivo para visualizar mapas en Internet desde fuentes remotas. Algunos de los proyectos que proveen dicho componente usan únicamente tecnología del lado del cliente mientras que la amplia mayoría depende de funcionalidades del lado del servidor para ejecutar tareas avanzadas como seguridad, administración de usuarios y grupos, análisis espacial y personalización de controles y funcionalidades de interfaces gráficas de usuario, entre otras.

El OGC promueve el uso de estándares para servicios web geográficos que han ayudado a establecer un marco común de trabajo para visualizar y descargar información geográfica en la internet (Web Map Service –WMS, Web Feature Service –WFS , Web Coverage Service –WCS), descubrirla (Catalog Service for the Web –CSW), presentarla por medio de estilos (Style Layer Descriptor –SLD), filtrarla (Filter encoding), almacenarla, transportarla (Geography Markup Language –GML y Keyhole Markup Language –KML) y procesarla (Web Processing Service –WPS).

Esta comparación está enfocada en proyectos de software libre y código abierto con capacidad de acceder a servicios de visualización (WMS) y de acceso a datos (WFS y WCS) del OGC.

NOVEDADES DE ESTA VERSIÓN

  • Doce (12) clientes han sido agregados a la comparación, estos son: AtlasMapper, GPAAMP Viewer, GWT-OpenLayers, Heron Mapping Client, Leaflet, Legato, MapGuide OS Ajax Viewer, MapQuery, OL4JSF, QGIS Web Client, ReadyMap Web SDK y SLMapViewer.
  • Los datos de los clientes restantes han sido actualizados.
  • Se ha agregado un nuevo ítem de comparación a la primera tabla (Descripción general) llamado “Categoría”.
  • La gráfica “Relación entre clientes web de servicios web geográficos” ahora incluye la categoría de cada cliente.

RELACIÓN ENTRE CLIENTES

A continuación se presenta una gráfica que muestra la relación entre clientes web de servicios web geográficos, específicamente proyectos de software libre y código abierto.

Relación entre clientes web

Esta gráfica permite observar que la mayoría de proyectos gira en torno a dos paradigmas: UMN MapServer y OpenLayers. Los clientes que utilizan como base UMN MapServer fueron creados años atrás aprovechando las características que este cliente dispone: mapa, escala, mapa de referencia, herramientas de navegación básica, identificación de objetos espaciales; y su Interfaz de Programación de Aplicaciones (API) llamada MapScript que ha sido implementada en diferentes lenguajes de programación como PHP, Python, Java, Perl y Ruby. Por otra parte, una generación más reciente de clientes utiliza OpenLayers debido a su óptimo rendimiento en tareas de renderización en la web y al gran número de formatos de datos que soporta. Diferentes empresas contribuyen a su desarrollo y proyectos como MapBuilder han finalizado para acelerar su progreso, lo cual la ha convertido en la librería base para construir aplicaciones SIG en la web. Actualmente incluso proyectos con su propio componente de renderizado están adoptando o por lo menos soportando OpenLayers con el fin de evitar duplicar esfuerzos en un área en donde ya existe un proyecto dominante. Cabe resaltar que algunos proyectos utilizan Flash/Flex para la construcción de aplicaciones enriquecidas de Internet (RIAs), como por ejemplo Flamingo, worldKit, OpenScales y Geoide, brindando una experiencia más agradable a los usuarios que no solo buscan consultar sino también interactuar con mapas en línea. Finalmente, la última generación de clientes se basa en HTML5, aprovechando mejoras significativas en cuanto a interacción con contenido multimedia y vectorial, ya no a través de plug-ins sino de manera nativa. Leaflet y ReadyMap Web SDK son ejemplos de proyectos basados en tecnologías de HTML5, el segundo, basado en WebGL, permitiendo incluso la renderización de globos 3D con tan solo JavaScript.

CATEGORÍAS

Debido a la gran cantidad de clientes web de servicios web geográficos es útil pensar en agruparlos por medio de categorías. Otros autores coinciden en que esto puede ser una tarea compleja debido al traslape que existe entre los proyectos en términos de arquitectura y alcance.

En esta comparación, las categorías para clientes web de servicios web geográficos han sido extraídas de la descripción oficial de los proyectos. De este modo, hay librerías, wrappers (envoltorios), frameworks, toolkits y clientes. Estas cinco categorías cumplen con la definición propuesta en la sección “CLIENTES WEB DE SERVICIOS WEB GEOGRÁFICOS” y representan una forma más especializada de mirar los proyectos, permitiendo entender, al menos en una primera instancia, sus objetivos y alcances.

  • Librerías: Exponen clases y funciones permitiendo construir aplicaciones a un nivel más alto de programación.
  • Wrappers: Según el Free On-Line Dictionary of Computing, un wrapper “[…] actúa como una interfaz entre quien lo llama y el código contenido en el wrapper. Esto puede hacerse por compatibilidad, por ejemplo, si el código contenido en el wrapper está en un lenguaje de programación diferente o utiliza diferentes convenciones de llamado o por seguridad […] La implicación es que el código contenido en el wrapper solo puede ser accedido a través del wrapper”.
  • Toolkits: P. Ramsey los describe como “más modulares y fácilmente integrables en una aplicación personalizada”.
  • Frameworks: De acuerdo con el glosario del OGC, un framework es “[…] una plantilla o esqueleto de software reutilizable, a partir del cual […] servicios secundarios pueden ser seleccionados, configurados e integrados con código de la aplicación.” Para P. Ramsey, estos “son más apropiados para personalizar que para integrar”.
  • Clientes: Esta categoría comprende visores y aplicaciones web para SIG listas para usar.

Esta manera de categorizar los clientes web de servicios web geográficos constituye una primera aproximación para distinguirlos y de esta forma facilitar el proceso de selección.

LA COMPARACIÓN

La comparación está basada en proyectos de software libre y de código abierto con capacidad para acceder a servicios web regulados por el OGC, mostrando diferentes parámetros como son: su licencia, su país de origen, los idiomas que manejan, su soporte comercial, los lenguajes de programación que permiten, su independencia con respecto a programas servidores de mapas y el manejo de metadatos, entre otros.

La comparación se divide en tres partes para facilitar su visualización:

  1. Descripción general, en donde se da una introducción a los proyectos mostrando los siguientes parámetros: Licencia, País de origen, Entidad o empresa de origen, Documentación (idiomas, niveles, formatos), Categoría, Apoyo de OSGeo y Observaciones.
  2. Características técnicas, en donde se presentan datos técnicos de los programas para facilitar una descripción más detallada y se muestra: Lenguaje en el que está escrito, Lenguaje de programación que admite su API, Servicios OGC que consume, Soporte de mapas basados en teselas, ¿Requiere plugins privativos?, ¿Incluye componente de metadatos? y Listas de correo.
  3. Enlaces de interés, en donde se muestra una captura de pantalla, la versión actual del cliente web y enlaces a la página oficial, a la documentación, a la página de descargas, a la página de funcionalidades y a la página de galería o en su defecto a una demostración de la aplicación.

CONVENCIONES

Ventaja, Desventaja.

Cliente oficialmente abandonado Cliente oficialmente abandonado.

Cliente sin versión reciente Cliente sin versión reciente (más de un año sin una nueva versión).

RECOMENDACIÓN: Se recomienda emplear un navegador web como Mozilla Firefox, K-Meleon, SeaMonkey u Opera entre otros para visualizar correctamente las tablas.

Web mapping client comparison
Part 1. General description
[1] BSD compatible.
[2] GPL compatible.
[3] It can be changed by a “commercial license” by request. See: https://www.legato.net/display/LEGATO/Licenses
[4] See: http://www.mapserver.org/copyright.html#license
[5] Very quickly support from USA, Netherlands, Brazil and Italy.
[6] Developed by Martin Hűgh.
[7] City of Saint Paul, Minnesota.
[8] Developed by Evgeny Gazdovsky.
[9] Originally, developed by Volker Mische and Geodan.
[10] Developed by Xavier Pons.
[11] Developed by Robert Anderson.
[12] Developed by Armin Burger.
[13] Originally, developed by Andreas Neumann.
[14] Incomplete documentation.
[15] The available documentation is related only to the installation process.
[16] The documentation is incomplete for some of the mentioned languages.
[17] The user interface is in Spanish and in Latvian as well.
[18] There are translations to several languages such as Swedish, Spanish, Bulgarian, Pole, Italian, French, Czech and Slovene, among others.
[19] The user interface has been translated to 20 languages.
[20] The user interface is available in several languages such as English, German, French, Italian and Portuguese, among others.
[21] OSGeo doesn’t support it as an official project, but hosts their mailing list and Trac.
[22] The copyright will be transferred to OSGeo.
[23] GeoMOOSE is in the incubation process.
[24] The graduated project is actually Deegree and iGeoPortal is part of it.
[25] The graduated project is actually MapGuide OS and the AJAX Viewer is part of it.
[26] The graduated project is actually QGIS and QGIS Web Client is part of it.
[27] Even though UMN MapServer is widely known as web map server, this comparison evaluates it as client and thus considers it to be a library because it exposes classes through MapScript.
Parameter of comparison
License
Origin country
Origin company or entity
Documentation
OSGeo project?
Category
Comments

AppForMap AtlasMapper CartoWeb Chameleon Dracones ET – Map Flamingo FlexLayers Fusion GeoExt Geoide Geomajas GeoMOOSE GisClient GMap GPAAMP Viewer GWT-OpenLayers Heron Mapping Client HSLayers i3Geo iGeoPortal ka-Map kvwmap Leaflet Legato Mapbender MapBuilder MapFaces MapFish MapGuide OS Ajax Viewer MapQuery MiraMon msCross OL4JSF OpenLayers OpenScales p.mapper QGIS Web Client ReadyMap Web SDK SLMapViewer TimeMap UMN MapServer WebGIS Public worldKit
GNU GPL v.2 GNU GPL v.3 GNU GPL Chameleon License 1 BSD GNU GPL v.2 GNU GPL v.2 GNU LGPL MIT BSD GNU LGPL GNU AGPL v.3 MIT-style v.2+; City of Saint Paul Open Source License v.1.x GNU GPL v.3 GNU GPL Apache License v.2.0 Apache License v.2.0 GNU GPL v.3 GNU GPL v.3 GNU GPL v.2 GNU LGPL MIT 2 GNU GPL BSD GNU GPL v.3 3 GNU GPL; Simplified BSD License GNU LGPL GNU LGPL v.3 GNU GPL v.3 GNU LGPL MIT GNU GPL v.3 GNU GPL Apache License v.2.0 BSD-style GNU LGPL v.3 GNU GPL BSD GNU LGPL GNU GPL v.2 GNU GPL; GNU LGPL MIT-style4 GNU GPL v.3 GNU GPL v.2
5
6 Australian Institute of Marine Science Camptocamp SA DM Solutions Group McGill University (Surveillance Lab) SEDesign Flamingo MC Community GeoVISTA Center (Penn State University) Autodesk; DM Soultions Group Camptocamp SA; OpenGeo; OSGIS IDgis DFC Software Engineering; GeoSparc 7 GIS & WEB S.r.l. DM Soultions Group Global Biodiversity Information Facility (GBIF) 8 Dutch Kadaster GEORZ Lab and Research Help Service – Remote Sensing (HS – RS) Ministério del Médio Ambiente de Brasil; Portal do Software Público Brasileiro lat/lon; GIS Research Group of the Department of Geography of University of Bonn DM Soultions Group University of Rostock CloudMade disy Informationssysteme GmbH CCGIS Geomatys Camptocamp SA Autodesk 9 10 Center for Advanced Studies, Research and Development in Sardinia 11 Metacarta Atos Worldline 12 13 Pelican Mapping Gaiocorp University of Sydney (Archaeological Computing Laboratory) University of Minnesota SWECO Position AB Mapufacture
Languages: English
Formats: HTML
Levels: Users 14
Languages: English
Formats: HTML; Issue Tracker; Wiki
Levels: Users 14
Languages: English; French
Formats: HTML; PDF; Wiki
Levels: Users; Developers
Languages: English
Formats: HTML; Wiki
Levels: Users; Developers
Languages: English
Formats: HTML
Levels: Users; Developers
Languages: German
Formats: txt
Levels: Users15
Languages: Dutch; English
Formats: HTML; Trac; Wiki
Levels: Users; Developers
Languages: English
Formats: Wiki
Levels: Users 14
Languages: English; French
Formats: PDF; Trac; Wiki
Levels: Users; Developers
Languages: English
Formats: Blog; HTML; Trac; Wiki
Levels: Users; Developers
Languages: Dutch; English; German
Formats: PDF; Wiki
Levels: Users; Developers
Languages: English
Formats: HTML; Issue tracker; PDF
Levels: Users; Developers
Languages: English
Formats: HTML; PDF; Trac; Wiki
Levels: Users; Developers
Languages: English; German; Italian 16
Formats: HTML; PDF; Trac; Video; Wiki
Levels: Users
Languages: English
Formats: txt
Levels: Users 14
Languages: English
Formats: HTML; Issue Tracker; Video
Levels: Users
Languages: English
Formats: HTML; Javadoc; Trac; Wiki
Levels: Users; Developers 14
Languages: Dutch; English
Formats: HTML; Issue Tracker; PDF; Wiki
Levels: Users; Developers 14
Languages: Czech; English 17
Formats: Blog; Trac; Wiki
Levels: Users; Developers 14
Languages: Portuguese
Formats: Blog; HTML; PDF; Trac; Twitter; Video; Wiki
Levels: Users; Developers
Languages: German; English
Formats: HTML; Issue tracker; PDF; Wiki
Levels: Users; Developers
Languages: English; French; Japanese
Formats:HTML; PDF; Wiki
Levels: Users; Developers
Languages: German
Formats: HTML; PDF; Wiki
Levels: Users; Developers
Languages: English
Formats: HTML; Issue Tracker; Twitter
Levels: Users; Developers
Languages: English; German
Formats: HTML; Issue Tracker (Jira); PDF; Video
Levels: Users; Developers
Languages: English; German; 18
Formats: ODP; PDF; Trac; Twitter; Video; Wiki
Levels: Users; Developers
Languages: English
Formats: Wiki
Levels: Users; Developers
Languages: English
Formats: HTML; Wiki
Levels: Users; Developers 14
Languages: English; French
Formats: Blog; HTML; Trac; Twitter; Wiki
Levels: Users; Developers
Languages: English; French
Formats: HTML; PDF; Trac; Video; Wiki
Levels: Users; Developers
Languages: English
Formats: HTML; Issue Tracker; Wiki
Levels: Users; Developers 14
Languages: Catalan; English; Spanish
Formats: HTML
Levels: Users
Languages: English; French; Italian
Formats: HTML; Tracker
Levels: Users; Developers 14
Languages: English; Portuguese
Formats: Flash; HTML; Issue Tracker; PDF
Levels: Users 14
Languages: English; French; Portuguese; Russian; Spanish
Formats: Blog; HTML; Trac; Wiki
Levels: Users; Developers
Languages: Chinese; English
Formats: HTML; Issue tracker; Twitter; Wiki
Levels: Users; Developers
Languages: English 19
Formats: HTML; PDF; Trac; Wiki
Levels: Users
Languages: English 20
Formats: HTML; Issue Tracker; PDF; TXT; Wiki
Levels: Users 14
Languages: English
Formats: HTML; Issue Tracker; Twitter; Wiki
Levels: Users 14
Languages: English
Formats: HTML; Issue Tracker
Levels: Users 14
Languages: English
Formats: HTML; PDF
Levels: Users; Developers
Languages: English; French; German; Spanish 16
Formats: HTML; PDF; Trac; Wiki
Levels: Users; Developers
Languages: English
Formats: HTML; Wiki
Levels: Users; Developers
Languages: English
Formats: Blog; HTML
Levels: Users; Developers
No No No No No No No No No 21 No 22 No Yes (Graduated) No 23 No No No No No No No Yes (Graduated) 24 No No No No Yes (Graduated) Yes (Graduated) No Yes (Graduated) Yes (Graduated) 25 No No No No Yes (Graduated) No No Yes (Graduated) 26 No No No Yes (Graduated) No No
Client Client Framework Framework Framework Client Client Library Framework Toolkit Client Framework Framework Client Client Client Wrapper Client Framework Client Framework Library Framework Library Client Framework Library Library Framework Client Wrapper Client Client Wrapper Library Framework Framework Client Toolkit Client Client Library 27 Library Client
It uses SFA-SQL to query and modify PostgreSQL/PostGIS databases. Uses PHP/MapScript to operate as UMN MapServer client (optional). Recently, the possibility to use OpenLayers as mapping component and jQuery for AJAX-related tasks has been added. It is able to work as WFS server. It allows a catalogue of map layers (WMS, KML and other formats supported by OpenLayers) to be easily browsed, layered, re-styled and compared side-by-side in a web browser. It is built upon ExtJS, OpenLayers, and GeoExt. It has both client and server modules, the latter allows the client to be configured with Web Map Server data sources. It has an object oriented architecture that makes it modular. It might be configured as SOAP web service. All its potential is obtained when working with PostgreSQL/PostGIS. It has a consolidated and well documented JavaScript API. Accelerated growth by means of customized widgets. It is based on MapScript from UMN MapServer in both Python and PHP. It was built from the DraconesPH application. It has server and client components. It uses jQuery in the client side and provides a map widget which works with AJAX requests. Doesn’t work with AJAX by default. Takes some JavaScript functions from the p.mapper project. Its development has come to an end. It has been developed based on a set of components that perform common tasks of navigation and queries. It has an authentication component. It is a partial port of OpenLayers API to ActionScript 3. The OpenScales project uses its code as basis and has begun to maintain its development. It allows to build RIAs quickly. It uses OpenLayers as base API and JX JavaScript library for the graphic interface. Through PHP it can be integrated with MapGuide OS for using server tools. It has a dynamic web layout making use of HTML and CSS. It can be configured through an under-development authoring tool called Maestro. It has commercial support. It is based on OpenLayers and Ext JS. It aims to provide controls for building rich web mapping applications. It has additional functionalities and controls also known as GeoExt ux, which are not maintained by the GeoExt Team but by other persons or companies. GeoExt can be extended using plug-ins. It can use the MapFish print module. It has client and server components. On the server side it is based on deegree. It may be configured with OpenJump. It uses a PostgreSQL or Oracle database to store configuration parameters. It can be incorporated into other applications by means of JSP. It allows online edition. It has a tool called Geoide Author for configuring the viewer functionalities and web geographic services. It is both a client and a server framework. It is based on GWT for implementing the client side as a RIA. It can use OpenLayers as alternative mapping component. It is fully modular, allowing to be extended by means of plug-ins. It has tools for editing, snapping, measurement, advanced queries and analysis. It has an advanced security component. It is configurable and it has a modular architecture. It can act as a client either for UMN MapServer layers using PHP/MapScript or for WMS layers. It uses OpenLayers as mapping component. It allows the inclusion of user extensions. The client is configured by means of an XML file. It has commercial support. It is an AJAX client for UMN MapServer. It uses PHP/MapScript and PostgreSQL/PostGIS. It has two components: a viewer and a configuration tool for the web geographic services to be shown. The coming version 3 will bring structural changes such as integration with jQuery, OpenLayers and TileCache for improving performance. It is an example application for the PHP/MapScript extension. It is usually found in utility packages such as MS4W or FGS. It is used in the MapLab project. GPAAMP Viewer stands for Global Protected Areas Assessment and Monitoring Pilot Viewer. Supporting viewing and download services, it functions primarily as a means for visualizing information from disparate sources delivered through standards-based web services. It is based on the stack ExtJS, OpenLayers and GeoExt. It is a Java wrapper for the OpenLayers JavaScript API. It allows GWT projects to use OpenLayers. It has both client and server modules. The main goal of this project is to make it easy to create web mapping applications like viewers for maps and editors for geodata. It is built on GeoExt, OpenLayers and ExtJS. It aims to follow declarative programming principles, i.e., to specify what the application has to do, rather than how to do it. It is based on OpenLayers and Ext JS. Is part of the HS – RS company’s solution to build geoportals following the principles of INSPIRE. It has a light version to incorporate it in web pages without using Ext JS components. It is an integrated interface of geoprocessing tools for the Internet. It is based on UMN MapServer and uses PHP/MapScript. Besides the original one, it is able to use OpenLayers or Flamingo as alternative mapping component. It has a lighter version for slow connections as well as a mobile version. It has a modular architecture. It is based on OGC and ISO/TC 211 standards. It has a security component. It supports Gazetteer for spatial queries by names or adresses. It has a standard version (does not work with AJAX) based on JavaScript and JSP, a version based on Ext JS and a portlet version based on Apache Jetspeed. There is an under-development 3d module for this project. It provides a JavaScript API acting as an interface to PHP/MapScript. It is designed to use caching as much as possible and to render maps quickly by means of tiles. It is used in official administrations. It has client and server components. It is based on PHP/MapScript from UMN MapServer. It uses PostgreSQL/PostGIS, MySQL (for storing user data) and SVG (for client interaction), among other technologies. It allows online edition. It is a lightweight JavaScript library for making tile-based interactive maps for both desktop and mobile web browsers. It uses cutting-edge technologies included in HTML5. Its top priorities are usability, performance, small size, A-grade browser support, flexibility and easy to use API. It can be configured in a declarative way by means of XML or JSON. It can be easily embedded into web pages and portals, CMS and individual web applications. It adds richer components to OpenLayers. It provides a generic WPS client that builds on-the-fly dialogs for input parameters. Optionally, it includes Java-based modules for exposing server-side tools. It has commercial support. It is both a client and a server framework. It helps to manage, organize, protect and monitor map services, users and applications. It has a Gazetteer client. The under-development version 3 has a REST architecture and incorporates MapQuery to interact with OpenLayers through JQuery. In the server side it uses Symfony2. It shares its vector rendering engine with OpenLayers. It has a SLD editor. Has commercial support (LISAsoft from Australia and DM Solutions Group from Canada). Its development has come to an end. It provides a library of JSF components for building web mapping applications. Currently uses a highly simplified version of OpenLayers. It is based on Geotoolkit in the server side. It is oriented to make the RIAs development easier. It is based on Pylons. On the client side it uses and extends OpenLayers, GeoExt y Ext JS. It has an interface called ‘Studio’ for the management of web mapping applications. It is the basic AJAX viewer for MapGuide OS (Fusion is the advanced one). It has a static layout design (3 columns), whereas Fusion has a dynamic one. It can be configured through an under-development authoring tool called Maestro. Supports redlining, feature buffering and querying, printing and plotting. It uses HTML Frames. It includes user authentication. It is an incipient project. It is a pure JavaScript project which builds upon OpenLayers, jQuery and jQuery UI to provide an easy to use webmapping library. It is meant for jQuery application developers who want to build RIAs with maps. Currently it provides a few basic widgets to create functionality around a map and an easy API to write your own widgets. It is an AJAX client. Consists of HTML and JavaScript files. It is funded by the Centre de Supercomputació de Catalunya (CESCA-FCR). It was created as an AJAX client for UMN MapServer and currently is able to operate without it. Consists of a single JavaScript file. It aims to provide a set of JSF components built on top of OpenLayers library to facilitate the development of GIS applications. It has a built-in OpenLayers editor. The development architecture is based on Maven, inspired by GMaps4JSF project. It is a JavaScript library with no server-side dependencies. It provides the basis component for several web mapping projects. It has a fast development. It has functionalities for online edition. Its web site provides lots of examples. It offers broad mobile support. It is based on ActionScript 3 and Flex. It was built taking FlexLayers as basis. It was designed to build RIAs easily. It runs as desktop, web and mobile application. It allows online edition. It has a compiled version (known as Viewer) that is configured by XML. It has been adopted by the France’s IGN as 2D API for its Géoportail. It is based on UMN MapServer and PHP/MapScript. It provides a good set of out-of-the-box tools. It has a plugin API to add functionalities. It uses JQuery for AJAX functions as well as for the graphic interface. It has commercial support from companies in several countries. It is an incipient project. It is a generic Web GIS front-end for WMS servers, supporting all additional features of QGIS Server like highlighting, printing and metadata. It is based on the stack ExtJS, OpenLayers and GeoExt. It is recommended being used together with QGIS Server. It supports 2D “slippy” maps and 3D global maps. It leverages WebGL technology to render high-performance 3D maps. It allows for embedding web maps in an HTML5 application. It uses jQuery. It is a Silverlight-based map viewer for UMN MapServer. It is based on the MapFlash Viewer framework by Paolo Corti. It is a Java applet (TMJava). Is focused in multi-temporal data which presents through animations. Can be packaged in a CD-ROM to run as an independent application through a web browser. It has a publishing tool and data management for Windows (TMWin) but its use is optional. It can be used to build web mapping applications either with HTML templates (using the UMN MapServer CGI program) or with the more flexible MapScript API. The CGI version has many features out-of-the-box, whereas with MapScript everything has to be done from scratch. UMN MapServer provides functionalities to generate graphical scale, legend and reference map. It is based on OpenLayers and Ext JS. Its main developer has announced its support for the GeoExt project to avoid duplicating efforts. Its development has come to an end. It is a Flash application. It can be configurated through XML. Supports GeoRSS and background images on JPEG format. Displays notes and photographs associated with map objects.

Web mapping client comparison
Part 2. Technical features
[1] When MapGuide Open Source is present, Fusion is able to use a PHP API.
[2] Does not yet have a published API.
[3] The WFS only works for points.
[4] Supports the GetCapabilities, GetFeatureOfInterest and GetObservation requests of the SOS specification.
[5] As a server additionally supports the WCS and SOS services.
[6] Takes this feature from OpenLayers.
[7] In the last version it was introduced an example with OSM but with no tiles.
[8] Consuming third-party tiles is only available in Fusion.
[9] Supports a large number of map sources based on tiles.
[10] It only supports the TMS Global Geodetic profile.
[11] Runs through a Java applet.
[12] It displays the metadata information (the layer abstract) included in the WMS capabilities document associated with the layers.
[13] Camptocamp SA has added support for the GetDomain and GetRecords requests of the CSW specification to OpenLayers.
[14] It has a search component that uses either a thesaurus or the CSW specification.
[15] The HS – RS company offers it as a component of its solution for geoportals.
[16] Currently, there is a proposal to build a metadata catalogue client using GeoNetwork. (See: https://trac.mapfish.org/trac/mapfish/wiki/Proposals/Catalogue and http://www.camptocamp.com/fr/blog/2009/06/732/)
[17] Supports the GetDomain and GetRecords requests of the CSW specification.
[18] There is a Google group for developers.
[19] It has a single mailing list for users and developers.
[20] It does not have its own mailing lists, they are from the Deegree project.
[21] It does not have its own mailing lists, they are from the MapGuide OS project.
[22] It has mailing lists for: Users, developers, commits, announcements, tilecache and trac, among others.
[23] It does not have its own mailing lists, they are from the QGIS project.
[24] It has a mailing list in German.
Parameter of comparison
Source code language
API language
Supported OGC services
Tile-based maps support
Does it require proprietary plug-ins?
Does it include meta-data component?
Mailing lists

AppForMap AtlasMapper CartoWeb Chameleon Dracones ET – Map Flamingo FlexLayers Fusion GeoExt Geoide Geomajas GeoMOOSE GisClient GMap GPAAMP Viewer GWT-OpenLayers Heron Mapping Client HSLayers i3Geo iGeoPortal ka-Map kvwmap Leaflet Legato Mapbender MapBuilder MapFaces MapFish MapGuide OS Ajax Viewer MapQuery MiraMon msCross OL4JSF OpenLayers OpenScales p.mapper QGIS Web Client ReadyMap Web SDK SLMapViewer TimeMap UMN MapServer WebGIS Public worldKit
JavaScript; PHP Java; JavaScript PHP JavaScript; PHP JavaScript; PHP; Python JavaScript; PHP ActionScript ActionScript 3 JavaScript; PHP JavaScript ActionScript 2 Java JavaScript; PHP JavaScript; PHP PHP JavaScript; PHP Java; JavaScript JavaScript JavaScript; PHP; Python JavaScript; PHP Java JavaScript; PHP JavaScript; PHP JavaScript Java; JavaScript JavaScript; PHP JavaScript Java; JavaScript JavaScript; Python C++ JavaScript JavaScript JavaScript Java JavaScript ActionScript 3 JavaScript; PHP JavaScript; Python JavaScript ASP.NET; C# Java C/C++ JavaScript ActionScript
JavaScript; PHP Java; JavaScript PHP JavaScript; PHP JavaScript; PHP; Python JavaScript; PHP ActionScript; JavaScript ActionScript 3 JavaScript 1 JavaScript ActionScript 2; JavaScript Java; JavaScript JavaScript; PHP JavaScript; PHP PHP JavaScript; PHP Java JavaScript JavaScript JavaScript; PHP JavaScript; ASP.NET; JSP JavaScript; PHP PHP JavaScript JavaScript PHP JavaScript Java Java; JavaScript; PHP; Python; Ruby JavaScript; ASP.NET; JSP; PHP JavaScript JavaScript JavaScript Java; JavaScript JavaScript ActionScript 3; JavaScript JavaScript; PHP 2 JavaScript ASP.NET; C# JavaScript; JSP Java; .NET; Perl; PHP; Python; Ruby JavaScript JavaScript
WMS; WFS WMS WMS; WFS WMS WMS; WFS WMS WMS; WMS-C; WFS; WFS-T WMS; WMS-C; WFS WMS WMS; WFS; WFS-T WMS; WFS; WFS-T WMS; WFS WMS; WFS WMS; WFS WMS; WFS WMS; WFS; WFS-T WMS; WFS WMS; WFS WMS; WFS WMS; WMS-T; WFS; WCS; SOS WMS; WFS; WCS; CSW; WFS-G; WPS; WTS; WCTS; SOS; WPVS WMS; WFS 3 WMS; WFS; WCS; SOS WMS WMS; WFS; WPS WMS; WFS; WFS-T; CSW WMS; WMS-C; WFS; WFS-T WMS; WFS; WFS-T; WCS; CSW; SOS WMS; WFS WMS; WFS WMS; WFS WMS; WFS 3; WCS WMS; WFS 3 WMS; WFS WMS; WFS; 4 WMS; WMS-C; WFS WMS; WFS WMS WMS WMS WMS WMS; WFS 5 WMS WMS
Yes 6 Yes 6 No No No No Yes (TMS) Yes 6 Yes (OSM; Google Maps; Yahoo Maps; Microsoft Virtual Earth) Yes 6 Yes (TMS; WMTS) Yes (OSM; Google Maps) Yes (OSM; Google Maps; Yahoo Maps; Bing Maps; Microsoft Virtual Earth) No No Yes 6 Yes 6 Yes (OSM; Bing Maps; Google Maps; Yahoo Maps) Yes 6 Yes 6 (OSM; Flamingo; Google Maps) No 7 Yes No Yes Yes (Google Maps; Yahoo Maps) Yes 6 Yes 6 No Yes 6 Yes 8 Yes 6 Yes (WMTS) No Yes 6 Yes 9 Yes (TMS; WMTS; OSM; Yahoo) No Yes 6 Yes (TMS) No No No Yes 6 Yes (TMS 10; NASA OnEarth)
No No No No No No Yes (Adobe Flash Player) Yes (Adobe Flash Player) No No Yes (Adobe Flash Player) No No No No No No No No No No No No No No No No No No No No No No No No Yes (Adobe Flash Player) No No No Yes (Microsoft Silverlight) No 11 No No Yes (Adobe Flash Player)
No Yes 12 No No No No No No No Yes 13 Yes 14 No No No No No No No Yes (CSW client, ISO 19115/19119/19139/15836) 15 No Yes (CSW client, ISO 19115/19119) No Yes (ISO-19115) No No Yes (ISO-19119; CSW client) No Yes (CSW client) No16 No No No No No Yes 17 No No No No No Yes (It handles basic metadata for the map) No No No
No No Yes (Users; Developers) Yes (Announcements; Users; Developers) No No (Forums only) No (Forums only) No Yes (Users; Developers; Commits; Trac) Yes (Users; Developers; Commits; Trac) Yes (Users) Yes (Users; Developers; Commits; Issues) Yes (Users; Developers) Yes 18 No No Yes (Users) Yes 18 Yes 19 No (Forums only) Yes (Announcements; Users; Developers) 20 Yes (Users; Developers) Yes (Users) No Yes (Users) Yes (Users; Developers; Commits) Yes (Announcements; Users; Developers) Yes (Users; Developers; Announcements; SCM) Yes (Users; Developers; Commits; Trac) Yes (Announcements; Users; Developers; Commits; Trac) 21 Yes (Users) Yes (Commits) Yes (Users) Yes (Announcements; Users; Developers; Commits; Issues) Yes 22 Yes 18 Yes (Users) Yes (Users; Developers) 23 Yes (Users) No No Yes (Announcements; Users; Developers) 24 No Yes 19

Web mapping client comparison
Part 3. Links of interest
[1] The author keeps updating the base code without releasing another official version.
[2] Camptocamp has abandoned the development of CartoWeb to focus in MapFish, which was introduced as Cartoweb v.4 in FOSS4G 2007. However, Cartoweb is still supported through the mailing list. More information on this thread: http://lists.maptools.org/pipermail/cartoweb-users/2010-January/004609.html
[3] There will be no more versions of this software.
[4] The initial code was released with no version in 09.03.2009 and it has not been modified.
[5] There is one version for each file. Here was taken the gmap75.inc.php file as reference, because it contains the GMap PHP functions. The last version of the project can be found in the package FGS: http://dl.maptools.org/dl/fgs/dev/dev-20091216/modules/
[6] There is no a first release yet.
[7] There are no releases for this project, the updates are based on user or client demand.
[8] It is the TMJava version.
[9] See the section OGC Support and Configuration, where it is explained how to use UMN MapServer as a client.
Parameter
Screenshot
Current version
(Jan 2012)
Official website
Downloads
Documentation
Features / Roadmap
Gallery / Demo

AppForMap AtlasMapper CartoWeb Chameleon Dracones ET – Map Flamingo FlexLayers Fusion GeoExt Geoide Geomajas GeoMOOSE GisClient GMap GPAAMP Viewer GWT-OpenLayers Heron Mapping Client HSLayers i3Geo iGeoPortal ka-Map kvwmap Leaflet Legato Mapbender MapBuilder MapFaces MapFish MapGuide OS Ajax Viewer MapQuery MiraMon msCross OL4JSF OpenLayers OpenScales p.mapper QGIS Web Client ReadyMap Web SDK SLMapViewer TimeMap UMN MapServer WebGIS Public worldKit
0.7a 1 ( 22.02.2007 ) 1.0 rc1 ( 21.11.2011 ) 3.5.0 2 ( 04.09.2008 ) 2.6 rc1 ( 06.09.2007 ) 1.1.3 ( 06.12.2010 ) 0.5 3 ( 23.02.2007 ) 3.2.1 ( 26.09.2010 ) 4 2.2.0 ( 01.06.2011 ) 1.1 ( 22.12.2011 ) 2.5.1 ( 14.07.2010 ) 1.9.0 ( 11.08.2011 ) 2.4 ( 13.05.2011 ) 2.1.5 ( 16.05.2011 ) 1.3 ( 28.01.2010 ) 5 0.8 RC1 ( 21.03.2011 ) 0.6 ( 10.09.2011 ) 0.66 ( 18.12.2011 ) 2.0.0 beta ( 08.10.2009 ) 4.6 beta 2 ( 07.12.2011 ) 2.5 ( 29.06.2011 ) 1.0 3 ( 05.02.2007 ) 1.8.0 ( 07.09.2011 ) 0.2.1 ( 18.06.2011 ) 1.1.2 ( 12.12.2011 ) 3.0 build0 ( 15.09.2011 ) 1.5 3 ( 16.07.2009 ) 6 2.2 ( 22.06.2011 ) 2.2 ( 02.05.2011 ) 0.1 ( 28.07.2011 ) 4.10 ( 27.06.2008 ) 1.1.9 ( 18.02.2007 ) 2.2 ( 05.12.2011 ) 2.11 ( 11.09.2011 ) 2.0.0 ( 24.12.2011 ) 4.2.0 ( 17.07.2011 ) 7 0.0.1 ( 29.09.2011 ) 1.0 ( 11.03.2010 ) 2.2.60 8 ( 02.10.2007 ) 6.0.1 ( 13.07.2011 ) 1.2.4 3 ( 23.04.2009 ) 3.3 ( 03.05.2007 )
http://www.mapuse.net/node/16 https://code.google.com/p/atlasmapper/ http://www.cartoweb.org http://chameleon.maptools.org http://code.google.com/p/dracones http://sedesign.de/de_produkte_et-map.html http://flamingo.gbo-provincies.nl http://code.google.com/p/flexlayers http://trac.osgeo.org/fusion/ http://geoext.org http://www.geoide.nl http://www.geomajas.org http://www.geomoose.org/moose/ http://www.gisclient.org http://code.google.com/p/gbif-geospatial/ http://gwt-openlayers.sourceforge.net http://heron-mc.org http://dev.bnhelp.cz/trac/hslayers http://mapas.mma.gov.br/download http://testing.deegree.org/igeoportal-std http://ka-map.maptools.org http://kvwmap.geoinformatik.uni-rostock.de http://leaflet.cloudmade.com/ http://www.legato.net http://www.mapbender.org http://communitymapbuilder.osgeo.org http://mapfaces.codehaus.org http://www.mapfish.org http://mapguide.osgeo.org http://mapquery.org http://www.creaf.uab.es/miramon/mmn/ http://sourceforge.net/projects/mscross/ http://java.net/projects/ol4jsf http://openlayers.org http://openscales.org http://www.pmapper.net http://hub.qgis.org/projects/qgis-web-client http://readymap.com/websdk.html http://slmapviewer.codeplex.com http://www.timemap.net http://www.mapserver.org http://code.google.com/p/webgispublic/ http://worldkit.org
http://sourceforge.net/projects/appformap/files/ https://code.google.com/p/atlasmapper/downloads/list http://www.cartoweb.org/downloads.html http://chameleon.maptools.org/index.phtml?page=downloads.html http://code.google.com/p/dracones/downloads/list http://flamingo.gbo-provincies.nl/media/6/default.aspx http://code.google.com/p/flexlayers/source/checkout http://trac.osgeo.org/fusion/wiki/GetIt http://geoext.org/downloads.html http://geoikia.idgis.eu/wiki-english/index.php/Download_and_Installation http://www.geomajas.org/download http://www.geomoose.org/moose/info/download.html http://www.gisclient.org/download-en-us http://dl.maptools.org/dl/ http://code.google.com/p/gbif-geospatial/downloads/list http://sourceforge.net/projects/gwt-openlayers/files/gwt-openlayers/ http://www.heron-mc.org/downloads.html http://dev.bnhelp.cz/trac/hslayers/wiki/download http://code.google.com/p/i3geo-download/downloads/list http://deegree.org/deegree/#v2.4 http://ka-map.maptools.org/index.phtml?page=downloads.html http://sourceforge.net/projects/kvwmap/files/ http://leaflet.cloudmade.com/download.html https://www.legato.net/display/LEGATO/Download http://mapbender3.org/index.php/Download http://communitymapbuilder.osgeo.org/display/MAP/Downloads http://mapfaces.codehaus.org/download.html http://www.mapfish.org/downloads/ http://trac.osgeo.org/mapguide/wiki/Release/2.2/Notes https://github.com/mapquery/mapquery/zipball/v0.1 http://projectes.lafarga.cat/projects/navmapesmiramon/downloads http://mscross.svn.sourceforge.net/ http://java.net/projects/ol4jsf/downloads http://trac.openlayers.org/wiki/HowToDownload http://openscales.org/downloads/index.html http://www.pmapper.net/download.shtml https://github.com/qgis/qgis-web-client/downloads https://github.com/gwaldron/godzi-webgl http://slmapviewer.codeplex.com/releases/view/41756 http://www.timemap.net/index.php?option=com_content&task=view&id=44&Itemid=63 http://www.mapserver.org/download.html http://code.google.com/p/webgispublic/downloads/list http://worldkit.org/download.php
https://code.google.com/p/atlasmapper/wiki/install?tm=6 http://www.cartoweb.org/documentation.html http://chameleon.maptools.org/index.phtml?page=docs.html http://surveillance.mcgill.ca/dracones/doc/index.php http://flamingo.gbo-provincies.nl/content/Documentatie.aspx http://trac.osgeo.org/fusion/wiki/Documentation http://geoext.org/docs.html http://geoikia.idgis.eu/wiki-english/index.php/Main_Page http://www.geomajas.org/gis-documentation http://www.geomoose.org/moose/#geomoose-documentation http://www.gisclient.org/documenti http://code.google.com/p/gbif-geospatial/wiki/TableOfContents http://gwt-openlayers.sourceforge.net/maven-site-latest/user-reference.html http://www.heron-mc.org/docs.html http://dev.bnhelp.cz/trac/hslayers/wiki/documentation http://pt.wikibooks.org/wiki/I3geo/Índice http://download.deegree.org/deegree2.3/docs/igeoportal/html/deegree_igeoportal_documentation_en.html http://ka-map.maptools.org/index.phtml?page=docs.html http://kvwmap.geoinformatik.uni-rostock.de/index.php/Dokumentation http://leaflet.cloudmade.com/reference.html https://www.legato.net/display/LEGATO/Documentation http://www.mapbender.org/Tutorials http://communitymapbuilder.osgeo.org/display/MAP/Tutorials http://docs.codehaus.org/display/MAPFACES/home http://www.mapfish.org/doc/index.html http://mapguide.osgeo.org/documentation.html https://github.com/mapquery/mapquery/wiki/_pages http://projectes.lafarga.cat/projects/navmapesmiramon/ http://trac.openlayers.org/wiki/Documentation http://openscales.org/documentation/index.html http://svn.pmapper.net/trac/wiki https://github.com/qgis/qgis-web-client/blob/master/README https://github.com/gwaldron/godzi-webgl/wiki/ReadyMap-SDK http://slmapviewer.codeplex.com/documentation http://www.timemap.net/index.php?option=com_content&task=view&id=169&Itemid=94 http://www.mapserver.org/documentation.html 9 http://code.google.com/p/webgispublic/w/list http://worldkit.org/doc/
http://www.cartoweb.org/doc/cw3.5/xhtml/intro.feature.html http://trac.osgeo.org/fusion/wiki/Widgets http://geoikia.idgis.eu/wiki-english/index.php/Overview_of_all_buttons http://www.geomajas.org/geomajas-functional-overview http://www.gisclient.org/documentazione/flayer1.pdf/at_download/file http://code.google.com/p/gbif-geospatial/wiki/Admin#Features http://code.google.com/p/geoext-viewer/#Features http://www.bnhelp.cz/produkty/mapy-na-webu/ http://mapas.mma.gov.br/i3geo/ajuda_usuario.php http://wiki.deegree.org/deegreeWiki/WebClients#iGeoPortal http://ka-map.ominiverdi.org/wiki/index.php/Main_Page#Features http://kvwmap.geoinformatik.uni-rostock.de/index.php/Dokumentation#Funktionalit.C3.A4t_im_Client http://leaflet.cloudmade.com/features.html https://www.legato.net/display/LEGATO/Features+and+USPs http://www.mapbender.org/What_is_Mapbender http://communitymapbuilder.osgeo.org/#Home-KeyFeatures http://mapfaces.codehaus.org/components.html http://mapguide.osgeo.org/features.html https://github.com/mapquery/mapquery/wiki/API-for-the-application-developer http://java.net/jira/browse/OL4JSF?selectedTab=com.atlassian.jira.plugin.system.project:Aroadmap-panel http://openscales.org/#features http://svn.pmapper.net/trac/wiki/HomeAbout http://www.gaiocorp.com/home/index.php?option= com_content&task=view&id=53&Itemid=65 http://www.timemap.net/index.php?option=com_content&task=view&id=172&Itemid=151 http://www.mapserver.org/about.html
http://e-atlas.org.au/atlasmapperdemo http://www.cartoweb.org/demo.html http://chameleon.maptools.org/index.phtml?page=twiki_application_gallery.html http://surveillance.mcgill.ca/dracones/examples/index.php http://flamingo.gbo-provincies.nl/wikis/voorbeelden/voorbeelden.aspx http://www.apps.geovista.psu.edu/FlexLayersDemo/FlexLayersDemo.html http://trac.osgeo.org/fusion/wiki/Gallery http://geoext.org/examples.html http://www.geoide.nl/index.php?option=com_content&view=section&layout=blog&id=5&Itemid=69&lang=en http://apps.geomajas.org/showcase http://www.geomoose.org/wiki/index.php/GeoMOOSE_Gallery http://www.gisclient.org/documenti/tutorial/gallery/ http://code.google.com/p/gbif-geospatial/wiki/Demos http://code.google.com/p/geoext-viewer/#Gallery http://geoportal.bnhelp.cz/map/?SID=&lang=eng http://mapas.mma.gov.br/download/exemplos http://demo.deegree.org http://ka-map.ominiverdi.org/wiki/index.php/Links_to_some_ka-Map_applications http://kvwmap.geoinformatik.uni-rostock.de/index.php/Screenshots http://leaflet.cloudmade.com/examples.html https://www.legato.net/display/LEGATO/Gallery http://www.mapbender.org/Mapbender_Gallery http://communitymapbuilder.osgeo.org/display/MAP/Examples http://mapfaces.codehaus.org/examples.html http://demo.mapfish.org/mapfishsample/2.0/ http://data.mapguide.com/mapguide/phpviewersample/ajaxtiledviewersample.php http://mapquery.org/demo http://www.creaf.uab.es/miramon/mmn/17-06-2008/exemple/index.htm?LANGUAGE=eng http://www.keck-atlas.de/keck-atlas/indikatoren/ http://openlayers.org/dev/examples/ http://openscales.org/demo/index.html http://www.pmapper.net/gallery.shtml http://webgis.uster.ch http://demo.pelicanmapping.com/rmweb/webgl/tests/index.html http://www.timemap.net/index.php?option=com_content&task=view&id=32&Itemid=146 http://www.mapserver.org/introduction.html#gallery http://www.wololo.org/webgispublic/example.html http://worldkit.org/examples.php

NOTAS CON RESPECTO A LA COMPARACIÓN

  • Los datos correspondientes a los clientes fueron recogidos directamente de sus sitios web y posteriormente se validaron a través de listas de correos, foros o correo electrónico.
  • Las celdas en blanco indican datos que no se pudieron recoger.
  • El apoyo de OSGeo se da cuando el proyecto se gradúa del proceso de incubación, por lo cual los proyectos que están en la incubadora no son proyectos oficiales de OSGeo y no reciben su soporte. (Ver: http://www.osgeo.org/node/343)

CONCLUSIÓN

Además de presentar una descripción general, datos técnicos y enlaces relevantes de los clientes web, se ha examinado la relación que existe entre ellos y se han categorizado para diferenciarlos.

Se observó que existe abundancia de proyectos libres para construir clientes web de servicios web geográficos, algunos muy profesionales y elaborados que permiten realizar una gestión integral de la información y que reciben soporte de OSGeo debido a que involucran eficientemente a toda una comunidad; otros, resultado de esfuerzos individuales destacados que cumplen necesidades básicas. Algunos han desaparecido por duplicación de esfuerzos y otros han tomado como base desarrollos previos para ampliar sus alcances funcionales.

AGRADECIMIENTOS

El autor agradece a los miembros del Capítulo Local de la comunidad hispanohablante de OSGeo: Jorge Sanz, Lorenzo Becchi, y Evaristo Gestoso; a Paolo Cavallini de Faunalia; a Bob Basques; a los miembros de GeoTux: William Guerrero, Remy Galán, Samuel Mesa; y finalmente al usuario Mavka; por su participación en la elaboración del estudio.

Tú puedes colaborar

Si ves algún error u omisión en la comparación por favor comunicámelo y con prontitud haré la corrección. Si conoces algún otro cliente web y te gustaría verlo en la comparación escríbeme para investigarlo y anexarlo.

LICENCIA

Este artículo puede ser utilizado bajo la licencia “Attribution 2.5 Colombia”, obsérvala en este enlace: http://creativecommons.org/licenses/by/2.5/co/

REFERENCIAS

  • Página web oficial de cada proyecto (Ver parte 3 de la comparación, Enlaces de interés).