http://wiki.icaci.org/api.php?action=feedcontributions&user=Tebogo+Mokwena&feedformat=atomICA Wiki - User contributions [en]2024-03-28T12:25:32ZUser contributionsMediaWiki 1.35.1http://wiki.icaci.org/index.php?title=ISO_19115-2:2009_Geographic_information_-_Metadata_-_Part_2:_Extensions_for_imagery_and_gridded_data&diff=854ISO 19115-2:2009 Geographic information - Metadata - Part 2: Extensions for imagery and gridded data2016-06-24T11:02:50Z<p>Tebogo Mokwena: /* Overview */</p>
<hr />
<div>==Overview==<br />
{| class="wikitable"<br />
| Full name<br />
| [http://www.iso.org/iso/home/store/catalogue_tc/catalogue_detail.htm?csnumber=39229 ISO 19115-2:2009, Geographic information – Metadata – Part 2: Extensions for imagery and gridded data]<br />
|-<br />
| Version<br />
| Edition 1<br />
|-<br />
| Amendments<br />
| None<br />
|-<br />
| Corrigenda<br />
| None<br />
|-<br />
| Published by<br />
| ISO/TC 211<br />
|-<br />
| Languages<br />
| English, French<br />
|-<br />
| Online overview<br />
| https://www.iso.org/obp/ui/#iso:std:iso:19115:-2:ed-1:v1:en<br />
|-<br />
| Type of standard<br />
| ISO International Standard<br />
Application level<br />
|-<br />
| Related standard(s)<br />
|[http://wiki.icaci.org/index.php?title=Metadata ISO 19115:2003, Geographic information – Metadata] <br/>[http://wiki.icaci.org/index.php?title=Metadata_%E2%80%93_XML_schema_implementation ISO 19139:2007, Geographic information – Metadata – XML schema implementation]<br/>[http://wiki.icaci.org/index.php?title=Metadata_%E2%80%93_XML_schema_implementation_%E2%80%93_Part_2:_Extensions_for_imagery_and_gridded_data ISO/TS 19139-2:2012, Geographic information – Metadata – XML schema implementation – Part 2: Extensions for imagery and gridded data]<br />
|-<br />
| Application<br />
| The standard specifies how to document metadata for imagery and gridded data, which includes information on data quality, lineage, etc.<br />
|-<br />
| Conformance classes<br />
| Completeness<br/>Maximum occurrence<br/>Short name<br/>Data type<br/>Domain<br/>Schema<br/>Exclusiveness<br/>Definition<br/>Standard metadata<br/>Metadata profiles<br />
|}<br />
<br />
== Scope ==<br />
This part of ISO 19115 extends the existing geographic metadata standard by defining the schema required for describing imagery and gridded data. It provides information about the properties of the measuring equipment used to acquire the data, the geometry of the measuring process employed by the equipment, and the production process used to digitize the raw data. This extension deals with metadata needed to describe the derivation of geographic information from raw data, including the properties of the measuring system, and the numerical methods and computational procedures used in the derivation. The metadata required to address coverage data in general is addressed sufficiently in the general part of ISO 19115.<br />
<br />
== Implementation benefits ==<br />
ISO 19115-2:2009 is an extension of ISO 19115:2003, ''Geographic information – Metadata'', defining metadata for imagery and gridded data. As such, it needs to be used in conjunction with ISO 19115:2003, as the latter defines the metadata for the dataset in general and for coverages in general. ISO 19115-2:2009 defines the metadata for the measuring equipment used to acquire the data (such as a satellite-borne sensor), the geometry of the acquisition and the production processes to produce the dataset.<br />
<br />
As the revision of ISO 19115:2003, namely ISO 19115-1:2014, Geographic information – Metadata – Part 1: Fundamentals, has now been published, ISO 19115-2:2009 will need to be revised to benefit from ISO 19115-1:2014. The current version of ISO 19115-2:2009 will be deprecated when its revision is published, but will still be available because of the masses of legacy metadata conforming to ISO 19115-2:2009.<br />
<br />
== Implementation guidelines ==<br />
Implementing ISO 19115-2:2009 is essentially the same as implementing ISO 19115:2003 and it is also supported by a wide variety of proprietary and open-source GISs and stand-alone and web-based metadata editors. Note that ISO 19115-2:2009 refers to quality elements defined in ISO 19115:2003 and when ISO 19115-2:2009 is revised, these will refer to the quality elements now in ISO 19157:2013. To the metadata packages, entities and elements defined in ISO 19115:2003, ISO 19115-2:2009 adds the following:<br />
<br />
* '''Metadata entity set – Imagery''': the package MI_Metadata are for the acquisition information for the imagery or gridded data.<br />
* '''Data quality information''': imagery, coverage result, lineage and usability. For the imagery coverage result, QE_CoverageResult consists of the spatial representation, coverage description and data format, which are all defined in ISO 19115:2003. This is necessary because the actual spatial representation of the imagery or gridded data might differ from that of its related coverage (e.g. if the coverage is computed from a subset of the whole dataset). This is coupled with MX_DataFile, which is defined in ISO 19139:2007, Geographic information – Metadata – XML schema implementation, and is a description of the transfer dataset in XML. For usability, QE_Useability specifies the degree of adherence of the dataset to a specific set of user requirements. For the extensions to lineage, there are six new classes specified: LE_Source (input and output datasets), LE_ProcessStep (the event or transformation of the process step from one version of the dataset to the next), LE_ProcessStepReport (the report produced by the process step), LE_Processing (the procedures, processes and algorithms applied during the process step), LE_Algorithm (methodology for obtaining geospatial data from the instrument readings) and LE_NominalResolution (scanning and ground resolution).<br />
* '''Spatial representation information – Imagery''': extension to georectified and georeferenceable classes, and ground control point quality. MI_GCP specifies a ground control point, which can have its data quality specified using the data quality elements in ISO 19115:2003. MI_GCPCollection is then a designated set of GCPs, which MI_GeolocationInformation uses to determine geographic location corresponding to image location. MI_Georeferenceable uses MI_GeolocationInformation to allow the geographic or map locations of the raster points to be located. MI_Georectified uses MI_GCP to provide checkpoints.<br />
* '''Content information – Imagery''': further details of the coverage, imagery, band, polarisation, transfer function and range element. MI_Band provides details of the wavelength band, its boundaries, nominal spatial resolution, transfer function for scaling, and transmitted and detected polarization. MI_CoverageDescription and MI_ImageDescription describe the specific range elements of the coverage and image respectively, using MI_RangeElementDescription, which names and describes the range elements (the range of a sensor is across its track, so the elements in the range should be the same for each sweep of the sensor).<br />
<br />
'''Acquisition information – Imagery''': further details of the platform, plan, instrument, operation, environmental record, objective and requirement. MI_EnvironmentalRecord documents the air temperature, relative humidity, maximum altitude and other meteorological conditions for photo flights. MI_Event documents the trigger, context, sequence and time of a significant collection point for an objective and pass of an instrument. MI_Instrument documents a particular instrument. MI_Objective documents the priority, type, function, spatial and temporal extents, and events of a target for a pass of an instrument. MI_Operation documents the status, type and other details of the plan and platform for an operation, including its relationships with possible child and parent operations. MI_Plan documents the type, status and authority of a plan, the activities that satisfy the plan and the requirement satisfied by the plan. MI_Platform documents a platform, including its sensors and sponsor. MI_PlatformPass documents the collection coverage of a pass. MI_RequestedDate documents the preferred and latest date and time for a desired collection. MI_Requirement documents the requirements to be satisfied by the planned data acquisition, including the requestor, recipient, priority and dates.</div>Tebogo Mokwenahttp://wiki.icaci.org/index.php?title=ISO_15836:2009_Information_and_documentation_-_The_Dublin_Core_metadata_element_set&diff=853ISO 15836:2009 Information and documentation - The Dublin Core metadata element set2016-06-24T11:00:52Z<p>Tebogo Mokwena: /* Overview of ISO 15836:2009 */</p>
<hr />
<div>== Overview of ISO 15836:2009 ==<br />
<br />
{| class="wikitable"<br />
| Full name<br />
| [http://www.iso.org/iso/home/store/catalogue_tc/catalogue_detail.htm?csnumber=52142 ISO 15836:2009, Information and documentation – The Dublin Core metadata element set]<br />
|-<br />
| Version<br />
| Edition 2<br />
|-<br />
| Amendments<br />
| None<br />
|-<br />
| Corrigenda<br />
| None<br />
|-<br />
| Published by<br />
| ISO/TC 46/SC 4<br />
|-<br />
| Languages<br />
| English, French<br />
|-<br />
| Online overview<br />
| https://www.iso.org/obp/ui/#iso:std:iso:15836:ed-2:v1:en<br />
|-<br />
| Type of standard<br />
| ISO International Standard Application level<br />
|-<br />
| Related standard(s) <br />
| [http://wiki.icaci.org/index.php?title=Metadata ISO 19115:2003, Geographic information -- Metadata]<br />
|-<br />
| Application <br />
| This standard specifies how to document metadata for a wide variety of resources.<br />
|-<br />
| Conformance classes<br />
| None<br />
|}<br />
<br />
== Scope ==<br />
<br />
ISO 15836:2009 establishes a standard for cross-domain resource description, known as the Dublin Core Metadata Element Set. Like RFC 3986, this International Standard does not limit what might be a resource.<br />
<br />
ISO 15836:2009 defines the elements typically used in the context of an application profile, which constrains or specifies their use in accordance with local or community-based requirements and policies. However, it does not define implementation detail, which is outside the scope of ISO 15836:2009.<br />
<br />
== Implementation benefits ==<br />
<br />
Because ISO 15836 is so popular, it is probably useful for providing high-level metadata of the likes of a dataset series (e.g. a national medium scale mapping series), so that it can be documented with other resources within the organisation. However, because it uses free text and is at a high level, it is difficult to use effectively any such metadata describing an individual geo-spatial dataset, never mind describing individual features within the dataset.<br />
<br />
== Implementation guidelines ==<br />
<br />
ISO 15836:2009 is very short (only 13 pages) and hence easy to understand. It is widely used for describing documents and other resources, not only within the library community (where it originated). It specifies 15 metadata elements (properties) for describing a resource, which are documented using free text: title, creator, subject, description, publisher, contributor, date, type, format, identifier, source, language, relation, coverage and rights. This makes it easy to write Dublin Core metadata (any text will conform to the standard), but very difficult to automate metadata operations.<br />
<br />
However, ISO 15836:2009 is essentially only the high-level framework for metadata (the 15 metadata elements listed in the previous paragraph) and the Dublin Core Metadata Initiative (DCMI) has developed many other resources built on it, such as more-detailed metadata vocabularies, encodings, resource classes, profiles and tools. DCMI has also done much work on embedding Dublin Core metadata into the work of the World Wide Web Consortium (W3C), particularly implementing Dublin Core in RDF (Resource Description Framework) for supporting linked data. For more details and resources, see: [[http://dublincore.org/]].</div>Tebogo Mokwenahttp://wiki.icaci.org/index.php?title=IHO_Standards_for_Hydrographic_Surveys&diff=852IHO Standards for Hydrographic Surveys2016-06-24T10:59:32Z<p>Tebogo Mokwena: /* Overview */</p>
<hr />
<div>==Overview==<br />
{| class="wikitable"<br />
| Full name<br />
| [http://www.iho.int/iho_pubs/standard/S-44_5E.pdf S-44, Standards for Hydrographic Surveys]<br />
|-<br />
| Version<br />
| Edition 5<br />
|-<br />
| Amendments<br />
| None<br />
|-<br />
| Corrigenda<br />
| None<br />
|-<br />
| Published by<br />
| IHO<br />
|-<br />
| Languages<br />
| English, French, Spanish, Portuguese<br />
|-<br />
| Online overview<br />
| http://iho.int/iho_pubs/standard/S-44_5E.pdf<br />
|-<br />
| Type of standard<br />
| IHO International Standard <br/> Meta level<br />
|-<br />
| Related standard(s)<br />
| [http://wiki.icaci.org/index.php?title=Metadata ISO 19115:2003, Geographic information – Metadata] <br/> S-100 IHO Universal Hydrographic Data Model <br/>[http://wiki.icaci.org/index.php?title=IHO_Standards_for_Hydrographic_Surveys S-44, Standards for Hydrographic Surveys] <br/>ISO/IEC 98:1995 Guide to the expression of uncertainty in measurement <br/>ISO/IEC 99:2007 International Vocabulary of Metrology – Basic and general concepts and associated terms (VIM)<br />
|-<br />
| Application<br />
| S-44 sets the minimum requirements for surveys conducted for the safety of surface navigation.<br />
|-<br />
| Conformance classes<br />
| None specified<br />
|}<br />
<br />
==Scope==<br />
This publication is designed to provide a set of standards for the execution of hydrographical surveys for the collection of data, which will primarily be used to compile navigational charts to be used for the safety of surface navigation and the protection of the marine environment.<br />
<br />
It must be realised that this publication only provides the minimum standards that are to be achieved. Where the bathymetry and expected shipping use requires it, hydrographical offices / organisations wishing to gather data may need to define more stringent standards. Also, this publication does not contain procedures for setting up the necessary equipment, for conducting the survey or for processing the resultant data. These procedures (which are a fundamental part of the complete survey system) must be developed by the hydrographical office/organisation wishing to gather data that is compliant with these Standards. Consideration must be made of the order of survey they wish to achieve, the equipment they have at their disposal and the type of topography that they intend to survey. Annexes A and B provide guidelines for Quality control and Data Processing and it is intended that these will be moved to the Manual on Hydrography (IHO Publication M-13) which provides further guidance on how to perform hydrographical surveys.<br />
<br />
There is nothing to stop users adopting these Standards for other uses. Indeed, such a broadening of the use of these Standards is welcomed. However, users who wish to adopt these for other means must bear in mind the reason why they were written and therefore accept that not all parts may be suitable for their specific needs.<br />
<br />
To be compliant with an S-44 Order a survey must be compliant with ALL specifications for that order included in these Standards.<br />
<br />
It is also important to note that the adequacy of a survey is the end product of the entire survey system and processes used during its collection. The uncertainties quoted in the following chapters reflect the total propagated uncertainties of all parts of the system. Simply using a piece of equipment that is theoretically capable of meeting the required uncertainty is not necessarily sufficient to meet the requirements of these Standards. How the equipment is set up, used and how it interacts with the other components in the complete survey system must all be taken into consideration.<br />
<br />
All components and their combination must be capable of providing data to the required standard. The hydrographical office / organisation needs to satisfy itself that this is so by, for example, conducting appropriate trials with the equipment to be used and by ensuring that adequate calibrations are performed prior to, as well as during and, if appropriate, after the survey being carried out. The surveyor is an essential component of the survey process and must possess sufficient knowledge and experience to be able to operate the system to the required standard. Measuring this can be difficult although surveying qualifications (e.g. having passed an IHO Cat A/B recognised hydrographical surveying course) may be of considerable benefit in making this assessment.<br />
<br />
It should be noted that the issue of this new edition to the standard does not invalidate surveys, or the charts and nautical publications based on them, conducted in accordance with previous editions, but rather sets the standards for future data collection to better respond to user needs.<br />
<br />
It should also be noted that where the sea floor is dynamic (e.g. sand waves), surveys conducted to any of the Orders in these Standards would quickly become out-dated. Such areas need to be resurveyed at regular intervals to ensure that the survey data remains valid. The intervals between these resurveys, which will depend on the local conditions, should be determined by national authorities.<br />
<br />
==Implementation benefits==<br />
The requirements set out in S-44 are of great importance to improve the safety of navigation. The data captured by hydrographical surveys are used to compile navigational charts. These navigational charts are used for surface navigation and the protection of the marine environment. S-44 defines four types of order of surveys and the measurements and observations required to ensure that navigational charts of the highest quality and standardized worldwide.<br />
<br />
==Implementation guidelines==<br />
First to be addressed by the IHO standards for hydrographical surveys (S-44) is the Classification of surveys. This chapter specifies the orders of survey that are acceptable to allow hydrographical offices or organisations to produce navigational products. The navigational products will allow the expected shipping to navigate safely across the area surveyed. Due to varying requirements four types of orders of survey are defined:<br />
<br />
:#Special Order is the most rigorous and is only intended for areas where under-keel clearance is critical. Its type of order requires the full sea floor to be searched and the size of feature to be detected is kept small.<br />
:#Order 1a is intended for areas where the sea is sufficiently shallow to allow natural or man-made features on the seabed to be of concern to the type of surface shipping expected to transit. Under-keel clearance is not as critical. Order 1a also requires a full sea floor search, however the size of the feature to be detected are larger than for Special Order. Order 1a surveys may be limited to water shallower than 100 metres.<br />
:#Order 1b is meant for areas shallower than 100 metres where the general depiction of the seabed is considered adequate for the type of surface shipping expected to transit the area. Some features may be missed, since a full sea floor search is not required. This order of survey is only recommended where under-keel clearance is not required.<br />
:#Order 2 is intended for areas where the water depth is such that a general depiction of the seabed is considered adequate. A full sea floor search is not required. This order of survey is recommended for water deeper than 100 metres.<br />
<br />
Positions should be referenced to a geocentric reference frame based on the International Terrestrial Reference System (ITRS), for example WGS84. Uncertainty of a position is the uncertainty at the position of the sounding or feature within the geodetic reference frame. S-44 further sets out the requirements for the horizontal uncertainty of features significant to navigation, the coastline and topographic features.<br />
<br />
The navigation of vessels requires accurate knowledge of the water depth in order to exploit safely the maximum cargo carrying capacity, and the maximum available water for safe navigation. The measured depths and drying heights shall be referenced to a vertical datum that is compatible with the products to be made or updated from the survey. S-44 specifies the requirements for the following depth measurements: vertical uncertainty, water-level observations, depth measurement, feature detection, and sounding density.<br />
<br />
Other measurements standardized by S-44 are seabed sampling, chart and land survey vertical datum connection, and tidal prediction. These measurements are not required for all order of surveys.<br />
<br />
S-44 recommends the use of S-100 IHO Universal Hydrographic Data Model to perform a comprehensive assessment of the quality of the data. If a Bathymetric Model is required, the metadata should include the following: model resolution, computational model, underlying data density, uncertainty estimate, and a description of the underlying data. The Report of Survey shall provide a clear and comprehensive account of how the survey was performed, the results, the difficulties encountered, and the shortcomings. The report is the means by which the Surveyor in charge approves the survey record.<br />
<br />
To improve the safety of navigation, it is desirable to eliminate doubtful data. This is achieved through carefully defining the area to be searched and subsequently surveying that area according to the standards outlined in S-44.</div>Tebogo Mokwenahttp://wiki.icaci.org/index.php?title=S-100_IHO_Universal_hydrographic_data_model&diff=851S-100 IHO Universal hydrographic data model2016-06-24T10:58:42Z<p>Tebogo Mokwena: /* Overview */</p>
<hr />
<div>==Overview==<br />
{| class="wikitable"<br />
| Full name<br />
| [http://www.iho.int/iho_pubs/standard/S-100/S-100_Ed_2/S_100_V2.0.0_June-2015.pdf S-100, IHO Universal hydrographic data model]<br />
|-<br />
| Version<br />
| Edition 1.0.0<br />
|-<br />
| Amendments<br />
| None<br />
|-<br />
| Corrigenda<br />
| None<br />
|-<br />
| Published by<br />
| IHO<br />
|-<br />
| Languages<br />
| English<br />
|-<br />
| Online overview<br />
| http://iho.int/iho_pubs/standard/S-100/S-100_Version_1.0.0.zip<br />
|-<br />
| Type of standard<br />
| IHO International Standard <br/> Meta level<br />
|-<br />
| Related standard(s)<br />
| [http://wiki.icaci.org/index.php?title=Conceptual_schema_language ISO/TS 19103:2005, Geographic information – Conceptual schema language] <br/>[http://wiki.icaci.org/index.php?title=Profiles ISO 19106:2004, Geographic information – Profiles] <br/>[http://wiki.icaci.org/index.php?title=Spatial_schema ISO 19107:2003, Geographic information – Spatial schema] <br/>[http://wiki.icaci.org/index.php?title=Rules_for_application_schema ISO 19109:2005, Geographic information – Rules for application schema] <br/>[http://wiki.icaci.org/index.php?title=Methodology_for_feature_cataloguing ISO 19110:2005, Geographic information – Methodology for feature cataloguing ]<br/>[http://wiki.icaci.org/index.php?title=Spatial_referencing_by_coordinates ISO 19111:2007, Geographic information – Spatial referencing by coordinates] <br/>[http://wiki.icaci.org/index.php?title=Metadata ISO 19115:2005, Geographic information – Metadata] <br/>[http://wiki.icaci.org/index.php?title=Metadata_%E2%80%93_Part_2:_Extensions_for_imagery_and_gridded_data ISO 19115-2:2009, Geographic information – Metadata – Part 2: Extensions for imagery and gridded data] <br/>[http://wiki.icaci.org/index.php?title=Portrayal ISO 19117:2012, Geographic information – Portrayal ]<br/> ISO 19118:2011, Geographic information – Encoding <br/>[http://wiki.icaci.org/index.php?title=Schema_for_coverage_geometry_and_functions ISO 19123:2005, Geographic information – Schema for coverage geometry and functions] <br/>[http://wiki.icaci.org/index.php?title=Feature_concept_dictionaries_and_registries ISO 19126:2009, Geographic Information – Feature concept dictionaries and registers] <br/>[http://wiki.icaci.org/index.php?title=Imagery,_gridded_and_coverage_data_framework ISO/TS 19129:2009, Geographic information – Imagery, Gridded and Coverage Data Framework] <br/> ISO 19130:2012, Geographic information – Sensor and data models for imagery and gridded data <br/>ISO 19135:2005, Geographic Information – Procedures for registration of items of geographic information <br/>[http://wiki.icaci.org/index.php?title=Data_quality ISO 19157:2013, Geographic information – Data quality] <br/>OMG Unified Modeling Language (OMG UML), Superstructure, V2.1.2 <br/> ISO 8601:2004, Data elements and interchange formats - Information interchange – Representation of dates and times <br/> ISO/IEC 8211:1994, Specification for a data descriptive file for information interchange Structure implementations <br/>ISO/IEC 12087-5:1998 - Computer graphics and image processing -- Image Processing and Interchange (IPI) - Functional Specification - Basic Image Interchange Format (BIIF) <br/>[http://wiki.icaci.org/index.php?title=JPEG_2000_image_coding_system:_Core_coding_system ISO/IEC 15444-13:2008 - Information Technology -- JPEG 2000 image coding system ]<br/> S-57 Cumulative Maintenance Document N°8 <br/>[http://wiki.icaci.org/index.php?title=Specifications_for_chart_content_and_display_aspects_of_ECDIS S-52 Specifications for Chart Content and Display Aspects of ECDIS ]<br/> S-61 Product Specification for Raster Navigational Charts (RNC) <br/>American National Standard T1.523-2001 - Telecommunications Glossary 2000 <br/><br />
|-<br />
| Application<br />
| S-100 specify the methods and tools for data management, processing, analysing, accessing, presenting and transferring of hydrographical or related data.<br />
|-<br />
| Conformance classes<br />
| None specified<br />
|-<br />
| Fundamental geospatial dataset<br />
| Category: ''Infrastructure'' <br/> Data Theme: ''Transportation''<br />
|}<br />
<br />
==Scope==<br />
S-100 – IHO Hydrographic Geospatial Standard for Marine Data and Information comprises twelve related parts that give the user the appropriate tools and framework to develop and maintain hydrographical related data, products and registers. These standards specify, for hydrographical and related information, methods and tools for data management, processing, analysing, accessing, presenting and transferring such data in digital/electronic form between different users, systems and locations. By following this set of geo-spatial hydrographical standards users will be able to build constituent parts of an S-100 compliant product specification.<br />
<br />
S-100 conforms as far as is reasonably possible to the ISO TC 211 series of geographic information standards, and where necessary has been tailored to suit hydrographical requirements.<br />
<br />
S-100 details the standard to be used for the exchange of hydrographical and related geospatial data between national hydrographical offices as well as between other organisations and for its distribution to manufacturers, mariners and other data users.<br />
<br />
S-100 comprises multiple parts that profile standards developed by the ISO Technical Committee 211. ISO TC 211 is responsible for the ISO series of standards for geographic information. The objective is that, together, the standards will form a framework for the development of sector specific applications that use geographic information. S-100 is an example of such an application.<br />
<br />
This standard specifies the procedures to be followed for:<br />
<br />
:#establishing and maintaining registers of hydrographical and related information;<br />
:#creating product specifications, feature catalogues and a definition of the general feature model;<br />
:#using spatial, imagery and gridded data, and metadata specifically aimed at fulfilling hydrographical requirements.<br />
<br />
==Implementation benefits==<br />
S-100 covers a wide range of activities with the hope of harmonizing them for hydrographical data and ensuring interoperability. The profiles define a subset of requirements that are specific for hydrographical data, but ensure interoperability with other data sources. Each profile would have its own implementation benefits, for example, the metadata profile defines a metadata schema for hydrographical data and extends the ISO 19115 for this application to ensure that all the aspects of hydrographical data are covered in the profile.<br />
<br />
==Implementation guidelines==<br />
S-100 was developed to align and exploit ISO/TC 211 standards to support a variety of data formats, products and customers. The data model will allow the development of new applications that leverage the new technologies and reaches beyond the traditional scope of hydrographical applications. S-100 encapsulates the use of best practice methods and procedures by including guidelines on implementing efficient production methods, optimizing the quality of products and services, and enabling interoperability through common interfaces.<br />
<br />
S-100 specifies a framework of components that can be used by interested communities to develop their own maritime geo-spatial products and services. S-100 consists of eleven profiles of ISO/TC 211 standards:<br />
<br />
#Conceptual Schema Language<br/>The first part of S-100 specifies a CSL and basic types that shall be used within the IHO community. The CSL is defined as a combination of UML and a set of basic data type definitions for specification of geographic information. Guidelines on the use of UML to create standardized geographic information and service models are also provided. Basic knowledge of the Object Management Group (OMG) UML is required to understand and implement the CSL profile.<br />
#Management of IHO Geospatial Information Registries<br/>The management of IHO geo-spatial information registries profile specifies the procedures that shall be followed when maintaining and publishing registers of unique, unambiguous and permanent identifiers assigned to items of geographic, hydrographical and metadata information. The roles and responsibilities for management of a registry and its registers are defined and described.<br/>This part also specifies a feature concept dictionary registers. A FCD specifies hydrographical definitions that may be used to describe geographic information. Such a register will improve the IHO’s ability to manage and extend multiple products based on S-100.<br />
#General Feature Model and Rules for Application Schema <br/>The General Feature Model defines a conceptual model of features, their characteristics and associations, and the rules for developing an application schema. This part further deals with conceptual modelling of features and their properties, conceptual modelling of information types and associated attributes, and the development of application schemas and the related rules for such a schema.<br />
#Metadata <br/>The S-100 metadata profile described is divided into three parts and provides specifications for describing, validating and exchanging metadata of data produced by hydrographical organisations. This profile is based on ISO 19115:2003, ISO 19115-2:2006, and ISO 19139:2007. The primary intent of this profile is to describe digital geo-spatial data. However, it can also be used for other products, such as charts, maps, images, textual documents and non-geographic resources. The profile is not limited to ISO 19115 since it can be extended to include additional resources.<br />
#Feature Catalogue<br/>The feature catalogue specifies a framework for organisation and reporting the classification of real world phenomena as geographic data. It defines the methodology for classification of the feature types and specifies how they are organised in a feature catalogue and presented to the users of a set of geographic data. A feature catalogue shall be defined for each product specification. This profile is for defining geographic features at the type level.<br />
#Coordinate Reference Systems<br/>The location of an object shall be defined by means of coordinates, which relate to the feature’s position. This profile describes the elements required to define the referencing by means of coordinate systems and datums. A conceptual schema for describing spatial referencing by coordinates and the minimum requirements for multi-dimensional spatial coordinate references are defined.<br />
#Spatial Schemas <br/> S-100 spatial schema requirements are less comprehensive than ISO 19107, which contains all the information necessary for describing and manipulating the spatial characteristics of geographic features. This part is only a profile of ISO 19107 and contains thus only a subset of the classes. The profile added additional constraints (omitted optional elements or constrained cardinalities) for hydrographical data.<br />
#Imagery and Gridded data <br/>Imagery and gridded data have become common forms of geographic data and there exist many external standards designed to handle such data. S-100 shall not preclude compatibility with external sources of data. This profile aligns with the ISO/TC 211 standards on imagery and gridded data in order to support multiple sources of data and uses the common information structures. This allows the data to be combined with various other data types. This part defines specific grid organisations to be used for hydrographical data and images associated with hydrographical data. Both simple grids and complex multidimensional grids are defined, as well as point sets and TINs.<br />
#Portrayal<br/>Portrayal is not included in this version of S-100 and will be developed at a later date.<br />
#Encoding Formats<br/>S-100 does not mandate particular encoding formats. The developer of a product specification can decide on suitable encoding standards and shall then document their chosen format. Encoding is complicated because numerous encoding standards are available. The parts provide guidelines on the selection and documentation of an encoding format.<br />
#Product Specification<br/>A data product specification defines a geo-spatial data product, and describes all the features, attributes and relationships of a given application and their mapping to a dataset. This part describes data product specifications for hydrographical requirements for geographic data products. Its aim is to provide a clear and similar structure for any data product specification to be written.</div>Tebogo Mokwenahttp://wiki.icaci.org/index.php?title=ISO_14825:2011_Intelligent_transport_systems_-_Geographic_Data_Files_(GDF)_-_GDF5.0&diff=850ISO 14825:2011 Intelligent transport systems - Geographic Data Files (GDF) - GDF5.02016-06-24T10:57:49Z<p>Tebogo Mokwena: /* Overview */</p>
<hr />
<div>==Overview==<br />
{| class="wikitable"<br />
| Full name<br />
| [http://www.iso.org/iso/home/store/catalogue_tc/catalogue_detail.htm?csnumber=54610 ISO 14825:2011, Intelligent transport systems – Geographic Data Files (GDF) – GDF5.0]<br />
|-<br />
| Version<br />
| Edition 2<br />
|-<br />
| Amendments<br />
| None<br />
|-<br />
| Corrigenda<br />
| None<br />
|-<br />
| Published by<br />
| ISO/TC 204, Intelligent transport systems<br />
|-<br />
| Languages<br />
| English<br />
|-<br />
| Online overview<br />
| Not available yet<br />
|-<br />
| Type of standard<br />
| ISO International Standard <br/> Application level<br />
|-<br />
| Related standard(s)<br />
| ISO 14813-1:2015, Intelligent transport systems – Reference model architecture(s) for the <br/>ITS sector, ITS service domains, service groups and services <br/> ISO 17572-1:2008, Intelligent transport systems (ITS) – Location referencing for <br/>geographic databases, General requirements and conceptual model <br/>ISO 17572-2:2015, Intelligent transport systems (ITS) – Location referencing for <br/>geographic databases, Pre-coded location references (pre-coded profile) <br/>[http://wiki.icaci.org/index.php?title=Metadata ISO 19115:2003, Geographic information – Metadata] <br/> ISO 19132:2007, Geographic information – Location-based services – Reference model <br/> ISO/DIS 19147:2015, Geographic information – Transfer nodes<br />
|-<br />
| Application<br />
| Exchange of data for intelligent transport systems, automotive navigation systems, traffic, <br/>fleet and dispatch management, road traffic analysis, automatic vehicle location and other <br/>transport applications.<br />
|-<br />
| Conformance classes<br />
| None specified<br />
|-<br />
| Fundamental geospatial dataset<br />
| Category: ''Infrastructure'' <br/> Data Theme: ''Transportation''<br />
|}<br />
<br />
==Scope==<br />
ISO 14825:2011 specifies the conceptual and logical data model and physical encoding formats for geographic databases for Intelligent Transport Systems (ITS) applications and services. It includes a specification of potential contents of such databases (data dictionaries for Features, Attributes and Relationships), a specification of how these contents shall be represented, and of how relevant information about the database itself can be specified (metadata).<br />
<br />
The focus of ISO 14825:2011 is on ITS applications and services and it emphasises road and road related information. ITS applications and services, however, also require information in addition to road and road related information.<br />
<br />
EXAMPLE 1 ITS applications and services need information about addressing systems in order to specify locations and/or destinations. Consequently, information about the administrative and postal subdivisions of an area is essential.<br />
<br />
EXAMPLE 2 Map display is an important component of ITS applications and services. For proper map display, the inclusion of contextual information such as land and water cover is essential.<br />
<br />
EXAMPLE 3 Point-of-Interest (POI) or service information is a key feature of traveller information. It adds value to end-user ITS applications and services.<br />
<br />
The Conceptual Data Model has a broader focus than ITS applications and services. It is application independent, with observance for harmonization of this International Standard with other geographic database standards.<br />
<br />
==Implementation benefits==<br />
ISO 14825:2011 is widely used for intelligent transport systems (ITS) and related applications, and services, by vehicle manufacturers, electronic components manufacturers, manufacturers of global positioning system receivers, and geospatial data vendors. Note that while the geospatial data might be distributed using GDF, it is typically encoded into proprietary formats for more efficient processing within navigation systems and other components.<br />
<br />
ISO 14825:2011 has been harmonised with the relevant ISO/TC 211 standards and includes all the core metadata defined in ISO 19115:2003.<br />
<br />
However, it does not appear that GDF is used much for other types of applications.<br />
<br />
==Implementation guidelines==<br />
ISO 14825:2011 is a very large document (over 1200 pages), as in addition to the data format (physical encoding), it includes the conceptual and logical data models, media record specifications, XML schema specifications, SQL encoding specifications, rules for data capture and portrayal, metadata and a comprehensive feature catalogue (classification system) with attributes, relationships and extensive code lists. The standard also includes annexes with extensive examples of how to use GDF, such as for complex time domains and generalizing networks. However, it is not clear why the standard has an annex duplicating ISO 639-2, Codes for the Representation of Names of Languages Part 2: Alpha-3 Code (as it was on 3 March 2009), and ISO 3166-1, Codes for the representation of names of countries and their subdivisions — Part 1: Country codes (as it was on 17 October 2008). Both ISO 639-2 and ISO 3166-1 are updated from time to time and freely available on the ISO website.<br />
<br />
While very large, ISO 14825:2011 is probably relatively easy (though rather tedious) to implement, as it has extensive definitions, descriptions and illustrations, and snippets of pseudo-code and XML. However, it is probably only of interest to those implementing intelligent transport systems (ITS) and related transport applications.</div>Tebogo Mokwenahttp://wiki.icaci.org/index.php?title=ISO/TS_19130:2010_Geographic_information_-_Imagery_sensor_models_for_geopositioning&diff=849ISO/TS 19130:2010 Geographic information - Imagery sensor models for geopositioning2016-06-24T10:56:13Z<p>Tebogo Mokwena: /* Overview */</p>
<hr />
<div>==Overview==<br />
{| class="wikitable"<br />
| Full name<br />
| [http://www.iso.org/iso/home/store/catalogue_tc/catalogue_detail.htm?csnumber=51789 ISO/TS 19130:2010, Geographic information – Imagery sensor models for geopositioning]<br />
|-<br />
| Version<br />
| Edition 1<br />
|-<br />
| Amendments<br />
| None<br />
|-<br />
| Corrigenda<br />
| None<br />
|-<br />
| Published by<br />
| ISO/TC 211<br />
|-<br />
| Languages<br />
| English<br />
|-<br />
| Online overview<br />
| Not available yet<br />
|-<br />
| Type of standard<br />
| ISO Technical Specification <br/> Meta level<br />
|-<br />
| Related standard(s)<br />
| [http://wiki.icaci.org/index.php?title=Metadata ISO 19115:2003, Geographic information – Metadata] <br/> [http://wiki.icaci.org/index.php?title=Metadata_%E2%80%93_Part_2:_Extensions_for_imagery_and_gridded_data ISO 19115-2:2009, Geographic information – Metadata – Part 2: Extensions for imagery and gridded data] <br/> ISO 19123:2005, Geographic information – Schema for coverage geometry and functions <br/> [http://wiki.icaci.org/index.php?title=Quality_assurance_of_data_supply ISO/TS 19138:2006, Geographic information – Data quality measures, which has been replaced by ISO/TC 19158:2012, Geographic information – Quality assurance of data supply]<br />
|-<br />
| Application<br />
| The technical specification defines sensor models and geopositioning metadata to support interoperability of imaging data between applications and to facilitate exchange of imaging data.<br />
|-<br />
| Correspondence Model<br />
| Correspondence Model <br/> Physical Model – Synthetic Aperture Radar <br/> Physical Model – Electro-optical <br/> True Replacement Model <br/> Ground Control Point collection<br />
|-<br />
| Fundamental geospatial dataset<br />
| Category: Base geography <br/> Data Theme: Rectified imagery<br />
|}<br />
<br />
==Scope==<br />
ISO/TS 19130:2010 identifies the information required to determine the relationship between the position of a remotely sensed pixel in image coordinates and its geoposition. It supports exploitation of remotely sensed images. It defines the metadata to be distributed with the image to enable user determination of geographic position from the observations.<br />
<br />
ISO/TS 19130:2010 specifies several ways in which information in support of geopositioning may be provided.<br />
<br />
#It may be provided as a sensor description with the associated physical and geometric information necessary to rigorously construct a Physical Sensor Model. For the case where precise geoposition information is needed, ISO/TS 19130:2010 identifies the mathematical formulae for rigorously constructing Physical Sensor Models that relate two-dimensional image space to three-dimensional ground space and the calculation of the associated propagated errors. ISO/TS 19130:2010 provides detailed information for three types of passive electro-optical/infrared (IR) sensors (frame, pushbroom and whiskbroom) and for an active microwave sensing system [Synthetic Aperture Radar (SAR)]. It provides a framework by which these sensor models can be extended to other sensor types.<br />
#It may be provided as a True Replacement Model, using functions whose coefficients are based on a Physical Sensor Model so that they provide information for precise geopositioning, including the calculation of errors, as precisely as the Physical Sensor Model they replace.<br />
#It may be provided as a Correspondence Model that provides a functional fitting based on observed relationships between the geopositions of a set of ground control points and their image coordinates.<br />
#It may be provided as a set of ground control points that can be used to develop a Correspondence Model or to refine a Physical Sensor Model or True Replacement Model.<br />
<br />
ISO/TS 19130:2010 does not specify either how users derive geoposition data or the format or content of the data the users generate.<br />
<br />
==Implementation benefits==<br />
Vast amounts of remotely sensed imaging data are collected through a variety of sensors. In order to use this data in geo-spatial applications it needs to be geopositioned, i.e. image coordinates have to be converted to coordinates relative to the Earth. Due to the diversity in sensor types and the lack of a common sensor model, the metadata required for geopositioning differs from one imaging product to another.<br />
<br />
ISO/TS 19130:2010 specifies standardized sensor models and geopositioning metadata to support interoperability of imaging data between applications and to facilitate exchange of imaging data. For example, the standard enables the development of software products for imaging data from multiple data producers and/or a variety of sensors.<br />
<br />
==Implementation guidelines==<br />
Image geopositioning refers to the process of determining the coordinates of a feature relative to the Earth from image coordinates. ISO/TS 19130:2010 specifies the geopositioning information required for three approaches to geopositioning:<br />
# Image geopositioning refers to the process of determining the coordinates of a feature relative to the Earth from image coordinates. ISO/TS 19130:2010 specifies the geopositioning information required for three approaches to geopositioning:Physical Sensor Models employ a mathematical representation of the physics and geometry of the image sensing system to determine the Earth coordinates. Firstly, a sensor model for the type of sensor under consideration is constructed mathematically. Secondly, information to relate the sensing event to the ground coordinate reference system is needed to apply the model to a given image. This information can be in one of two forms: 1) accurate data about the position, attitude, and dynamics of the sensor during imaging; or 2) ground control information such as a set of Global Navigation Satellite System (GNSS)- determined ground control points (GCPs).<br />
#In True Replacement Models the equations to describe the sensor and its relationship to the Earth coordinate reference system are replaced with a set of equations that directly describe the relationship between the image coordinates and the Earth coordinates.<br />
#In Correspondence Models a set of ground control points (Earth coordinates) and their corresponding image coordinates are identified and used to derive the Earth coordinates of other image coordinates. Correspondence Models are widely used but less rigorous than the other two models.<br />
<br />
Geolocating refers to the geopositioning of an object using a Physical Sensor Model or a True Replacement Model. Georeferencing refers to geopositioning through correspondence modelling.<br />
<br />
ISO/TS 19130:2010 specifies a conformance class for each method of providing geopositioning information. The requirements for each class are indicated in the following table. Conditional requirements are indicated with a ‘C’. For example, the geopositioning metadata for an image conforms to the Correspondence Model if the metadata meets the requirements specified in ISO/TS 19130:2010 for geopositioning information, GCP collection, GCP repository, functional fitting and the Correspondence Model. An overview of the geopositioning metadata requirements is provided in the remainder of this section. Refer to ISO/TS 19130:2010 for UML model diagrams and a data dictionary that describe these requirements in detail. The specification also includes extensive informative text to explain geopositioning and the three different approaches to geopositioning.<br />
<br />
'''Overview of conformance classes and requirements in ISO/TS 19130:2010'''<br />
{| class="wikitable"<br />
| rowspan="2" | Requirement <BR/> Conformance class<br />
| rowspan="2" | <BR/>Geopositioning information<br />
| colspan="2" style="text-align: center;" | GCPs<br />
| colspan="5" style="text-align: center;" | Physical Sensor Model<br />
| rowspan="2" | Functional fitting<br />
| rowspan="2" | True Replacement Model<br />
| rowspan="2" | Correspondence Model<br />
|-<br />
| GCP collection<br />
| GCP repository<br />
| Sensor model completeness<br />
| Platforminformation<br />
| Sensorinformation<br />
| Optics<br />
| SAR<br />
|-<br />
| Correspondence Model<br />
| style="text-align: center;" | X<br />
| style="text-align: center;" | X<br />
| style="text-align: center;" | X<br />
| <br />
| <br />
| <br />
| <br />
| <br />
| style="text-align: center;" | X<br />
| <br />
| style="text-align: center;" | X<br />
|-<br />
| Physical Sensor Model ? SAR<br />
| style="text-align: center;" | X<br />
| <br />
| <br />
| style="text-align: center;" | X<br />
| style="text-align: center;" | X<br />
| style="text-align: center;" | X<br />
| <br />
| style="text-align: center;" | X<br />
| <br />
| <br />
| <br />
|-<br />
| Physical Sensor Model?Electro-optical<br />
| style="text-align: center;" | X<br />
| <br />
| <br />
| style="text-align: center;" | X<br />
| style="text-align: center;" | X<br />
| style="text-align: center;" | X<br />
| style="text-align: center;" | X<br />
| <br />
| <br />
| <br />
| <br />
|-<br />
| True Replacement Model<br />
| style="text-align: center;" | X<br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| <br />
| style="text-align: center;" | X<br />
| style="text-align: center;" | X<br />
| <br />
|-<br />
| GCP collection<br />
| style="text-align: center;" | X<br />
| style="text-align: center;" | X<br />
| style="text-align: center;" | X<br />
| style="text-align: center;" | C<br />
| style="text-align: center;" | C<br />
| style="text-align: center;" | C<br />
| style="text-align: center;" | C<br />
| style="text-align: center;" | C<br />
| style="text-align: center;" | C<br />
| style="text-align: center;" | C<br />
| style="text-align: center;" | C<br />
|}<br />
<br />
Geopositioning information shall consist of sensor model information and a set ground control points, where applicable. Optionally, quality information may be provided together with the set of ground control points to allow the generation of a fitting function in the Correspondence Model.<br />
<br />
A GCP collection consists of one or more GCPs and shall have an identifier, a name and an attribute to specify the coordinate reference system of its GCPs. A GCP shall have at least two horizontal coordinates (X, Y) and an optional vertical coordinate (Z). A GCP is specified either in correspondence to image coordinates or as a description that allows a user to identify the GCP in the image. It is possible to specify the GCP collection as a grid (as opposed to a one-dimensional list).<br />
<br />
A GCP repository is a library of GCP collections, which may be used to lookup GCP information if such information is not provided with the image itself. Access to the repository may be restricted.<br />
<br />
The Physical Sensor Model requirement specifies the content to be included in the description of a Physical Sensor Model, amongst others, internal sensor parameters (e.g. focal length, principal point offset, pixel size, distortion coefficients), external sensor/platform parameters (e.g. sensor location, sensor orientation, collection platform velocity), the ground-to-image function, the reverse image-to-ground function, error propagation and adjustable model parameters. Quality information for Physical Sensor Models shall be provided using the appropriate quality measures specified in ISO/TS 19138:2006 (replaced by ISO 19158:2012).<br />
<br />
The functional fitting requirement describes the information to be provided if a functional fit between image and geographic coordinates is used to geoposition the image. The function may be based on a Physical Sensor Model, as in the case of a True Replacement Model, or it may be a simple Correspondence Model based upon ground control points. The function may be a single polynomial applicable to the entire image or it may be a set of polynomials, each applicable to a separate partition. The fit may also be derived by interpolating between points in a grid where both the grid and geographic coordinates are known. A function produced by interpolation cannot be expressed in a simple analytic form over the entire image; its first derivative is discontinuous at grid cell boundaries.<br />
<br />
The True Replacement Model requirement specifies the content to be included in the description of a True Replacement Model, amongst others, the region of validity, accuracy, information about the fitting function and geolocation information.<br />
<br />
The Correspondence Model requirement specifies the content to be included in the description of a Correspondence Model, amongst others, the GCP collection, the region of validity and information about the fitting function.</div>Tebogo Mokwenahttp://wiki.icaci.org/index.php?title=OGC_GeoPackage_Encoding_Standard&diff=848OGC GeoPackage Encoding Standard2016-06-24T10:54:39Z<p>Tebogo Mokwena: /* Overview */</p>
<hr />
<div>== Overview ==<br />
{| class="wikitable sortable"<br />
|-<br />
| Full name<br />
|[http://www.opengeospatial.org/standards/geopackage OGC GeoPackage Encoding Standard]<br />
|-<br />
| Version<br />
| V 1.0.1<br />
|-<br />
| Amendments<br />
| None<br />
|-<br />
| Corrigenda<br />
| None<br />
|-<br />
| Published by<br />
| OGC<br />
|-<br />
| Languages<br />
| English<br />
|-<br />
| Online overview<br />
| http://www.opengeospatial.org/standards/geopackage<br />
|-<br />
| Type of standard<br />
| OpenGIS Implementation Specification<br />
Application level<br />
|-<br />
| Related standard(s)<br />
| ISO/IEC 9075-11:2011, Information technology -- Database languages -- SQL -- Part 11:Information and Definition Schemas (SQL/Schemata),<br/> [http://www.iso.org/iso/home/store/catalogue_tc/catalogue_detail.htm?csnumber=40115 ISO 19125-2:2004, Geographic information – Simple feature access – Part 2: SQL option]<br />
|-<br />
| Application<br />
| This OGC encoding standard defines GeoPackage for exchange and GeoPackage SQLite extension for direct access of vector and raster images for enterprise production platform and mobile hand-held devices. A GeoPackage is a platform independent SQLite database file comprising of the data and metadata tables. The extended GeoPackage allows the addition of any data elements or SQL constructs outside of this encoding standard.<br />
|}</div>Tebogo Mokwenahttp://wiki.icaci.org/index.php?title=ISO_19136:2007_Geographic_information_-_Geography_Markup_Language_(GML)&diff=847ISO 19136:2007 Geographic information - Geography Markup Language (GML)2016-06-24T10:53:04Z<p>Tebogo Mokwena: /* Overview */</p>
<hr />
<div>== Overview ==<br />
{| class="wikitable sortable"<br />
|-<br />
| Full name<br />
| [http://www.iso.org/iso/home/store/catalogue_tc/catalogue_detail.htm?csnumber=32554 ISO 19136:2007, Geographic information – Geography Markup Language (GML) (also published as OpenGIS Geography Markup Language (GML) Encoding Standard)]<br />
|-<br />
| Version<br />
| ISO: Edition 1<br />
OGC: V 3.2.1<br />
|-<br />
| Amendments<br />
| None <br />
|-<br />
| Corrigenda<br />
| None<br />
|-<br />
| Published by<br />
| ISO/TC 211 and OGC<br />
|-<br />
| Languages<br />
| English, French<br />
|-<br />
| Online overview<br />
| http://www.opengeospatial.org/standards/gml<br />
|-<br />
| Type of standard<br />
| ISO International Standard and OpenGIS Implementation Specification,Application level.<br />
|-<br />
| Related standard(s)<br />
| [http://wiki.icaci.org/index.php?title=Spatial_schema ISO 19107:2003, Geographic information – Spatial schema],<br/>[http://wiki.icaci.org/index.php?title=Rules_for_application_schema ISO 19109:2015, Geographic information – Rules for application schema],<br/>ISO 19118:2011, Geographic information -- Encoding,<br/>[http://wiki.icaci.org/index.php?title=Core_profile_of_the_spatial_schema ISO 19137:2007, Geographic information – Core profile of the spatial schema.]<br />
|-<br />
| Application<br />
| GML is an Extensible Markup Language (XML) encoding for transport and storage of geographic information.It is typically used for vector geometry with associated attribute data, such as, a road network or cadastral data. GML is specifically powerful for web processing of geo-spatial data.<br />
|-<br />
| Implementation benefits<br />
|GML is a human readable and machine ‘processable’ encoding which makes it ideal for web data dissemination. GML is based on XML, which brings a number of advantages, such as, XML providing a method for verifying data integrity; the XML structure allowing easy integration of GML data with non-spatial data; and XML transformations. GML allows topology to be encoded in the schema.<br />
|}</div>Tebogo Mokwenahttp://wiki.icaci.org/index.php?title=ISO_19105:2000_Geographic_information_-_Conformance_and_testing&diff=846ISO 19105:2000 Geographic information - Conformance and testing2016-06-24T10:51:16Z<p>Tebogo Mokwena: /* Overview */</p>
<hr />
<div>== Overview == <br />
{| class="wikitable sortable"<br />
|-<br />
| Full name<br />
|[http://www.iso.org/iso/home/store/catalogue_tc/catalogue_detail.htm?csnumber=26010 ISO 19105:2000, Geographic information -- Conformance and testing]<br />
|-<br />
| Version<br />
| Edition 1 <br />
|-<br />
| Amendments<br />
| None <br />
|-<br />
| Corrigenda<br />
| None<br />
|-<br />
| Published by<br />
| ISO/TC 211<br />
|-<br />
| Languages<br />
| English<br />
|-<br />
| Online overview<br />
| https://www.iso.org/obp/ui/#iso:std:iso:19105:ed-1:v1:en<br />
|-<br />
| Type of standard<br />
| ISO International Standard<br />
Meta level<br />
|-<br />
| Related standard(s)<br />
| [http://wiki.icaci.org/index.php?title=Profiles ISO 19106:2004, Geographic information – Profiles],<br/>ISO/IEC Guide 25:1990, General requirements for the competence of calibration and testing laboratories.<br/> ISO/IEC TR 13233:1995, Information technology — Interpretation of accreditation requirements in ISO/IEC Guide 25 — Accreditation of Information Technology and Telecommunications testing laboratories for software and protocol testing services<br />
|-<br />
| Application<br />
| [http://www.iso.org/iso/home/store/catalogue_tc/catalogue_detail.htm?csnumber=26010 ISO 19105] specifies the framework, concepts and methodology for conformance testing of the ISO/TC 211 suite of standards. Requirements for specifying abstract test suites (ATS) and the procedure for testing conformance to the ISO/TC 211 standards are defined. ISO/TC 211 standards implement [http://www.iso.org/iso/home/store/catalogue_tc/catalogue_detail.htm?csnumber=26010 ISO 19105] to specify requirements for claiming conformance to a specific standard.<br />
|}</div>Tebogo Mokwenahttp://wiki.icaci.org/index.php?title=ISO_19103:2015_Geographic_information_-_Conceptual_schema_language&diff=845ISO 19103:2015 Geographic information - Conceptual schema language2016-06-24T10:49:17Z<p>Tebogo Mokwena: /* Overview */</p>
<hr />
<div>== Overview == <br />
{| class="wikitable sortable"<br />
|-<br />
| Full name<br />
| [http://www.iso.org/iso/home/store/catalogue_tc/catalogue_detail.htm?csnumber=56734 ISO 19103:2015, Geographic information – Conceptual schema language]<br />
|-<br />
| Version<br />
| Edition 1 (but replacing ISO/TS 19103:2005)<br />
|-<br />
| Amendments<br />
| None <br />
|-<br />
| Corrigenda<br />
| None<br />
|-<br />
| Published by<br />
| ISO/TC 211<br />
|-<br />
| Languages<br />
| English<br />
|-<br />
| Online overview<br />
| https://www.iso.org/obp/ui/#iso:std:iso:ts:19103:ed-1:v1:en<br />
|-<br />
| Type of standard<br />
| ISO International Standard<br />
Meta-meta level<br />
|-<br />
| Related standard(s)<br />
| ISO 19150-1:2012, Geographic information -- Ontology -- Part 1: Framework<br/> ISO 19150-2, Geographic information -- Ontology -- Part 2: Rules for developing ontologies in the Web Ontology Language (OWL)<br/> S-100 IHO Universal hydrographical data model]<br />
|-<br />
| Application<br />
| ISO 19103 specifies rules and guidelines for the use of UML, the preferred Conceptual Schema Language (CSL) in the ISO/TC 211 suite of standards. The ISO/TC 211 suite of standards aims to create a framework in which data interchange and service interoperability can be achieved across multiple implementation environments. The adoption and consistent use of a CSL is fundamental to achieving this goal because it allows the specification of unambiguous schemas, which form the basis for data interchange and definition.<br />
|}<br />
<br />
== External links ==<br />
* [https://github.com/ISO-TC211/UML-Best-Practices/wiki ISO/TC 211 UML Best Practices], a collection of best practices for modelling geographic information in UML, and to make the models understandable for both machines and humans.</div>Tebogo Mokwenahttp://wiki.icaci.org/index.php?title=OpenGIS_Sensor_Observation_Service_Interface_Standard&diff=844OpenGIS Sensor Observation Service Interface Standard2016-06-24T10:47:41Z<p>Tebogo Mokwena: /* Overview */</p>
<hr />
<div>==Overview==<br />
{| class="wikitable"<br />
| Full name<br />
| [http://www.opengeospatial.org/standards/sos OpenGIS Sensor Observation Service Interface Standard]<br />
|-<br />
| Version<br />
| V 2.0<br />
|-<br />
| Amendments<br />
| None<br />
|-<br />
| Corrigenda<br />
| None<br />
|-<br />
| Published by<br />
| OGC<br />
|-<br />
| Languages<br />
| English<br />
|-<br />
| Online overview<br />
| http://www.opengeospatial.org/standards/sos<br />
|-<br />
| Type of standard<br />
| ISO International Standard and OpenGIS Implementation Specification<br/>Application level<br />
|-<br />
| Related standard(s)<br />
| [http://wiki.icaci.org/index.php?title=Observations_and_Measurements ISO 19156:2011, Geographic information – Observations and Measurements] <br/>[http://portal.opengeospatial.org/files/?artifact_id=38478 OGC Sensor Planning Service Implementation Standard Service] <br/>[http://wiki.icaci.org/index.php?title=Symbology_Encoding OGC SensorML: Model and XML Encoding Standard]<br />
|-<br />
| Application<br />
| OpenGIS Sensor Observation Service Interface Standard defines a standardized interface for managing and retrieving metadata and observations from heterogeneous sensor systems.<br />
|-<br />
| Conformance classes<br />
| Main Requirements class <br/>Transactional Extension <br/>Result Handling Extension <br/>Enhanced Operations Extension <br/>Spatial Filtering Profile <br/>Binding Extension<br />
|-<br />
| Implementation benefits<br />
| Sensors are currently the largest contributor of data in the geo-spatial system. The OGC Sensor Observation Service (SOS) allows the aggregation of readings from live, in-situ and remote sensors. OGC SOS provides the client with the capability to discover or bind with individual sensors, sensor platforms, or networked constellations of sensors.<br />
|-<br />
| Products<br />
| An open source implementation of the SOS service interface is available from 52° North, 52N Sensor Observation Service (SOS) 4.0.<br />
|}</div>Tebogo Mokwenahttp://wiki.icaci.org/index.php?title=OpenGIS_Catalogue_Service_Implementation_Specification&diff=843OpenGIS Catalogue Service Implementation Specification2016-06-24T10:46:08Z<p>Tebogo Mokwena: /* Overview */</p>
<hr />
<div>==Overview==<br />
{| class="wikitable"<br />
| Full name<br />
| [http://www.opengeospatial.org/standards/cat OpenGIS Catalogue Service Implementation Specification]<br />
|-<br />
| Version<br />
| V3.0<br />
|-<br />
| Amendments<br />
| None<br />
|-<br />
| Corrigenda<br />
| None<br />
|-<br />
| Published by<br />
| OGC<br />
|-<br />
| Languages<br />
| English<br />
|-<br />
| Online overview<br />
| http://www.opengeospatial.org/standards/cat<br />
|-<br />
| Type of standard<br />
| ISO International Standard and OpenGIS Implementation Specification<br/>Application level<br />
|-<br />
| Related standard(s)<br />
| [http://wiki.icaci.org/index.php?title=Metadata ISO 19115:2003, Geographic information – Metadata] <br/>[http://wiki.icaci.org/index.php?title=Services ISO 19119:2016, Geographic information – Services] <br/>[http://wiki.icaci.org/index.php?title=Web_Map_Server_interface ISO 19128:2005, Geographic information – Web Map Server interface] <br/>[http://wiki.icaci.org/index.php?title=Geography_Markup_Language ISO 19136:2007, Geographic information -- Geography Markup Language (GML)] <br/>[http://wiki.icaci.org/index.php?title=Web_Feature_Service ISO 19142:2010, Geographic information – Web Feature Service] <br/>[http://wiki.icaci.org/index.php?title=Web_Map_Tile_Service OpenGIS Web Map Tile Service Implementation Standard OpenGIS]<br />
|-<br />
| Application<br />
| Catalogue services support the ability to publish and search collections of descriptive information (metadata) for data, services, and related information objects. The OGC Catalogue Services Specification defines the requirements for the interface and bindings to realise these functionalities. This specification includes an HTTP protocol binding, called the Catalogue Services for the Web (CSW).<br />
|-<br />
| Conformance classes<br />
| None specified<br />
|-<br />
| Implementation benefits<br />
| Catalogue services are an important aspect of most spatial data infrastructures (SDI). It allows the client to search and discover data and associated services. The catalogue service relies on metadata of the data and service.<br />
|-<br />
| Products<br />
| The geoportal of an SDI is commonly an example of a catalogue service. A proprietary catalogue service implementation is the Esri Geoportal Server 1.2.5.<br />
|}</div>Tebogo Mokwenahttp://wiki.icaci.org/index.php?title=ISO_19143:2010_Geographic_information_-_Filter_encoding&diff=842ISO 19143:2010 Geographic information - Filter encoding2016-06-24T10:43:12Z<p>Tebogo Mokwena: /* Overview */</p>
<hr />
<div>==Overview==<br />
{| class="wikitable"<br />
| Full name<br />
| [http://www.iso.org/iso/home/store/catalogue_tc/catalogue_detail.htm?csnumber=42137 ISO 19143:2010, Geographic information – Filter encoding (also published as OpenGIS Filter Encoding 2.0 Encoding Standard)]<br />
|-<br />
| Version<br />
| ISO: Edition 1 <br/>OGC: V2.0.0<br />
|-<br />
| Amendments<br />
| None<br />
|-<br />
| Corrigenda<br />
| None<br />
|-<br />
| Published by<br />
| ISO/TC 211 and OGC<br />
|-<br />
| Languages<br />
| English, French<br />
|-<br />
| Online overview<br />
| https://www.iso.org/obp/ui/#iso:std:iso:19143:ed-1:v1:en<br />
|-<br />
| Type of standard<br />
| ISO International Standard and OpenGIS Implementation Specification<br/>Application level<br />
|-<br />
| Related standard(s)<br />
| [http://wiki.icaci.org/index.php?title=Portrayal ISO 19117:2012, Geographic information -- Portrayal] <br/>[http://wiki.icaci.org/index.php?title=Services ISO 19119:2016, Geographic information – Services] <br/>[http://wiki.icaci.org/index.php?title=Web_Map_Server_interface ISO 19128:2005, Geographic information – Web Map Server interface] <br/>[http://wiki.icaci.org/index.php?title=Web_Feature_Service ISO 19142:2010, Geographic information – Web Feature Service ]<br/>[http://wiki.icaci.org/index.php?title=Styled_Layer_Descriptor OpenGIS Styled Layer Descriptor Profile of the Web Map Service Implementation Specification ]<br/>[http://wiki.icaci.org/index.php?title=Symbology_Encoding OpenGIS Symbology Encoding Implementation Specification]<br />
|-<br />
| Application<br />
| ISO 19143 describes XML and Key-Value Pairs (KVP) encodings of a system-neutral syntax for expressing projections, selections and sorting clauses, collectively called a query expression. <br />
|-<br />
| Conformance classes<br />
| Query <br/>Ad-hoc Query <br/>Functions <br/>Resource Identification <br/>Minimum Standard Filter <br/>Standard Filter <br/>Minimum Spatial Filter <br/>Spatial Filter <br/>Minimum Temporal Filter <br/>Temporal Filter <br/>Version navigation <br/>Sorting <br/>Extended Operators <br/>Minimum XPath <br/>Schema Element Function<br />
|-<br />
| Implementation benefits<br />
| Filter Encoding (FE) describes XML and KVP encodings for expressing filters for spatial queries to select a subset of features based on specific attributes. FE is used in conjunction with other standards and thus allows a client to, for example, create a map using a WMS that only shows residential areas.<br />
|-<br />
| Products<br />
| FE is implemented in conjunction with other services, such as WMS or WFS. An open source examples of an implementation of FE is OpenGeo Suite 4.1.1.<br />
|}</div>Tebogo Mokwenahttp://wiki.icaci.org/index.php?title=ISO_19142:2010_Geographic_information_-_Web_Feature_Service&diff=841ISO 19142:2010 Geographic information - Web Feature Service2016-06-24T10:40:40Z<p>Tebogo Mokwena: /* Overview */</p>
<hr />
<div>==Overview==<br />
{| class="wikitable"<br />
| Full name<br />
| [http://www.iso.org/iso/home/store/catalogue_tc/catalogue_detail.htm?csnumber=42136 ISO 19142:2010, Geographic information – Web Feature Service (also published as OpenGIS Web Feature Service Implementation Specification)]<br />
|-<br />
| Version<br />
| ISO: Edition 2 <br/>OGC: V2.0.0<br />
|-<br />
| Amendments<br />
| None<br />
|-<br />
| Corrigenda<br />
| None<br />
|-<br />
| Published by<br />
| ISO/TC 211 and OGC<br />
|-<br />
| Languages<br />
| English, French<br />
|-<br />
| Online overview<br />
| http://www.opengeospatial.org/standards/wfs<br />
|-<br />
| Type of standard<br />
| ISO International Standard and OpenGIS Implementation Specification<br/>Application level<br />
|-<br />
| Related standard(s)<br />
| [http://wiki.icaci.org/index.php?title=Services ISO 19119:2016, Geographic information – Services] <br/>[http://wiki.icaci.org/index.php?title=Web_Map_Server_interface ISO 19128:2005, Geographic information – Web Map Server interface] <br/>[http://wiki.icaci.org/index.php?title=Web_Map_Tile_Service OpenGIS Web Map Tile Service Implementation Standard], [http://wiki.icaci.org/index.php?title=Catalogue_Service OpenGIS Catalogue Services Specification]<br />
|-<br />
| Application<br />
| ISO 19142 describes the interface for a Web Feature Service (WFS). WFS allow a client to access and perform transactions on geographic features independent of the underlying data store. These WFS implementations allow clients to edit geographic features online and store the changes to the underlying data store. <br />
|-<br />
| Conformance classes<br />
| Simple WFS <br/>Basic WFS <br/>Transactional WFS <br/>Locking WFS<br />
|-<br />
| Implementation benefits<br />
| WFS allow a client to retrieve features or values of features (attribute data) from an underlying data store, and also to access the features to modify or delete features. With WFS the data can be stored in any database or as a shapefile on a server, for example, and the same operations can be performed on the data. This allows the user to query and edit data without having to consider the format of the data.<br />
|-<br />
| Products<br />
| deegree 3.3 is an example of an OGC compliant open source implementation of the WFS interface.<br />
|}</div>Tebogo Mokwenahttp://wiki.icaci.org/index.php?title=OpenGIS_Web_Map_Tile_Service_Implementation_Standard&diff=840OpenGIS Web Map Tile Service Implementation Standard2016-06-24T10:38:23Z<p>Tebogo Mokwena: /* Overview */</p>
<hr />
<div>==Overview==<br />
{| class="wikitable"<br />
| Full name<br />
| [http://www.opengeospatial.org/standards/wmts OpenGIS Web Map Tile Service Implementation Standard]<br />
|-<br />
| Version<br />
| V1.0.0<br />
|-<br />
| Amendments<br />
| None<br />
|-<br />
| Corrigenda<br />
| None<br />
|-<br />
| Published by<br />
| OGC<br />
|-<br />
| Languages<br />
| English<br />
|-<br />
| Online overview<br />
| http://www.opengeospatial.org/standards/wmts<br />
|-<br />
| Type of standard<br />
| OpenGIS Implementation Specification<br/>Application level<br />
|-<br />
| Related standard(s)<br />
| [http://wiki.icaci.org/index.php?title=Services ISO 19119:2016, Geographic information – Services ]<br/>[http://wiki.icaci.org/index.php?title=Web_Feature_Service ISO 19142:2010, Geographic information – Web Feature Service ]<br/>[http://wiki.icaci.org/index.php?title=Catalogue_Service OpenGIS Catalogue Service Implementation Specification]<br />
|-<br />
| Application<br />
| The OGC WMTS provides a complementary approach to the Web Map Service (WMS) for tiling maps. WMS focuses on rendering custom maps and is an ideal solution for dynamic data or custom styled maps (combined with the OGC Style Layer Descriptor (SLD) standard). WMTS trades the flexibility of custom map rendering for the scalability possible by serving of static data (base maps) where the bounding box and scales have been constrained to discrete tiles. The fixed set of tiles allows for the implementation of a WMTS service using a web server that simply returns existing files. The fixed set of tiles also enables the use of standard network mechanisms for scalability such as distributed cache systems.<br />
|-<br />
| Conformance classes<br />
| Client test module <br/>Server test module<br />
|-<br />
| Implementation benefits<br />
| With WMS (ISO 19128) custom maps can be rendered for dynamic data or custom styled data. OGC WMTS trades the flexibility of custom maps for the scalability possible by serving static data (base maps) more efficiently.<br/>The main benefit of using WMTS is that tiles can be rendered server-side and then cached client-side. This reduces waiting time and bandwidth limitations. OGC WMTS is used to accelerate and optimize map image rendering and delivery.<br />
|-<br />
| Products<br />
| GeoWebCache 1.5.3 is one example of an implementation of OGC WMTS.<br />
|}</div>Tebogo Mokwenahttp://wiki.icaci.org/index.php?title=OpenGIS_Web_Map_Tile_Service_Implementation_Standard&diff=839OpenGIS Web Map Tile Service Implementation Standard2016-06-24T10:37:37Z<p>Tebogo Mokwena: /* Overview */</p>
<hr />
<div>==Overview==<br />
{| class="wikitable"<br />
| Full name<br />
| [http://www.opengeospatial.org/standards/wmts OpenGIS Web Map Tile Service Implementation Standard]<br />
|-<br />
| Version<br />
| V1.0.0<br />
|-<br />
| Amendments<br />
| None<br />
|-<br />
| Corrigenda<br />
| None<br />
|-<br />
| Published by<br />
| OGC<br />
|-<br />
| Languages<br />
| English<br />
|-<br />
| Online overview<br />
| http://www.opengeospatial.org/standards/wmts<br />
|-<br />
| Type of standard<br />
| OpenGIS Implementation Specification<br/>Application level<br />
|-<br />
| Related standard(s)<br />
| [http://wiki.icaci.org/index.php?title=Services ISO 19119:2016, Geographic information – Services ]<br/>[http://wiki.icaci.org/index.php?title=Web_Feature_Service ISO 19142:2010, Geographic information – Web Feature Service ]<br/>[http://wiki.icaci.org/index.php?title=Catalogue_ServiceOpenGIS Catalogue Service Implementation Specification]<br />
|-<br />
| Application<br />
| The OGC WMTS provides a complementary approach to the Web Map Service (WMS) for tiling maps. WMS focuses on rendering custom maps and is an ideal solution for dynamic data or custom styled maps (combined with the OGC Style Layer Descriptor (SLD) standard). WMTS trades the flexibility of custom map rendering for the scalability possible by serving of static data (base maps) where the bounding box and scales have been constrained to discrete tiles. The fixed set of tiles allows for the implementation of a WMTS service using a web server that simply returns existing files. The fixed set of tiles also enables the use of standard network mechanisms for scalability such as distributed cache systems.<br />
|-<br />
| Conformance classes<br />
| Client test module <br/>Server test module<br />
|-<br />
| Implementation benefits<br />
| With WMS (ISO 19128) custom maps can be rendered for dynamic data or custom styled data. OGC WMTS trades the flexibility of custom maps for the scalability possible by serving static data (base maps) more efficiently.<br/>The main benefit of using WMTS is that tiles can be rendered server-side and then cached client-side. This reduces waiting time and bandwidth limitations. OGC WMTS is used to accelerate and optimize map image rendering and delivery.<br />
|-<br />
| Products<br />
| GeoWebCache 1.5.3 is one example of an implementation of OGC WMTS.<br />
|}</div>Tebogo Mokwenahttp://wiki.icaci.org/index.php?title=ISO_19119:2005_Geographic_information_-_Services&diff=838ISO 19119:2005 Geographic information - Services2016-06-24T10:35:59Z<p>Tebogo Mokwena: /* Overview */</p>
<hr />
<div>==Overview ==<br />
{| class="wikitable"<br />
| Full name<br />
| [http://www.iso.org/iso/home/store/catalogue_tc/catalogue_detail.htm?csnumber=59221 ISO 19119:2005, Geographic information – Services]<br />
|-<br />
| Version<br />
| Edition 1<br />
|-<br />
| Amendments<br />
| Amendment 1<br />
|-<br />
| Corrigenda<br />
| None<br />
|-<br />
| Published by<br />
| ISO/TC 211<br />
|-<br />
| Languages<br />
| English, French<br />
|-<br />
| Online overview<br />
| https://www.iso.org/obp/ui/#iso:std:iso:19119:ed-1:v1:en:1<br />
|-<br />
| Type of standard<br />
| ISO International Standard<br/>Meta level<br />
|-<br />
| Related standard(s)<br />
| [http://wiki.icaci.org/index.php?title=Web_Map_Server_interface ISO 19128:2005, Geographic information – Web Map Server interface ]<br/>[http://wiki.icaci.org/index.php?title=Web_Feature_Service ISO 19142:2010, Geographic information – Web Feature Service]<br />
|-<br />
| Application<br />
| ISO 19119 is a high-level standard that describes service architectural patterns, presents a taxonomy for geographic services, and provides guidelines for the selection of services. OGC Web Service Common Implementation Specification is a similar standard.<br />
|-<br />
| Conformance classes<br />
| Service architecture test module <br/>Service specification test module<br />
|-<br />
| Implementation benefits<br />
|The taxonomy provides standard terms that can be used to describe services in a standard way. ISO 19119 provides details on chaining patterns that assist developers when implementing a service chain. Furthermore, the standard defines the basic concepts required when developing or implementing services to ensure integration and interoperability of the services.<br />
|-<br />
| Products<br />
| Standards such as Web Map Server and Web Feature Service are based on the concepts described in ISO 19119.<br />
|}</div>Tebogo Mokwenahttp://wiki.icaci.org/index.php?title=OpenGIS_Symbology_Encoding_Implementation_Specification&diff=837OpenGIS Symbology Encoding Implementation Specification2016-06-24T10:34:31Z<p>Tebogo Mokwena: /* Overview */</p>
<hr />
<div>==Overview==<br />
{| class="wikitable"<br />
| Full name<br />
| [http://www.opengeospatial.org/standards/se OpenGIS Symbology Encoding Implementation Specification]<br />
|-<br />
| Version<br />
| V1.1.0<br />
|-<br />
| Amendments<br />
| None<br />
|-<br />
| Corrigenda<br />
| None<br />
|-<br />
| Published by<br />
| OGC<br />
|-<br />
| Languages<br />
| English<br />
|-<br />
| Online overview<br />
| http://www.opengeospatial.org/standards/se<br />
|-<br />
| Type of standard<br />
| ISO International Standard and OpenGIS Implementation Specification<br/>Application level<br />
|-<br />
| Related standard(s)<br />
| [http://wiki.icaci.org/index.php?title=Portrayal ISO 19117:2012, Geographic information -- Portrayal] <br/>[http://wiki.icaci.org/index.php?title=Services ISO 19119:2005, Geographic information – Services] <br/>[http://wiki.icaci.org/index.php?title=Web_Map_Server_interface ISO 19128:2005, Geographic information – Web Map Server interface] <br/>[http://wiki.icaci.org/index.php?title=Filter_encoding ISO 19143:2010, Geographic information – Filter encoding] <br/>[http://wiki.icaci.org/index.php?title=Styled_Layer_Descriptor OpenGIS Styled Layer Descriptor Profile of the Web Map Service Implementation Specification]<br />
|-<br />
| Application<br />
| The OGC Symbology Encoding (SE) standard has initially been a part of the Styled Layer Descriptor (SLD) 1.0 standard. OGC SE describes the actual syntax for the description of styles.<br />
|-<br />
| Conformance classes<br />
| Basic Schema conformance <br/>Basic Feature Styling Functionality <br/>Basic Coverage Styling Functionality <br/>Full Feature Styling Functionality <br/>Full Coverage Styling Functionality<br />
|-<br />
| Implementation benefits<br />
| OGC SE defines a language for specifying the style of a map. This language can be used to portray the output of WMS, WFS and CSW. <br />
|-<br />
| Products<br />
| SE is implemented in conjunction with a SLD. An example of an SE implementation is GeoServer 2.5.2.<br />
|}</div>Tebogo Mokwenahttp://wiki.icaci.org/index.php?title=OpenGIS_Styled_Layer_Descriptor_Profile_of_the_Web_Map_Service_Implementation_Specification&diff=836OpenGIS Styled Layer Descriptor Profile of the Web Map Service Implementation Specification2016-06-24T10:32:11Z<p>Tebogo Mokwena: /* Overview */</p>
<hr />
<div>==Overview==<br />
{| class="wikitable"<br />
| Full name<br />
| [http://www.opengeospatial.org/standards/sld OpenGIS Styled Layer Descriptor Profile of the Web Map Service Implementation Specification]<br />
|-<br />
| Version<br />
| V1.1<br />
|-<br />
| Amendments<br />
| None<br />
|-<br />
| Corrigenda<br />
| None<br />
|-<br />
| Published by<br />
| OGC<br />
|-<br />
| Languages<br />
| English<br />
|-<br />
| Online overview<br />
| http://www.opengeospatial.org/standards/sld<br />
|-<br />
| Type of standard<br />
| ISO International Standard and OpenGIS Implementation Specification<br/>Application level<br />
|-<br />
| Related standard(s)<br />
| [http://wiki.icaci.org/index.php?title=Portrayal ISO 19117:2012, Geographic information -- Portrayal] <br/>[http://wiki.icaci.org/index.php?title=Services ISO 19119:2005, Geographic information – Services] <br/>[http://wiki.icaci.org/index.php?title=Web_Map_Server_interface ISO 19128:2005, Geographic information – Web Map Server interface] <br/>[http://wiki.icaci.org/index.php?title=Filter_encoding ISO 19143:2010, Geographic information – Filter encoding] <br/>[http://wiki.icaci.org/index.php?title=Symbology_Encoding OpenGIS Symbology Encoding Implementation Specification]<br />
|-<br />
| Application<br />
| SLD is an XML schema that defines the structure of a layer style. SLD defines styles that <br/>can be used for publishing raster and vector data available through a WMS. Basically, <br/>SLD is what makes the map more colourful and user-friendly and it is responsible for <br/>telling the server how to render the map.<br />
|-<br />
| Conformance classes<br />
| Integrated SLD-WMS <br/>Component SLD-WMS <br/>Feature Portrayal Service <br/>Coverage Portrayal Service<br />
|-<br />
| Implementation benefits<br />
| SLD allows users to define their own styles. With SLD users can develop style sheets that can be used for specific maps, such as topographic maps. This provides consistency and is an effective method for generating maps. The SLD style sheets are reusable and interoperable.<br />
|-<br />
| Products<br />
| Commonly, SLD is implemented in conjunction with a WMS. A number of these implementations also provide extensions on the standard SLD. An example of an SLD implementation is GeoServer 2.5.2.<br />
|}</div>Tebogo Mokwenahttp://wiki.icaci.org/index.php?title=S-66_Facts_about_electronic_charts_and_carriage_requirements&diff=835S-66 Facts about electronic charts and carriage requirements2016-06-24T10:29:18Z<p>Tebogo Mokwena: /* Overview */</p>
<hr />
<div>== Overview == <br />
{| class="wikitable"<br />
| Full name<br />
| [http://www.iho.int/iho_pubs/standard/S-66/S-66_e1.0.0_EN.pdf S-66, Facts about electronic charts and carriage requirements]<br />
|-<br />
| Version<br />
| Edition 1.0.0<br />
|-<br />
| Amendments<br />
| None<br />
|-<br />
| Corrigenda<br />
| None<br />
|-<br />
| Published by<br />
| IHO<br />
|-<br />
| Languages<br />
| English, Spanish, Portuguese, Japanese<br />
|-<br />
| Online overview<br />
| http://iho.int/iho_pubs/standard/S-66/S-66_e1.0.0_EN.pdf<br />
|-<br />
| Type of standard<br />
| n/a<br />
|-<br />
| Related standard(s)<br />
| S-57 IHO transfer standard for digital hydrographic data <br/>[http://wiki.icaci.org/index.php?title=Specifications_for_chart_content_and_display_aspects_of_ECDIS S-52 Specifications for chart content and display aspects of ECDIS]<br/>[http://wiki.icaci.org/index.php?title=ENCs:_Production,_maintenance_and_distribution_guidance S-65 ENCs: Production, maintenance and distribution guidance]<br />
|-<br />
| Application<br />
| S-66 was developed to avoid uncertainty regarding terminology, to provide rules for professional marine navigation, and to describe the types of electronic charts that are available.<br />
|-<br />
| Conformance classes<br />
| None specified<br />
|}<br />
<br />
== Scope == <br />
The International Convention on the Safety of Life at Sea (SOLAS) includes a requirement for all ships to carry to up-to-date nautical charts and publications for the intended voyage. Progressively from 2012, the chart carriage requirement for certain classes of vessels is to be satisfied by electronic means using an Electronic Chart Display and Information System (ECDIS).<br />
<br />
Feedback from those involved in the use of charts and electronic charting systems including manufacturers, distributors, users, ship owners, regulatory authorities, pilots, harbour authorities and others indicates a requirement to provide guidance on the regulations and the status of equipment that is available in the market today. In particular the differences between the various types of equipment and the differences between the various types of chart data offered to the users are unclear with respect to the regulations in place.<br />
<br />
This document has been produced to help clarify some of the uncertainties. It is not intended to replace or amend national or international rules and regulations. Readers should always refer to the relevant national administration or Flag State for the latest detailed information.<br />
<br />
This document consists of a number of interrelated sections. This first section contains information on various aspects of electronic charts and electronic chart display systems in the form of questions and answers. The main emphasis is on what can be used to satisfy the SOLAS carriage requirements for charts.<br />
<br />
:* Section 1: Overview of electronic charting and regulations<br />
:* Section 2: A list of points of contact for detailed information on Flag State Implementation of ECDIS<br />
:* Section 3: ECDIS Training<br />
:* Section 4: Technical aspects of electronic charts<br />
:* Section 5: Appendix: References, glossary, further reading<br />
<br />
== Implementation benefits ===<br />
S-66 is very beneficial to any person working with ENC or ECDIS. It provides a detailed introduction and general information on the field, and also useful information such as links to online resources, and a list of abbreviations.<br />
<br />
== Implementation guidelines ==<br />
S-66 is for information purposes and cannot be implemented. It provides detailed information on ENC, ECGIS, flag authorities, training objectives for ECDIS training, and technical details of electronic charts.</div>Tebogo Mokwenahttp://wiki.icaci.org/index.php?title=S-65_ENCs:_Production,_maintenance_and_distribution_guidance&diff=834S-65 ENCs: Production, maintenance and distribution guidance2016-06-24T10:27:31Z<p>Tebogo Mokwena: /* Overview */</p>
<hr />
<div>== Overview ==<br />
{| class="wikitable"<br />
| Full name<br />
| [http://www.iho.int/iho_pubs/standard/S-65/S-65_ed2.0.0_Apr12.pdf S-65 ENCs: Production, maintenance and distribution guidance]<br />
|-<br />
| Version<br />
| Edition 2.0.0<br />
|-<br />
| Amendments<br />
| None<br />
|-<br />
| Corrigenda<br />
| None<br />
|-<br />
| Published by<br />
| IHO<br />
|-<br />
| Languages<br />
| English, French<br />
|-<br />
| Online overview<br />
| http://iho.int/iho_pubs/standard/S-65/S-65_ed2.0.0_Apr12.pdf<br />
|-<br />
| Type of standard<br />
| IHO International Standard<br/>Application level<br />
|-<br />
| Related standard(s)<br />
| S-57 IHO transfer standard for digital hydrographic data <br/>[http://wiki.icaci.org/index.php?title=Specifications_for_chart_content_and_display_aspects_of_ECDIS S-52 Specifications for chart content and display aspects of ECDIS]<br />
|-<br />
| Application<br />
| S-65 provides guidelines for the production, maintenance and distribution of Electronic Navigational Charts (ENCs).<br />
|-<br />
| Conformance classes<br />
| None specified<br />
|}<br />
<br />
== Scope == <br />
This document provides a high level guide to the production, maintenance and distribution of Electronic Navigational Charts (ENCs). It offers a framework to inform hydrographical offices of the processes and requirements necessary to produce, maintain and distribute ENCs. It provides references to documentation, which can support each stage of the process. It is not intended to serve as a technical reference manual but to enable hydrographical offices to gain an overview of ENC production processes, and the requirements and procedures that need to be in place to set up an ENC production facility.<br />
<br />
== Implementation benefits ==<br />
S-65 enables Hydrographic Offices to gain an overview of ENC production processes, and the requirements and procedures that need to be in place to set up an ENC production facility. The process promotes accuracy and consistency across borders, provides up-to-date information in a timely manner, and satisfies user needs for safety in navigation.<br />
<br />
== Implementation guidelines == <br />
ENCs consist of digitized data conforming to the specification set out in S-57 which record the relevant charted features necessary for safe navigation, such as coastlines, bathymetry, buoys and lights. The basic unit of geographic coverage for ENC is called a cell. S-65 describes the entire ENC process from production to distribution, and provides guidelines to hydrographical offices on the process and requirements. The following stages form part of this process:<br />
<br />
:# Design production process <br/>This stage consists of two steps: production method and quality system. During the production method, decisions on the source material are made. These depend on factors such as the quality and format of existing survey data, availability of accurately transformed data, and the facilities to produce rectified raster images. After the decisions on the source materials have been made, the production process is designed and a Quality Management System (QMS) is developed. Procedures should be in place at all the stages of the production process to ensure accuracy and consistency. Quality control and quality assurance are important during the production of ENCs.<br />
:# Define ENC production requirements <br/>The following steps are recommended to each Regional Hydrographic Commission (RHC): identify key shipping routes and ports within the region, identify charts covering these routes and ports to be captured as ENCs, identify producer nations for ENCs, and arrange for their production. The national production plan shall define which geographic areas are to be captured, which navigational purposes are to be populated for each area, how the areas are to be divided into cells for each navigational purpose, and the order of capture. This plan depends on factors, such as the liaisons with bordering countries and priority traffic routes, to name a few.<br />
:# Acquire production system <br/>The production system should depend on the production plan and the extent of data capturing that will be contracted out. Dependencies should be specified in the statement of requirements. There are two main types of production systems. The first type populates and maintain a database of ENC objects, attributes and attribute values in a format that is conformant with S-57. The second type creates individual flat files for each single ENC cell.<br />
:# Obtain and train staff <br/>The data should be structured and follow other requirements as set out in S-57. The content of the ENC, limits of the cells and cell navigation purpose are not covered in S-57 and should be decided upon.<br />
:# Prepare specification for data capture <br/><br />
:# Capture data for new cells <br/>Data can be captured in-house or contracted out. The United Kingdom Hydrographic Office (UKHO) data capture specifications and quality procedures are recommended.<br />
:# Edge match data <br/>It is important that the borders of cells with the same navigational purpose match, and accuracy should always be kept in mind. The cells should also match between countries and the hydrographical offices should collaborate to achieve this.<br />
:# Verify and validate data <br/>Verification and validation are important to ensure that the ENC cell content is accurate and consistent. Cells need to be checked for content and capture accuracy. Validation checks as specified in S-58 should be performed.<br />
:# Maintain ENCs <br/>After the ENC cell has been produced and distributed to the end users, the data should be maintained. The overall Quality Management System should include a mechanism for updating the cell design to meet the user needs. The processes for updating paper charts and ENCs should be synchronised. When an update is performed or a new edition is available, a Notice to Mariners is published.<br />
:# Distribute ENC data <br/>The distribution mechanism shall provide users with up-to-date ENC data in a timely manner to ensure safe navigation. The distribution system shall also ensure data integrity and data protection. The system should allow automatic updates of ENC data.</div>Tebogo Mokwenahttp://wiki.icaci.org/index.php?title=S-65_ENCs:_Production,_maintenance_and_distribution_guidance&diff=833S-65 ENCs: Production, maintenance and distribution guidance2016-06-24T10:27:02Z<p>Tebogo Mokwena: /* Overview */</p>
<hr />
<div>== Overview ==<br />
{| class="wikitable"<br />
| Full name<br />
| [http://www.iho.int/iho_pubs/standard/S-65/S-65_ed2.0.0_Apr12.pdf S-65 ENCs: Production, maintenance and distribution guidance]<br />
|-<br />
| Version<br />
| Edition 2.0.0<br />
|-<br />
| Amendments<br />
| None<br />
|-<br />
| Corrigenda<br />
| None<br />
|-<br />
| Published by<br />
| IHO<br />
|-<br />
| Languages<br />
| English, French<br />
|-<br />
| Online overview<br />
| http://iho.int/iho_pubs/standard/S-65/S-65_ed2.0.0_Apr12.pdf<br />
|-<br />
| Type of standard<br />
| IHO International Standard<br/>Application level<br />
|-<br />
| Related standard(s)<br />
| [http://www.iho.int/iho_pubs/standard/S-57Ed3.1/31Main.pdf S-57 IHO transfer standard for digital hydrographic data] <br/>[http://wiki.icaci.org/index.php?title=Specifications_for_chart_content_and_display_aspects_of_ECDIS S-52 Specifications for chart content and display aspects of ECDIS]<br />
|-<br />
| Application<br />
| S-65 provides guidelines for the production, maintenance and distribution of Electronic Navigational Charts (ENCs).<br />
|-<br />
| Conformance classes<br />
| None specified<br />
|}<br />
<br />
== Scope == <br />
This document provides a high level guide to the production, maintenance and distribution of Electronic Navigational Charts (ENCs). It offers a framework to inform hydrographical offices of the processes and requirements necessary to produce, maintain and distribute ENCs. It provides references to documentation, which can support each stage of the process. It is not intended to serve as a technical reference manual but to enable hydrographical offices to gain an overview of ENC production processes, and the requirements and procedures that need to be in place to set up an ENC production facility.<br />
<br />
== Implementation benefits ==<br />
S-65 enables Hydrographic Offices to gain an overview of ENC production processes, and the requirements and procedures that need to be in place to set up an ENC production facility. The process promotes accuracy and consistency across borders, provides up-to-date information in a timely manner, and satisfies user needs for safety in navigation.<br />
<br />
== Implementation guidelines == <br />
ENCs consist of digitized data conforming to the specification set out in S-57 which record the relevant charted features necessary for safe navigation, such as coastlines, bathymetry, buoys and lights. The basic unit of geographic coverage for ENC is called a cell. S-65 describes the entire ENC process from production to distribution, and provides guidelines to hydrographical offices on the process and requirements. The following stages form part of this process:<br />
<br />
:# Design production process <br/>This stage consists of two steps: production method and quality system. During the production method, decisions on the source material are made. These depend on factors such as the quality and format of existing survey data, availability of accurately transformed data, and the facilities to produce rectified raster images. After the decisions on the source materials have been made, the production process is designed and a Quality Management System (QMS) is developed. Procedures should be in place at all the stages of the production process to ensure accuracy and consistency. Quality control and quality assurance are important during the production of ENCs.<br />
:# Define ENC production requirements <br/>The following steps are recommended to each Regional Hydrographic Commission (RHC): identify key shipping routes and ports within the region, identify charts covering these routes and ports to be captured as ENCs, identify producer nations for ENCs, and arrange for their production. The national production plan shall define which geographic areas are to be captured, which navigational purposes are to be populated for each area, how the areas are to be divided into cells for each navigational purpose, and the order of capture. This plan depends on factors, such as the liaisons with bordering countries and priority traffic routes, to name a few.<br />
:# Acquire production system <br/>The production system should depend on the production plan and the extent of data capturing that will be contracted out. Dependencies should be specified in the statement of requirements. There are two main types of production systems. The first type populates and maintain a database of ENC objects, attributes and attribute values in a format that is conformant with S-57. The second type creates individual flat files for each single ENC cell.<br />
:# Obtain and train staff <br/>The data should be structured and follow other requirements as set out in S-57. The content of the ENC, limits of the cells and cell navigation purpose are not covered in S-57 and should be decided upon.<br />
:# Prepare specification for data capture <br/><br />
:# Capture data for new cells <br/>Data can be captured in-house or contracted out. The United Kingdom Hydrographic Office (UKHO) data capture specifications and quality procedures are recommended.<br />
:# Edge match data <br/>It is important that the borders of cells with the same navigational purpose match, and accuracy should always be kept in mind. The cells should also match between countries and the hydrographical offices should collaborate to achieve this.<br />
:# Verify and validate data <br/>Verification and validation are important to ensure that the ENC cell content is accurate and consistent. Cells need to be checked for content and capture accuracy. Validation checks as specified in S-58 should be performed.<br />
:# Maintain ENCs <br/>After the ENC cell has been produced and distributed to the end users, the data should be maintained. The overall Quality Management System should include a mechanism for updating the cell design to meet the user needs. The processes for updating paper charts and ENCs should be synchronised. When an update is performed or a new edition is available, a Notice to Mariners is published.<br />
:# Distribute ENC data <br/>The distribution mechanism shall provide users with up-to-date ENC data in a timely manner to ensure safe navigation. The distribution system shall also ensure data integrity and data protection. The system should allow automatic updates of ENC data.</div>Tebogo Mokwenahttp://wiki.icaci.org/index.php?title=S-52_Specifications_for_chart_content_and_display_aspects_of_ECDIS&diff=832S-52 Specifications for chart content and display aspects of ECDIS2016-06-24T10:25:50Z<p>Tebogo Mokwena: /* Overview */</p>
<hr />
<div>== Overview ==<br />
{| class="wikitable"<br />
| Full name<br />
| [http://www.iho.int/iho_pubs/standard/S-52/S-52_e6.0_EN.pdf S-52, Specifications for chart content and display aspects of ECDIS]<br />
|-<br />
| Version<br />
| Edition 6.0.0<br />
|-<br />
| Amendments<br />
| None<br />
|-<br />
| Corrigenda<br />
| None<br />
|-<br />
| Published by<br />
| IHO<br />
|-<br />
| Languages<br />
| English<br />
|-<br />
| Online overview<br />
| http://iho.int/iho_pubs/standard/S-52/S-52_e6.0_EN.pdf<br />
|-<br />
| Type of standard<br />
| IHO International Standard<br/>Application level<br />
|-<br />
| Related standard(s)<br />
| IMO Performance Standards for ECDIS, 1995 edition <br/> S-57 IHO Transfer Standard for Digital Hydrographic Data <br/>IHO INT 1 Symbols, Abbreviations, Terms used on Charts <br/>IEC 62288 Presentation of navigation related information - General requirements, methods of test and required test results <br/>IEC 61174 ECDIS - Operational and performance requirements, methods of testing and required test results <br/>IEC 60945 Maritime Navigation and Radio Communication Equipment and Systems – General Requirements – Methods of Testing and Required Test Results <br/> IHO S-32 Appendix 1: Hydrographic Dictionary - Glossary of ECDIS-related terms <br/> IHO S-60 User´s Handbook on Datum Transformations involving WGS-84 <br />
|-<br />
| Application<br />
| S-52 defines the specifications for Chart Content and Display Aspects of Electronic Chart Display and Information Systems (ECDIS), which are intended to contribute to the safe operation of ECDIS.<br />
|-<br />
| Conformance classes<br />
| None specified<br />
|}<br />
<br />
== Scope == <br />
These Specifications for Chart Content and Display Aspects of ECDIS are intended to contribute to the safe operation of ECDIS by:<br />
<br />
:* ensuring a base and supplementary levels of display for ENC data; standards of symbols, colours and their standardized assignment to features; scale limitations of data presentation; and appropriate compatibility with paper chart symbols as standardized in the Chart Specifications of the IHO.<br />
:* ensuring the display is clear and unambiguous,<br />
:* ensuring that there is no uncertainty over the meaning of colours and symbols on the display,<br />
:* establishing an accepted pattern for ECDIS presentation that becomes familiar to mariners and so can be recognized instantly without confusion.<br />
<br />
== Implementation benefits == <br />
S-52 was developed to ensure safety and efficiency of navigation by satisfying the requirements set out in the performance standards for ECDIS. The colours and symbols defined in S-52 are based on common symbology of conventional paper charts. However, due to the special conditions of the ECDIS chart display as a computer generated image, the ECDIS presentation of ENC data does not match the appearance of a conventional paper chart closely. The specification of symbols and colours ensures that the charts can be used and understood by individuals from different regions.<br />
<br />
== Implementation guidelines == <br />
ECDIS have become popular with the widespread use of computer systems. S-52 provides specifications to ensure that these ECDIS are developed and used optimally. S-52 consists of the following components:<br />
<br />
:# Considerations – organising the display <br/>The design considerations go into great detail about the display and the different aspects of the data to be displayed. They provide detailed guidelines for the design process.<br />
:# Symbol specifications for areas, lines and points, and for text <br/>The symbol set for ECDIS is described in this specification and illustrations can be obtained in the ECDIS Chart 1 (in the Presentation Library).<br />
:# Specifications for colours <br/>EDCIS manufacturers can use any technology to develop their display as long as it meets the requirements set out in this specification. The requirements for the colours are described in detail and an accompanying file can be downloaded from the Presentation Library.<br />
:# Specifications for the display screen <br/>The physical display requirements specify a minimum screen size of 270mm X 270mm, a resolution greater than 864 lines per mm, and the use of 64 colours. The calibration of the display should be performed according to the guidelines in Annex 1 of S-52.<br />
<br />
There are also two annexes on the procedure for initial calibration of colour displays and the maintenance thereof.</div>Tebogo Mokwenahttp://wiki.icaci.org/index.php?title=S-52_Specifications_for_chart_content_and_display_aspects_of_ECDIS&diff=831S-52 Specifications for chart content and display aspects of ECDIS2016-06-24T10:25:23Z<p>Tebogo Mokwena: /* Overview */</p>
<hr />
<div>== Overview ==<br />
{| class="wikitable"<br />
| Full name<br />
| [http://www.iho.int/iho_pubs/standard/S-52/S-52_e6.0_EN.pdf S-52, Specifications for chart content and display aspects of ECDIS]<br />
|-<br />
| Version<br />
| Edition 6.0.0<br />
|-<br />
| Amendments<br />
| None<br />
|-<br />
| Corrigenda<br />
| None<br />
|-<br />
| Published by<br />
| IHO<br />
|-<br />
| Languages<br />
| English<br />
|-<br />
| Online overview<br />
| http://iho.int/iho_pubs/standard/S-52/S-52_e6.0_EN.pdf<br />
|-<br />
| Type of standard<br />
| IHO International Standard<br/>Application level<br />
|-<br />
| Related standard(s)<br />
| IMO Performance Standards for ECDIS, 1995 edition <br/> S-57 IHO Transfer Standard for Digital Hydrographic Data <br/>IHO INT 1 Symbols, Abbreviations, Terms used on Charts <br/>IEC 62288 Presentation of navigation related information - General requirements, methods of test and required test results <br/>IEC 61174 ECDIS - Operational and performance requirements, methods of testing and required test results <br/>IEC 60945 Maritime Navigation and Radio Communication Equipment and Systems – General Requirements – Methods of Testing and Required Test Results <br/> IHO S-32 Appendix 1: Hydrographic Dictionary - Glossary of ECDIS-related terms <br/>[http://www.iho.int/iho_pubs/standard/S60_Ed3Eng.pdf IHO S-60 User´s Handbook on Datum Transformations involving WGS-84] <br />
|-<br />
| Application<br />
| S-52 defines the specifications for Chart Content and Display Aspects of Electronic Chart Display and Information Systems (ECDIS), which are intended to contribute to the safe operation of ECDIS.<br />
|-<br />
| Conformance classes<br />
| None specified<br />
|}<br />
<br />
== Scope == <br />
These Specifications for Chart Content and Display Aspects of ECDIS are intended to contribute to the safe operation of ECDIS by:<br />
<br />
:* ensuring a base and supplementary levels of display for ENC data; standards of symbols, colours and their standardized assignment to features; scale limitations of data presentation; and appropriate compatibility with paper chart symbols as standardized in the Chart Specifications of the IHO.<br />
:* ensuring the display is clear and unambiguous,<br />
:* ensuring that there is no uncertainty over the meaning of colours and symbols on the display,<br />
:* establishing an accepted pattern for ECDIS presentation that becomes familiar to mariners and so can be recognized instantly without confusion.<br />
<br />
== Implementation benefits == <br />
S-52 was developed to ensure safety and efficiency of navigation by satisfying the requirements set out in the performance standards for ECDIS. The colours and symbols defined in S-52 are based on common symbology of conventional paper charts. However, due to the special conditions of the ECDIS chart display as a computer generated image, the ECDIS presentation of ENC data does not match the appearance of a conventional paper chart closely. The specification of symbols and colours ensures that the charts can be used and understood by individuals from different regions.<br />
<br />
== Implementation guidelines == <br />
ECDIS have become popular with the widespread use of computer systems. S-52 provides specifications to ensure that these ECDIS are developed and used optimally. S-52 consists of the following components:<br />
<br />
:# Considerations – organising the display <br/>The design considerations go into great detail about the display and the different aspects of the data to be displayed. They provide detailed guidelines for the design process.<br />
:# Symbol specifications for areas, lines and points, and for text <br/>The symbol set for ECDIS is described in this specification and illustrations can be obtained in the ECDIS Chart 1 (in the Presentation Library).<br />
:# Specifications for colours <br/>EDCIS manufacturers can use any technology to develop their display as long as it meets the requirements set out in this specification. The requirements for the colours are described in detail and an accompanying file can be downloaded from the Presentation Library.<br />
:# Specifications for the display screen <br/>The physical display requirements specify a minimum screen size of 270mm X 270mm, a resolution greater than 864 lines per mm, and the use of 64 colours. The calibration of the display should be performed according to the guidelines in Annex 1 of S-52.<br />
<br />
There are also two annexes on the procedure for initial calibration of colour displays and the maintenance thereof.</div>Tebogo Mokwenahttp://wiki.icaci.org/index.php?title=S-4_Regulations_of_the_IHO_for_international_(INT)_charts_and_chart_specifications_of_the_IHO&diff=830S-4 Regulations of the IHO for international (INT) charts and chart specifications of the IHO2016-06-24T10:23:51Z<p>Tebogo Mokwena: /* Overview */</p>
<hr />
<div>== Overview == <br />
{| class="wikitable"<br />
| Full name<br />
|[http://www.iho.int/iho_pubs/standard/S-4/S4%20V4-6-0_ENG_April16.pdf S-4, Regulations of the IHO for international (INT) charts and chart specifications of the IHO]<br />
|-<br />
| Version<br />
| Edition 4.6.0<br />
|-<br />
| Amendments<br />
| None<br />
|-<br />
| Corrigenda<br />
| None<br />
|-<br />
| Published by<br />
| IHO<br />
|-<br />
| Languages<br />
| English, French<br />
|-<br />
| Online overview<br />
| http://www.iho.int/iho_pubs/standard/S-4/S4%20V4-6-0_ENG_April16.pdf<br />
|-<br />
| Type of standard<br />
| IHO Regulations <br/>Application level<br />
|-<br />
| Related standard(s)<br />
| [http://wiki.icaci.org/index.php?title=Guidance_for_the_preparation_and_maintenance_of_international_chart_schemes_and_catalogue_of_international_charts S-11 Guidance for the preparation and maintenance of international chart schemes and catalogue of international charts] <br/>S-57 IHO transfer standard for digital hydrographic data <br/>[http://wiki.icaci.org/index.php?title=Specifications_for_chart_content_and_display_aspects_of_ECDIS S-52 Specifications for chart content and display aspects of ECDIS] <br/>[http://wiki.icaci.org/index.php?title=ENCs:_Production,_maintenance_and_distribution_guidance S-65 ENCs: Production, maintenance and distribution guidance]<br />
|-<br />
| Application<br />
| S-4 specifies regulations of the IHO for International (INT) charts and chart specifications of the IHO. It specifically looks at regulations of the IHO for International (INT) charts, chart specifications of the IHO for medium- and large-scale National and International (INT) charts, and chart specifications of the IHO for small-scale International (INT) charts.<br />
|-<br />
| Conformance classes<br />
| None specified<br />
|}<br />
<br />
== Scope == <br />
The publication S-4 (previously M-4) ‘Regulations of the IHO for International (INT) Charts and Chart Specifications of the IHO’, includes:<br />
:* Part A: ‘Regulations of the IHO for International (INT) Charts’<br />
:* Part B: ‘Chart Specifications of the IHO for Medium- and Large-scale National and International (INT) Charts’<br />
:* Part C: ‘Chart Specifications of the IHO for Small-Scale International (INT) Charts’<br />
<br />
The three parts of S-4 are further subdivided into Sections dealing with specific topics. Regulations and Specifications relating to particular topics may be found either by their subject matter in the Contents page at the beginning of each Section, or by reference to column 5 of INT 1 for Part B and the index for Part C. Cross referencing draws attention to related Regulations, Technical Resolutions and Specifications. This publication was developed and maintained by the IHO’s Chart Standardization Committee to 2003. Its maintenance is now the responsibility of the Chart Standardization and Paper Chart Working Group, to which comments and corrections should be advised.<br />
<br />
== Implementation benefits == <br />
The regulations set out in S-4 are very detailed and provide guidelines for every aspect of a chart from design through production to dissemination. It is important that charts are designed and produced according to these regulations and guidelines to ensure safety for navigation. The intended users need to be able to read and understand charts produced by any country at any scale; this can only be ensured through rigorous regulations.<br />
<br />
== Implementation guidelines == <br />
When S-4 was originally prepared, the term chart referred to a paper chart. Since then, electronic charts have become widely used. Digital charts require additional regulations, which are set out in S-52, S-57 and S-61. S-4 provides regulations for three types of charts:<br />
<br />
:# International Charts<br/>There are two types of international charts: marine navigation and information source. Marine navigation charts are produced by national hydrographical offices to cover international waters. The main aim of these charts is to assist in the safe navigation of coastal waters. Information sources are large-scale chart publications showing the detailed configuration of the seabed offshore. The information about the seabed shape is required by various users, for example, for navigation and construction purposes.<br />
:# Medium- and Large-scale Charts <br/>Medium- and large-scale charts are charts with a scale of 1:2 000 000 and larger.<br />
:# Small-Scale Charts <br/> Small-scale charts are charts with a scale smaller than 1:2 000 000. These charts provide a complete and comprehensive small-scale coverage, usable by all nations, for the world’s oceans.<br />
<br />
S-4 specifies regulations for the following aspects of international charts: general, schemas of International charts, specifications for International charts, maintenance of international charts, exchange of reproduction material, and financial aspects.<br />
<br />
For medium- and large-scale charts the regulations are more detailed. The regulations cover topics such as the terms and conventions used, translations of terms, symbology, geographic units, text styles, and use of colour.<br />
<br />
Lastly, the regulations for small scale charts look at the chart in general, the format of the chart, topography, hydrography and aids to navigation, geographic names, and style sheets.</div>Tebogo Mokwenahttp://wiki.icaci.org/index.php?title=ISO_19117:2012_Geographic_information_-_Portrayal&diff=829ISO 19117:2012 Geographic information - Portrayal2016-06-24T10:18:07Z<p>Tebogo Mokwena: /* Overview */</p>
<hr />
<div>== Overview ==<br />
{| class="wikitable"<br />
| Full name<br />
|[http://www.iso.org/iso/home/store/catalogue_tc/catalogue_detail.htm?csnumber=46226 ISO 19117:2012, Geographic information -- Portrayal]<br />
|-<br />
| Version<br />
| Edition 2<br />
|-<br />
| Amendments<br />
| None<br />
|-<br />
| Corrigenda<br />
| None<br />
|-<br />
| Published by<br />
| ISO/TC 211<br />
|-<br />
| Languages<br />
| English, French<br />
|-<br />
| Online overview<br />
| Not available yet<br />
|-<br />
| Type of standard<br />
| ISO International Standard <br/>Meta level<br />
|-<br />
| Related standard(s)<br />
| [http://wiki.icaci.org/index.php?title=Styled_Layer_Descriptor OpenGIS Styled Layer Descriptor Profile of the Web Map Service Implementation Specification] <br/>[http://wiki.icaci.org/index.php?title=Symbology_Encoding Symbology Encoding Implementation Specification]<br />
|-<br />
| Application<br />
| ISO 19117 specifies a conceptual schema for describing symbols, portrayal functions that map geo-spatial features to symbols, and the collection of symbols and portrayal functions into portrayal catalogues.<br />
|-<br />
| Conformance classes<br />
| Portrayal core (general) <br/>Portrayal core – symbol <br/>Portrayal core – portrayal function <br/>Portrayal core – portrayal catalogue <br/>Portrayal core plus condition function extension <br/>Portrayal core plus context extension <br/>Portrayal core plus symbol parameter extension <br/>Portrayal core plus compound symbol extension <br/>Portrayal core plus complex symbol extension <br/>Portrayal core plus reusable symbol component extension <br/>Portrayal core plus symbol parameter extension<br />
|}<br />
<br />
== Scope ==<br />
This International Standard specifies a conceptual schema for describing symbols, portrayal functions that map geo-spatial features to symbols, and the collection of symbols and portrayal functions into portrayal catalogues. This conceptual schema can be used in the design of portrayal systems. It allows feature data to be separate from portrayal data, permitting data to be portrayed in a dataset independent manner.<br />
<br />
:This International Standard does not address the following:<br />
:* standard symbol collection (e.g. International Chart 1 – IHO);<br />
:* a standard for symbol graphics (e.g. scalable vector graphics [SVG]);<br />
:* portrayal services (e.g. web map service);<br />
:* capability for non-visual portrayal (e.g. aural symbology);<br />
:* dynamic rendering (e.g. on the fly contouring of tides);<br />
:* portrayal finishing rules (e.g. generalization, resolve overprinting, displacement rules);<br />
:* 3D symbolization (e.g. simulation modelling).<br />
<br />
== Implementation benefits == <br />
The conceptual schema defined by ISO 19117 allows the development of a portrayal for a specific application field. This schema can be exchanged and implemented in different applications. One of the main benefits of ISO 19117 is that it will allow datasets to be displayed according to some specification without changing or manipulating the original dataset. Portrayal allows the client to create a unique representation for features to communicate an explicit meaning. ISO 19117 can be applied to a variety of products, such as hard copy maps, digital maps, and online representations in a web browser.<br />
<br />
== Implementation guidelines == <br />
Portrayal is the process of presenting information to humans. The portrayal mechanism (as shown in the figure below) makes it possible to portray a single dataset in multiple ways without altering the dataset. Each feature will point to a rule that is applied when the feature is generated on a map, for example.<br />
<br />
[[File:Figure 11.1.png|thumbnail|center|alt= Illustration of the portrayal mechanism (Source ISO 19117:2012).|Figure 11.1 Illustration of the portrayal mechanism (Source ISO 19117:2012).]]<br />
<br />
The conceptual schema described in ISO 19117 is based on UML and follows the guidelines set out in ISO/TS 19103. The schema contains a series of UML packages, defining the portrayal core, and extensions for conditional functions, context, compound symbols, reusable components, parameterised symbols and the portrayal functions that use parameterised symbols. Fundamental to the concept of portrayal is that the symbols and portrayal functions shall be not be part of the dataset.<br />
<br />
: The portrayal core package is divided into three sub packages:<br />
<br />
:#Portrayal Function package<br/>This package is used to define mapping functions. The information to be portrayed shall be defined in an application schema, and all mandatory and conditional (if required) portrayal function elements shall be present in the functions. This package also ensures that elements, which are not being portrayed, are mapped to symbols with no components.<br />
:#Symbol package<br/>Symbol package is used to define symbols. For the symbol package a default symbol needs to be assigned, and all the mandatory and conditional (if required) symbol elements that shall be present. The core symbol class supports basic symbols, however, one can extend it, for example, with hatch fills or reusable symbols.<br />
:#Portrayal Catalogue package<br/>The portrayal catalogue package is used to define portrayal catalogues. The portrayal information, such as the feature portrayal functions and applicable symbols shall be present in the portrayal.</div>Tebogo Mokwenahttp://wiki.icaci.org/index.php?title=ISO_19117:2012_Geographic_information_-_Portrayal&diff=828ISO 19117:2012 Geographic information - Portrayal2016-06-24T10:17:07Z<p>Tebogo Mokwena: /* Overview */</p>
<hr />
<div>== Overview ==<br />
{| class="wikitable"<br />
| Full name<br />
|[http://www.iso.org/iso/home/store/catalogue_tc/catalogue_detail.htm?csnumber=46226 ISO 19117:2012, Geographic information -- Portrayal]<br />
|-<br />
| Version<br />
| Edition 2<br />
|-<br />
| Amendments<br />
| None<br />
|-<br />
| Corrigenda<br />
| None<br />
|-<br />
| Published by<br />
| ISO/TC 211<br />
|-<br />
| Languages<br />
| English, French<br />
|-<br />
| Online overview<br />
| Not available yet<br />
|-<br />
| Type of standard<br />
| ISO International Standard <br/>Meta level<br />
|-<br />
| Related standard(s)<br />
| [http://wiki.icaci.org/index.php?title=Styled_Layer_Descriptor OpenGIS Styled Layer Descriptor Profile of the Web Map Service Implementation Specification] <br/>[http://wiki.icaci.org/index.php?title=Symbology_EncodingOpenGIS Symbology Encoding Implementation Specification]<br />
|-<br />
| Application<br />
| ISO 19117 specifies a conceptual schema for describing symbols, portrayal functions that map geo-spatial features to symbols, and the collection of symbols and portrayal functions into portrayal catalogues.<br />
|-<br />
| Conformance classes<br />
| Portrayal core (general) <br/>Portrayal core – symbol <br/>Portrayal core – portrayal function <br/>Portrayal core – portrayal catalogue <br/>Portrayal core plus condition function extension <br/>Portrayal core plus context extension <br/>Portrayal core plus symbol parameter extension <br/>Portrayal core plus compound symbol extension <br/>Portrayal core plus complex symbol extension <br/>Portrayal core plus reusable symbol component extension <br/>Portrayal core plus symbol parameter extension<br />
|}<br />
<br />
== Scope ==<br />
This International Standard specifies a conceptual schema for describing symbols, portrayal functions that map geo-spatial features to symbols, and the collection of symbols and portrayal functions into portrayal catalogues. This conceptual schema can be used in the design of portrayal systems. It allows feature data to be separate from portrayal data, permitting data to be portrayed in a dataset independent manner.<br />
<br />
:This International Standard does not address the following:<br />
:* standard symbol collection (e.g. International Chart 1 – IHO);<br />
:* a standard for symbol graphics (e.g. scalable vector graphics [SVG]);<br />
:* portrayal services (e.g. web map service);<br />
:* capability for non-visual portrayal (e.g. aural symbology);<br />
:* dynamic rendering (e.g. on the fly contouring of tides);<br />
:* portrayal finishing rules (e.g. generalization, resolve overprinting, displacement rules);<br />
:* 3D symbolization (e.g. simulation modelling).<br />
<br />
== Implementation benefits == <br />
The conceptual schema defined by ISO 19117 allows the development of a portrayal for a specific application field. This schema can be exchanged and implemented in different applications. One of the main benefits of ISO 19117 is that it will allow datasets to be displayed according to some specification without changing or manipulating the original dataset. Portrayal allows the client to create a unique representation for features to communicate an explicit meaning. ISO 19117 can be applied to a variety of products, such as hard copy maps, digital maps, and online representations in a web browser.<br />
<br />
== Implementation guidelines == <br />
Portrayal is the process of presenting information to humans. The portrayal mechanism (as shown in the figure below) makes it possible to portray a single dataset in multiple ways without altering the dataset. Each feature will point to a rule that is applied when the feature is generated on a map, for example.<br />
<br />
[[File:Figure 11.1.png|thumbnail|center|alt= Illustration of the portrayal mechanism (Source ISO 19117:2012).|Figure 11.1 Illustration of the portrayal mechanism (Source ISO 19117:2012).]]<br />
<br />
The conceptual schema described in ISO 19117 is based on UML and follows the guidelines set out in ISO/TS 19103. The schema contains a series of UML packages, defining the portrayal core, and extensions for conditional functions, context, compound symbols, reusable components, parameterised symbols and the portrayal functions that use parameterised symbols. Fundamental to the concept of portrayal is that the symbols and portrayal functions shall be not be part of the dataset.<br />
<br />
: The portrayal core package is divided into three sub packages:<br />
<br />
:#Portrayal Function package<br/>This package is used to define mapping functions. The information to be portrayed shall be defined in an application schema, and all mandatory and conditional (if required) portrayal function elements shall be present in the functions. This package also ensures that elements, which are not being portrayed, are mapped to symbols with no components.<br />
:#Symbol package<br/>Symbol package is used to define symbols. For the symbol package a default symbol needs to be assigned, and all the mandatory and conditional (if required) symbol elements that shall be present. The core symbol class supports basic symbols, however, one can extend it, for example, with hatch fills or reusable symbols.<br />
:#Portrayal Catalogue package<br/>The portrayal catalogue package is used to define portrayal catalogues. The portrayal information, such as the feature portrayal functions and applicable symbols shall be present in the portrayal.</div>Tebogo Mokwenahttp://wiki.icaci.org/index.php?title=S-99_Operational_procedures_for_the_organisation_and_management_of_S-100_geospatial_information_registry&diff=827S-99 Operational procedures for the organisation and management of S-100 geospatial information registry2016-06-24T10:15:24Z<p>Tebogo Mokwena: /* Overview */</p>
<hr />
<div>==Overview==<br />
{| class="wikitable"<br />
| Full name<br />
| [http://www.iho.int/iho_pubs/standard/S-99/S-99_Ed1.1.0_Nov12_EN.pdf S-99, Operational procedures for the organisation and management of S-100 geospatial information registry]<br />
|-<br />
| Version<br />
| Edition 1.1.0<br />
|-<br />
| Amendments<br />
| None<br />
|-<br />
| Corrigenda<br />
| None<br />
|-<br />
| Published by<br />
| IHO<br />
|-<br />
| Languages<br />
| English <br />
|-<br />
| Online overview<br />
| [http://iho.int/iho_pubs/standard/S-99/Draft_S-99_Ed1.1.0_Nov12_EN.pdf http://iho.int/iho_pubs/standard/S-99/Draft_S-99_Ed1.1.0_Nov12_EN.pdf] <br />
|-<br />
| Type of standard<br />
| IHO International Standard<br/>Application level<br />
|-<br />
| Related standard(s)<br />
| ISO 19135:2005, Geographic information -- Procedures for item registration<br/> S-100 IHO Universal Hydrographic Data Model<br />
|-<br />
| Application<br />
| S-99 defines the roles, responsibilities and procedures for operating and managing the S-100 Geospatial Information Registry and its component registers. <br />
|-<br />
| Conformance classes<br />
| None specified<br />
|}<br />
<br />
== Scope ==<br />
In January 2010 the IHO adopted S-100, a framework geo-spatial standard for hydrographical and related data. S-100 is aligned with the ISO 19100 series of geographic standards – thereby making the use of hydrographical and other geographic data more interoperable than previously using the IHO S-57 data transfer standard. S-100 is underpinned by a Registry and component Registers based on ISO 19135 - Procedures for registration of items of geographic information. IHO owns and manages the Registry. This document describes the roles, responsibilities and procedures for operating and managing the S-100 Geospatial Information Registry and its component Registers. <br />
<br />
As a result of the practical use of the S-100 Registry by the Registry Manager and other organisations outside the IHO that are using S-100, a number of revisions have been introduced in edition 1.1.0. These revisions concern conceptual rather than substantive changes to the notion of domains and the previous theoretical subdivision of the Registry into main and supplementary registers. The time limit on consideration of proposals has also been extended from 30 days to 60 days in order to allow stakeholders, as represented by the Domain Control Bodies, more time for consideration. <br />
<br />
== Implementation benefits ==<br />
S-99 clears up the roles and responsibilities for registers and registries within IHO. This ensures that the process is transparent to avoid mistakes and disagreements, and confirms that the responsibilities are clear to the tasked individual. <br />
<br />
== Implementation guidelines ==<br />
Roles and responsibilities for management of the registry and registers are addressed. IHO is the owner of the registry and all registers in the S-100 Geospatial Information Registry. A registry manager shall be appointed to perform the day-to-day operations, maintenance and backup of the database. The registry manager shall ensure that for each register being managed 1) all aspects of the registration process are handled in accordance with good business practices; 2) the content of the register is accurate; and 3) only authorised persons can make changes to the content of the register. <br />
<br />
A Domain Control Body (DCB) shall be appointed and be responsible for acting as the spokesperson for their domain, gather opinions on any new proposals, and forward a decision to the register manager within a given time frame. An Executive Control Body (ECB) shall consist of representatives of each of the domains. The ECB shall monitor and advise the register manager(s) and act as the arbiters for any decisions or disputes. Criteria for the eligibility of members to the bodies are provided in S-99. <br />
<br />
Proposals for new register items, clarification of existing register items, and suppression or retirement of register items can be submitted by organisations through a register web interface. The proposals will be evaluated and either be accepted, rejected or sent back to the submitting organisation for changes. Appeals are allowed.</div>Tebogo Mokwenahttp://wiki.icaci.org/index.php?title=S-58_IHO_Recommended_ENC_validation_checks&diff=826S-58 IHO Recommended ENC validation checks2016-06-24T10:14:33Z<p>Tebogo Mokwena: /* Overview */</p>
<hr />
<div>== Overview ==<br />
{| class="wikitable"<br />
| Version<br />
| Edition 5.0.0<br />
|-<br />
| Amendments<br />
| None<br />
|-<br />
| Corrigenda<br />
| None<br />
|-<br />
| Published by<br />
| IHO<br />
|-<br />
| Languages<br />
| English<br />
|-<br />
| Online overview<br />
| http://iho.int/iho_pubs/draft_pubs/S-58_e5.0.0/Draft_S-58_ENC_Validation_Checks_e5.0.0.pdf<br />
|-<br />
| Type of standard<br />
| IHO Recommendation <br/>Instance level<br />
|-<br />
| Related standard(s)<br />
| S-57 IHO transfer standard for digital hydrographic data<br />
|-<br />
| Application<br />
| S-57 recommends the validation checks which producers of validation tools for Electronic Navigational Charts (ENC) should implement in their software. S-58 replaces S-57 IHO transfer standard for digital hydrographic data Edition 3.1.0.<br />
|-<br />
| Conformance classes<br />
| None specified<br />
|-<br />
| Implementation benefits<br />
| ENC software validates that data are conformant with the IHO S-57 ENC product specification. Conformance violations are labelled as either an error or as a warning. This is important to ensure that the correct ENC is produced and that the software is implemented according to the same standard.<br />
|-<br />
| Products<br />
| S-58 should be implemented by all ENC applications.<br />
|}</div>Tebogo Mokwenahttp://wiki.icaci.org/index.php?title=ISO_19159-1:2014_Geographic_information_-_Calibration_and_validation_of_remote_sensing_imagery_sensors_-_Part_1:_Optical_sensors&diff=825ISO 19159-1:2014 Geographic information - Calibration and validation of remote sensing imagery sensors - Part 1: Optical sensors2016-06-24T10:13:22Z<p>Tebogo Mokwena: /* Overview */</p>
<hr />
<div>==Overview==<br />
{| class="wikitable"<br />
| Full name<br />
| [http://www.iso.org/iso/home/store/catalogue_tc/catalogue_detail.htm?csnumber=60080 ISO 19159-1:2014, Geographic information – Calibration and validation of remote sensing imagery sensors – Part 1: Optical sensors]<br />
|-<br />
| Version<br />
| Edition 1<br />
|-<br />
| Amendments<br />
| None<br />
|-<br />
| Corrigenda<br />
| None<br />
|-<br />
| Published by<br />
| ISO/TC 211<br />
|-<br />
| Languages<br />
| English<br />
|-<br />
| Online overview<br />
| Not available yet <br />
|-<br />
| Type of standard<br />
| ISO Technical Specification<br/>Application level<br />
|-<br />
| Related standard(s)<br />
| [http://wiki.icaci.org/index.php?title=Metadata_%E2%80%93_Part_2:_Extensions_for_imagery_and_gridded_data ISO 19115-2:2009, Geographic information – Metadata – Part 2: Extensions for imagery and gridded data]<br/>[http://wiki.icaci.org/index.php?title=Imagery_sensor_models_for_geopositioning ISO/TS 19130:2010, Geographic information – Imagery sensor models for geopositioning]<br/>[http://wiki.icaci.org/index.php?title=Schema_for_coverage_geometry_and_functions ISO 19123:2005, Geographic information – Schema for coverage geometry and functions]<br />
|-<br />
| Application<br />
| The specification defines the service metadata for the calibration procedures of optical remote sensing sensors, as well as the associated data types and code lists. Such information is useful for the evaluation of the quality of images recorded by sensors. Future parts of this specification will specify calibration and validation for other types of sensors.<br />
|-<br />
| Conformance classes<br />
| Project <br/>OpticsSensor: Geometry <br/>OpticsSensor: Radiometry <br/>OpticsCalibrationFacility: Geometry <br/>OpticsCalibrationFacility: Radiometry <br/>OpticsValidation <br/>Documentation<br />
|}<br />
<br />
== Scope ==<br />
ISO/TS 19159-1 defines the calibration and validation of airborne and space borne remote sensing imagery sensors. <br />
<br />
The term calibration refers to geometry, radiometry and spectral, and includes the instrument calibration in a laboratory as well as in-situ calibration methods. <br />
<br />
The validation methods address validation of the calibration information. <br />
<br />
ISO/TS 19159-1 also addresses the associated metadata related to calibration and validation that has not been defined in other ISO geographic information standards. <br />
<br />
The specified sensors include optical sensors of the type frame cameras and line cameras (2D CCD scanners).<br />
<br />
== Implementation benefits ==<br />
Vast amounts of remotely sensed imaging data are collected through a variety of sensors. The images themselves are used as is, but are also frequently used in the preparation of derived geo-spatial datasets, such as, topographic data and digital elevation models. The quality of these geo-spatial datasets depends, amongst others, on the quality of the measuring instruments that originally sensed the images. The quality of the measuring instruments is determined and documented during calibration.<br />
<br />
Calibration can be a costly and time-consuming exercise. Therefore, sometimes strategies are devised to combine longer time intervals between subsequent calibrations with simplified intermediate calibration procedures. The simplified intermediate calibrations save on costs and bridge the time gap, while still ensuring a traceable level of quality. ISO/TS 19159-1:2014 refers to these intermediate calibrations as validations. <br />
<br />
The quality of a wide variety of geo-spatial datasets depends on the quality of the measuring instruments used to sense images. Sharing information about the calibration and validation of the quality measuring instruments of sensors facilitates the evaluation of the quality of the images. The different parts of ISO/TS 19159 specify service and data requirements for the calibration of remote sensing imagery sensors and the validation of the calibration information and procedures. They do not, however, address the validation of the data and the derived products. The first part, ISO/TS 19159-1:2014, is concerned with optical sensors, i.e. airborne photogrammetric cameras and space borne optical sensors. These include digital frame cameras that take 2-dimensional images as a whole, line cameras that apply the pushbroom or whiskbroom principle, as well as sensors that record electromagnetic radiation of the infrared spectrum, such as, thermal, multispectral and hyperspectral cameras.<br />
<br />
== Implementation guidelines ==<br />
ISO 19159-1:2014 specifies service and/or data conformance in seven conformance classes:<br />
<br />
* Project<br />
* OpticsSensor: Geometry<br />
* OpticsSensor: Radiometry<br />
* OpticsCalibrationFacility: Geometry<br />
* OpticsCalibrationFacility: Radiometry<br />
* OpticsValidation<br />
* Documentation<br />
<br />
Service conformance requires the use of an appropriate service interface for the project, sensor, calibration facility and validation respectively. To test conformance, the relevant service interface documentation is verified against the service interface requirements specified in ISO 19159-1:2014.<br />
<br />
Data conformance requires an adequate application class for the expression of information about the project, sensor, calibration facility, validation and documentation respectively. To test conformance, the application schema documentation is verified against the requirements specified in ISO 19159-1:2014.<br />
<br />
Data and service interface requirements in ISO 19150-1:2014 are specified in a UML model and associated data dictionary. For example, data conformance for a project requires the application class with information about a project to make use of the three codelists illustrated in Classes with information about calibration and validation, i.e. CA_CalibrationType, CA_TargetEnvironment and CA_IrradianceModel. Note that additional values may be added to a codelist for a specific implementation. As another example, service conformance of the project’s service interface requires it to use the interfaces specified in the CA_CalibrationValidation, CA_PhotoFlight, CA_Radiation and CA_Target classes in Classes with information about calibration and validation.<br />
<br />
<br />
[[File:MAfA_SectionC_Integrated_V10_html_10_3.png|center|thumbnail|Classes with information about calibration and validation (Source ISO/TS 19159-1:2014)]]</div>Tebogo Mokwenahttp://wiki.icaci.org/index.php?title=ISO/TS_19158:2012_Geographic_information_-_Quality_assurance_of_data_supply&diff=824ISO/TS 19158:2012 Geographic information - Quality assurance of data supply2016-06-24T10:10:22Z<p>Tebogo Mokwena: /* Overview */</p>
<hr />
<div>==Overview==<br />
{| class="wikitable"<br />
| Full name<br />
| [http://www.iso.org/iso/home/store/catalogue_tc/catalogue_detail.htm?csnumber=32576 ISO/TS 19158:2012, Geographic information – Quality assurance of data supply]<br />
|-<br />
| Version<br />
| Edition 1<br />
|-<br />
| Amendments<br />
| None<br />
|-<br />
| Corrigenda<br />
| None<br />
|-<br />
| Published by<br />
| ISO/TC 211<br />
|-<br />
| Languages<br />
| English<br />
|-<br />
| Online overview<br />
| [https://www.iso.org/obp/ui/#iso:std:iso:ts:19158:ed-1:v1:en https://www.iso.org/obp/ui/#iso:std:iso:ts:19158:ed-1:v1:en] <br />
|-<br />
| Type of standard<br />
| ISO Technical Specification<br/>Application level<br />
|-<br />
| Related standard(s)<br />
| [http://wiki.icaci.org/index.php?title=Data_product_specifications ISO 19131:2007, Geographic information – Data product specifications]<br/>[http://wiki.icaci.org/index.php?title=Data_quality ISO 19157:2012, Geographic information – Data quality]<br/> ISO 9000:2015, Quality management systems – Fundamentals and vocabulary<br />
|-<br />
| Application<br />
| The standard provides a quality assurance framework for the producer and customer in their production relationship. Methods to manage the quality of production are identified. <br />
|-<br />
| Conformance classes<br />
| Organisation (i.e. supplier of geographic data)<br />
|}<br />
<br />
== Scope ==<br />
ISO 19158:2012 provides a framework for quality assurance specific to geographic information. It is based upon the quality principles and quality evaluation procedures of geographic information identified in ISO 19157 and the general quality management principles defined in ISO 9000.<br />
<br />
The framework enables a customer to satisfy itself that its suppliers, both internal and external, are capable of delivering geographic information to the required quality. Fundamental to the framework is the assurance of the supplier’s ability to understand and meet the quality requirements. Through the quality assurance framework both the customer and the supplier are able to consider the quality required at the earliest opportunity in the production/update process.<br />
<br />
Principles and responsibilities of the relationship between the customer and the supplier that facilitate the framework are provided. The responsibility for the quality assessment procedure is shared between the customer and the supplier.<br />
<br />
ISO 19158:2012 is applicable to customers and suppliers of all geographic information where the quality of the product may be impacted upon by the supplier’s processes in any of the following scenarios:<br />
<br />
* there is an agreement or legislation for the supply of data acquisition services,<br />
* data acquisition services are being tendered for, and<br />
* one or more suppliers exist in the supply chain.<br />
<br />
ISO 19158:2012 is not applicable for the supply of legacy datasets or ‘off the shelf’ products where there is no further data production or update activity to manage.<br />
<br />
== Implementation benefits ==<br />
By applying the quality assurance framework in ISO 19158:2012, an organisation can facilitate the production of a product that meets requirements in terms of cost, quantity, quality and timeliness. Applying the framework also provides opportunities for better understanding of requirements by all involved in production and update especially within multiple producer environments; reduced data throughput time; reduced rework; improved data quality; and increased confidence within a mutually beneficial relationship leading to lower costs for both supplier and organisation.<br />
<br />
== Implementation guidelines ==<br />
In a typical approach to the production and/or update of geographic information, a customer requests a supplier to produce geographic information according to a data product specification, expecting the supplier to deliver the product on time, within budget and according to the specified data quality requirements. However, the customer has little or no input into the supplier’s processes. This approach creates risks, because until the product is delivered, there is limited proof that the supplier has the appropriate capabilities to deliver the required product. These risks are aggravated by complex data, a demand for increased speed to market and outsourcing, i.e. the customer and supplier are in different organisations. <br />
<br />
A product is created from the involvement of individuals and teams in several interrelated processes combining outputs to produce a final product. For example, the production of a map of lookout points in a nature reserve comprises two processes: data collection and map production. The data collection process comprises a first sub-process where a team collects the coordinates of the lookout points using GPS devices. During the second sub-process, an individual at a desktop adds appropriate attributes for each lookout point, e.g. the name, animals likely to be seen and surrounding vegetation types. The map production process can be subdivided into a map preparation sub-process and a printing sub-process. By introducing quality evaluation processes to the outputs from each process, sub-process, team and individual, it is possible to determine how the quality of the final product will be affected. Example: Quality assurance framework applied to the production of a map of lookout points provides an overview of the quality assurance framework applied to the example above. <br />
<br />
<br />
[[File:MAfA_SectionC_Integrated_V10_html_10_2.gif|center|thumbnail|Example: Quality assurance framework applied to the production of a map of lookout points]]<br />
<br />
<br />
An organisation implementing ISO 19158:2012 ensures that its suppliers of geographic information implement quality assurance and quality assessment procedures conforming to ISO 19158:2012. Quality assurance is a quality management activity focused on providing confidence that quality requirements will be fulfilled (by a supplier), while a quality assessment procedure is a procedure by which a customer assures that a supplier is capable of consistently delivering a product to the required quality.<br />
<br />
A supplier of geographic information conforms to ISO 19158:2012 if its quality assurance<br />
<br />
* has identified the necessary processes and sub-processes for the production and/or update of the geographic information;<br />
* has identified the geographic data quality requirements for each process and sub-process according to the requirements in ISO 19157; <br />
* has identified the quality requirements for the volume of delivery, schedule of delivery and cost of production and/or update for each process and sub-process; and <br />
* has identified the output quality of the process, sub-process and individuals for data production and/or update. <br />
<br />
Three levels of quality assurance with increasing opportunity for risk mitigation are specified in ISO 19158:2012: basic, operational and full. The customer confirms the level of assurance achieved by a production process: <br />
<br />
# Basic quality assurance is achieved if the supplier can demonstrate to the customer that the product specification, the data quality acceptance levels (or limits) and the delivery schedule are understood and that a process is in place to deliver the required volumes and data quality.<br />
# Operational quality assurance is achieved if the customer has assured that the processes, sub-processes, teams and individuals involved in the production of a product deliver the required quality. The operational quality assessment procedure has to start immediately after confirmation that the basic level of assurance has been achieved and the quality assessment has to be completed within the agreed period. <br />
# Full quality assurance is achieved if the supplier has sustained operational quality assurance for all sub-processes in the production or update process for a period agreed between the supplier and the customer.<br />
<br />
In the example above, basic quality assurance may only assure the customer of the supplier’s intent to produce a map, whilst operational quality assurance will assure the customer of the supplier’s capability to produce the map in its operating environment. Full quality assurance assures the customer that the supplier has sustained the capability to produce maps over an agreed period of time. <br />
<br />
ISO 19158:2012 provides guidance and examples on how to implement the quality assessment framework, as well as the supplier’s responsibilities in the quality assurance procedure.</div>Tebogo Mokwenahttp://wiki.icaci.org/index.php?title=ISO/TS_19158:2012_Geographic_information_-_Quality_assurance_of_data_supply&diff=823ISO/TS 19158:2012 Geographic information - Quality assurance of data supply2016-06-24T10:09:43Z<p>Tebogo Mokwena: /* Overview */</p>
<hr />
<div>==Overview==<br />
{| class="wikitable"<br />
| Full name<br />
| [http://www.iso.org/iso/home/store/catalogue_tc/catalogue_detail.htm?csnumber=32576 ISO/TS 19158:2012, Geographic information – Quality assurance of data supply]<br />
|-<br />
| Version<br />
| Edition 1<br />
|-<br />
| Amendments<br />
| None<br />
|-<br />
| Corrigenda<br />
| None<br />
|-<br />
| Published by<br />
| ISO/TC 211<br />
|-<br />
| Languages<br />
| English<br />
|-<br />
| Online overview<br />
| [https://www.iso.org/obp/ui/#iso:std:iso:ts:19158:ed-1:v1:en https://www.iso.org/obp/ui/#iso:std:iso:ts:19158:ed-1:v1:en] <br />
|-<br />
| Type of standard<br />
| ISO Technical Specification<br/>Application level<br />
|-<br />
| Related standard(s)<br />
| [http://wiki.icaci.org/index.php?title=Data_product_specifications ISO 19131:2007, Geographic information – Data product specifications]<br/>[http://wiki.icaci.org/index.php?title=Data_quality ISO 19157:2012, Geographic information – Data quality]<br/>[http://www.iso.org/iso/home/store/catalogue_tc/catalogue_detail.htm?csnumber=45481 ISO 9000:2015, Quality management systems – Fundamentals and vocabulary]<br />
|-<br />
| Application<br />
| The standard provides a quality assurance framework for the producer and customer in their production relationship. Methods to manage the quality of production are identified. <br />
|-<br />
| Conformance classes<br />
| Organisation (i.e. supplier of geographic data)<br />
|}<br />
<br />
== Scope ==<br />
ISO 19158:2012 provides a framework for quality assurance specific to geographic information. It is based upon the quality principles and quality evaluation procedures of geographic information identified in ISO 19157 and the general quality management principles defined in ISO 9000.<br />
<br />
The framework enables a customer to satisfy itself that its suppliers, both internal and external, are capable of delivering geographic information to the required quality. Fundamental to the framework is the assurance of the supplier’s ability to understand and meet the quality requirements. Through the quality assurance framework both the customer and the supplier are able to consider the quality required at the earliest opportunity in the production/update process.<br />
<br />
Principles and responsibilities of the relationship between the customer and the supplier that facilitate the framework are provided. The responsibility for the quality assessment procedure is shared between the customer and the supplier.<br />
<br />
ISO 19158:2012 is applicable to customers and suppliers of all geographic information where the quality of the product may be impacted upon by the supplier’s processes in any of the following scenarios:<br />
<br />
* there is an agreement or legislation for the supply of data acquisition services,<br />
* data acquisition services are being tendered for, and<br />
* one or more suppliers exist in the supply chain.<br />
<br />
ISO 19158:2012 is not applicable for the supply of legacy datasets or ‘off the shelf’ products where there is no further data production or update activity to manage.<br />
<br />
== Implementation benefits ==<br />
By applying the quality assurance framework in ISO 19158:2012, an organisation can facilitate the production of a product that meets requirements in terms of cost, quantity, quality and timeliness. Applying the framework also provides opportunities for better understanding of requirements by all involved in production and update especially within multiple producer environments; reduced data throughput time; reduced rework; improved data quality; and increased confidence within a mutually beneficial relationship leading to lower costs for both supplier and organisation.<br />
<br />
== Implementation guidelines ==<br />
In a typical approach to the production and/or update of geographic information, a customer requests a supplier to produce geographic information according to a data product specification, expecting the supplier to deliver the product on time, within budget and according to the specified data quality requirements. However, the customer has little or no input into the supplier’s processes. This approach creates risks, because until the product is delivered, there is limited proof that the supplier has the appropriate capabilities to deliver the required product. These risks are aggravated by complex data, a demand for increased speed to market and outsourcing, i.e. the customer and supplier are in different organisations. <br />
<br />
A product is created from the involvement of individuals and teams in several interrelated processes combining outputs to produce a final product. For example, the production of a map of lookout points in a nature reserve comprises two processes: data collection and map production. The data collection process comprises a first sub-process where a team collects the coordinates of the lookout points using GPS devices. During the second sub-process, an individual at a desktop adds appropriate attributes for each lookout point, e.g. the name, animals likely to be seen and surrounding vegetation types. The map production process can be subdivided into a map preparation sub-process and a printing sub-process. By introducing quality evaluation processes to the outputs from each process, sub-process, team and individual, it is possible to determine how the quality of the final product will be affected. Example: Quality assurance framework applied to the production of a map of lookout points provides an overview of the quality assurance framework applied to the example above. <br />
<br />
<br />
[[File:MAfA_SectionC_Integrated_V10_html_10_2.gif|center|thumbnail|Example: Quality assurance framework applied to the production of a map of lookout points]]<br />
<br />
<br />
An organisation implementing ISO 19158:2012 ensures that its suppliers of geographic information implement quality assurance and quality assessment procedures conforming to ISO 19158:2012. Quality assurance is a quality management activity focused on providing confidence that quality requirements will be fulfilled (by a supplier), while a quality assessment procedure is a procedure by which a customer assures that a supplier is capable of consistently delivering a product to the required quality.<br />
<br />
A supplier of geographic information conforms to ISO 19158:2012 if its quality assurance<br />
<br />
* has identified the necessary processes and sub-processes for the production and/or update of the geographic information;<br />
* has identified the geographic data quality requirements for each process and sub-process according to the requirements in ISO 19157; <br />
* has identified the quality requirements for the volume of delivery, schedule of delivery and cost of production and/or update for each process and sub-process; and <br />
* has identified the output quality of the process, sub-process and individuals for data production and/or update. <br />
<br />
Three levels of quality assurance with increasing opportunity for risk mitigation are specified in ISO 19158:2012: basic, operational and full. The customer confirms the level of assurance achieved by a production process: <br />
<br />
# Basic quality assurance is achieved if the supplier can demonstrate to the customer that the product specification, the data quality acceptance levels (or limits) and the delivery schedule are understood and that a process is in place to deliver the required volumes and data quality.<br />
# Operational quality assurance is achieved if the customer has assured that the processes, sub-processes, teams and individuals involved in the production of a product deliver the required quality. The operational quality assessment procedure has to start immediately after confirmation that the basic level of assurance has been achieved and the quality assessment has to be completed within the agreed period. <br />
# Full quality assurance is achieved if the supplier has sustained operational quality assurance for all sub-processes in the production or update process for a period agreed between the supplier and the customer.<br />
<br />
In the example above, basic quality assurance may only assure the customer of the supplier’s intent to produce a map, whilst operational quality assurance will assure the customer of the supplier’s capability to produce the map in its operating environment. Full quality assurance assures the customer that the supplier has sustained the capability to produce maps over an agreed period of time. <br />
<br />
ISO 19158:2012 provides guidance and examples on how to implement the quality assessment framework, as well as the supplier’s responsibilities in the quality assurance procedure.</div>Tebogo Mokwenahttp://wiki.icaci.org/index.php?title=ISO_19157:2013_Geographic_information_-_Data_quality&diff=822ISO 19157:2013 Geographic information - Data quality2016-06-24T10:08:06Z<p>Tebogo Mokwena: /* Overview */</p>
<hr />
<div>==Overview==<br />
{| class="wikitable"<br />
| Full name<br />
| [http://www.iso.org/iso/home/store/catalogue_tc/catalogue_detail.htm?csnumber=32575 ISO 19157:2013, Geographic information – Data quality]<br />
|-<br />
| Version<br />
| Edition 1<br />
|-<br />
| Amendments<br />
| None<br />
|-<br />
| Corrigenda<br />
| None<br />
|-<br />
| Published by<br />
| ISO/TC 211<br />
|-<br />
| Languages<br />
| English<br />
|-<br />
| Online overview<br />
| [https://www.iso.org/obp/ui/#iso:std:iso:19157:ed-1:v1:en https://www.iso.org/obp/ui/#iso:std:iso:19157:ed-1:v1:en] <br />
|-<br />
| Type of standard<br />
| ISO International Standard<br/>Meta level<br />
|-<br />
| Related standard(s)<br />
| [http://wiki.icaci.org/index.php?title=Metadata_Fundamentals ISO 19115-1:2013, Geographic information – Metadata – Part 1: Fundamentals]<br/>[http://wiki.icaci.org/index.php?title=Metadata_%E2%80%93_Part_2:_Extensions_for_imagery_and_gridded_data ISO 19115-2:2009, Geographic information – Metadata – Part 2: Extensions for imagery and gridded data]<br/>[http://wiki.icaci.org/index.php?title=Quality_assurance_of_data_supply ISO 19158:2012, Geographic information – Quality assurance of data supply]<br />
|-<br />
| Application<br />
| The standard specifies the description, evaluation and reporting of the quality of geographic data. <br />
|-<br />
| Conformance classes<br />
| Data quality evaluation process<br/>Data quality metadata<br/>Standalone quality report<br/>Data quality measure<br />
|}<br />
<br />
== Scope ==<br />
[http://www.iso.org/iso/home/store/catalogue_tc/catalogue_detail.htm?csnumber=32575 ISO 19157:2013] establishes the principles for describing the quality for geographic data. It defines components for describing data quality; specifies components and content structure of a register for data quality measures; describes general procedures for evaluating the quality of geographic data; and establishes principles for reporting data quality.<br />
<br />
The standard also defines a set of data quality measures for use in evaluating and reporting data quality. It is applicable to data producers providing quality information to describe and assess how well a dataset conforms to its product specification and to data users attempting to determine whether or not specific geographic data are of sufficient quality for their particular application.<br />
<br />
The standard does not attempt to define minimum acceptable levels of quality for geographic data.<br />
<br />
==Implementation benefits==<br />
[http://www.iso.org/iso/home/store/catalogue_tc/catalogue_detail.htm?csnumber=32575 ISO 19157:2013] provides a standard way for describing the quality of geographic data. Such descriptions are useful when a producer has to evaluate how well a dataset meets the criteria described in its product specification. For example, if the producer outsourced the acquisition of the data, [http://www.iso.org/iso/home/store/catalogue_tc/catalogue_detail.htm?csnumber=32575 ISO 19157:2013] could be used to evaluate and describe the quality of the received data during acceptance testing. <br />
<br />
Geographic data are increasingly shared and exchanged. As a result, geographic data are often used for purposes that differ from the purpose for which it was originally captured. Complete descriptions of the quality of a dataset encourage and facilitate the sharing, interchange and use of appropriate datasets.<br />
<br />
Another benefit of implementing [http://www.iso.org/iso/home/store/catalogue_tc/catalogue_detail.htm?csnumber=32575 ISO 19157:2013] is that the quality information could assist a user who has to decide whether a specific dataset is appropriate for an intended use or application. If the user has to decide between two or more datasets, standardized quality descriptions simplify comparing the datasets. If [http://www.iso.org/iso/home/store/catalogue_tc/catalogue_detail.htm?csnumber=32575 ISO 19157:2013] is implemented, quality reports are expressed in a comparable way and there is a common understanding of the quality measures that have been used. A project to develop an XML of [http://www.iso.org/iso/home/store/catalogue_tc/catalogue_detail.htm?csnumber=32575 ISO 19157:2013] has begun.<br />
<br />
==Implementation guidelines ==<br />
ISO 19157:2013 cancels and replaces ISO/TS 19138:2006, ISO 19114:2003 and ISO 19113:2002. According to ISO 19157:2013, data quality comprises six elements: completeness, thematic accuracy, logical consistency, temporal quality, positional accuracy and usability. Each element is comprised of a number of sub-elements, for example, completeness (commission and omission), logical consistency (conceptual, domain, format, topological), etc. These elements are used to describe data quality, i.e. how well a specific dataset meets the criteria for the different elements set forth in its product specification or user requirements. Evaluation against the criteria is done either quantitatively or subjectively (non-quantitatively). The latter case applies if a detailed data product specification does not exist or if the data product specification lacks quantitative measures and descriptors. Three metaquality elements – confidence, ‘representativity’ and homogeneity – provide quantitative and qualitative statements about the evaluation against the criteria and its result. <br />
<br />
Quality information can be provided for different units of data, e.g. a dataset series, a dataset or a subset of a dataset with common characteristics. A data quality unit comprises of a scope and data quality elements. The scope specifies the extent, spatial and/or temporal and/or common characteristic(s) of the unit for which the quality information is provided. <br />
<br />
In ISO 19157:2013, quality related information provided by purpose, usage and lineage of geographic data conforms to [http://wiki.icaci.org/index.php?title=Metadata_Fundamentals ISO 19115-1:2014]. <br />
<br />
ISO 19157:2013 specifies four conformance classes, i.e. the standard can be implemented for four different quality aspects of geo-spatial datasets, each briefly described below. <br />
<br />
<br />
1. Implementing a data quality evaluation process conforming to ISO 19157:2013<br />
<br />
A data quality evaluation process conforming to ISO 19157:2013 comprises of four steps: <br />
<br />
* Step 1 - Specify the data quality units to be evaluated. Study the data product specification to identify applicable data quality units and their scope. For each data quality unit, identify the applicable data quality element(s). See example in Example: Data quality units.<br />
* Step 2 - Specify the data quality measures to be used to describe quality of each data quality element of a data quality unit. The requirements in the data product specification provide guidance on applicable data quality measures. See example in Example: Data quality measures. The data quality measures in the table are from the list of standardized data quality measures in ISO 19157:2013. It is also possible to describe user-defined quality measures, see further below, and to maintain a collection of such measures in a catalogue or register. <br />
* Step 3 - Specify the data quality evaluation procedures, i.e. the evaluation method(s) to be applied. The method can be direct (based on inspection of the items in the dataset) or indirect (based on external knowledge, such as lineage metadata). Direct evaluation is further classified by the source against which the evaluation is done: internal if only the data in the dataset is evaluated or external if there is reference to external data (e.g. satellite imagery or ground truth). ISO 19157:2013 includes guidance on how to sample data for evaluation.<br />
* Step 4 - Determine the output of the data quality evaluation, i.e. perform the data quality evaluation described in Steps 1-3 above. Additional results may be produced by aggregating or by deriving from existing results without carrying out a new evaluation. How to report the results of the data quality evaluation is described elsewhere in this chapter.<br />
<br />
{| class="wikitable"<br />
|+Example: Data quality units<br />
| '''Data quality unit'''<br />
| '''Scope'''<br />
| '''Data quality elements'''<br />
|-<br />
| Topographic dataset<br />
| All features in the dataset<br />
| Completeness (commission and omission), thematic accuracy (correct classification)<br />
|-<br />
| Street network<br />
| Street features in the entire dataset<br />
| Logical inconsistency (topological inconsistency)<br />
|}<br />
<br />
<br />
{| class="wikitable"<br />
|+Example: Data quality measures<br />
| '''Data quality unit'''<br />
| '''Data quality element'''<br />
| '''Data quality measure'''<br />
| '''Method'''<br />
|-<br />
| Topographic dataset <br />
| Completeness (commission)<br />
| Measure 1: Excess item<br/><br />
Measure 2: Number of excess items<br/><br />
Measure 3: Number of duplicate feature instances<br />
| Direct external<br/><br />
Direct external<br/><br />
Direct internal<br />
|-<br />
| Topographic dataset<br />
| Completeness (omission)<br />
| Measure 1: Missing item<br />
Measure 2: Number of missing items<br />
| Direct external<br />
Direct external<br />
|-<br />
| Topographic dataset<br />
| Thematic accuracy (correct classification)<br />
| Measure 1: Number of incorrectly classified features<br/><br />
Measure 2: Misclassification rate<br />
| Direct external<br/><br />
Direct external<br />
|-<br />
| Street network<br />
| Logical inconsistency (topological inconsistency)<br />
| Measure 1: Number of missing connections due to undershoots<br/><br />
Measure 2: Number of missing connections due to overshoots<br/><br />
Measure 3: Number of invalid self-intersect errors<br/><br />
Measure 4: Number of invalid self-overlap errors<br />
| Direct internal<br/><br />
Direct internal<br/><br />
Direct internal<br/><br />
Direct internal<br />
|}<br />
<br />
<br />
''2. Implementing data quality metadata conforming to ISO 19157:2013''<br />
<br />
Data quality metadata describes the quality of geographic data. ISO 19157:2013 specifies a conceptual model of the different components to be used when describing the quality of geographic data. Overview of the components to be used to describe data quality provides and overview of the components and their relationships to each other. A data dictionary, including definitions for all the components, is provided in the standard. Data quality metadata conforming to ISO 19157:2013 conforms to this conceptual model and is reported in conformance with ISO 19115:2003 and ISO 19115-2:2009 <br />
<br />
<br />
[[File:MAfA_SectionC_Integrated_V10_html_10_1.png|center|thumb|Overview of the components to be used to describe data quality (Source: ISO 19157:2013)]]<br />
<br />
<br />
<br />
''3. Implementing data quality reports conforming to ISO 19157:2013''<br />
<br />
The first (and obvious) requirement is that the quality report comprises quality metadata conforming to ISO 19157:2013 (see 2. above), i.e. it includes sections on all appropriate aspects of quality and the description of components follow the rules defined in the standard. Additional information can be added to the report, but the structure of the report is not prescribed. Example: Section of a data quality report is an example of a section of a data quality report for the quality evaluation process described above. <br />
<br />
<br />
{| class="wikitable"<br />
|+Example: Section of a data quality report<br />
| '''Data quality unit'''<br />
| '''Data quality element'''<br />
| '''Data quality measure'''<br />
| '''Result'''<br />
<br />
|-<br />
| Topographic dataset <br />
| Completeness (commission)<br />
| Measure 2: Number of excess items<br/><br />
Measure 3: Number of duplicate feature instances<br />
| 153<br/><br />
1,036<br />
|-<br />
| Topographic dataset<br />
| Completeness (omission)<br />
| Measure 2: Number of missing items<br />
| 697<br />
|-<br />
| Topographic dataset<br />
| Thematic accuracy (correct classification)<br />
| Measure 1: Number of incorrectly classified features<br/><br />
Measure 2: Misclassification rate<br />
| 8,774 <br/><br />
10%<br />
|-<br />
| Street network<br />
| Logical inconsistency (topological inconsistency)<br />
| Measure 1: Number of missing connections due to undershoots<br/><br />
Measure 2: Number of missing connections due to overshoots<br/><br />
Measure 3: Number of invalid self-intersect errors<br/><br />
Measure 4: Number of invalid self-overlap errors<br />
| 139<br/><br />
57<br/><br />
11<br/><br />
6<br />
|}<br />
<br />
<br />
''4. Implementing data quality measures conforming to ISO 19157:2013''<br />
<br />
A data quality measure conforming to ISO 19157:2013 is structurally and semantically well defined and described and modelled as specified in the standard. Such a measure is described by at least an identifier, a name, an element name, definition and a value type. Optional descriptors are an alias, description, a value structure, example, a basic measure and one or more source references and/or parameters. Note that full inspection is most appropriate for small populations or for tests that can be accomplished by automated means. For larger populations, checking a representative part of the data and reporting the quality result as a percentage rate is more appropriate and practical.</div>Tebogo Mokwenahttp://wiki.icaci.org/index.php?title=ISO_19131:2007_Geographic_information_-_Data_product_specifications&diff=821ISO 19131:2007 Geographic information - Data product specifications2016-06-24T10:05:56Z<p>Tebogo Mokwena: /* Overview */</p>
<hr />
<div><br />
==Overview==<br />
{| class="wikitable sortable"<br />
|-<br />
| Full name<br />
|[http://www.iso.org/iso/home/store/catalogue_tc/catalogue_detail.htm?csnumber=36760 ISO 19131:2007, Geographic information – Data product specifications.]<br />
|-<br />
| Version<br />
| Edition 1<br />
|-<br />
| Amendments<br />
| ISO 19131:2007/Amd 1:2011<br />
|-<br />
| Corrigenda<br />
| None<br />
|-<br />
| Published by<br />
| ISO/TC 211<br />
|-<br />
| Languages<br />
| English, French<br />
|-<br />
| Online overview<br />
| https://www.iso.org/obp/ui/#iso:std:iso:19131:ed-1:v1:en<br />
|-<br />
| Type of standard<br />
| ISO International Standard<br/>Meta level<br />
|-<br />
| Related standard(s)<br />
|[http://wiki.icaci.org/index.php?title=Metadata ISO 19115:2003, Geographic information -- Metadata]<br />
|-<br />
| Application<br />
| The standard is essentially the inverse of ISO 19115 and uses the metadata concepts,elements and entities in ISO 19115. ISO 19131 describes what the user wants (datasets,services, etc.) – the product specification – in a structured way so that it can be compared directly to the metadata of candidate offerings or used to create a new product that meets the specification.<br />
|-<br />
| Conformance<br />
classes<br />
|Data product specification sections<br/>Mandatory items<br/>Item details.<br />
|}<br />
<br />
==Scope==<br />
ISO 19131:2007 describes requirements for the specification of geographic data products, based upon the concepts of other ISO 19100 International Standards. It also provides help in the creation of data product specifications, so that they are easily understood and fit for their intended purpose.<br />
<br />
==Implementation benefits==<br />
ISO 19131:2007 describes in a structured way what the user wants, that is, the specification of the product required. While aimed primarily at specifying required datasets, the standard can also be used to specify services and other geospatial products. The standard is essentially the inverse of ISO 19115:2003 and uses the concepts and metadata elements and entities in ISO 19115:2003. Hence, it means that one can compare a product specification directly and in detail with the metadata of candidate offerings.<br />
<br />
As the specification and metadata are both structured and contain many encoded elements, much of the matching can be done automatically, to filter out candidates that do not meet the specification. Candidate products can be obtained from within a user’s domain, but also from elsewhere. Hence, even an expert user might not be aware of possible sources for suitable products. This powerful capability enables of the ISO 19115:2003 and ISO 19131:2007 combination to filter out suitable candidates automatically.<br />
<br />
An ISO 19131:2007 product specification can also be used to guide the development of a new product that meets the specification, and for others needing a similar product to see if the proposed product will also meet their needs. In South Africa, for example, the Committee for Spatial Information (CSI) is using ISO 19131:2007 for developing the form to be used by data custodians for informing the CSI of their planned data capture programmes, such as for aerial photography.<br />
<br />
==Implementation guidelines==<br />
While ISO 19131:2007 does include annexes with UML class diagrams and data dictionaries as tables (as is done in ISO 19115:2003), it is probably still necessary for the user to consult ISO 19115:2003 when using ISO 19131:2007, as ISO 19115:2003 has more details about the metadata (and hence, product specification) concepts, elements and entities.<br />
ISO 19131:2007 specifies that a data product specification shall describe the following aspects of the product:<br />
<br />
# Overview: source and provenance of the specification, relevant terminology and an informal description of the required product, such as the dataset content, spatial and temporal extents, purpose, sources, production processes and maintenance.<br />
# Specification scopes: the scope of the required product, in terms of spatial and temporal extent, feature types, property types, property values, spatial representation, product hierarchy and partitioning (e.g. between the dynamic and static sorts of data in the required product), The concept ‘product hierarchy’ is not defined in the standard, but this applies to each of the partitions of the product being specified, as they can be at different levels: attribute, attribute type, feature, feature type, tile, dataset, series, etc. For each partition, the level code, level name, level description, extent and coverage are to be specified.<br />
# Data product identification: title, abstract, topic category (one of the pre-defined themes that applies to the required product, such as farming, boundaries, elevation or transportation) and geographic description (actually, spatial extent) shall be provided and alternate title, purpose, spatial representation type (e.g. vector or raster), spatial resolution and supplemental information may be provided.<br />
# Data content and structure: feature-based, coverage-based or imagery data. The content of a feature-based product shall be described in terms of an application schema (content, structure and constraints applicable) and a feature catalogue (or classification system). The application schema can be very complicated, catering for relationships between feature, property and attribute types, such as feature operations, feature association, inheritance relations and constraints. Imagery data are a form of coverage and a coverage is a sub-type of a feature, which behaves like a function returning one or more feature attribute values for some point within a spatiotemporal domain. A coverage requires an identifier, a description, the type and additional information.<br />
# Reference systems: the spatial reference system (using coordinates or geographic identifiers) and the temporal reference system.<br />
# Data quality: the data quality requirements, acceptable conformance quality levels and corresponding data quality measures. In ISO 19131:2007, the data quality requirements are specified in terms of ISO 19113 and ISO/TS 19138, but these have now been revised by ISO 19157:2013 (described in [[Data quality]]).<br />
# Data capture: an optional specification of the sources and processes that shall or may be used for the data capture.<br />
# Data maintenance: an optional specification of the principles and criteria to be applied in maintaining the product, such as maintenance and update frequency.<br />
# Portrayal: an optional specification of the portrayal rules and a set of portrayal specifications, for specifying how the data may be represented graphically. This could be particularly important for a web service, for example.<br />
# Data product delivery: delivery format (e.g. transfer standard) and delivery medium (e.g. CD-ROM). The delivery format details may include the name and version of the format; subset, profile or product specification; structure of the delivery file; language(s) and character encoding. The delivery medium details may include units of delivery (how the data are arranged on the medium), estimated sizes, name of the delivery medium and other delivery information.<br />
# Additional information: a catchall for anything else to be specified for the product, such as constraint information regarding access and use.<br />
# Metadata: the metadata that shall be provided with the product, defined in terms of ISO 19115:2003.<br />
<br />
With the publication of [http://www.iso.org/iso/home/store/catalogue_tc/catalogue_detail.htm?csnumber=46226 ISO 19117:2012, Geographic information – Portrayal], [http://www.iso.org/iso/home/store/catalogue_tc/catalogue_detail.htm?csnumber=32575 ISO 19157:2013, Geographic information – Data quality], and ISO 19115-1:2014, Geographic information – Metadata – Part 1: Fundamentals, ISO 19131:2007 is due to be revised.</div>Tebogo Mokwenahttp://wiki.icaci.org/index.php?title=ISO_19112:2003_Geographic_information_-_Spatial_referencing_by_geographic_identifiers&diff=820ISO 19112:2003 Geographic information - Spatial referencing by geographic identifiers2016-06-24T10:04:43Z<p>Tebogo Mokwena: /* Overview */</p>
<hr />
<div>==Overview==<br />
{| class="wikitable"<br />
|-<br />
| Full name<br />
| [http://www.iso.org/iso/home/store/catalogue_tc/catalogue_detail.htm?csnumber=26017 ISO 19112:2003, Geographic information – Spatial referencing by geographic identifiers]<br />
|-<br />
| Version<br />
| Edition 1 <br />
|-<br />
| Amendments<br />
| None<br />
|-<br />
| Corrigenda<br />
| None<br />
|-<br />
| Published by<br />
| ISO/TC 211<br />
|-<br />
| Languages<br />
| English<br />
|-<br />
| Online overview<br />
| https://www.iso.org/obp/ui/#iso:std:iso:19112:ed-1:v1:en<br />
|-<br />
| Type of standard<br />
| ISO International Standard Meta level<br />
|-<br />
| Related standard(s)<br />
| [http://wiki.icaci.org/index.php?title=Conformance_and_testing ISO 19105:2000, Geographic information — Conformance and testing] <br/>[http://wiki.icaci.org/index.php?title=Spatial_schema ISO 19107:2003, Geographic information — Spatial schema] <br/>[http://wiki.icaci.org/index.php?title=Spatial_referencing_by_coordinates ISO 19111:2007, Geographic information – Spatial referencing by coordinates] <br/> [http://wiki.icaci.org/index.php?title=Metadata ISO 19115:2003, Geographic information – Metadata]<br />
|-<br />
| Application<br />
| A spatial reference system is a system for identifying position in the real world. There are two ways of identifying positions: using coordinates or using geographic identifiers. In a spatial reference system using geographic identifiers, positions are identified by a label or code that identifies a location. <br/>The standard can be applied in two ways: firstly, to describe a spatial reference system using geographic identifiers, and secondly, to describe a directory of geographic identifiers, known as a gazetteer.<br />
|-<br />
| Conformance classes<br />
| Spatial reference system <br/> Gazetteer<br />
|-<br />
| Fundamental geo-spatial dataset<br />
| Category: Administration and spatial organisation <br/> Data Theme: Geographic names<br />
|}<br />
<br />
==Scope==<br />
<br />
ISO 19112:2003 defines the conceptual schema for spatial references based on geographic identifiers. It establishes a general model for spatial referencing using geographic identifiers, defines the components of a spatial reference system and defines the essential components of a gazetteer.<br />
<br />
Spatial referencing by coordinates is addressed in ISO 19111. However, a mechanism for recording complementary coordinate references is included.<br />
<br />
ISO 19112:2003 enables producers of data to define spatial reference systems using geographic identifiers and assists users in understanding the spatial references used in datasets. It enables gazetteers to be constructed in a consistent manner and supports the development of other standards in the field of geographic information.<br />
<br />
ISO 19112:2003 is applicable to digital geographic data, and its principles may be extended to other forms of geographic data such as maps, charts and textual documents.<br />
<br />
==Implementation benefits==<br />
Spatial reference systems assist users in understanding the spatial references used in geographic datasets, maps, charts or textual documents. Conforming to ISO 19112:2003 ensures that gazetteers and their location instances are well defined. This facilitates interoperability and exchange of gazetteers. For example, a gazetteer can be used in more than one software product or different gazetteers can be used in the same software. Well-defined gazetteers also support the maintenance (e.g. through versioning) of location instances.<br />
<br />
==Implementation guidelines==<br />
A spatial reference identifies the position of a feature in the real world. The position can be identified either explicitly by using coordinates, or indirectly by using a geographic identifier, i.e. a label or code that uniquely identifies a location on, below or above the earth’s surface. In ISO 19112:3003 the location identified by the geographic identifier is regarded as a (feature and) reference for other features.<br />
<br />
A spatial reference system using geographic identifiers is comprised of a set of one or more location types, together with their corresponding geographic identifiers. These location types may be related to each other through aggregation or disaggregation, possibly forming a hierarchy. Refer to the table above for examples of spatial reference systems.<br />
<br />
{{vanchor|foo}}<br />
<div id="what_to_link_to">'''Examples of spatial reference systems by identifier'''</div><br />
{| class="wikitable"<br />
! scope="200" style="width: 225px;" | Spatial reference system<br />
! scope="200" style="width: 225px;" | Location types<br />
! scope="200" style="width: 700px;" |Geographic identifiers<br />
|-<br />
| Municipalities of South Africa<br />
| Province <br/> District municipality <br/> Metropolitan municipality <br/> Municipality<br />
| Province name <br/> District municipality name or identifier <br/> Metropolitan municipality name or identifier <br/> Municipality name or identifier<br />
|-<br />
| Human settlements in a region<br />
| Municipality <br/> Village<br />
| Municipality name or identifier <br/> Village name<br />
|-<br />
| Road names<br />
| Suburb <br/> Road<br />
| Suburb name <br/> Road name or identifier<br />
|}<br />
<br />
A gazetteer is a directory of geographic identifiers for location instances. A location instance is an instance of a specific location type. For example, ‘South Africa’ is a location instance of the ‘country’ location type. The gazetteer may include information about the position of each location instance, such as, a coordinate reference or any other descriptive information about the location instance. More than one gazetteer could exist for a location type. For example, for the ‘Village’ location type '''Table 10.33''', there could be gazetteers for different time periods.<br />
<br />
A spatial reference system by identifier conforming to ISO 19112:2003 meets the following requirements (see examples in ''table below''):<br />
<br />
# The spatial reference system comprises of a set of one or more ISO 19112:2003 conformant location types with a common theme.<br />
# The spatial reference system is described by at least the following four attributes: <br />
#* name, which serves as identifier;<br />
#* theme, which characterises the spatial reference system;<br />
#* overall owner, i.e. the authority with overall responsibility for the spatial reference system; and<br />
#* domain of validity, i.e. the geographic area within which the reference system occurs.<br />
# The spatial reference system is versioned as follows:<br />
#* The version information is included in the name attribute.<br />
#* A new version is created whenever a location type is added, removed or replaced by a new version of a location type.<br />
<br />
'''Descriptions of spatial reference systems by identifier conforming to ISO 19112:2003'''<br />
<br />
{| class="wikitable"<br />
! Name<br />
! Theme<br />
! Overall owner<br />
! Domain of validity<br />
! Location types<br />
|-<br />
| Census 2001 <br/> geographic area <br/> hierarchy structure<br />
| Census<br />
| StatsSA<br />
| South Africa<br />
| Province <br/> Municipality <br/> Main place <br/> Sub place <br/> Enumeration area<br />
|-<br />
| Enumeration area <br/> Karoo after 1994<br />
| Population<br />
| Department of Human Settlements<br />
| Karoo<br />
| Municipality <br/> Village<br />
|-<br />
| Boreholes in the <br/> Kalahari V1.0<br />
| Hydrography<br />
| Department of Water Affairs<br />
| Kalahari desert within Botswana’s borders<br />
| Water management <br/> area <br/> Borehole<br />
|}<br />
<br />
A location type in a spatial reference system conforms to ISO 19112:2003 if it meets the following requirements (see examples in the following table):<br />
# The location type is described by at least the following six attributes:<br />
#* name;<br />
#* theme, e.g. ‘administration’, ‘electoral’, ‘postal’;<br />
#* identification, i.e. the method of uniquely identifying location instances;<br />
#* definition, i.e. the way in which location instances are defined;<br />
#* territory of use, i.e. the geographic area within which the location type occurs; and<br />
#* owner, i.e. the name of an organisation or class of organisations with the ability to create and destroy location instances.<br />
# The location type is versioned; a new version is created whenever one of its attributes is modified. While ISO 19112:2003 does not specify this, it is practical to include version information in the name of the location type.<br />
# The location type is uniquely identified by means of one or more geographic identifiers.<br />
# There is at least one gazetteer of location instances for the location type.<br />
# The location type may be related to parent and child location types, possibly forming a hierarchy.<br />
<br />
'''Example: Descriptions of location types conforming to ISO 19112:2003'''<br />
{| class="wikitable"<br />
! Name<br />
! Theme<br />
! Identification<br />
! Definition<br />
! Territory of use<br />
! Owner<br />
|-<br />
| Municipality<br />
| Administrative boundaries<br />
| Name assigned by the Municipal Demarcation Board<br />
| Municipal boundary demarcated by the Municipal Demarcation Board<br />
| South Africa<br />
| Municipal Demarcation Board<br />
|-<br />
| Village<br />
| Settlement patterns<br />
| Name used by the village population<br />
| A cluster of twenty or more dwellings<br />
| Karoo<br />
| Department of Human Settlements<br />
|-<br />
| Water of management area<br />
| Water resource management<br />
| Alphanumeric identifier assigned by the Department of Water Affairs<br />
| Administrative boundary for the management of water resources<br />
| Botswana<br />
| Department of Water Affairs<br />
|-<br />
| Borehole<br />
| Water resources<br />
| Alphanumeric identifier, which is a combination of the land parcel identifier and a sequence number starting with 1 for each land parcel<br />
| A narrow shaft bored into the ground for the extraction of water<br />
| Kalahari desert within Botswana’s borders<br />
| Department of Water Affairs<br />
|}<br />
<br />
A gazetteer conforming to ISO 19112:2003 meets the following requirements (see examples in following table):<br />
# The gazetteer is described by at least the following four attributes:<br />
#* identifier;<br />
#* territory of use, i.e. the geographic domain covered by the gazetteer;<br />
#* custodian, i.e. the organisation responsible for maintenance of the gazetteer; and<br />
#* the location types for which instances are recorded in the gazetteer.<br />
# Optionally, the gazetteer may also be described by the following two attributes:<br />
#* scope, i.e. description of the location types in the gazetteer; and<br />
#* coordinate reference system, i.e. name of the coordinate reference system used to describe positions of location instances in the gazetteer.<br />
# The gazetteer is versioned; a new version is created whenever any location instance is added, removed or replaced with a new version of a location instance. The version information is included in the name attribute.<br />
# All location instances are recorded in the gazetteer and location instances conform to ISO 19113:2003.<br />
<br />
'''Example: Gazetteer descriptions conforming to ISO 19112:2003'''<br />
{| class="wikitable"<br />
| '''Name'''<br />
| Census 2001 geographic area hierarchy v2000-03<br />
| Karoo villages v2004<br />
| Karoo villages v2006<br />
|-<br />
| '''Territory of use'''<br />
| South Africa<br />
| Northern Cape province<br />
| Northern Cape province<br />
|-<br />
| '''Custodian'''<br />
| StatsSA<br />
| Northern Cape Premier’s Office<br />
| Northern Cape Premier’s Office<br />
|-<br />
| '''Scope'''<br />
| Hierarchical structure of geographic areas used for the Census<br />
| Villages<br />
| Villages<br />
|-<br />
| '''Coordinate reference system'''<br />
| WGS 84 (EPSG::4326)<br />
| WGS 84 (EPSG::4326)<br />
| WGS 84 (EPSG::4326)<br />
|}<br />
<br />
A location instance in a gazetteer conforms to ISO 19112:2003 if it meets the following requirements (see examples in the following table):<br />
# The location instance is associated with a location type.<br />
# The location instance is described by at least the following three attributes:<br />
#* geographic identifier, i.e. the unique identifier for the location instance;<br />
#* geographic extent, i.e. description of the location instance itself; and<br />
#* administrator, i.e. the organisation responsible for defining the characteristics of the location instance.<br />
# Optionally, the location instance may also be described by the following three attributes:<br />
#* temporal extent, i.e. the date on which this location instance was created in the gazetteer;<br />
#* alternative geographic identifier (for the same location instance);<br />
#* position, i.e. coordinates of a representative point of the location instance (e.g. centroid of an administrative area). Note that positions shall be recorded if the geographic identified contains insufficient information to identify the location.<br />
# The location instance is versioned; a new version of a location instance is created whenever any of its attributes is modified, for example, when the boundary of a municipality changes during a demarcation process. The version information is recorded in the temporal extent attribute.<br />
# The location instance may be related to parent and child location instances.<br />
<br />
'''Example: Location instances of the ‘Karoo villages v2004’ gazetteer conforming to ISO 19112:2003'''<br />
{| class="wikitable"<br />
| '''Location type'''<br />
| Municipality<br />
| Village<br />
| Village<br />
|-<br />
| '''Geographic identifier'''<br />
| Hantam<br />
| Buitepos<br />
| Bergsig<br />
|-<br />
| '''Geographic extent'''<br />
| <polygon boundary><br />
| <polygon boundary><br />
| <polygon boundary><br />
|-<br />
| '''Administrator'''<br />
| Municipal Demarcation Board<br />
| Department of Human Settlements<br />
| Department of Human Settlements<br />
|-<br />
| '''Temporal extent'''<br />
| 20010628<br />
| 20040228<br />
| 20040301<br />
|-<br />
| '''Alternative geographic identifier'''<br />
| Hantam Local Municipality (NC 065)<br />
| -<br />
| Mountain view<br />
|-<br />
| '''Position'''<br />
| <coordinates><br />
| <coordinates><br />
| <coordinates><br />
|-<br />
| '''Parent location instance'''<br />
| -<br />
| Hantam<br />
| Hantam<br />
|-<br />
| '''Child location instances'''<br />
| Buitepos <br/> Bergsig<br />
| - <br/> -<br />
| - <br/> -<br />
|}<br />
<br />
[[File:Fig 10 4 UML SRS Gazetteers.jpg |thumbnail|center|alt= UML representation of spatial reference systems and gazetteers (Source ISO 19112:2003)|'''UML representation of spatial reference systems and gazetteers (Source ISO 19112:2003)''']]</div>Tebogo Mokwenahttp://wiki.icaci.org/index.php?title=ISO_19111:2007_Geographic_information_-_Spatial_referencing_by_coordinates&diff=819ISO 19111:2007 Geographic information - Spatial referencing by coordinates2016-06-24T10:02:23Z<p>Tebogo Mokwena: /* Overview */</p>
<hr />
<div>== Overview ==<br />
{| class="wikitable"<br />
| Full name<br />
| [http://www.iso.org/iso/home/store/catalogue_tc/catalogue_detail.htm?csnumber=41126 ISO 19111:2007, Geographic information – Spatial referencing by coordinates]<br />
|-<br />
| Version<br />
| Edition 2<br />
|-<br />
| Amendments<br />
| None<br />
|-<br />
| Corrigenda<br />
| None<br />
|-<br />
| Published by<br />
| ISO/TC 211<br />
|-<br />
| Languages<br />
| English, French<br />
|-<br />
| Online overview<br />
| https://www.iso.org/obp/ui/#iso:std:iso:19111:ed-2:v1:en<br />
|-<br />
| Type of standard<br />
| ISO International Standard<br/>Meta level<br />
|-<br />
| Related standard(s)<br />
| [http://wiki.icaci.org/index.php?title=Temporal_schema ISO 19108:2002, Geographic information – Temporal schema] <br/> ISO/IEC 18026:2009 Information technology -- Spatial Reference Model (SRM)<br />
|-<br />
| Application<br />
| ISO 19111 defines the conceptual schema for the description of spatial referencing by coordinates, optionally extended to spatio-temporal referencing, used in geographic information systems and on maps and charts to store and depict geographic information.<br />
|-<br />
| Conformance classes<br />
| Coordinate reference systems<br/>Coordinate operations between two coordinate reference systems<br />
|-<br />
| Implementation benefits<br />
| Coordinates are vague until the system to which they relate is fully defined. ISO 19111 defines a conceptual schema for describing coordinate reference systems. The schema allows interoperability of the coordinate reference system. It also assists in the development of applications that allow the transformation of coordinates.<br />
|-<br />
| Products<br />
| The concepts from ISO 19111 are implemented commonly in GIS software packages.<br />
|}</div>Tebogo Mokwenahttp://wiki.icaci.org/index.php?title=S-11_Guidance_for_the_preparation_and_maintenance_of_international_chart_schemes_and_catalogue_of_international_charts&diff=818S-11 Guidance for the preparation and maintenance of international chart schemes and catalogue of international charts2016-06-24T10:00:47Z<p>Tebogo Mokwena: /* Overview */</p>
<hr />
<div>==Overview==<br />
{| class="wikitable"<br />
| Full name<br />
| S-11, Guidance for the preparation and maintenance of international chart schemes and catalogue of international charts (formerly M-11)<br />
|-<br />
| Version<br />
| Edition 2.0.5 of May 2012<br />
|-<br />
| Amendments<br />
| None<br />
|-<br />
| Corrigenda<br />
| None<br />
|-<br />
| Published by<br />
| IHO<br />
|-<br />
| Languages<br />
| English, French<br />
|-<br />
| Online overview<br />
| http://iho.int/iho_pubs/standard/S-11/S-11.htm<br />
|-<br />
| Type of standard<br />
| IHO Guide and Catalogue <br/>Application level<br />
|-<br />
| Related standard(s)<br />
| S-4, Regulations for International (INT) Charts and Chart Specifications of the IHO<br />
|-<br />
| Application<br />
| A guideline for preparing and maintaining international nautical charts for printing on paper.<br />
|-<br />
| Conformance classes<br />
| None<br />
|}<br />
<br />
==Implementation benefits==<br />
S-11 is currently only for paper nautical charts, and only for international charts, which have less detail than national charts, to limit updates to items essential for international shipping. It is relevant to those wanting to produce charts of coastal areas and possibly also charts of large inland water bodies, particularly where they include international boundaries, such as the Great Lakes in eastern Africa.<br />
<br />
==Implementation guidelines==<br />
This guideline should only be used by those who have been trained to produce nautical charts and who are familiar with all the relevant IHO standards, including S-4, ''Regulations for International (INT) Charts and Chart Specifications of the IHO'', because of the dangers associated with incorrect, incomplete or inaccurate charts. Section 3 provides guidelines on what features and their attributes to include in the international chart, covering port selection, shipping routes, comparison of catalogues, scale (for berthing, harbours, approaches, coastal navigation, general charts and overviews), projections, dimensions of the chart, limits, overlaps, chart numbering, draft schemes and consultation on them, allocation of producers, and review of the charts.<br />
<br />
Annex A lists the potential printer nations (which are available for printing one’s international chart), which in Africa are Algeria, Morocco, South Africa and Tunisia. Note that most countries will only print maps covering certain areas. Annex B indicates whether or not the potential printer nations can print on A0 paper, and all four African countries can. Annex C provides the terms of reference for the International Charting Coordination Working Groups (ICCWG).<br />
<br />
Part B of S-11 is a catalogue of available international charts by region, which gets updated frequently. Note that Africa’s coasts fall into the International Charting Regions F (Mediterranean), G (Eastern Atlantic), H (SE Atlantic and SW Indian Oceans) and J (North Indian Ocean).</div>Tebogo Mokwenahttp://wiki.icaci.org/index.php?title=ISO_19126:2009_Geographic_information_-_Feature_concept_dictionaries_and_registries&diff=817ISO 19126:2009 Geographic information - Feature concept dictionaries and registries2016-06-24T09:59:50Z<p>Tebogo Mokwena: /* Overview */</p>
<hr />
<div>==Overview==<br />
{| class="wikitable"<br />
| Full name<br />
| [http://www.iso.org/iso/home/store/catalogue_tc/catalogue_detail.htm?csnumber=44875 ISO 19126:2009, Geographic information – Feature concept dictionaries and registries]<br />
|-<br />
| Version<br />
| Edition 1<br />
|-<br />
| Amendments<br />
| None<br />
|-<br />
| Corrigenda<br />
| None<br />
|-<br />
| Published by<br />
| ISO/TC 211<br />
|-<br />
| Languages<br />
| English, French<br />
|-<br />
| Online overview<br />
| https://www.iso.org/obp/ui/#iso:std:iso:19126:ed-1:v1:en<br />
|-<br />
| Type of standard<br />
| ISO International Standard <br/>Meta level<br />
|-<br />
| Related standard(s)<br />
| [http://wiki.icaci.org/index.php?title=Conceptual_schema_language ISO/TS 19103:2005, Geographic information – Conceptual schema language] <br/>[http://wiki.icaci.org/index.php?title=Methodology_for_feature_cataloguing ISO 19110:2005, Geographic information – Methodology for feature cataloguing] <br/>[http://wiki.icaci.org/index.php?title=Metadata ISO 19115:2003, Geographic information – Metadata] <br/>[http://wiki.icaci.org/index.php?title=Data_product_specifications ISO 19131:2007, Geographic information -- Data product specifications] <br/>ISO 19135:2005, Geographic information – Procedures for item registration<br />
|-<br />
| Application<br />
| The main function of this standard is for creating an online register of abstract feature concepts in a dictionary that can then be specified in detail as feature types and in feature catalogues.<br />
|-<br />
| Conformance classes<br />
| General conformance to ISO 19135 <br/>Conformance to ISO 19135 as a hierarchical register <br/>Feature concept dictionary <br/>Register of feature concept dictionaries and/or feature catalogues<br />
|}<br />
<br />
==Scope==<br />
ISO 19126:2009 specifies a schema for feature concept dictionaries to be established and managed as registers. It does not specify schemas for feature catalogues or for the management of feature catalogues as registers. However, because feature catalogues are often derived from feature concept dictionaries, this International Standard does specify a schema for a hierarchical register of feature concept dictionaries and feature catalogues. These registers are in accordance with ISO 19135.<br />
<br />
==Implementation benefits==<br />
The main function of [http://www.iso.org/iso/home/store/catalogue_tc/catalogue_detail.htm?csnumber=44875 ISO 19126:2009] is to specify how to create an online register for a feature concept dictionary, that contains abstract feature concepts, which may then be specified in detail as feature types or in feature catalogues, using [http://www.iso.org/iso/home/store/catalogue_tc/catalogue_detail.htm?csnumber=39965 ISO 19110:2005, Geographic information – Methodology for feature catalogues], or in data product specifications, using [http://www.iso.org/iso/home/store/catalogue_tc/catalogue_detail.htm?csnumber=36760 ISO 19131:2007, Geographic information -- Data product specifications].<br />
<br />
Superficially, this might appear that [http://www.iso.org/iso/home/store/catalogue_tc/catalogue_detail.htm?csnumber=44875 ISO 19126:2009] is too abstract or too theoretical for most users. However, the power of [http://www.iso.org/iso/home/store/catalogue_tc/catalogue_detail.htm?csnumber=44875 ISO 19126:2009] is that it allows different scientific and other disciplines to define and maintain concepts relevant to their field in online registers. Any community of interest can then use these registers in defining their feature types and constructing their feature catalogues appropriately. This is similar to the meta-languages or domain models used in [http://www.iso.org/iso/home/store/catalogue_tc/catalogue_detail.htm?csnumber=44342 ISO 19144-2:2012, Geographic information – Classification systems – Part 2: Land Cover Meta Language (LCML)], and [http://www.iso.org/iso/home/store/catalogue_tc/catalogue_detail.htm?csnumber=51206 ISO 19152, Geographic information – Land Administration Domain Model (LADM)].<br />
<br />
==Implementation guidelines==<br />
Clause 5 of [http://www.iso.org/iso/home/store/catalogue_tc/catalogue_detail.htm?csnumber=44875 ISO 19126:2009] is primarily about establishing a register, according to ISO 19135:2005, Geographic information – Procedures for item registration. A register is defined as a “set of files containing identifiers assigned to items with descriptions of the associated items”, and is maintained in an information system known as a registry. Each register has a register owner (the organisation that establishes the register), a register manager (to whom responsibility for running the register has been delegated by the register owner), a control body (the group of technical experts that makes the decisions about the contents of the register) and users.<br />
<br />
Clause 6 specifies the feature concept dictionary schema, which may include definitions of feature concepts, feature attribute concepts, feature association concepts, feature operation concepts feature role concepts (link between an association and an attribute or operation) and nominal value concepts (category, class, kind or type that may be identified as an element of an enumeration or code list). Each feature concept dictionary has a scope, a possible field of application and possible themes.<br />
<br />
Clause 7 specifies procedures for the management of feature concept dictionaries as registers, which are taken largely from ISO 19135:2005. Clause 8 describes a register of feature concept dictionaries and feature catalogues, again drawing largely on ISO 19135:2005.<br />
<br />
Annex A provides an overview of how feature concepts in dictionaries, catalogues and application schemas relate to one another. Annex C describes the information to be included in registration proposals. Annex D provides an example implementation of the feature concept dictionary schema as a register. Annex E describes the UML notation used.</div>Tebogo Mokwenahttp://wiki.icaci.org/index.php?title=ISO_19126:2009_Geographic_information_-_Feature_concept_dictionaries_and_registries&diff=816ISO 19126:2009 Geographic information - Feature concept dictionaries and registries2016-06-24T09:58:26Z<p>Tebogo Mokwena: /* Overview */</p>
<hr />
<div>==Overview==<br />
{| class="wikitable"<br />
| Full name<br />
| [http://www.iso.org/iso/home/store/catalogue_tc/catalogue_detail.htm?csnumber=44875 ISO 19126:2009, Geographic information – Feature concept dictionaries and registries]<br />
|-<br />
| Version<br />
| Edition 1<br />
|-<br />
| Amendments<br />
| None<br />
|-<br />
| Corrigenda<br />
| None<br />
|-<br />
| Published by<br />
| ISO/TC 211<br />
|-<br />
| Languages<br />
| English, French<br />
|-<br />
| Online overview<br />
| https://www.iso.org/obp/ui/#iso:std:iso:19126:ed-1:v1:en<br />
|-<br />
| Type of standard<br />
| ISO International Standard <br/>Meta level<br />
|-<br />
| Related standard(s)<br />
| [http://wiki.icaci.org/index.php?title=Conceptual_schema_language4 ISO/TS 19103:2005, Geographic information – Conceptual schema language] <br/>http://wiki.icaci.org/index.php?title=Methodology_for_feature_cataloguing ISO 19110:2005, Geographic information – Methodology for feature cataloguing] <br/>[http://wiki.icaci.org/index.php?title=Metadata ISO 19115:2003, Geographic information – Metadata <br/>[http://wiki.icaci.org/index.php?title=Data_product_specifications ISO 19131:2007, Geographic information -- Data product specifications] <br/>ISO 19135:2005, Geographic information – Procedures for item registration<br />
|-<br />
| Application<br />
| The main function of this standard is for creating an online register of abstract feature concepts in a dictionary that can then be specified in detail as feature types and in feature catalogues.<br />
|-<br />
| Conformance classes<br />
| General conformance to ISO 19135 <br/>Conformance to ISO 19135 as a hierarchical register <br/>Feature concept dictionary <br/>Register of feature concept dictionaries and/or feature catalogues<br />
|}<br />
<br />
==Scope==<br />
ISO 19126:2009 specifies a schema for feature concept dictionaries to be established and managed as registers. It does not specify schemas for feature catalogues or for the management of feature catalogues as registers. However, because feature catalogues are often derived from feature concept dictionaries, this International Standard does specify a schema for a hierarchical register of feature concept dictionaries and feature catalogues. These registers are in accordance with ISO 19135.<br />
<br />
==Implementation benefits==<br />
The main function of [http://www.iso.org/iso/home/store/catalogue_tc/catalogue_detail.htm?csnumber=44875 ISO 19126:2009] is to specify how to create an online register for a feature concept dictionary, that contains abstract feature concepts, which may then be specified in detail as feature types or in feature catalogues, using [http://www.iso.org/iso/home/store/catalogue_tc/catalogue_detail.htm?csnumber=39965 ISO 19110:2005, Geographic information – Methodology for feature catalogues], or in data product specifications, using [http://www.iso.org/iso/home/store/catalogue_tc/catalogue_detail.htm?csnumber=36760 ISO 19131:2007, Geographic information -- Data product specifications].<br />
<br />
Superficially, this might appear that [http://www.iso.org/iso/home/store/catalogue_tc/catalogue_detail.htm?csnumber=44875 ISO 19126:2009] is too abstract or too theoretical for most users. However, the power of [http://www.iso.org/iso/home/store/catalogue_tc/catalogue_detail.htm?csnumber=44875 ISO 19126:2009] is that it allows different scientific and other disciplines to define and maintain concepts relevant to their field in online registers. Any community of interest can then use these registers in defining their feature types and constructing their feature catalogues appropriately. This is similar to the meta-languages or domain models used in [http://www.iso.org/iso/home/store/catalogue_tc/catalogue_detail.htm?csnumber=44342 ISO 19144-2:2012, Geographic information – Classification systems – Part 2: Land Cover Meta Language (LCML)], and [http://www.iso.org/iso/home/store/catalogue_tc/catalogue_detail.htm?csnumber=51206 ISO 19152, Geographic information – Land Administration Domain Model (LADM)].<br />
<br />
==Implementation guidelines==<br />
Clause 5 of [http://www.iso.org/iso/home/store/catalogue_tc/catalogue_detail.htm?csnumber=44875 ISO 19126:2009] is primarily about establishing a register, according to ISO 19135:2005, Geographic information – Procedures for item registration. A register is defined as a “set of files containing identifiers assigned to items with descriptions of the associated items”, and is maintained in an information system known as a registry. Each register has a register owner (the organisation that establishes the register), a register manager (to whom responsibility for running the register has been delegated by the register owner), a control body (the group of technical experts that makes the decisions about the contents of the register) and users.<br />
<br />
Clause 6 specifies the feature concept dictionary schema, which may include definitions of feature concepts, feature attribute concepts, feature association concepts, feature operation concepts feature role concepts (link between an association and an attribute or operation) and nominal value concepts (category, class, kind or type that may be identified as an element of an enumeration or code list). Each feature concept dictionary has a scope, a possible field of application and possible themes.<br />
<br />
Clause 7 specifies procedures for the management of feature concept dictionaries as registers, which are taken largely from ISO 19135:2005. Clause 8 describes a register of feature concept dictionaries and feature catalogues, again drawing largely on ISO 19135:2005.<br />
<br />
Annex A provides an overview of how feature concepts in dictionaries, catalogues and application schemas relate to one another. Annex C describes the information to be included in registration proposals. Annex D provides an example implementation of the feature concept dictionary schema as a register. Annex E describes the UML notation used.</div>Tebogo Mokwenahttp://wiki.icaci.org/index.php?title=ISO_19110:2005_Geographic_information_-_Methodology_for_feature_cataloguing&diff=815ISO 19110:2005 Geographic information - Methodology for feature cataloguing2016-06-24T09:56:20Z<p>Tebogo Mokwena: /* Overview */</p>
<hr />
<div>==Overview==<br />
{| class="wikitable"<br />
| Full name<br />
| [http://www.iso.org/iso/home/store/catalogue_tc/catalogue_detail.htm?csnumber=39965 ISO 19110:2005, Geographic information – Methodology for feature cataloguing]<br />
|-<br />
| Version<br />
| Edition 1<br />
|-<br />
| Amendments<br />
| ISO 19110:2005/Amd 1:2011<br />
|-<br />
| Corrigenda<br />
| None<br />
|-<br />
| Published by<br />
| ISO/TC 211<br />
|-<br />
| Languages<br />
| English, French<br />
|-<br />
| Online overview<br />
| https://www.iso.org/obp/ui/#iso:std:iso:19110:ed-1:v1:en<br />
|-<br />
| Type of standard<br />
| ISO International Standard <br/>Meta and application level<br />
|-<br />
| Related standard(s)<br />
| [http://wiki.icaci.org/index.php?title=Conceptual_schema_language ISO/TS 19103:2015, Geographic information – Conceptual schema language]<br/>[http://wiki.icaci.org/index.php?title=Rules_for_application_schema ISO 19109:2015, Geographic information – Rules for application schema] <br/>[http://wiki.icaci.org/index.php?title=Metadata ISO 19115:2003, Geographic information – Metadata] <br/>[http://wiki.icaci.org/index.php?title=Portrayal ISO 19117:2012, Geographic information – Portrayal]<br/>[http://wiki.icaci.org/index.php?title=Feature_concept_dictionaries_and_registries ISO 19126:2009, Geographic information – Feature concept dictionaries and registries] <br/>ISO 19135:2005, Geographic information — Procedures for item registration <br/>[http://wiki.icaci.org/index.php?title=Metadata_%E2%80%93_XML_schema_implementation ISO/TS 19139:2007, Geographic information — Metadata — XML schema implementation]<br />
|-<br />
| Application<br />
| This standard does not define a feature catalogue (or feature classification system, as many would understand it), but specifies the methodology for cataloguing feature types (or feature classes, as many would understand it) to compile a feature catalogue. However, it does not specify how to decide what the feature types should be (their collection criteria).<br />
|-<br />
| Conformance classes<br />
| None specified<br />
|-<br />
| Implementation benefits<br />
| ENC software validates that data are conformant with the IHO S-57 ENC product specification. Conformance violations are labelled as either an error or as a warning. This is important to ensure that the correct ENC is produced and that the software is implemented according to the same standard.<br />
|-<br />
| Products<br />
| Catalogue with single-use feature attributes <br/>Catalogue with single-use feature attributes and association roles <br/>Catalogue with single-use feature attributes, association roles and operations <br/>Catalogue with multiple-use feature attributes, associations and operations <br/>Catalogue with single-use feature attributes and inheritance <br/>Catalogue with single-use feature attributes and association roles with inheritance <br/>Catalogue with single-use feature attributes, association roles and operations with inheritance<br />
|}<br />
<br />
==Scope==<br />
ISO 19110:2005 defines the methodology for cataloguing feature types. This International Standard specifies how feature types can be organised into a feature catalogue and presented to the users of a set of geographic data. ISO 19110:2005 is applicable to creating catalogues of feature types in previously uncatalogued domains and to revising existing feature catalogues to comply with standard practice. ISO 19110:2005 applies to the cataloguing of feature types that are represented in digital form. Its principles can be extended to the cataloguing of other forms of geographic data. Feature catalogues are independent of feature concept dictionaries defined in ISO 19126 and can be specified without having to use or create a feature concept dictionary.<br />
<br />
ISO 19110:2005 is applicable to the definition of geographic features at the type level. ISO 19110:2005 is not applicable to the representation of individual instances of each type. ISO 19110:2005 excludes portrayal schemas as specified in ISO 19117.<br />
<br />
ISO 19110:2005 can be used as a basis for defining the universe of discourse being modelled in a particular application, or to standardize general aspects of real world features being modelled in more than one application.<br />
<br />
==Implementation benefits==<br />
ISO 19110:2005 provides a rigorous methodology for cataloguing feature types (feature classes) to compile a feature catalogue (also known as a classification system) and for publishing the catalogue in a registry (a formal online repository). Closely related to ISO 19110:2005 is ISO 19126:2009, Geographic information – Feature concept dictionaries and registries (see 11.3.2), which specifies how to set up a concept dictionary of the abstract feature concepts that can be specified in detail in creating a feature catalogue. However, ISO 19110:2005 does not actually define a feature catalogue and it does not specify how to decide what the feature types should be (their collection criteria), which is actually a poorly understood problem.<br />
<br />
==Implementation guidelines==<br />
ISO 19110:2005 and ISO 19126:2009 probably have a more sophisticated approach to classifying features in a geospatial dataset than most users are accustomed to, which probably makes them a bit challenging. The amendment to ISO 19110:2005 was published in 2011 and makes significant changes to the standard – the amendment is almost as long as the original standard itself. It also makes it more difficult to understand the standard, unfortunately, as the amendment is published separately and not merged into the original standard. Further, the amendment uses UML classes from ISO/TS 19139:2007, Geographic information – Metadata – XML schema implementation, without expanding them in the tables, so it can appear that some things were deleted by the amendment, when they were not. The main changes introduced by the amendment are to improve harmonization with other ISO/TC 211 standards, cater for XML, facilitate using ISO 19110:2005 to create geographic feature catalogues, ensure consistent descriptions of the feature types of an application schema, and enable registering feature catalogues and their feature types. This discussion is of ISO 19110:2005 as amended in 2011.<br />
<br />
ISO 19110:2005 is also currently being revised and as it received 100% support in February 2014 in the DIS ballot, it is likely that the revised standard will be published before the end of 2014.<br />
<br />
A feature occurs on two levels, as an instance, which is the actual thing in the real or imaginary world being modelled (a discrete phenomenon associated with its geographic and temporal coordinates that may be portrayed by a particular graphic symbol), or as a type, which is a grouping of instances into a class with common characteristics. Recognising and selecting the relevant characteristics (and hence the classification itself) is subjective and depends upon the needs of particular applications.<br />
<br />
Clause 5.2 describes the XML namespaces used in this standard, namely gco, gfc, gmd and gmx. Clause 6 of ISO 19110:2005 provides an overview of the general requirements for a feature catalogue: the form of names and definitions; the requirements for feature types, feature attributes and feature attribute values; and the requirements for the complex relationships between feature types, namely:<br />
<br />
:* '''Feature operation''': an action or query that can be performed on a feature, such as upgrading or downgrading an attribute (e.g. the category for an Important Bird Area), or checking the water level at a weir. A feature operation may have attributes that trigger it, that provide inputs for it or that are affected by it.<br />
:* '''Feature association''': a relationship linking one feature to another, such as between a river and its catchment, or between a bridge and what it carries and what it spans.<br />
:* '''Association roles''': the function or undertaking of each feature type or instance in the association. An association role can be navigable, meaning that it can be used to find the target feature from the source feature. An association role can also be bound to a particular feature type.<br />
<br />
'''Annex B''' provides the feature catalogue template, which has tables similar to the data dictionary in ISO 19115:2003, Geographic information – Metadata '''(see 11.2.2)''', and UML diagrams.<br />
<br />
Essentially, each feature catalogue is required to have a name, scope, version number, version date, producer and a set of feature types. It may have an identifier, language, character set, locale, described field of application and a set of definition sources (unfortunately, not linked to the definitions taken from each of them), inheritance relationships, global properties, and if its feature types have feature operations, it may have a functional language for defining them.<br />
<br />
A feature type then has a name, a definition, links to the feature catalogues that contain it, and an indicator of whether or not it is abstract (i.e. a superclass with no instances in practice). It may also have a code, aliases, superclasses (from which it inherits operations, associations and properties), subclasses (which inherit operations, associations and properties from it), properties, constraints, and a definition reference. Note that a class (feature type) may have more than one parent, meaning that a feature catalogue is not restricted to a pure hierarchy, but could also be a partially ordered set (poset).<br />
<br />
'''Annex C''' provides feature cataloguing examples and '''Annex D''' provides more detailed descriptions of the feature cataloguing concepts, namely feature operations, feature attributes, feature relationships (particularly generalization and aggregation), and synonyms and included terms (aliases or alternative names), and also provides some examples. The amendment adds two normative annexes, '''Annex E''', which provides the XML encoding description, and '''Annex F''' which specifies the management of feature catalogue registers. The amendment also adds '''Annex G''', which contains XML implementation examples.</div>Tebogo Mokwenahttp://wiki.icaci.org/index.php?title=ISO/TS_19139-2:2012_Geographic_information_-_Metadata_-_XML_schema_implementation_-_Part_2:_Extensions_for_imagery_and_gridded_data&diff=814ISO/TS 19139-2:2012 Geographic information - Metadata - XML schema implementation - Part 2: Extensions for imagery and gridded data2016-06-24T09:52:55Z<p>Tebogo Mokwena: /* Overview */</p>
<hr />
<div>==Overview==<br />
{| class="wikitable"<br />
| Full name<br />
| [http://www.iso.org/iso/home/store/catalogue_tc/catalogue_detail.htm?csnumber=57104 ISO/TS 19139-2:2012, Geographic information – Metadata – XML schema implementation – Part 2: Extensions for imagery and gridded data]<br />
|-<br />
| Version<br />
| Edition 1<br />
|-<br />
| Amendments<br />
| None<br />
|-<br />
| Corrigenda<br />
| None<br />
|-<br />
| Published by<br />
| ISO/TC 211<br />
|-<br />
| Languages<br />
| English<br />
|-<br />
| Online overview<br />
| Not yet available<br />
|-<br />
| Type of standard<br />
| ISO Technical Specification<br />
Application level<br />
|-<br />
| Related standard(s)<br />
| [http://wiki.icaci.org/index.php?title=Rules_for_application_schema ISO 19109:2005, Geographic information - Rules for application schema]<br/>[http://wiki.icaci.org/index.php?title=Metadata ISO 19115:2003, Geographic information – Metadata]<br/>[http://wiki.icaci.org/index.php?title=Metadata_%E2%80%93_Part_2:_Extensions_for_imagery_and_gridded_data ISO 19115-2:2009, Geographic information – Metadata – Part 2: Extensions for imagery and gridded data]<br/> ISO 19118:2011, Geographic information – Encoding<br/>[http://wiki.icaci.org/index.php?title=Geography_Markup_Language ISO 19136:2007, Geographic information – Geography Markup Language (GML)]<br/>[http://wiki.icaci.org/index.php?title=Metadata_%E2%80%93_XML_schema_implementation ISO/TS 19139:2007, Geographic information – Metadata – XML schema implementation]<br />
|-<br />
| Application<br />
| XML implementation of ISO 19115-2:2009, ''Geographic information – Metadata – Part 2: Extensions for imagery and gridded data''<br />
|-<br />
| Conformance classes<br />
| XML Schema implementation<br/>XML document<br />
|}<br />
<br />
== Scope ==<br />
This Technical Specification defines Geographic Metadata for imagery and gridded data (gmi) encoding. This is an XML Schema implementation derived from ISO 19115-2, Geographic information – Metadata – Part 2: Extensions for imagery and gridded data.<br />
<br />
== Implementation benefits ==<br />
This standard specifies the implementation of ISO 19115-2:2009, Geographic information – Metadata – Part 2: Extensions for imagery and gridded data, in XML. It uses and extends ISO 19139:2007, Geographic information – Metadata – XML schema implementation, which uses parts of GML, which is defined in ISO 19136:2007, Geographic information – Geography Markup Language (GML).<br />
<br />
As the revision of ISO 19115:2003, Geographic information – Metadata, namely ISO 19115-1:2014, Geographic information – Metadata – Part 1: Fundamentals, has now been published, ISO 19115-2:2009 and ISO 19139-2:2012 will both need to be revised to benefit from ISO 19115-1:2014. As with the revision of ISO 19115:2003, the current versions of ISO 19115-2:2009 and ISO 19139-2:2012 will then be deprecated when their revisions are published, but will still be available because of the masses of legacy metadata conforming to ISO 19115-2:2009 and ISO 19139:2012.<br />
<br />
The benefit of implementing ISO 19139-2:2012 will be to access all the metadata encoded using it and to promote one’s products and services by providing one’s metadata to clearinghouses using ISO 19139-2:2012 for disseminating metadata.<br />
<br />
However, this does not mean that the only way to implement ISO 19115-2:2009 is through XML, as defined in ISO 19139-2:2012. ISO 19115-2:2009 can be implemented in databases and GISs, and encoded using other markup languages such as JSON or GeoJSON, interchange formats such as ISO/IEC 8211 or ASN.1, or even as comma-separated values.<br />
<br />
== Implementation guidelines ==<br />
ISO 19139-2:2012 is an extension to ISO 19139:2007 and implements the metadata defined in ISO 19115-2:2009 through a collection of XML schema that conform to ISO 19118:2011, Geographic information – Encoding. Unsurprisingly, the standard requires a sound knowledge of XML to understand it. The reader also needs to understand ISO 19118.<br />
<br />
Clause 5.2 specifies the UML model stereotypes used in this standard. Clause 6 describes the XML namespaces used in this standard, namely gmi, gco, gmd, gml, gmx, gss, gsr and gts. With the exception of gmi (Geographic Metadata for imagery and gridded data), these are the same namespaces used in ISO 19139:2007. Clause 6 also provides the XML Schema Definitions (XSDs) for gmi. Clause 7 briefly describes the XML document requirements.<br />
<br />
Annex B briefly describes the XML resources related to geographic metadata for imagery and gridded data and Annex C provides some implementation examples. The actual XML defined in ISO 19139-2:2012 is provided in an online repository, rather than just printed out in the standard. This is not the ISO repository used for ISO 19139:2007, but rather an ISO/TC 211 repository that is also used for ISO 19139:2007 and other standards from ISO/TC 211. See [http://www.isotc211.org/2005/ http://www.isotc211.org/2005/].</div>Tebogo Mokwenahttp://wiki.icaci.org/index.php?title=ISO/TS_19139:2007_Geographic_information_-_Metadata_-_XML_schema_implementation&diff=813ISO/TS 19139:2007 Geographic information - Metadata - XML schema implementation2016-06-24T09:49:42Z<p>Tebogo Mokwena: /* Overview */</p>
<hr />
<div>==Overview==<br />
{| class="wikitable"<br />
| Full name<br />
| [http://www.iso.org/iso/home/store/catalogue_tc/catalogue_detail.htm?csnumber=32557 ISO/TS 19139:2007, Geographic information – Metadata – XML schema implementation]<br />
|-<br />
| Version<br />
| Edition 1<br />
|-<br />
| Amendments<br />
| None<br />
|-<br />
| Corrigenda<br />
| None<br />
|-<br />
| Published by<br />
| ISO/TC 211<br />
|-<br />
| Languages<br />
| English<br />
|-<br />
| Online overview<br />
| Not yet available<br />
|-<br />
| Type of standard<br />
| ISO Technical Specification<br />
Application level<br />
|-<br />
| Related standard(s)<br />
| [http://wiki.icaci.org/index.php?title=Rules_for_application_schema ISO 19109:2015, Geographic information - Rules for application schema]<br/>[http://wiki.icaci.org/index.php?title=Metadata ISO 19115:2003, Geographic information – Metadata]<br/>[http://wiki.icaci.org/index.php?title=Metadata_%E2%80%93_Part_3:_XML_implementation_of_fundamentals ISO/TS 19115-3, Geographic information – Metadata – Part 3: XML implementation of fundamentals]<br/> ISO 19118:2011, Geographic information – Encoding<br/>[http://wiki.icaci.org/index.php?title=Geography_Markup_Language ISO 19136:2007, Geographic information – Geography Markup Language (GML)]<br/>[http://wiki.icaci.org/index.php?title=Metadata_%E2%80%93_Part_2:_Extensions_for_imagery_and_gridded_data ISO/TS 19139-2:2012, Geographic information – Metadata – XML schema implementation – Part 2: Extensions for imagery and gridded data]<br />
|-<br />
| Application<br />
| XML implementation of ISO 19115:2003, ''Geographic information – Metadata''<br />
|-<br />
| Conformance classes<br />
| Constraints by-value or by-reference or gco:nilReason<br/>Co-constraints<br/>Extensions<br/>Restrictions<br />
|}<br />
<br />
== Scope ==<br />
ISO/TS 19139:2007 defines Geographic MetaData XML (gmd) encoding, an XML schema implementation derived from ISO 19115.<br />
<br />
== Implementation benefits ==<br />
This standard specifies the implementation of ISO 19115:2003, Geographic information – Metadata, in XML, using parts of GML, which is defined in ISO 19136:2007, Geographic information – Geography Markup Language (GML). In the same way that ISO 19115-1:2014 replaces ISO 19115:2003, while leaving a legacy of much metadata conforming to ISO 19115:2003, ISO/TS 19115-3, Geographic information – Metadata – Part 3: XML implementation of fundamentals (the XML implementation of ISO 19115-1:2014), will replace ISO 19139:2007 as the preferred XML schema implementation, but will not invalidate all the metadata already generated that conforms to ISO 19139:2007. ISO 19139:2007 also defines some general rules and is being revised to cater for them, and not the XML schema implementation of metadata.<br />
<br />
The benefit of implementing ISO 19139:2007 will be to access all the metadata encoded using it, and until ISO 19115-3 has been published and implemented, to promote one’s products and services by providing one’s metadata to clearinghouses using ISO 19139:2007 for disseminating metadata.<br />
<br />
However, this does not mean that the only way to implement ISO 19115:2003 is through XML, as defined in ISO 19139:2007. ISO 19115:2003 can be implemented in databases and GISs, and encoded using other markup languages such as JSON or GeoJSON, interchange formats such as ISO/IEC 8211 or ASN.1, or even as comma-separated values.<br />
<br />
== Implementation guidelines ==<br />
ISO 19139:2007 implements the metadata defined in ISO 19115:2003 through a collection of XML schema that conform to ISO 19118:2011, Geographic information – Encoding. Unsurprisingly, the standard requires a sound knowledge of XML to understand it. The reader also needs to understand ISO 19118.<br />
<br />
Clause 5.2 specifies the namespaces used in this standard and clause 5.4 the UML model stereotypes. Clauses 6.1 to 6.8 provide brief overviews of the gmd namespace (geographic metadata extensible markup language), rule-based encoding, quality, web implementations, incorporating other existing XML schemas, multi-lingual support, polymorphism (supporting both multiple languages in the metadata and more detailed versions of metadata elements), and explaining how ISO 19139 conforms to ISO 19109:2005, Geographic information - Rules for application schema. Clause 7 describes how to implement extensions to the UML models, not so much for extensions to the metadata defined in ISO 19115:2003, but particularly for extending the CharacterString class to cater better for XML, including hyperlinks, URIs (uniform resource identifier) and file types; implementing multi-lingual free text and locales (language, country and character set) for text, which are not catered for in plain XML; transferring and aggregating datasets; and catalogues of coordinate reference systems, units of measure and code lists. Clause 8 provides details of how the encoding rules of ISO 19118:2001 have been implemented in ISO 19139:2007, particularly as ISO 19118 allows for multiple ways of transforming UML into XML. It covers the default XML Class Type encoding (a class is made up of one or more properties, such as attributes, associations, aggregations and compositions), XML Class Global Element encoding, XML Class Property Type encoding, special case encodings (abstract classes, inheritance, subclasses, enumerations, code lists, unions, metaclasses and externally identified implementations), XML namespace package encoding, and XML schema package encoding. Clause 9 provides the encoding descriptions, the relationships between the various namespaces used (gmx, gmd, gts, gss, gsr, gco), the organisation of the namespaces and their many XML Schema Definitions (XSDs) for all the metadata and other relevant packages, entities and elements defined in ISO 19115:2003 and other standards.<br />
<br />
Annex B provides a data dictionary for extensions defined in clause 7, for web environment extensions, cultural and linguistic adaptability extensions, interchange or transfer, and code lists and enumerations. Annex C provides a brief summary of geographic metadata XML resources, specifically their URIs. Annex D provides implementation examples in XML. The actual XML defined in ISO 19139:2007 is provided in an online repository, rather than just printed out in the standard. The repository is maintained by ISO itself and caters for standards from a variety of ISO Technical Committees. See [http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/ http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/] and [http://standards.iso.org/iso/19139/ http://standards.iso.org/iso/19139/].</div>Tebogo Mokwenahttp://wiki.icaci.org/index.php?title=ISO_19115-1:2014_Geographic_information_-_Metadata_-_Part_1:_Fundamentals&diff=812ISO 19115-1:2014 Geographic information - Metadata - Part 1: Fundamentals2016-06-24T09:44:12Z<p>Tebogo Mokwena: /* Overview */</p>
<hr />
<div>==Overview==<br />
{| class="wikitable"<br />
| Full name<br />
| [http://www.iso.org/iso/home/store/catalogue_tc/catalogue_detail.htm?csnumber=53798 ISO 19115-1:2014, Geographic information – Metadata – Part 1: Fundamentals]<br />
|-<br />
| Version<br />
| Edition 1<br />
|-<br />
| Amendments<br />
| None<br />
|-<br />
| Corrigenda<br />
| None<br />
|-<br />
| Published by<br />
| ISO/TC 211<br />
|-<br />
| Languages<br />
| English, French<br />
|-<br />
| Online overview<br />
| https://www.iso.org/obp/ui/#iso:std:iso:19115:-1:ed-1:v1:en<br />
|-<br />
| Type of standard<br />
| ISO International Standard<br/><br />
Application level<br />
|-<br />
| Related standard(s)<br />
| [http://wiki.icaci.org/index.php?title=Metadata ISO 19115:2003, Geographic information -- Metadata] <br/>[http://wiki.icaci.org/index.php?title=Metadata_%E2%80%93_Part_2:_Extensions_for_imagery_and_gridded_data ISO 19115-2:2009, Geographic information — Metadata — Part 2: Extensions for imagery and gridded data]<br/>[http://wiki.icaci.org/index.php?title=Metadata_%E2%80%93_Part_3:_XML_implementation_of_fundamentals ISO 19115-3, Geographic information – Metadata – Part 3: XML schema implementation of metadata fundamentals]<br/>[http://wiki.icaci.org/index.php?title=Data_product_specifications ISO 19131:2007, Geographic information – Data product specifications]<br/>[http://wiki.icaci.org/index.php?title=Metadata_%E2%80%93_XML_schema_implementation ISO/TS 19139:2007, Geographic information – Metadata – XML schema implementation]<br/>[http://wiki.icaci.org/index.php?title=Metadata_%E2%80%93_XML_schema_implementation_%E2%80%93_Part_2:_Extensions_for_imagery_and_gridded_data ISO/TS 19139-2:2012, Geographic information -- Metadata -- XML Schema Implementation -- Part 2 : Extensions for imagery and gridded data]<br/>[http://wiki.icaci.org/index.php?title=Data_quality ISO 19157:2013, Geographic information – Data quality]<br/>[http://wiki.icaci.org/index.php?title=Dublin_Core ISO 15836:2009, Information and documentation – The Dublin Core metadata element set]<br />
|-<br />
| Application<br />
| The standard specifies how to document metadata, which includes information on data quality, lineage, etc.<br />
|-<br />
| Conformance classes<br />
| Completeness test<br/>Maximum occurrence test<br/>Data type test<br/>Domain test<br/>Schema test<br/>Exclusiveness test<br/>Definition test<br/>Standard metadata test<br/>Metadata profiles<br />
|}<br />
<br />
== Scope ==<br />
This part of ISO 19115 defines the schema required for describing geographic information and services by means of metadata. It provides information about the identification, the extent, the quality, the spatial and temporal aspects, the content, the spatial reference, the portrayal, distribution, and other properties of digital geographic data and services.<br />
<br />
This part of ISO 19115 is applicable to:<br />
<br />
* the cataloguing of all types of resources, clearinghouse activities, and the full description of datasets and services;<br />
* geographic services, geographic datasets, dataset series, and individual geographic features and feature properties.<br />
<br />
This part of ISO 19115 defines:<br />
<br />
* mandatory and conditional metadata sections, metadata entities, and metadata elements;<br />
* the minimum set of metadata required to serve most metadata applications (data discovery, determining data fitness for use, data access, data transfer, and use of digital data and services);<br />
* optional metadata elements – to allow for a more extensive standard description of resources, if required;<br />
* a method for extending metadata to fit specialized needs.<br />
<br />
Though this part of ISO 19115 is applicable to digital data and services, its principles can be extended to many other types of resources such as maps, charts, and textual documents as well as non-geographic data. Certain conditional metadata elements might not apply to these other forms of data.<br />
<br />
== Implementation benefits ==<br />
ISO 19115-1:2014 is a revision of ISO 19115:2003 (with its corrigendum) and hence replaces it, but because of the sheer volume of legacy metadata already in the latter format, ISO 19115:2003 will probably remain available through ISO (as withdrawn rather than deleted). Hence, while one will probably need to support ISO 19115 for all the legacy metadata one will use, it will be better to implement ISO 19115-1:2014 for all new metadata captured. Many proprietary and open source GISs already support ISO 19115:2003 and they should soon support ISO 19115-1:2014. Nevertheless, it is still necessary to understand the standard to be able to interpret the metadata.<br />
<br />
== Implementation guidelines ==<br />
ISO 19115-1:2014 is structured similarly to ISO 19115:2003, but all the UML diagrams have been included together in Clause 6, rather than split between the main text and an annex. The abstract test suite is now in Annex A (as is usual for the standards of ISO/TC 211), the data dictionary is still in Annex B, and the rules for extensions and profiles are still in Annex C. The annex with the comprehensive dataset metadata application profile has been removed. The informative annexes have been consolidated into two: Annex D has implementation examples and Annex E covers metadata implementation. There is also a new, normative Annex F, which provides the discovery metadata for geographic resources – effectively, it is the minimum metadata to be implemented for inclusion in a catalogue of products and/or services. Referring to the last sentence of the scope, an example of a conditional metadata element that does not apply to other forms of data is the element ‘defaultLocale’, which is only relevant for digital data.<br />
<br />
Most importantly for migrating from ISO 19115:2003 to ISO 19115-1:2014, Annex G provides the details of the changes made in the revision, which are also summarised in the Introduction. Most of the changes were adding new attributes (but not new mandatory ones) and extending code lists to improve the functionality of the standard, such as catering better for online services and repositories. The major changes were:<br />
<br />
* Removing the data quality information package, which is now part of ISO 19157:2013, Geographic information – Data quality.<br />
* Including the service metadata from ISO 19119:2005, Geographic information – Services, and ISO 19119:2005/Amd 1:2008.<br />
* Removing the concept of “core metadata”.<br />
* Making clear that the scope of ISO 19115-1:2014 is not limited only to describing conventional, structured geospatial datasets, but is also for describing services, unstructured datasets with geospatial references, initiatives, repositories, analogue maps and other analogue resources, such as specimens and other artefacts.<br />
* The UML packages, classes, and elements in ISO 19115-1:2014 have different identifiers from those in ISO 19115:2003, because they are independent standards and to ensure that there is no confusion caused by a mixed environment of metadata to be discovered and interpreted.<br />
<br />
* Where elements were changed, the old one was deleted and replaced with a new one with a different name.<br />
* Some definitions were broadened.<br />
* The “Short name” and “Domain code” are no longer used, as they are now redundant. This removes one column from the data dictionary tables in Annex B.<br />
<br />
The abstract class DS_Resource has been added to the high-level metadata application diagram (Figure 1 in ISO 19115:2014) to make clear that ISO 19115-1:2014 metadata applies to resources and aggregations of resources other than just geospatial datasets, such as services.</div>Tebogo Mokwenahttp://wiki.icaci.org/index.php?title=ISO/TS_19115-3_Geographic_information_-_Metadata_-_Part_3:_XML_implementation_of_fundamentals&diff=811ISO/TS 19115-3 Geographic information - Metadata - Part 3: XML implementation of fundamentals2016-06-24T09:41:07Z<p>Tebogo Mokwena: /* Overview */</p>
<hr />
<div>==Overview==<br />
{| class="wikitable"<br />
| Full name<br />
| ISO/TS 19115-3, Geographic information – Metadata – Part 3: XML implementation of fundamentals<br />
|-<br />
| Version<br />
| Draft Technical Specification (DTS)<br />
|-<br />
| Amendments<br />
| None<br />
|-<br />
| Corrigenda<br />
| None<br />
|-<br />
| Published by<br />
| ISO/TC 211<br />
|-<br />
| Languages<br />
| English<br />
|-<br />
| Online overview<br />
| Not yet available<br />
|-<br />
| Type of standard<br />
| ISO International Standard<br />
Application level<br />
|-<br />
| Related standard(s)<br />
| ISO 19118:2011, Geographic information – Encoding<br/>[http://wiki.icaci.org/index.php?title=Geography_Markup_Language ISO 19136:2007, Geographic information – Geography Markup Language (GML)]<br/>[http://wiki.icaci.org/index.php?title=Metadata_%E2%80%93_XML_schema_implementation ISO/TS 19139:2007, Geographic information – Metadata – XML schema implementation]<br />
|-<br />
| Application<br />
| XML implementation of ISO 19115-1, ''Geographic information – Metadata – Part 1: Fundamentals''<br />
|-<br />
| Conformance classes<br />
| As this standard is an XML implementation, it specifies many conformance classes for the XML schema implementation that can be tested automatically by a validation tool that implements the full W3C XML Schema.<br />
|}<br />
<br />
== Scope ==<br />
ISO/TS 19115-3 defines five artefacts to support the use of ISO 19115-1 compliant metadata and migration from ISO19115 to ISO19115-1. These include <br />
<br />
1) an XML Schema that implements ISO 19115-1 using encoding rules from ISO 19118 Annex A and ISO 19139 for XML metadata encoding; <br />
<br />
2) a set of ISO/IEC 19757-3 (Schematron) rules that implement validation constraints included in the ISO 19115-1 UML Model that are not specified by the XML schema; <br />
<br />
2a) a set of ISO/IEC 19757-3 (Schematron) rules that identify content in documents encoded using the XML schema defined in ISO 19115-1 (this Technical Specification) that will not translate to ISO 19115 metadata encoded using the ISO 19139 XML schema; <br />
<br />
3) an Extensible Stylesheet Language Transformation (XSLT) for transforming XML-encoded ISO 19115 metadata using the ISO 19139 XML schema into an equivalent document encoded using the XML schema defined in ISO 19115-3 (this Technical Specification); and <br />
<br />
3a) an Extensible Stylesheet Language Transformation (XSLT) for transforming metadata encoded using the XML schema defined in ISO 19115-3 (this Technical Specification) into an XML-encoded ISO 19115 metadata document using the ISO 19139 XML schema (this transform will not include all content in the 19115-1 document).<br />
<br />
== Implementation benefits ==<br />
This standard specifies the implementation of ISO 19115-1:2014, Geographic information – Metadata – Part 1: Fundamentals, in XML, using parts of the GML, which is defined in ISO 19136:2007, Geographic information – Geography Markup Language (GML). While this standard is still a draft and hence likely to change, it should not change significantly as ISO 19115-1:2014 has already been published. The benefit of implementing ISO 19115-3 will be to access all the metadata encoded using it, and to promote one’s products and services by providing one’s metadata to clearinghouses using ISO 19115-3 for disseminating metadata.<br />
<br />
However, this does not mean that the only way to implement ISO 19115-1:2014 is through XML, as defined in ISO 19115-3. ISO 19115-1 can be implemented in databases and GISs, and encoded using other markup languages such as JSON or GeoJSON, interchange formats such as ISO/IEC 8211 or ASN.1, or even as comma-separated values (CSV).<br />
<br />
In the same way that ISO 19115-1:2014 replaces ISO 19115:2003, while leaving a legacy of much metadata conforming to ISO 19115:2003, ISO 19115-3 will replace ISO/TS 19139:2007, Geographic information – Metadata – XML schema implementation (the XML implementation of ISO 19115:2003) as the preferred XML schema implementation, but will not invalidate all the metadata already generated that conforms to ISO 19139:2007. ISO 19115-3 also specifies the XSLT (Extensible Stylesheet Language Transformation) for converting metadata from ISO 19139:2007 to ISO 19115-3 and vice versa, though converting from ISO 19115-3 to ISO 19139:2007 will obviously lose that content not defined in ISO 19139:2007. ISO 19139:2007 also defines some general rules and is being revised to cater for them, and not the XML schema implementation of metadata.<br />
<br />
== Implementation guidelines ==<br />
ISO 19115-3 implements the entire UML model from ISO 19115-1:2014, through a collection of XML schema that conform to ISO 19118:2011, Geographic information – Encoding, and ISO 19139:2007. The XML schemas are derived algorithmically from the UML. Unsurprisingly, the standard requires a sound knowledge of XML to understand it.<br />
<br />
Clause 6.1 provides an overview of the XML schema for geospatial metadata. Clause 5.2 specifies the namespaces used in this standard, clause 5.4 the UML model stereotypes, clause 6.2 the multi-lingual adaptability and polymorphism, and clauses 6.3, 6.4, 6.5 and 6.6 the requirements classes. Clause 6.7 shows in a diagram, the dependencies between encoding requirements classes.<br />
<br />
Clause 7 provides the model extensions defined in ISO 19139:2007. Clause 8 provides the encoding rules, which are also described in ISO 19139:2007. Annex D provides encoding descriptions and Annex E provides some implementation examples.<br />
<br />
The actual XML is provided in an online repository [http://standards.iso.org/iso/19115/-3/ http://standards.iso.org/iso/19115/-3/].</div>Tebogo Mokwenahttp://wiki.icaci.org/index.php?title=ISO_19115-2:2009_Geographic_information_-_Metadata_-_Part_2:_Extensions_for_imagery_and_gridded_data&diff=810ISO 19115-2:2009 Geographic information - Metadata - Part 2: Extensions for imagery and gridded data2016-06-24T09:38:05Z<p>Tebogo Mokwena: /* Overview */</p>
<hr />
<div>==Overview==<br />
{| class="wikitable"<br />
| Full name<br />
| [http://www.iso.org/iso/home/store/catalogue_tc/catalogue_detail.htm?csnumber=39229 ISO 19115-2:2009, Geographic information – Metadata – Part 2: Extensions for imagery and gridded data]<br />
|-<br />
| Version<br />
| Edition 1<br />
|-<br />
| Amendments<br />
| None<br />
|-<br />
| Corrigenda<br />
| None<br />
|-<br />
| Published by<br />
| ISO/TC 211<br />
|-<br />
| Languages<br />
| English, French<br />
|-<br />
| Online overview<br />
| https://www.iso.org/obp/ui/#iso:std:iso:19115:-2:ed-1:v1:en<br />
|-<br />
| Type of standard<br />
| ISO International Standard<br />
Application level<br />
|-<br />
| Related standard(s)<br />
|[http://wiki.icaci.org/index.php?title=Metadata_Fundamentals ISO 19115:2003, Geographic information – Metadata] <br/>[http://wiki.icaci.org/index.php?title=Metadata_%E2%80%93_XML_schema_implementation ISO 19139:2007, Geographic information – Metadata – XML schema implementation]<br/>[http://wiki.icaci.org/index.php?title=Metadata_%E2%80%93_XML_schema_implementation_%E2%80%93_Part_2:_Extensions_for_imagery_and_gridded_data ISO/TS 19139-2:2012, Geographic information – Metadata – XML schema implementation – Part 2: Extensions for imagery and gridded data]<br />
|-<br />
| Application<br />
| The standard specifies how to document metadata for imagery and gridded data, which includes information on data quality, lineage, etc.<br />
|-<br />
| Conformance classes<br />
| Completeness<br/>Maximum occurrence<br/>Short name<br/>Data type<br/>Domain<br/>Schema<br/>Exclusiveness<br/>Definition<br/>Standard metadata<br/>Metadata profiles<br />
|}<br />
<br />
== Scope ==<br />
This part of ISO 19115 extends the existing geographic metadata standard by defining the schema required for describing imagery and gridded data. It provides information about the properties of the measuring equipment used to acquire the data, the geometry of the measuring process employed by the equipment, and the production process used to digitize the raw data. This extension deals with metadata needed to describe the derivation of geographic information from raw data, including the properties of the measuring system, and the numerical methods and computational procedures used in the derivation. The metadata required to address coverage data in general is addressed sufficiently in the general part of ISO 19115.<br />
<br />
== Implementation benefits ==<br />
ISO 19115-2:2009 is an extension of ISO 19115:2003, ''Geographic information – Metadata'', defining metadata for imagery and gridded data. As such, it needs to be used in conjunction with ISO 19115:2003, as the latter defines the metadata for the dataset in general and for coverages in general. ISO 19115-2:2009 defines the metadata for the measuring equipment used to acquire the data (such as a satellite-borne sensor), the geometry of the acquisition and the production processes to produce the dataset.<br />
<br />
As the revision of ISO 19115:2003, namely ISO 19115-1:2014, Geographic information – Metadata – Part 1: Fundamentals, has now been published, ISO 19115-2:2009 will need to be revised to benefit from ISO 19115-1:2014. The current version of ISO 19115-2:2009 will be deprecated when its revision is published, but will still be available because of the masses of legacy metadata conforming to ISO 19115-2:2009.<br />
<br />
== Implementation guidelines ==<br />
Implementing ISO 19115-2:2009 is essentially the same as implementing ISO 19115:2003 and it is also supported by a wide variety of proprietary and open-source GISs and stand-alone and web-based metadata editors. Note that ISO 19115-2:2009 refers to quality elements defined in ISO 19115:2003 and when ISO 19115-2:2009 is revised, these will refer to the quality elements now in ISO 19157:2013. To the metadata packages, entities and elements defined in ISO 19115:2003, ISO 19115-2:2009 adds the following:<br />
<br />
* '''Metadata entity set – Imagery''': the package MI_Metadata are for the acquisition information for the imagery or gridded data.<br />
* '''Data quality information''': imagery, coverage result, lineage and usability. For the imagery coverage result, QE_CoverageResult consists of the spatial representation, coverage description and data format, which are all defined in ISO 19115:2003. This is necessary because the actual spatial representation of the imagery or gridded data might differ from that of its related coverage (e.g. if the coverage is computed from a subset of the whole dataset). This is coupled with MX_DataFile, which is defined in ISO 19139:2007, Geographic information – Metadata – XML schema implementation, and is a description of the transfer dataset in XML. For usability, QE_Useability specifies the degree of adherence of the dataset to a specific set of user requirements. For the extensions to lineage, there are six new classes specified: LE_Source (input and output datasets), LE_ProcessStep (the event or transformation of the process step from one version of the dataset to the next), LE_ProcessStepReport (the report produced by the process step), LE_Processing (the procedures, processes and algorithms applied during the process step), LE_Algorithm (methodology for obtaining geospatial data from the instrument readings) and LE_NominalResolution (scanning and ground resolution).<br />
* '''Spatial representation information – Imagery''': extension to georectified and georeferenceable classes, and ground control point quality. MI_GCP specifies a ground control point, which can have its data quality specified using the data quality elements in ISO 19115:2003. MI_GCPCollection is then a designated set of GCPs, which MI_GeolocationInformation uses to determine geographic location corresponding to image location. MI_Georeferenceable uses MI_GeolocationInformation to allow the geographic or map locations of the raster points to be located. MI_Georectified uses MI_GCP to provide checkpoints.<br />
* '''Content information – Imagery''': further details of the coverage, imagery, band, polarisation, transfer function and range element. MI_Band provides details of the wavelength band, its boundaries, nominal spatial resolution, transfer function for scaling, and transmitted and detected polarization. MI_CoverageDescription and MI_ImageDescription describe the specific range elements of the coverage and image respectively, using MI_RangeElementDescription, which names and describes the range elements (the range of a sensor is across its track, so the elements in the range should be the same for each sweep of the sensor).<br />
<br />
'''Acquisition information – Imagery''': further details of the platform, plan, instrument, operation, environmental record, objective and requirement. MI_EnvironmentalRecord documents the air temperature, relative humidity, maximum altitude and other meteorological conditions for photo flights. MI_Event documents the trigger, context, sequence and time of a significant collection point for an objective and pass of an instrument. MI_Instrument documents a particular instrument. MI_Objective documents the priority, type, function, spatial and temporal extents, and events of a target for a pass of an instrument. MI_Operation documents the status, type and other details of the plan and platform for an operation, including its relationships with possible child and parent operations. MI_Plan documents the type, status and authority of a plan, the activities that satisfy the plan and the requirement satisfied by the plan. MI_Platform documents a platform, including its sensors and sponsor. MI_PlatformPass documents the collection coverage of a pass. MI_RequestedDate documents the preferred and latest date and time for a desired collection. MI_Requirement documents the requirements to be satisfied by the planned data acquisition, including the requestor, recipient, priority and dates.</div>Tebogo Mokwenahttp://wiki.icaci.org/index.php?title=ISO_19115-1:2014_Geographic_information_-_Metadata_-_Part_1:_Fundamentals&diff=809ISO 19115-1:2014 Geographic information - Metadata - Part 1: Fundamentals2016-06-24T09:36:22Z<p>Tebogo Mokwena: /* Overview */</p>
<hr />
<div>==Overview==<br />
{| class="wikitable"<br />
| Full name<br />
| [http://www.iso.org/iso/home/store/catalogue_tc/catalogue_detail.htm?csnumber=53798 ISO 19115-1:2014, Geographic information – Metadata – Part 1: Fundamentals]<br />
|-<br />
| Version<br />
| Edition 1<br />
|-<br />
| Amendments<br />
| None<br />
|-<br />
| Corrigenda<br />
| None<br />
|-<br />
| Published by<br />
| ISO/TC 211<br />
|-<br />
| Languages<br />
| English, French<br />
|-<br />
| Online overview<br />
| https://www.iso.org/obp/ui/#iso:std:iso:19115:-1:ed-1:v1:en<br />
|-<br />
| Type of standard<br />
| ISO International Standard<br/><br />
Application level<br />
|-<br />
| Related standard(s)<br />
| [http://wiki.icaci.org/index.php?title=Metadata_Fundamentals ISO 19115:2003, Geographic information -- Metadata] <br/>[http://wiki.icaci.org/index.php?title=Metadata_%E2%80%93_Part_2:_Extensions_for_imagery_and_gridded_data ISO 19115-2:2009, Geographic information — Metadata — Part 2: Extensions for imagery and gridded data]<br/>[http://wiki.icaci.org/index.php?title=Metadata_%E2%80%93_Part_3:_XML_implementation_of_fundamentals ISO 19115-3, Geographic information – Metadata – Part 3: XML schema implementation of metadata fundamentals]<br/>[http://wiki.icaci.org/index.php?title=Data_product_specifications ISO 19131:2007, Geographic information – Data product specifications]<br/>[http://wiki.icaci.org/index.php?title=Metadata_%E2%80%93_XML_schema_implementation ISO/TS 19139:2007, Geographic information – Metadata – XML schema implementation]<br/>[http://wiki.icaci.org/index.php?title=Metadata_%E2%80%93_XML_schema_implementation_%E2%80%93_Part_2:_Extensions_for_imagery_and_gridded_data ISO/TS 19139-2:2012, Geographic information -- Metadata -- XML Schema Implementation -- Part 2 : Extensions for imagery and gridded data]<br/>[http://wiki.icaci.org/index.php?title=Data_quality ISO 19157:2013, Geographic information – Data quality]<br/>[http://wiki.icaci.org/index.php?title=Dublin_Core ISO 15836:2009, Information and documentation – The Dublin Core metadata element set]<br />
|-<br />
| Application<br />
| The standard specifies how to document metadata, which includes information on data quality, lineage, etc.<br />
|-<br />
| Conformance classes<br />
| Completeness test<br/>Maximum occurrence test<br/>Data type test<br/>Domain test<br/>Schema test<br/>Exclusiveness test<br/>Definition test<br/>Standard metadata test<br/>Metadata profiles<br />
|}<br />
<br />
== Scope ==<br />
This part of ISO 19115 defines the schema required for describing geographic information and services by means of metadata. It provides information about the identification, the extent, the quality, the spatial and temporal aspects, the content, the spatial reference, the portrayal, distribution, and other properties of digital geographic data and services.<br />
<br />
This part of ISO 19115 is applicable to:<br />
<br />
* the cataloguing of all types of resources, clearinghouse activities, and the full description of datasets and services;<br />
* geographic services, geographic datasets, dataset series, and individual geographic features and feature properties.<br />
<br />
This part of ISO 19115 defines:<br />
<br />
* mandatory and conditional metadata sections, metadata entities, and metadata elements;<br />
* the minimum set of metadata required to serve most metadata applications (data discovery, determining data fitness for use, data access, data transfer, and use of digital data and services);<br />
* optional metadata elements – to allow for a more extensive standard description of resources, if required;<br />
* a method for extending metadata to fit specialized needs.<br />
<br />
Though this part of ISO 19115 is applicable to digital data and services, its principles can be extended to many other types of resources such as maps, charts, and textual documents as well as non-geographic data. Certain conditional metadata elements might not apply to these other forms of data.<br />
<br />
== Implementation benefits ==<br />
ISO 19115-1:2014 is a revision of ISO 19115:2003 (with its corrigendum) and hence replaces it, but because of the sheer volume of legacy metadata already in the latter format, ISO 19115:2003 will probably remain available through ISO (as withdrawn rather than deleted). Hence, while one will probably need to support ISO 19115 for all the legacy metadata one will use, it will be better to implement ISO 19115-1:2014 for all new metadata captured. Many proprietary and open source GISs already support ISO 19115:2003 and they should soon support ISO 19115-1:2014. Nevertheless, it is still necessary to understand the standard to be able to interpret the metadata.<br />
<br />
== Implementation guidelines ==<br />
ISO 19115-1:2014 is structured similarly to ISO 19115:2003, but all the UML diagrams have been included together in Clause 6, rather than split between the main text and an annex. The abstract test suite is now in Annex A (as is usual for the standards of ISO/TC 211), the data dictionary is still in Annex B, and the rules for extensions and profiles are still in Annex C. The annex with the comprehensive dataset metadata application profile has been removed. The informative annexes have been consolidated into two: Annex D has implementation examples and Annex E covers metadata implementation. There is also a new, normative Annex F, which provides the discovery metadata for geographic resources – effectively, it is the minimum metadata to be implemented for inclusion in a catalogue of products and/or services. Referring to the last sentence of the scope, an example of a conditional metadata element that does not apply to other forms of data is the element ‘defaultLocale’, which is only relevant for digital data.<br />
<br />
Most importantly for migrating from ISO 19115:2003 to ISO 19115-1:2014, Annex G provides the details of the changes made in the revision, which are also summarised in the Introduction. Most of the changes were adding new attributes (but not new mandatory ones) and extending code lists to improve the functionality of the standard, such as catering better for online services and repositories. The major changes were:<br />
<br />
* Removing the data quality information package, which is now part of ISO 19157:2013, Geographic information – Data quality.<br />
* Including the service metadata from ISO 19119:2005, Geographic information – Services, and ISO 19119:2005/Amd 1:2008.<br />
* Removing the concept of “core metadata”.<br />
* Making clear that the scope of ISO 19115-1:2014 is not limited only to describing conventional, structured geospatial datasets, but is also for describing services, unstructured datasets with geospatial references, initiatives, repositories, analogue maps and other analogue resources, such as specimens and other artefacts.<br />
* The UML packages, classes, and elements in ISO 19115-1:2014 have different identifiers from those in ISO 19115:2003, because they are independent standards and to ensure that there is no confusion caused by a mixed environment of metadata to be discovered and interpreted.<br />
<br />
* Where elements were changed, the old one was deleted and replaced with a new one with a different name.<br />
* Some definitions were broadened.<br />
* The “Short name” and “Domain code” are no longer used, as they are now redundant. This removes one column from the data dictionary tables in Annex B.<br />
<br />
The abstract class DS_Resource has been added to the high-level metadata application diagram (Figure 1 in ISO 19115:2014) to make clear that ISO 19115-1:2014 metadata applies to resources and aggregations of resources other than just geospatial datasets, such as services.</div>Tebogo Mokwenahttp://wiki.icaci.org/index.php?title=ISO_15836:2009_Information_and_documentation_-_The_Dublin_Core_metadata_element_set&diff=808ISO 15836:2009 Information and documentation - The Dublin Core metadata element set2016-06-24T09:32:15Z<p>Tebogo Mokwena: /* Overview of ISO 15836:2009 */</p>
<hr />
<div>== Overview of ISO 15836:2009 ==<br />
<br />
{| class="wikitable"<br />
| Full name<br />
| [http://www.iso.org/iso/home/store/catalogue_tc/catalogue_detail.htm?csnumber=52142 ISO 15836:2009, Information and documentation – The Dublin Core metadata element set]<br />
|-<br />
| Version<br />
| Edition 2<br />
|-<br />
| Amendments<br />
| None<br />
|-<br />
| Corrigenda<br />
| None<br />
|-<br />
| Published by<br />
| ISO/TC 46/SC 4<br />
|-<br />
| Languages<br />
| English, French<br />
|-<br />
| Online overview<br />
| https://www.iso.org/obp/ui/#iso:std:iso:15836:ed-2:v1:en<br />
|-<br />
| Type of standard<br />
| ISO International Standard Application level<br />
|-<br />
| Related standard(s) <br />
| [http://wiki.icaci.org/index.php?title=Metadata_Fundamentals ISO 19115:2003, Geographic information -- Metadata]<br />
|-<br />
| Application <br />
| This standard specifies how to document metadata for a wide variety of resources.<br />
|-<br />
| Conformance classes<br />
| None<br />
|}<br />
<br />
== Scope ==<br />
<br />
ISO 15836:2009 establishes a standard for cross-domain resource description, known as the Dublin Core Metadata Element Set. Like RFC 3986, this International Standard does not limit what might be a resource.<br />
<br />
ISO 15836:2009 defines the elements typically used in the context of an application profile, which constrains or specifies their use in accordance with local or community-based requirements and policies. However, it does not define implementation detail, which is outside the scope of ISO 15836:2009.<br />
<br />
== Implementation benefits ==<br />
<br />
Because ISO 15836 is so popular, it is probably useful for providing high-level metadata of the likes of a dataset series (e.g. a national medium scale mapping series), so that it can be documented with other resources within the organisation. However, because it uses free text and is at a high level, it is difficult to use effectively any such metadata describing an individual geo-spatial dataset, never mind describing individual features within the dataset.<br />
<br />
== Implementation guidelines ==<br />
<br />
ISO 15836:2009 is very short (only 13 pages) and hence easy to understand. It is widely used for describing documents and other resources, not only within the library community (where it originated). It specifies 15 metadata elements (properties) for describing a resource, which are documented using free text: title, creator, subject, description, publisher, contributor, date, type, format, identifier, source, language, relation, coverage and rights. This makes it easy to write Dublin Core metadata (any text will conform to the standard), but very difficult to automate metadata operations.<br />
<br />
However, ISO 15836:2009 is essentially only the high-level framework for metadata (the 15 metadata elements listed in the previous paragraph) and the Dublin Core Metadata Initiative (DCMI) has developed many other resources built on it, such as more-detailed metadata vocabularies, encodings, resource classes, profiles and tools. DCMI has also done much work on embedding Dublin Core metadata into the work of the World Wide Web Consortium (W3C), particularly implementing Dublin Core in RDF (Resource Description Framework) for supporting linked data. For more details and resources, see: [[http://dublincore.org/]].</div>Tebogo Mokwenahttp://wiki.icaci.org/index.php?title=IHO_Standards_for_Hydrographic_Surveys&diff=807IHO Standards for Hydrographic Surveys2016-06-24T09:31:19Z<p>Tebogo Mokwena: /* Overview */</p>
<hr />
<div>==Overview==<br />
{| class="wikitable"<br />
| Full name<br />
| [http://www.iho.int/iho_pubs/standard/S-44_5E.pdf S-44, Standards for Hydrographic Surveys]<br />
|-<br />
| Version<br />
| Edition 5<br />
|-<br />
| Amendments<br />
| None<br />
|-<br />
| Corrigenda<br />
| None<br />
|-<br />
| Published by<br />
| IHO<br />
|-<br />
| Languages<br />
| English, French, Spanish, Portuguese<br />
|-<br />
| Online overview<br />
| http://iho.int/iho_pubs/standard/S-44_5E.pdf<br />
|-<br />
| Type of standard<br />
| IHO International Standard <br/> Meta level<br />
|-<br />
| Related standard(s)<br />
| [http://wiki.icaci.org/index.php?title=Metadata_Fundamentals ISO 19115:2003, Geographic information – Metadata] <br/> S-100 IHO Universal Hydrographic Data Model <br/>[http://wiki.icaci.org/index.php?title=IHO_Standards_for_Hydrographic_Surveys S-44, Standards for Hydrographic Surveys] <br/>ISO/IEC 98:1995 Guide to the expression of uncertainty in measurement <br/>ISO/IEC 99:2007 International Vocabulary of Metrology – Basic and general concepts and associated terms (VIM)<br />
|-<br />
| Application<br />
| S-44 sets the minimum requirements for surveys conducted for the safety of surface navigation.<br />
|-<br />
| Conformance classes<br />
| None specified<br />
|}<br />
<br />
==Scope==<br />
This publication is designed to provide a set of standards for the execution of hydrographical surveys for the collection of data, which will primarily be used to compile navigational charts to be used for the safety of surface navigation and the protection of the marine environment.<br />
<br />
It must be realised that this publication only provides the minimum standards that are to be achieved. Where the bathymetry and expected shipping use requires it, hydrographical offices / organisations wishing to gather data may need to define more stringent standards. Also, this publication does not contain procedures for setting up the necessary equipment, for conducting the survey or for processing the resultant data. These procedures (which are a fundamental part of the complete survey system) must be developed by the hydrographical office/organisation wishing to gather data that is compliant with these Standards. Consideration must be made of the order of survey they wish to achieve, the equipment they have at their disposal and the type of topography that they intend to survey. Annexes A and B provide guidelines for Quality control and Data Processing and it is intended that these will be moved to the Manual on Hydrography (IHO Publication M-13) which provides further guidance on how to perform hydrographical surveys.<br />
<br />
There is nothing to stop users adopting these Standards for other uses. Indeed, such a broadening of the use of these Standards is welcomed. However, users who wish to adopt these for other means must bear in mind the reason why they were written and therefore accept that not all parts may be suitable for their specific needs.<br />
<br />
To be compliant with an S-44 Order a survey must be compliant with ALL specifications for that order included in these Standards.<br />
<br />
It is also important to note that the adequacy of a survey is the end product of the entire survey system and processes used during its collection. The uncertainties quoted in the following chapters reflect the total propagated uncertainties of all parts of the system. Simply using a piece of equipment that is theoretically capable of meeting the required uncertainty is not necessarily sufficient to meet the requirements of these Standards. How the equipment is set up, used and how it interacts with the other components in the complete survey system must all be taken into consideration.<br />
<br />
All components and their combination must be capable of providing data to the required standard. The hydrographical office / organisation needs to satisfy itself that this is so by, for example, conducting appropriate trials with the equipment to be used and by ensuring that adequate calibrations are performed prior to, as well as during and, if appropriate, after the survey being carried out. The surveyor is an essential component of the survey process and must possess sufficient knowledge and experience to be able to operate the system to the required standard. Measuring this can be difficult although surveying qualifications (e.g. having passed an IHO Cat A/B recognised hydrographical surveying course) may be of considerable benefit in making this assessment.<br />
<br />
It should be noted that the issue of this new edition to the standard does not invalidate surveys, or the charts and nautical publications based on them, conducted in accordance with previous editions, but rather sets the standards for future data collection to better respond to user needs.<br />
<br />
It should also be noted that where the sea floor is dynamic (e.g. sand waves), surveys conducted to any of the Orders in these Standards would quickly become out-dated. Such areas need to be resurveyed at regular intervals to ensure that the survey data remains valid. The intervals between these resurveys, which will depend on the local conditions, should be determined by national authorities.<br />
<br />
==Implementation benefits==<br />
The requirements set out in S-44 are of great importance to improve the safety of navigation. The data captured by hydrographical surveys are used to compile navigational charts. These navigational charts are used for surface navigation and the protection of the marine environment. S-44 defines four types of order of surveys and the measurements and observations required to ensure that navigational charts of the highest quality and standardized worldwide.<br />
<br />
==Implementation guidelines==<br />
First to be addressed by the IHO standards for hydrographical surveys (S-44) is the Classification of surveys. This chapter specifies the orders of survey that are acceptable to allow hydrographical offices or organisations to produce navigational products. The navigational products will allow the expected shipping to navigate safely across the area surveyed. Due to varying requirements four types of orders of survey are defined:<br />
<br />
:#Special Order is the most rigorous and is only intended for areas where under-keel clearance is critical. Its type of order requires the full sea floor to be searched and the size of feature to be detected is kept small.<br />
:#Order 1a is intended for areas where the sea is sufficiently shallow to allow natural or man-made features on the seabed to be of concern to the type of surface shipping expected to transit. Under-keel clearance is not as critical. Order 1a also requires a full sea floor search, however the size of the feature to be detected are larger than for Special Order. Order 1a surveys may be limited to water shallower than 100 metres.<br />
:#Order 1b is meant for areas shallower than 100 metres where the general depiction of the seabed is considered adequate for the type of surface shipping expected to transit the area. Some features may be missed, since a full sea floor search is not required. This order of survey is only recommended where under-keel clearance is not required.<br />
:#Order 2 is intended for areas where the water depth is such that a general depiction of the seabed is considered adequate. A full sea floor search is not required. This order of survey is recommended for water deeper than 100 metres.<br />
<br />
Positions should be referenced to a geocentric reference frame based on the International Terrestrial Reference System (ITRS), for example WGS84. Uncertainty of a position is the uncertainty at the position of the sounding or feature within the geodetic reference frame. S-44 further sets out the requirements for the horizontal uncertainty of features significant to navigation, the coastline and topographic features.<br />
<br />
The navigation of vessels requires accurate knowledge of the water depth in order to exploit safely the maximum cargo carrying capacity, and the maximum available water for safe navigation. The measured depths and drying heights shall be referenced to a vertical datum that is compatible with the products to be made or updated from the survey. S-44 specifies the requirements for the following depth measurements: vertical uncertainty, water-level observations, depth measurement, feature detection, and sounding density.<br />
<br />
Other measurements standardized by S-44 are seabed sampling, chart and land survey vertical datum connection, and tidal prediction. These measurements are not required for all order of surveys.<br />
<br />
S-44 recommends the use of S-100 IHO Universal Hydrographic Data Model to perform a comprehensive assessment of the quality of the data. If a Bathymetric Model is required, the metadata should include the following: model resolution, computational model, underlying data density, uncertainty estimate, and a description of the underlying data. The Report of Survey shall provide a clear and comprehensive account of how the survey was performed, the results, the difficulties encountered, and the shortcomings. The report is the means by which the Surveyor in charge approves the survey record.<br />
<br />
To improve the safety of navigation, it is desirable to eliminate doubtful data. This is achieved through carefully defining the area to be searched and subsequently surveying that area according to the standards outlined in S-44.</div>Tebogo Mokwenahttp://wiki.icaci.org/index.php?title=S-100_IHO_Universal_hydrographic_data_model&diff=806S-100 IHO Universal hydrographic data model2016-06-24T09:27:51Z<p>Tebogo Mokwena: /* Overview */</p>
<hr />
<div>==Overview==<br />
{| class="wikitable"<br />
| Full name<br />
| [http://www.iho.int/iho_pubs/standard/S-100/S-100_Ed_2/S_100_V2.0.0_June-2015.pdf S-100, IHO Universal hydrographic data model]<br />
|-<br />
| Version<br />
| Edition 1.0.0<br />
|-<br />
| Amendments<br />
| None<br />
|-<br />
| Corrigenda<br />
| None<br />
|-<br />
| Published by<br />
| IHO<br />
|-<br />
| Languages<br />
| English<br />
|-<br />
| Online overview<br />
| http://iho.int/iho_pubs/standard/S-100/S-100_Version_1.0.0.zip<br />
|-<br />
| Type of standard<br />
| IHO International Standard <br/> Meta level<br />
|-<br />
| Related standard(s)<br />
| [http://wiki.icaci.org/index.php?title=Conceptual_schema_language ISO/TS 19103:2005, Geographic information – Conceptual schema language] <br/>[http://wiki.icaci.org/index.php?title=Profiles ISO 19106:2004, Geographic information – Profiles] <br/>[http://wiki.icaci.org/index.php?title=Spatial_schema ISO 19107:2003, Geographic information – Spatial schema] <br/>[http://wiki.icaci.org/index.php?title=Rules_for_application_schema ISO 19109:2005, Geographic information – Rules for application schema] <br/>[http://wiki.icaci.org/index.php?title=Methodology_for_feature_cataloguing ISO 19110:2005, Geographic information – Methodology for feature cataloguing ]<br/>[http://wiki.icaci.org/index.php?title=Spatial_referencing_by_coordinates ISO 19111:2007, Geographic information – Spatial referencing by coordinates] <br/>[http://wiki.icaci.org/index.php?title=Metadata_Fundamentals ISO 19115:2005, Geographic information – Metadata] <br/>[http://wiki.icaci.org/index.php?title=Metadata_%E2%80%93_Part_2:_Extensions_for_imagery_and_gridded_data ISO 19115-2:2009, Geographic information – Metadata – Part 2: Extensions for imagery and gridded data] <br/>[http://wiki.icaci.org/index.php?title=Portrayal ISO 19117:2012, Geographic information – Portrayal ]<br/> ISO 19118:2011, Geographic information – Encoding <br/>[http://wiki.icaci.org/index.php?title=Schema_for_coverage_geometry_and_functions ISO 19123:2005, Geographic information – Schema for coverage geometry and functions] <br/>[http://wiki.icaci.org/index.php?title=Feature_concept_dictionaries_and_registries ISO 19126:2009, Geographic Information – Feature concept dictionaries and registers] <br/>[http://wiki.icaci.org/index.php?title=Imagery,_gridded_and_coverage_data_framework ISO/TS 19129:2009, Geographic information – Imagery, Gridded and Coverage Data Framework] <br/> ISO 19130:2012, Geographic information – Sensor and data models for imagery and gridded data <br/>ISO 19135:2005, Geographic Information – Procedures for registration of items of geographic information <br/>[http://wiki.icaci.org/index.php?title=Data_quality ISO 19157:2013, Geographic information – Data quality] <br/>OMG Unified Modeling Language (OMG UML), Superstructure, V2.1.2 <br/> ISO 8601:2004, Data elements and interchange formats - Information interchange – Representation of dates and times <br/> ISO/IEC 8211:1994, Specification for a data descriptive file for information interchange Structure implementations <br/>ISO/IEC 12087-5:1998 - Computer graphics and image processing -- Image Processing and Interchange (IPI) - Functional Specification - Basic Image Interchange Format (BIIF) <br/>[http://wiki.icaci.org/index.php?title=JPEG_2000_image_coding_system:_Core_coding_system ISO/IEC 15444-13:2008 - Information Technology -- JPEG 2000 image coding system ]<br/> S-57 Cumulative Maintenance Document N°8 <br/>[http://wiki.icaci.org/index.php?title=Specifications_for_chart_content_and_display_aspects_of_ECDIS S-52 Specifications for Chart Content and Display Aspects of ECDIS ]<br/> S-61 Product Specification for Raster Navigational Charts (RNC) <br/>American National Standard T1.523-2001 - Telecommunications Glossary 2000 <br/><br />
|-<br />
| Application<br />
| S-100 specify the methods and tools for data management, processing, analysing, accessing, presenting and transferring of hydrographical or related data.<br />
|-<br />
| Conformance classes<br />
| None specified<br />
|-<br />
| Fundamental geospatial dataset<br />
| Category: ''Infrastructure'' <br/> Data Theme: ''Transportation''<br />
|}<br />
<br />
==Scope==<br />
S-100 – IHO Hydrographic Geospatial Standard for Marine Data and Information comprises twelve related parts that give the user the appropriate tools and framework to develop and maintain hydrographical related data, products and registers. These standards specify, for hydrographical and related information, methods and tools for data management, processing, analysing, accessing, presenting and transferring such data in digital/electronic form between different users, systems and locations. By following this set of geo-spatial hydrographical standards users will be able to build constituent parts of an S-100 compliant product specification.<br />
<br />
S-100 conforms as far as is reasonably possible to the ISO TC 211 series of geographic information standards, and where necessary has been tailored to suit hydrographical requirements.<br />
<br />
S-100 details the standard to be used for the exchange of hydrographical and related geospatial data between national hydrographical offices as well as between other organisations and for its distribution to manufacturers, mariners and other data users.<br />
<br />
S-100 comprises multiple parts that profile standards developed by the ISO Technical Committee 211. ISO TC 211 is responsible for the ISO series of standards for geographic information. The objective is that, together, the standards will form a framework for the development of sector specific applications that use geographic information. S-100 is an example of such an application.<br />
<br />
This standard specifies the procedures to be followed for:<br />
<br />
:#establishing and maintaining registers of hydrographical and related information;<br />
:#creating product specifications, feature catalogues and a definition of the general feature model;<br />
:#using spatial, imagery and gridded data, and metadata specifically aimed at fulfilling hydrographical requirements.<br />
<br />
==Implementation benefits==<br />
S-100 covers a wide range of activities with the hope of harmonizing them for hydrographical data and ensuring interoperability. The profiles define a subset of requirements that are specific for hydrographical data, but ensure interoperability with other data sources. Each profile would have its own implementation benefits, for example, the metadata profile defines a metadata schema for hydrographical data and extends the ISO 19115 for this application to ensure that all the aspects of hydrographical data are covered in the profile.<br />
<br />
==Implementation guidelines==<br />
S-100 was developed to align and exploit ISO/TC 211 standards to support a variety of data formats, products and customers. The data model will allow the development of new applications that leverage the new technologies and reaches beyond the traditional scope of hydrographical applications. S-100 encapsulates the use of best practice methods and procedures by including guidelines on implementing efficient production methods, optimizing the quality of products and services, and enabling interoperability through common interfaces.<br />
<br />
S-100 specifies a framework of components that can be used by interested communities to develop their own maritime geo-spatial products and services. S-100 consists of eleven profiles of ISO/TC 211 standards:<br />
<br />
#Conceptual Schema Language<br/>The first part of S-100 specifies a CSL and basic types that shall be used within the IHO community. The CSL is defined as a combination of UML and a set of basic data type definitions for specification of geographic information. Guidelines on the use of UML to create standardized geographic information and service models are also provided. Basic knowledge of the Object Management Group (OMG) UML is required to understand and implement the CSL profile.<br />
#Management of IHO Geospatial Information Registries<br/>The management of IHO geo-spatial information registries profile specifies the procedures that shall be followed when maintaining and publishing registers of unique, unambiguous and permanent identifiers assigned to items of geographic, hydrographical and metadata information. The roles and responsibilities for management of a registry and its registers are defined and described.<br/>This part also specifies a feature concept dictionary registers. A FCD specifies hydrographical definitions that may be used to describe geographic information. Such a register will improve the IHO’s ability to manage and extend multiple products based on S-100.<br />
#General Feature Model and Rules for Application Schema <br/>The General Feature Model defines a conceptual model of features, their characteristics and associations, and the rules for developing an application schema. This part further deals with conceptual modelling of features and their properties, conceptual modelling of information types and associated attributes, and the development of application schemas and the related rules for such a schema.<br />
#Metadata <br/>The S-100 metadata profile described is divided into three parts and provides specifications for describing, validating and exchanging metadata of data produced by hydrographical organisations. This profile is based on ISO 19115:2003, ISO 19115-2:2006, and ISO 19139:2007. The primary intent of this profile is to describe digital geo-spatial data. However, it can also be used for other products, such as charts, maps, images, textual documents and non-geographic resources. The profile is not limited to ISO 19115 since it can be extended to include additional resources.<br />
#Feature Catalogue<br/>The feature catalogue specifies a framework for organisation and reporting the classification of real world phenomena as geographic data. It defines the methodology for classification of the feature types and specifies how they are organised in a feature catalogue and presented to the users of a set of geographic data. A feature catalogue shall be defined for each product specification. This profile is for defining geographic features at the type level.<br />
#Coordinate Reference Systems<br/>The location of an object shall be defined by means of coordinates, which relate to the feature’s position. This profile describes the elements required to define the referencing by means of coordinate systems and datums. A conceptual schema for describing spatial referencing by coordinates and the minimum requirements for multi-dimensional spatial coordinate references are defined.<br />
#Spatial Schemas <br/> S-100 spatial schema requirements are less comprehensive than ISO 19107, which contains all the information necessary for describing and manipulating the spatial characteristics of geographic features. This part is only a profile of ISO 19107 and contains thus only a subset of the classes. The profile added additional constraints (omitted optional elements or constrained cardinalities) for hydrographical data.<br />
#Imagery and Gridded data <br/>Imagery and gridded data have become common forms of geographic data and there exist many external standards designed to handle such data. S-100 shall not preclude compatibility with external sources of data. This profile aligns with the ISO/TC 211 standards on imagery and gridded data in order to support multiple sources of data and uses the common information structures. This allows the data to be combined with various other data types. This part defines specific grid organisations to be used for hydrographical data and images associated with hydrographical data. Both simple grids and complex multidimensional grids are defined, as well as point sets and TINs.<br />
#Portrayal<br/>Portrayal is not included in this version of S-100 and will be developed at a later date.<br />
#Encoding Formats<br/>S-100 does not mandate particular encoding formats. The developer of a product specification can decide on suitable encoding standards and shall then document their chosen format. Encoding is complicated because numerous encoding standards are available. The parts provide guidelines on the selection and documentation of an encoding format.<br />
#Product Specification<br/>A data product specification defines a geo-spatial data product, and describes all the features, attributes and relationships of a given application and their mapping to a dataset. This part describes data product specifications for hydrographical requirements for geographic data products. Its aim is to provide a clear and similar structure for any data product specification to be written.</div>Tebogo Mokwenahttp://wiki.icaci.org/index.php?title=ISO_14825:2011_Intelligent_transport_systems_-_Geographic_Data_Files_(GDF)_-_GDF5.0&diff=805ISO 14825:2011 Intelligent transport systems - Geographic Data Files (GDF) - GDF5.02016-06-24T09:13:16Z<p>Tebogo Mokwena: /* Overview */</p>
<hr />
<div>==Overview==<br />
{| class="wikitable"<br />
| Full name<br />
| [http://www.iso.org/iso/home/store/catalogue_tc/catalogue_detail.htm?csnumber=54610 ISO 14825:2011, Intelligent transport systems – Geographic Data Files (GDF) – GDF5.0]<br />
|-<br />
| Version<br />
| Edition 2<br />
|-<br />
| Amendments<br />
| None<br />
|-<br />
| Corrigenda<br />
| None<br />
|-<br />
| Published by<br />
| ISO/TC 204, Intelligent transport systems<br />
|-<br />
| Languages<br />
| English<br />
|-<br />
| Online overview<br />
| Not available yet<br />
|-<br />
| Type of standard<br />
| ISO International Standard <br/> Application level<br />
|-<br />
| Related standard(s)<br />
| ISO 14813-1:2015, Intelligent transport systems – Reference model architecture(s) for the <br/>ITS sector, ITS service domains, service groups and services <br/> ISO 17572-1:2008, Intelligent transport systems (ITS) – Location referencing for <br/>geographic databases, General requirements and conceptual model <br/>ISO 17572-2:2015, Intelligent transport systems (ITS) – Location referencing for <br/>geographic databases, Pre-coded location references (pre-coded profile) <br/>[http://wiki.icaci.org/index.php?title=Metadata_Fundamentals ISO 19115:2003, Geographic information – Metadata] <br/> ISO 19132:2007, Geographic information – Location-based services – Reference model <br/> ISO/DIS 19147:2015, Geographic information – Transfer nodes<br />
|-<br />
| Application<br />
| Exchange of data for intelligent transport systems, automotive navigation systems, traffic, <br/>fleet and dispatch management, road traffic analysis, automatic vehicle location and other <br/>transport applications.<br />
|-<br />
| Conformance classes<br />
| None specified<br />
|-<br />
| Fundamental geospatial dataset<br />
| Category: ''Infrastructure'' <br/> Data Theme: ''Transportation''<br />
|}<br />
<br />
==Scope==<br />
ISO 14825:2011 specifies the conceptual and logical data model and physical encoding formats for geographic databases for Intelligent Transport Systems (ITS) applications and services. It includes a specification of potential contents of such databases (data dictionaries for Features, Attributes and Relationships), a specification of how these contents shall be represented, and of how relevant information about the database itself can be specified (metadata).<br />
<br />
The focus of ISO 14825:2011 is on ITS applications and services and it emphasises road and road related information. ITS applications and services, however, also require information in addition to road and road related information.<br />
<br />
EXAMPLE 1 ITS applications and services need information about addressing systems in order to specify locations and/or destinations. Consequently, information about the administrative and postal subdivisions of an area is essential.<br />
<br />
EXAMPLE 2 Map display is an important component of ITS applications and services. For proper map display, the inclusion of contextual information such as land and water cover is essential.<br />
<br />
EXAMPLE 3 Point-of-Interest (POI) or service information is a key feature of traveller information. It adds value to end-user ITS applications and services.<br />
<br />
The Conceptual Data Model has a broader focus than ITS applications and services. It is application independent, with observance for harmonization of this International Standard with other geographic database standards.<br />
<br />
==Implementation benefits==<br />
ISO 14825:2011 is widely used for intelligent transport systems (ITS) and related applications, and services, by vehicle manufacturers, electronic components manufacturers, manufacturers of global positioning system receivers, and geospatial data vendors. Note that while the geospatial data might be distributed using GDF, it is typically encoded into proprietary formats for more efficient processing within navigation systems and other components.<br />
<br />
ISO 14825:2011 has been harmonised with the relevant ISO/TC 211 standards and includes all the core metadata defined in ISO 19115:2003.<br />
<br />
However, it does not appear that GDF is used much for other types of applications.<br />
<br />
==Implementation guidelines==<br />
ISO 14825:2011 is a very large document (over 1200 pages), as in addition to the data format (physical encoding), it includes the conceptual and logical data models, media record specifications, XML schema specifications, SQL encoding specifications, rules for data capture and portrayal, metadata and a comprehensive feature catalogue (classification system) with attributes, relationships and extensive code lists. The standard also includes annexes with extensive examples of how to use GDF, such as for complex time domains and generalizing networks. However, it is not clear why the standard has an annex duplicating ISO 639-2, Codes for the Representation of Names of Languages Part 2: Alpha-3 Code (as it was on 3 March 2009), and ISO 3166-1, Codes for the representation of names of countries and their subdivisions — Part 1: Country codes (as it was on 17 October 2008). Both ISO 639-2 and ISO 3166-1 are updated from time to time and freely available on the ISO website.<br />
<br />
While very large, ISO 14825:2011 is probably relatively easy (though rather tedious) to implement, as it has extensive definitions, descriptions and illustrations, and snippets of pseudo-code and XML. However, it is probably only of interest to those implementing intelligent transport systems (ITS) and related transport applications.</div>Tebogo Mokwena