Release Notes Release Notes for ArcGIS for INSPIRE The Service Pack 1(SP1) provides updates on ArcGIS for INSPIRE version 1.0. This document contains a list of features and how the software with SP1 aligns with the INSPIRE regulations. It also lists the known issues for this product.
Standards and Conformity - Features General
Aligns with ArcGIS Server system architecture
Response streaming support between all layers:
Webtier – ArcGIS Server Object Extension
ArcGIS Server Object Extension – Feature Server backend
Convenient and flexible programming interface between Webtier and ArcGIS SOE tier
Webtier design prepared for any future web technology (SOAP x.y., REST, etc.) that may arise in INSPIRE context
Multi-lingual support for all components: INSPIRE Network Services, Administration/Configuration Pages, ArcMap INSPIRE Tools
Multi-linguality achievable without recompiling the code
Convenient administration/configuration UI within ArcCatalog
INSPIRE View Service Concerning INSPIRE View Services, the ArcGIS for INSPIRE provides:
Implementation of INSPIRE View Services following the Technical Guidance document 3.01 (seehttp://inspire.jrc.ec.europa.eu/documents/Network_Services/TechnicalGuidance_View Services_v3.0.pdf)
Support for GetFeatureInfo operation returning INSPIRE-conformant GML response on INSPIRE layers
Support for WMS 1.1.1 profile as described by Technical Guidance View Service 3.0
Support for INSPIRE style (SLD-based) and custom style (ArcMap Layout)
Style Layer Descriptor support for Annex I INSPIRE layers
Several bug fixes to ArcGIS Server WMS Extension
Support for both MXD and MSD based Map services
ArcMap INSPIRE Tools analyzes INSPIRE-compliant geodatabase layer and allows for immediately adding those to your map document
Combined knowledge about INSPIRE data models and Esri geodatabase implementation
Creates relates and joins automatically
Automatic support for all relevant INSPIRE reference systems
Support for all capabilities/metadata extension elements
Hides "technical" geodatabase layers, displays INSPIRE layers in capabilities metadata
INSPIRE Feature Download Service Concerning INSPIRE Feature Download Services, ArcGIS for INSPIRE provides:
Implementation of INSPIRE Feature Download Direct Access Service following “Draft Technical Guidance for INSPIRE Download Services”. This Draft Technical Guidance is based on the approved standard Web Feature Service 1.1 instead of the obsolete draft document ISO/DIS 19142. Support for the approved Web Feature Service 2.0 standard is currently planned for an upcoming release (seehttp://inspire.jrc.ec.europa.eu/documents/Network_Services/TechnicalGuidance_Disco veryServices_v3.0.pdf)
Full support for INSPIRE data models and GML output
Feature Server configuration for geodatabase and INSPIRE XML schema models
INSPIRE Feature Download Service: Pre-defined Dataset Service Concerning INSPIRE Pre-defined Dataset Services, ArcGIS for INSPIRE provides:
Implementation of INSPIRE Feature Download Pre-defined Dataset Services following “Draft Technical Guidance for INSPIRE Download Services”
Pre-defined Dataset Download Service is an extension to the Feature Download Service as this provides the functionality to execute queries specified by the user
Store queries
Store output files in the ArcGIS Server output folder
INSPIRE Annex I data models Esri Geodatabase implementation
Esri Geodatabase XML schema for INSPIRE Annex I Data themes
XML/HTML documentation on Geodatabase structure
INSPIRE Discovery Service, Geoportal Server Concerning INSPIRE Discovery Services, the ArcGIS for INSPIRE provides:
Implementation of INSPIRE Discovery Services following the Technical Guidance document 3.0
Improved Metadata editor that supports validation and editing of unbounded multiple instances of metadata elements
Known Issues ArcGIS for INSPIRE Desktop Extension Map Document .msd Support: During the configuration of an INSPIRE View Service it is necessary to gather detailed information about the map to be published. This is achieved in a programmatic way by investigating the underlying map document using the ArcObjects API. This approach works for all MXD-based map documents. However, ArcObjects currently does not provide a way to do this for MSD-based map documents. Workaround: The Administration page will check for a MXD document with the same name in the same folder as the MSD. So if an MXD file with the same data layers is saved to the MSD location, that can be read instead. This does not affect the service instance to be created. The View Service Configuration page just analyzes the MXD document for information on the available layers. ArcGIS for INSPIRE Server Extension View Service - GetFeatureInfo on mixed layer documents doesn't return a response for non-INSPIRE layers: If you request a GetFeatureInfo with a number of query layers > 1 layers that are from both INSPIRE layers & non-INSPIRE layers, the View Service does not return a response that is processed by WMS Server (non-INSPIRE layers); it only returns the responses from the Feature Server backend. View Service - Use of INSPIRE SLD Files: INSPIRE data specifications contain visualisation rules that are not expressible using SLD documents. Furthermore there may be differences in the rendering result if applying SLD documents on map services based on MXD documents or on MSD documents (different rendering engine used). Workaround: If ArcGIS for INSPIRE does not find an SLD document for a specific layer, it will use the ArcMap-defined visualisation rules and use them for both the INSPIRE:DEFAULT style and the default style. Feature Download Configuration - user interface displays all INSPIRE Layers: The Feature Download Configuration user interface analyzes the underlying Geodatabase schema and offers a list of INSPIRE Feature Types to be provided by the Feature Download Service. As the INSPIRE geodatabase contains feature classes and tables of all Annex I data themes, the Configuration user interface lists all INSPIRE Feature Types of Annex I although some of them might not contain data. Feature Download creation option appears when creating a Geodata Server via an mxd document:The Feature Download creation option appears when creating a Geodata server based on an mxd document. This is not a supported workflow. INSPIRE Geodatabase Template Profile of names and text strings: The INSPIRE data specification for Geographical Names allows for the implementation of a simplified profile of the complex data type GeographicalName. For many cases, a simple implementation is sufficient – and requires a significantly less complex model and database representation. In the standard geodatabase template for the Annex I themes, the simplest profile, a text string, has been implemented. For datasets which require support for a more complex profile, please contact Esri product support. Similarly, string-valued properties are limited to 255 characters in the standard geodatabase for the Annex I themes. This should be sufficient for most datasets; however, for datasets which require support for longer text values, please contact product support.
Arcs in Cadastral Parcel features: In the theme Cadastral Parcels, non-linear interpolations (circular arcs) are allowed. In this release, only geometries with linear interpolations in accordance with the Simple Feature standard ISO 19125-1 are supported.
Geoportal Server System Environment, Apache Tomcat: Apache Tomcat 6.0.13 and earlier not supported. If used, then when users access certain pages (Register Network Resource, the Search page), they'll be redirected to the Home Page. Logfile will show an error that the EL expression cannot be parsed. This is an issue with Apache Tomcat and not Geoportal code. Workaround is to use later version of Tomcat; recommended is version 6.0.24 and higher (but not Tomcat 7.x). User Management through Active Directory: Geoportal does not support registering new users through Register page or changing a password through the My Profile page if configured with Active Directory. Thumbnails with broken links: When the thumbnail in metadata is not found (eg., the link is broken), an empty image displays in the search result/details page. Thumbnails with partially encoded URL reference: In metadata, if the thumbnail URL references a partially encoded link (e.g., http://www.testserver.com/images/Note%20the%20encoding%20here/but no encoding here.JPG), the h:graphicImage java server faces component renders the link with plus signs in the spaces. Workaround is to use fully encoded URLs in thumbnail links. Using a partially encoded URL within the metadata document has issues: http://www.btm.ior.it/images/Immagini%20men%C3%B9%20di%20appoggio/Immagini scoliosi adulti.JPG Searching ArcGIS.com through federated search: Searching ArcGIS.com through federated search allows users to choose Live Data and extent for a search criteria, but these are not supported by ArcGIS.com. CDATA section in KML/KMZ: A KML and KMZ file having html code in the CDATA section as a description does not get rendered properly and shows the HTML string. Document titles in Search Results: When a document title is long with no spaces, HTML rendering does not wrap the title in search results. Point bounding boxes: If a bounding box for a metadata record consists of a point, the footprint on the search map for the metadata is not correct and shows a random bounding box. JVM calendars: The Geoportal calendar functions (selectable dates in a calendar on a form or search) does not work properly if a server is set with different locale in JVM such as Buddhist calendar. Apply Action to Result Set on Manage Metadata page: When the metadata status gets updated with the checkbox "Apply action to the entire result set", the status change gets updated in search and lucene index files when the next synchronization (to sync between lucene index and database) process run and finish. CSW Synchronisation: For the CSW protocol, incremental Synchronisation will not reharvest metadata that have been deleted from administration interface.
Last updated date and synchronisation: If a repository doesn't support last updated date info, Incremental synchronisation will act like full synchronisation.
