GeoNetwork and ESRI GIS Portal Toolkit Comparison and ESRI GIS Portal Toolkit Comparison ... require ArcGIS Server 9.3 Standard ... GeoNetwork and ESRI GIS Portal Toolkit Comparison ...

  • Published on

  • View

  • Download

Embed Size (px)


<ul><li><p>Information included in this document may not be disclosed to third parties unless with explicit written approval from ESRI Inc. </p><p>GeoNetwork and ESRI GIS Portal Toolkit Comparison The following software are being evaluated for the GeoSUR project for the implementation of GIS portal application for the South American region. The information collected for each software will be provided to the GeoSUR advisory board to be used for evaluation and selection of the portal software. General Requirements </p><p> ESRI GIS Portal Toolkit GeoNetwork OpenSource Recent Version 9.3 </p><p> 2.20 </p><p>Type Commercial. Current version of GIS Portal Toolkit is free as long as the ESRI training class is taken and the other prerequisite software is already purchased. Final licensing for GPT 9.3 is under discussion. GPT 9.3 will require ArcGIS Server 9.3 Standard Enterprise. </p><p>Free and Open Source </p><p>Operating System Red Hat Enterprise Linux AS/ES 4.0 Update 2 SUSE Linux Enterprise Server 10 Sun Solaris 9, 10 (SPARC) Windows 2000 SP4 Server Windows 2003 SP2 Server Windows Vista SP1 Ultimate, Enterprise, Business Windows XP SP2 Professional Edition </p><p>MS Windows Linux Mac OS X Potentially any Java Servlet environment </p><p>Hardware Requirements See recommended hardware requirements on </p><p>1 GHz or higher </p><p>Memory Requirement </p><p>See recommended hardware requirements on Note that this depends on deployment models and expected use. </p><p>512 MB memory or higher </p><p>Disk Requirement </p><p>See minimum disk space requirements on Note this will depend on type of DBMS, size of the catalog and size of the data used in the map service, gazetteer and optional data extraction service. </p><p>30 MB minimum / 250 suggested </p><p>Java Requirement Java 1.5 SDK is required. Either version 1.5.0_06 or 1.5.0_14 may be used </p><p>Java Runtime Environment (JRE 1.5.0) </p><p>Web Server IIS5, IIS6 or Apache 2.0.48 </p><p>NA, Apache or IIS can be configured to redirect traffic to the servlet engine </p><p>Servlet Engine Apache Tomcat 5.5.17 or 5.5.26. Note: other Servlet engines (IBM WebSphere, Oracle Application Server, Sun GlassFish, ServletExec, ) may be supported on a case-by-case basis per project requirements. </p><p>Apache Tomcat or Jetty </p><p>Database Oracle 9i Oracle 10g Microsoft SQL Server 2000 SP4 </p><p>JDBC Compliant DBMS such as MySQL PostgreSQL </p><p></p></li><li><p>Information included in this document may not be disclosed to third parties unless with explicit written approval from ESRI Inc. </p><p>Microsoft SQL Server 2005 SP2 PostgreSQL 8.3 </p><p>Oracle MS SQL Server </p><p>Other Required Software ArcGIS Server 9.3 Standard Enterprise (includes ArcSDE), ArcGIS Desktop is advised to author/manage oher services used in GPT and manage metadata, GPT 9.3 works with an LDAP user store and authentication service. Verified to work are: Apache Directory Server Sun OpenDS Microsoft ActiveDirectory Other LDAP servers may be supported on a case-by-case basis per project requirements. </p><p>NA Java applications included: Lucene Jeeves McKoi Jetty GeoServer Schematron InterMap </p><p>Required Apache Software Foundation Packages </p><p>Sun JSF Framework Sun Java Mail Sun JavaBeans Activation Framework Apache Commons Struts Tiles JSP Standard Tag Library Apache Commons File Upload Apache Commons IO JUnit Z39.50 Toolkit </p><p>NA </p><p>Supported Browsers GPT 9.3 supports IE 6+, FireFox, and Safari. </p><p>Firefox 1.5+, Internet Explorer Win v6+, Safari 3+ (Mac OS X Leopard) </p><p>Notes Common practice is to install Catalog Services and Metadata Viewer on dedicated server with Catalog Services database installed on separate dedicated server, however, everything can run on one machine. Alternatively, various services (basemap/searchmap/placefinder) may be used from ArcGIS Online and would thus not be hosted on the server, thus reducing the load on the server. These services are free of charge. </p><p>Common practice is to install all GeoNetwork components on a single machine. Could be distributed. Can interact with other GeoNetwork instances in a federated catalgoue environment </p><p> Standards Implementation </p><p> ESRI GIS Portal Toolkit GeoNetwork OpenSource Main Components Portal Module, Map Viewer, Administrator Module, Publisher </p><p>Module, CSW Client for ArcMap and ArcGIS Explorer, Harvesting Module </p><p>Metadata editor, metadata template system, user &amp; group management, harvesting management, backup management, map viewer, pdf map printing, sending WMC &amp; map preview by email, map server (GeoServer) </p><p>Metadata Standards FGDC, ISO 19115, ISO 19139, Dublin Core. Note: GPT 9.3 allows additional metadata profiles to be configured by the implementor of GPT without compiling. </p><p>ISO19139 (19115 &amp; 19119), FGDC, Dublin Core </p></li><li><p>Information included in this document may not be disclosed to third parties unless with explicit written approval from ESRI Inc. </p><p> Portal Acting as a Client </p><p>Metadata/Catalog: ArcIMS Metadata Server client, ISO 23950 with GEO Profile (ANSI Z39.50 with FGDC), Open Archives Initiative (OAI-PMH), OGC (ebRIM, OGCCORE, and APISO profiles as implemented by several vendors), Web Accessible Folder (WAF). Other Services: WMS, WFS/GML format conversion </p><p>Metadata/Catalog: Other GeoNetwork nodes, WebDav, CSW 2.0.2 ISO Metadata Application Profile, Open Archives Initiative (OAI-PMH), ISO 23950 with GEO Profile (ANSI Z39.50 with FGDC) Z39.50 client is included but currently disabled and being revised. WAF is supported via WebDAV </p><p>Portal Acting as a Service OGC WMS 1.1.1 that composites remote WMS requests, OGC CSW 2.0.1 server, ArcIMS Metadata Service, ISO 23950 GEO Profile service, OGC CSW 2.0.1 ebRIM Application Profile, OGC CSW 2.0.2 baseline, RSS/Atom </p><p>OGC WMS , OGC CSW 2.0.2 ISO Metadata Application Profile, ISO 23950 GEO Profile, OpenSearch protocol w/GeoRSS, RSS/Atom ** Will WFS, WCS or WMC be supported in the future? Yes, WMC is already. WFS and WCS will be supported through OpenLayers in the future </p><p>OGC Portal Reference Information on OGC portal information may be found at Since GIS Portal Toolkit 2.0 we have supported various OGC specs both as a client (WMS, WCS, WFS, WMC) and as a server (CSW). </p><p>Mostly - It now supports all components of the portal reference due to the embedded GeoServer map server </p><p>OGC Standards Compliance </p><p>GPT 9.3 is tested with WMS 1.0, 1.1, 1.1.1, 1.3 WFS 1.0, 1.1 WCS 1.0.0, 1.1.0, 1.1.1 WMC 1.1 KML 2.2 GeoRSS ESRI submits its software to OGC for interoperability certification. Certificates may be provided upon request. Additionally, GPT supports ArcIMS and ArcGIS Server map services </p><p>OGC WMS CSW 2.02 Reference implementation for CSW 2.0.1 and 2.0.2, GeoServer is reference implementation for WMS and WFS. It also supports WCS and KML output </p><p> Software Features </p><p> ESRI GIS Portal Toolkit GeoNetwork OpenSource Metadata Creation and Publication </p><p>1) Create metadata using ArcCatalog or any XML editor and upload to portal 2) Post metadata using portal online metadata entry form 3) Make metadata available on web server and register for harvesting GPT 9.3 includes a highly customizable metadata editor that can </p><p>Online editing of metadata with powerful template system. Scheduled harvesting and synchronization of metadata between catalogs 1) Create metadata using online editor 2) Upload XML 3) import or export MEF files that contain metadata, previews, data, </p><p></p></li><li><p>Information included in this document may not be disclosed to third parties unless with explicit written approval from ESRI Inc. </p><p>be configured by the implementing organization (without coding) to support arbitrary metadata standards and validation rules. GPT 9.3 will have a publishing tool for ArcCatalog that will go through a users folders and fetch metadata for resources that is then published to a GIS Portal. This includes files, personal geodatabases, as well as enterprise geodatabases. </p><p>privilege settings and categories </p><p>Metadata Validation Can validate against Dublin Core, FGDC, ISO 19115/ISO19139, ISO19119/ISO 19139. Publishers are informed of records that fail the validation. See above for additional profile support that may be configured by implementing organizations. </p><p>It validates structure against all metadata schemas (19139, FGDC and DC) and also allows for schematron validation rules to validate on content (this is a second step validation that goes well beyond just format validation) </p><p> Portal administrator can review and approve all technically validated metadata before final posting. Validation rules are configurable as part of the metadata schema definition. </p><p>Metadata can be approved via access constraints (ie, the portal administrator can restrict access to groups of users) Theres a user profile Content Reviewer that is allowed to publish content on the internet </p><p>Metadata Search &amp; Discovery </p><p>Searching metadata, sort results, relevance (both textual and spatial) </p><p>Free text search. Geographic Search. Can search on local and distributed catalogs. Sort on relevance, rating, popularity and change date. Discover through (geo)RSS search. Discover through social network bookmark sites (delicious, digit, facebook, stumbleupon) </p><p>Portal Topics Channel editor to provide access to key content, applications and events At GPT 9.3 the channel editor is replaced with integration with content management systems or Wiki software using Single Sign-on authentication when supported by the CMS software and leveraging the GPT REST interface </p><p>Allow to make an entry a featured map. Featured maps appear randomly on the front page </p><p>Types of Metadata Searches 1) Free text search 2) Geographic search 3) Thematic search, 4) Temporal search, 5) Resource type search Search is possible using a web interface, a OGC CSW interface, or a REST interface that supports the OpenSearch protocol ( </p><p>1) Free text search 2) Geographic search 3) Category search 4) Advanced search </p><p>Access to Spatial Resources Link Directly to URL, View information as live map, download data from implementors database. </p><p>View Metadata, Download Data, Interactive Map, Graphic Overviews, View OGC map services in Google Earth </p><p>Visualize Spatial Resources Portal map viewer uses distributed sources (combine WMS, WFS, WCS, ArcIMS, ArcGIS Server, GeoRSS), Save map views, change projection on fly, extensive query functionality, and map markup. </p><p>InterMap is java based map viewer which can use distributed sources. Save map views, open map views, send map views by email (all with annotations that can be added in the GUI). Direct access to Web Map Servers that can be preconfigured Cannot currently change projection on the fly but will be able to once OpenLayers is integrated. </p></li><li><p>Information included in this document may not be disclosed to third parties unless with explicit written approval from ESRI Inc. </p><p>Print Maps Printing maps are supported (using map templates), as well as exporting maps to SVG or as an image. </p><p>Online map layout generation - PDF export </p><p>Save Maps Save as a Web Map Context (WMC) file or save map to portal for reuse </p><p>Save as PDF Files, Save as Web Map Context (WMC) files </p><p>User Roles Administrators, Publishers, Channel Stewards, Registered users. Configurable in LDAP, so they can match existing organizational roles </p><p>Group and user management. Uses Privileges, roles and user groups. Administrator, User Administrator, Content Reviewer, Editor or Registered User </p><p>Data Security Publishers can designate if metadata is available to all users or to only specific groups of users. GPT 9.3 integrates with ArcGIS Server security capabilities and LDAP. </p><p>Fine grained access control </p><p>Customizable Interface Achieved through a series of installation specific file content value inputs and through resource file content that informs the basic toolkit functionality with graphics and text GPT 9.3 supports skins/themes that implement a user interface look-and-feel. Users may modify navigation elements, layout. Add custom topics etc. </p><p>Interface based on main components and a CSS files for toolbar graphics and HTML formatting. Achieved through XML transformation templates </p><p>Internationalization Interface can be translation to any language </p><p>Interface can be translated to any language </p><p>Available Language Packs Chinese, Dutch, French, German, Spanish </p><p>Translations available for English, French, Spanish, Italian, Dutch, German, Chinese, Arabic. Greek is coming and others may be out there in the community, but not in core yet. This includes translations done in Brazil for instance </p><p> General Features </p><p> ESRI GIS Portal Toolkit GeoNetwork OpenSource Ease of use (final user as well as administrator) </p><p>Simple vs advanced search. Hide functions not applicable to user, My searches/maps, consistent navigation, context sensitive help </p><p>Ajax based end used GUI should make interface more interactive. No popup windows </p><p>Skills needed to administer/upgrade the site (programmer, user with general ICT skills) </p><p>ESRI and its authorized trainers provide full supported training on configuration and managing GIS Portals as a user interface to SDI. There is a bigger picture beyond a GIS Portal that we address in these classes. Apart from a website, you need to consider why a GIS Portal is created and then support that. </p><p>General user skills via GUI for most functions. </p><p>Speed </p><p>GPT is used in GOS to deliver less than 3 second response times on a 200,000 item catalog. ESRI has a long history of providing system design advice to organizations across the world. This experience may be used to help clients determine </p><p>Search is based on Lucene indexes, making searches fast performing </p></li><li><p>Information included in this document may not be disclosed to third parties unless with explicit written approval from ESRI Inc. </p><p>the appropriate hardware architecture for a GIS Portal. This is not limited to search performance, but also covers availability, failover scenarios, certification and accreditation advise, integration into existing enterprise architectures, etc. </p><p>Possibility of incorporating or interacting with gazetteer services </p><p>Fully supported using ArcGIS Server locator service. This may be customized to support street address geocoding, single field geocoding, combinations, custom, etc. Gazetteer content may be exposed as OGC WFS Gazetteer Service (discussion paper) </p><p>Easy if available (instead of the fixed country selection box for instance) </p><p>Operational implementations (how many around the world?) </p><p>ESRI GIS Portal Toolkit is in use in over 50 production, non-prototype sites across the world. </p><p>Many. All over Europe in relation to INSPIRE, in the UN and the CGIAR, in Africa, chosen as main SDI component in a.o. Australia, Swiss, Net...</p></li></ul>


View more >