35.240.70 - IT applications in science
ICS 35.240.70 Details
IT applications in science
IT-Anwendungen in der Wissenschaft
Applications des TI dans les sciences
Uporabniške rešitve IT v znanosti
General Information
e-Library Subscription
Create subscription and get permanent access to documents within 35.240.70 - IT applications in science
Currently subscription includes documents marked with .We are working on making all documents available within the subscription.
This document defines a conceptual schema for observations, for features involved in the observation process, and for features involved in sampling when making observations. These provide models for the exchange of information describing observation acts and their results, both within and between different scientific and technical communities.
Observations commonly involve sampling of an ultimate feature-of-interest. This document defines a common set of sample types according to their spatial, material (for ex situ observations) or statistical nature. The schema includes relationships between sample features (sub-sampling, derived samples).
This document concerns only externally visible interfaces and places no restriction on the underlying implementations other than what is needed to satisfy the interface specifications in the actual situation.
- Standard164 pagesEnglish languagesale 10% offe-Library read for1 day
- Draft140 pagesEnglish languagesale 10% offe-Library read for1 day
This document defines an integrated XML implementation of ISO 19115-1 and ISO 19115-2 by defining the following artefacts:
— a set of XML schema required to validate metadata instance documents conforming to conceptual model elements defined in ISO 19115-1 and ISO 19115-2; and
— a set of ISO/IEC 19757-3 (Schematron) rules that implement validation constraints in the ISO 19115-1 and ISO 19115-2 UML models that are not validated by the XML schema.
This document describes the procedure used to generate XML schemas from ISO geographic information conceptual models related to metadata. The XML schemas are generated directly from the conceptual UML model (8.5).
- Draft64 pagesEnglish languagesale 10% offe-Library read for1 day
This document defines an integrated XML implementation of ISO 19115-1 and ISO 19115-2 by defining the following artefacts: — a set of XML schema required to validate metadata instance documents conforming to conceptual model elements defined in ISO 19115-1 and ISO 19115-2; and — a set of ISO/IEC 19757-3 (Schematron) rules that implement validation constraints in the ISO 19115-1 and ISO 19115-2 UML models that are not validated by the XML schema. This document describes the procedure used to generate XML schemas from ISO geographic information conceptual models related to metadata. The XML schemas are generated directly from the conceptual UML model (8.5).
- Standard100 pagesEnglish languagesale 15% off
- Standard109 pagesFrench languagesale 15% off
- Draft76 pagesFrench languagesale 15% off
- Draft16 pagesEnglish languagesale 10% offe-Library read for1 day
- Draft16 pagesEnglish languagesale 10% offe-Library read for1 day
- Standard13 pagesEnglish languagesale 15% off
- Standard11 pagesEnglish languagesale 15% off
This document establishes a standard registration and maintenance mechanism for the registration of ISO 19150-4-conformant geographic information service ontologies.
This document makes use of ISO 19135-1 whenever appropriate.
This document does not define semantics operators or rules for ontologies, and does not develop any application ontology.
In relation to ISO 19101-1:2014, 6.2, this document defines and formalizes the following purposes of the ISO geographic information reference model:
— geographic information service components and their behaviour for data processing purposes over the Web; and
— OWL ontologies to cast ISO/TC 211 International Standards to benefit from and support the Semantic Web.
In relation to ISO 19101-1:2014, 8.3, this document addresses the Application:Procedural foundation of the ISO geographic information reference model.
- Draft36 pagesEnglish languagesale 10% offe-Library read for1 day
This document defines a coverage processing language for server-side extraction, filtering, processing, analytics, and fusion of multi-dimensional geospatial coverages representing, for example, spatio-temporal sensor, image, simulation, or statistics datacubes. Services implementing this language provide access to original or derived sets of coverage information, in forms that are useful for client-side consumption.
This document relies on the ISO 19123-1 abstract coverage model. In this edition, regular and irregular multi-dimensional grids are supported for axes that can carry spatial, temporal or any other semantics. Future editions will additionally support further axis types as well as further coverage types from ISO 19123-1, specifically, point clouds and meshes.
- Draft80 pagesEnglish languagesale 10% offe-Library read for1 day
This document defines a conceptual schema for coverages. A coverage is a mapping from a spatial, temporal or spatiotemporal domain to attribute values sharing the same attribute type. A coverage domain consists of a collection of direct positions in a coordinate space that can be defined in terms of spatial and/or temporal dimensions, as well as non-spatiotemporal (in ISO 19111:2019, “parametric”) dimensions. Examples of coverages include point clouds, grids, meshes, triangulated irregular networks, and polygon sets. Coverages are the prevailing data structures in a number of application areas, such as remote sensing, meteorology and mapping of depth, elevation, soil and vegetation. This document defines the coverage concept including the relationship between the domain of a coverage and its associated attribute range. This document defines the characteristics of the domain. The characteristics of the attribute range are not defined in this document, but are defined in implementation standards. Consequently, the standardization target of this document consists of implementation standards, not concrete implementations themselves.
- Draft146 pagesEnglish languagesale 10% offe-Library read for1 day
This document establishes a standard registration and maintenance mechanism for the registration of ISO 19150-4-conformant geographic information service ontologies. This document makes use of ISO 19135-1 whenever appropriate. This document does not define semantics operators or rules for ontologies, and does not develop any application ontology. In relation to ISO 19101-1:2014, 6.2, this document defines and formalizes the following purposes of the ISO geographic information reference model: — geographic information service components and their behaviour for data processing purposes over the Web; and — OWL ontologies to cast ISO/TC 211 International Standards to benefit from and support the Semantic Web. In relation to ISO 19101-1:2014, 8.3, this document addresses the Application:Procedural foundation of the ISO geographic information reference model.
- Standard30 pagesEnglish languagesale 15% off
- Standard31 pagesFrench languagesale 15% off
- Draft31 pagesEnglish languagesale 15% off
- Draft38 pagesFrench languagesale 15% off
This document defines a coverage processing language for server-side extraction, filtering, processing, analytics, and fusion of multi-dimensional geospatial coverages representing, for example, spatio-temporal sensor, image, simulation, or statistics datacubes. Services implementing this language provide access to original or derived sets of coverage information, in forms that are useful for client-side consumption. This document relies on the ISO 19123-1 abstract coverage model. In this edition, regular and irregular multi-dimensional grids are supported for axes that can carry spatial, temporal or any other semantics. Future editions will additionally support further axis types as well as further coverage types from ISO 19123-1, specifically, point clouds and meshes.
- Standard77 pagesEnglish languagesale 15% off
- Standard82 pagesFrench languagesale 15% off
- Draft77 pagesEnglish languagesale 15% off
- Draft77 pagesEnglish languagesale 15% off
This document defines a conceptual schema for coverages. A coverage is a mapping from a spatial, temporal or spatiotemporal domain to attribute values sharing the same attribute type. A coverage domain consists of a collection of direct positions in a coordinate space that can be defined in terms of spatial and/or temporal dimensions, as well as non-spatiotemporal (in ISO 19111:2019, “parametric”) dimensions. Examples of coverages include point clouds, grids, meshes, triangulated irregular networks, and polygon sets. Coverages are the prevailing data structures in a number of application areas, such as remote sensing, meteorology and mapping of depth, elevation, soil and vegetation. This document defines the coverage concept including the relationship between the domain of a coverage and its associated attribute range. This document defines the characteristics of the domain. The characteristics of the attribute range are not defined in this document, but are defined in implementation standards. Consequently, the standardization target of this document consists of implementation standards, not concrete implementations themselves.
- Standard78 pagesEnglish languagesale 15% off
- Standard82 pagesFrench languagesale 15% off
- Draft78 pagesEnglish languagesale 15% off
- Draft78 pagesEnglish languagesale 15% off
This document establishes the principles for describing the quality of geographic data. It:
— defines a well-considered system of components for describing data quality;
— defines the process for defining additional, domain-specific components for describing data quality;
— specifies components and the content structure of data quality measures;
— describes general procedures for evaluating the quality of geographic data;
— establishes principles for reporting data quality.
This document 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.
This document does not attempt to define minimum acceptable levels of quality for geographic data. Such information is usually present as a requirement in a data product specification, defined in accordance with ISO 19131, for example.
- Standard112 pagesEnglish languagesale 10% offe-Library read for1 day
- Draft108 pagesEnglish languagesale 10% offe-Library read for1 day
ISO 19160-4:2017 defines key terms for postal addressing, postal address components and constraints on their use.
Specifically, ISO 19160-4:2017 defines postal address components organized into three hierarchical levels:
- elements, such as organization name or postcode, which have well-defined conceptual meaning and are not themselves made up of subordinate components, though they may be sub-divided for technical purposes;
- constructs, such as organization identification, which group elements into units form a logical portion of a postal address;
- segments, such as addressee specification, which group-related postal address constructs and/or postal address elements into units with a specific defined function.
ISO 19160-4:2017 also specifies a mechanism for creation of sub-elements, which correspond to either sub-divisions of element content, such as door type or door indicator or to multiple occurrences and locations of elements in an address, such as levels of administrative regions.
ISO 19160-4:2017 does not specify the length of any component nor the value range of any component.
Moreover, ISO 19160-4:2017 defines the codes to identify elements and sub-elements.
Further, ISO 19160-4:2017 specifies postal address rendering rules. This includes identification and ordering of output lines in a rendered address, conditions for selection of candidate lines, the order and concatenation of postal address components, required and optional components, parameters to contextualize address for rendering and the formatting of the components, subject to constraints on the space available for that task. Postal address rendering rules are represented in ISO 19160-4:2017 as a postal address template.
Finally, ISO 19160-4:2017 specifies language suitable for computer processing to formally express postal address templates.
- Standard74 pagesEnglish languagesale 10% offe-Library read for1 day
- Draft70 pagesEnglish languagesale 10% offe-Library read for1 day
This document defines a conceptual schema for observations, for features involved in the observation process, and for features involved in sampling when making observations. These provide models for the exchange of information describing observation acts and their results, both within and between different scientific and technical communities.
Observations commonly involve sampling of an ultimate feature-of-interest. This document defines a common set of sample types according to their spatial, material (for ex situ observations) or statistical nature. The schema includes relationships between sample features (sub-sampling, derived samples).
This document concerns only externally visible interfaces and places no restriction on the underlying implementations other than what is needed to satisfy the interface specifications in the actual situation.
- Standard164 pagesEnglish languagesale 10% offe-Library read for1 day
- Draft140 pagesEnglish languagesale 10% offe-Library read for1 day
This document defines a conceptual schema for observations, for features involved in the observation process, and for features involved in sampling when making observations. These provide models for the exchange of information describing observation acts and their results, both within and between different scientific and technical communities. Observations commonly involve sampling of an ultimate feature-of-interest. This document defines a common set of sample types according to their spatial, material (for ex situ observations) or statistical nature. The schema includes relationships between sample features (sub-sampling, derived samples). This document concerns only externally visible interfaces and places no restriction on the underlying implementations other than what is needed to satisfy the interface specifications in the actual situation.
- Standard151 pagesEnglish languagesale 15% off
- Draft151 pagesEnglish languagesale 15% off
- Draft151 pagesEnglish languagesale 15% off
The ISO 19124 series is focused on calibration and validation (Cal/Val) of remote sensing data, which are collected by a sensor on-board a platform in a mission, and products derived in part or whole from the data. The ISO 19124 series defines the metadata related to the calibration and validation process that has not been defined in other ISO/TC 211 International Standards. The metadata allows the data providers to provide a standardized description of the Cal/Val process they have applied to the data. It allows the data users to get the same forms of metadata from different data providers. This document addresses the overall framework and common calibration and validation processes related to Earth observation data and derived products from different types of remote sensors. Subsequent parts in the ISO 19124 series will target data from specific sensors, for example, infrared, ultraviolet/visible/near-infrared, microwave, or broadband, products derived from those data, and calibration and validation sites. Calibration addresses a geometric, radiometric, or spectral correction of the data. Validation addresses an evaluation of the quality and the accuracy of the data and the derived products.
- Technical specification55 pagesEnglish languagesale 15% off
- Draft54 pagesEnglish languagesale 15% off
- Draft54 pagesEnglish languagesale 15% off
This document establishes the principles for describing the quality of geographic data. It:
— defines a well-considered system of components for describing data quality;
— defines the process for defining additional, domain-specific components for describing data quality;
— specifies components and the content structure of data quality measures;
— describes general procedures for evaluating the quality of geographic data;
— establishes principles for reporting data quality.
This document 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.
This document does not attempt to define minimum acceptable levels of quality for geographic data. Such information is usually present as a requirement in a data product specification, defined in accordance with ISO 19131, for example.
- Standard112 pagesEnglish languagesale 10% offe-Library read for1 day
- Draft108 pagesEnglish languagesale 10% offe-Library read for1 day
This document establishes the principles for describing the quality of geographic data. It: — defines a well-considered system of components for describing data quality; — defines the process for defining additional, domain-specific components for describing data quality; — specifies components and the content structure of data quality measures; — describes general procedures for evaluating the quality of geographic data; — establishes principles for reporting data quality. This document 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. This document does not attempt to define minimum acceptable levels of quality for geographic data. Such information is usually present as a requirement in a data product specification, defined in accordance with ISO 19131, for example.
- Standard102 pagesEnglish languagesale 15% off
- Standard114 pagesFrench languagesale 15% off
- Draft102 pagesEnglish languagesale 15% off
- Draft102 pagesEnglish languagesale 15% off
- Draft116 pagesFrench languagesale 15% off
This document defines key terms for postal addressing, postal address components and constraints on their use.
Specifically, this document specifies postal address components organized into three hierarchical levels:
— elements, such as organization name or postcode, which have well-defined conceptual meaning and are not themselves made up of subordinate components, though they can be sub-divided for technical purposes;
— constructs, such as organization identification, which group elements into units form a logical portion of a postal address;
— segments, such as addressee specification, which group related postal address constructs and/or postal address elements into units with a specific defined function.
This document also specifies a mechanism for the creation of sub-elements, which correspond to either sub-divisions of element content, such as door type or door indicator or to multiple occurrences and locations of elements in an address, such as levels of administrative regions.
This document does not specify the length of any component nor the value range of any component.
Moreover, this document specifies the codes to identify elements and sub-elements.
Further, this document specifies postal address rendering rules. This includes:
— identification and ordering of output lines in a rendered address;
— conditions for the selection of candidate lines;
— the order and concatenation of postal address components;
— required and optional components;
— parameters to contextualize an address for rendering;
— the formatting of the components, subject to constraints on the space available for that task.
Postal address rendering rules are represented in this document as a postal address template.
Finally, this document specifies language suitable for computer processing to formally express postal address templates.
This document does not cover the topic of data protection. Users of the document are nevertheless reminded that the storage and exchange of personal data are subject to legislation in many countries.
- Standard74 pagesEnglish languagesale 10% offe-Library read for1 day
- Draft70 pagesEnglish languagesale 10% offe-Library read for1 day
This document defines key terms for postal addressing, postal address components and constraints on their use. Specifically, this document specifies postal address components organized into three hierarchical levels: — elements, such as organization name or postcode, which have well-defined conceptual meaning and are not themselves made up of subordinate components, though they can be sub-divided for technical purposes; — constructs, such as organization identification, which group elements into units form a logical portion of a postal address; — segments, such as addressee specification, which group related postal address constructs and/or postal address elements into units with a specific defined function. This document also specifies a mechanism for the creation of sub-elements, which correspond to either sub-divisions of element content, such as door type or door indicator or to multiple occurrences and locations of elements in an address, such as levels of administrative regions. This document does not specify the length of any component nor the value range of any component. Moreover, this document specifies the codes to identify elements and sub-elements. Further, this document specifies postal address rendering rules. This includes: — identification and ordering of output lines in a rendered address; — conditions for the selection of candidate lines; — the order and concatenation of postal address components; — required and optional components; — parameters to contextualize an address for rendering; — the formatting of the components, subject to constraints on the space available for that task. Postal address rendering rules are represented in this document as a postal address template. Finally, this document specifies language suitable for computer processing to formally express postal address templates. This document does not cover the topic of data protection. Users of the document are nevertheless reminded that the storage and exchange of personal data are subject to legislation in many countries.
- Standard64 pagesEnglish languagesale 15% off
- Standard68 pagesFrench languagesale 15% off
- Draft64 pagesEnglish languagesale 15% off
- Draft64 pagesEnglish languagesale 15% off
- Draft70 pagesFrench languagesale 15% off
ISO 19131:2007 specifies 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.
- Standard96 pagesEnglish languagesale 10% offe-Library read for1 day
- Draft93 pagesEnglish languagesale 10% offe-Library read for1 day
This document specifies the framework, concepts and methodology for conformance testing and criteria to be achieved to claim conformance to the family of applicable standardization documents regarding geographic information and relevant application domains. This document provides a framework for specifying abstract test suites composed of abstract test cases grouped in conformance classes and for defining the procedures to be followed during conformance testing.
Conformance can be claimed for data or software products or services or by specifications including any profile or functional standard. The structure of, and relationships between, conformance classes as defined in this document underly a systematic approach to configuration management involving managing dependencies within and between modules.
- Standard37 pagesEnglish languagesale 10% offe-Library read for1 day
- Draft32 pagesEnglish languagesale 10% offe-Library read for1 day
This document describes requirements for the specification of geographic data products, based upon the concepts of other International Standards in the ISO 19100 family of standards. It also provides guidance in the creation of data product specifications, so that they can be easily understood and fit for their intended purpose.
This document specifies XML encoding of data product specifications.
This document provides OWL representation of the underlying UML model. See Annex F.
This document is intended for use by data producers, data providers, service providers and potential users of data products.
- Standard96 pagesEnglish languagesale 10% offe-Library read for1 day
- Draft93 pagesEnglish languagesale 10% offe-Library read for1 day
This document specifies the representation of latitude and longitude and optionally height or depth
compatible with previous editions of ISO 6709.
This document also supports the representations of other coordinate types and time that can be
associated with those coordinates as defined through one or more coordinate reference systems (CRS).
This document describes a text string of coordinates, suitable for electronic data exchange, for
one point, including reference system identification to ensure that the coordinates unambiguously
represent the position of that point. Files containing multiple points with a single common reference
system identification are out of scope. This document also describes a simpler text string structure for
coordinate representation of a point location that is more suitable for human readability.
- Standard45 pagesEnglish languagesale 10% offe-Library read for1 day
- Draft40 pagesEnglish languagesale 10% offe-Library read for1 day
This document specifies an extension to the Geospatial API for Features — Part 1: Core standard that
defines the behaviour of a server that supports the ability to present geometry valued properties in a
response document in one from a list of supported Coordinates Reference Systems (CRS).
Each supported CRS is specified by reference using a uniform resource identifier (URI).
This document specifies:
— how, for each offered feature collection, a server advertises the list of supported CRS identifiers;
— how the coordinates of geometry valued feature properties can be accessed in one of the supported
CRSs;
— how features can be accessed from the server using a bounding box specified in one of the supported
CRSs; and
— how a server can declare the CRS used to present feature resources.
- Standard24 pagesEnglish languagesale 10% offe-Library read for1 day
- Draft21 pagesEnglish languagesale 10% offe-Library read for1 day
This document describes requirements for the specification of geographic data products, based upon the concepts of other International Standards in the ISO 19100 family of standards. It also provides guidance in the creation of data product specifications, so that they can be easily understood and fit for their intended purpose. This document specifies XML encoding of data product specifications. This document provides OWL representation of the underlying UML model. See Annex F. This document is intended for use by data producers, data providers, service providers and potential users of data products.
- Standard85 pagesEnglish languagesale 15% off
- Standard90 pagesFrench languagesale 15% off
- Draft85 pagesEnglish languagesale 15% off
- Draft85 pagesEnglish languagesale 15% off
- Draft92 pagesFrench languagesale 15% off
This document defines the calibration of space-borne passive microwave radiometers and the validation of the calibrated information.
- Technical specification51 pagesEnglish languagesale 15% off
This document specifies the representation of latitude and longitude and optionally height or depth compatible with previous editions of ISO 6709.
This document also supports the representations of other coordinate types and time that can be associated with those coordinates as defined through one or more coordinate reference systems (CRS).
This document describes a text string of coordinates, suitable for electronic data exchange, for one point, including reference system identification to ensure that the coordinates unambiguously represent the position of that point. Files containing multiple points with a single common reference system identification are out of scope. This document also describes a simpler text string structure for coordinate representation of a point location that is more suitable for human readability.
- Standard45 pagesEnglish languagesale 10% offe-Library read for1 day
- Draft40 pagesEnglish languagesale 10% offe-Library read for1 day
This document specifies an extension to the Geospatial API for Features — Part 1: Core standard that defines the behaviour of a server that supports the ability to present geometry valued properties in a response document in one from a list of supported Coordinates Reference Systems (CRS).
Each supported CRS is specified by reference using a uniform resource identifier (URI).
This document specifies:
— how, for each offered feature collection, a server advertises the list of supported CRS identifiers;
— how the coordinates of geometry valued feature properties can be accessed in one of the supported CRSs;
— how features can be accessed from the server using a bounding box specified in one of the supported CRSs; and
— how a server can declare the CRS used to present feature resources.
- Standard24 pagesEnglish languagesale 10% offe-Library read for1 day
- Draft21 pagesEnglish languagesale 10% offe-Library read for1 day
This document specifies the framework, concepts and methodology for conformance testing and criteria
to be achieved to claim conformance to the family of applicable standardization documents regarding
geographic information and relevant application domains. This document provides a framework for
specifying abstract test suites composed of abstract test cases grouped in conformance classes and for
defining the procedures to be followed during conformance testing.
Conformance can be claimed for data or software products or services or by specifications including
any profile or functional standard. The structure of, and relationships between, conformance classes
as defined in this document underly a systematic approach to configuration management involving
managing dependencies within and between modules.
- Standard37 pagesEnglish languagesale 10% offe-Library read for1 day
- Draft32 pagesEnglish languagesale 10% offe-Library read for1 day
- Amendment16 pagesEnglish languagesale 10% offe-Library read for1 day
- Draft10 pagesEnglish languagesale 10% offe-Library read for1 day
This document specifies the representation of latitude and longitude and optionally height or depth compatible with previous editions of ISO 6709. This document also supports the representations of other coordinate types and time that can be associated with those coordinates as defined through one or more coordinate reference systems (CRS). This document describes a text string of coordinates, suitable for electronic data exchange, for one point, including reference system identification to ensure that the coordinates unambiguously represent the position of that point. Files containing multiple points with a single common reference system identification are out of scope. This document also describes a simpler text string structure for coordinate representation of a point location that is more suitable for human readability.
- Standard35 pagesEnglish languagesale 15% off
- Standard36 pagesFrench languagesale 15% off
- Draft36 pagesEnglish languagesale 15% off
This document specifies an extension to the Geospatial API for Features — Part 1: Core standard that defines the behaviour of a server that supports the ability to present geometry valued properties in a response document in one from a list of supported Coordinates Reference Systems (CRS). Each supported CRS is specified by reference using a uniform resource identifier (URI). This document specifies: — how, for each offered feature collection, a server advertises the list of supported CRS identifiers; — how the coordinates of geometry valued feature properties can be accessed in one of the supported CRSs; — how features can be accessed from the server using a bounding box specified in one of the supported CRSs; and — how a server can declare the CRS used to present feature resources.
- Standard16 pagesEnglish languagesale 15% off
- Standard17 pagesFrench languagesale 15% off
- Standard17 pagesFrench languagesale 15% off
This document specifies the framework, concepts and methodology for conformance testing and criteria to be achieved to claim conformance to the family of applicable standardization documents regarding geographic information and relevant application domains. This document provides a framework for specifying abstract test suites composed of abstract test cases grouped in conformance classes and for defining the procedures to be followed during conformance testing. Conformance can be claimed for data or software products or services or by specifications including any profile or functional standard. The structure of, and relationships between, conformance classes as defined in this document underly a systematic approach to configuration management involving managing dependencies within and between modules.
- Standard29 pagesEnglish languagesale 15% off
- Standard30 pagesFrench languagesale 15% off
- Amendment16 pagesEnglish languagesale 10% offe-Library read for1 day
- Draft10 pagesEnglish languagesale 10% offe-Library read for1 day
- Standard10 pagesEnglish languagesale 15% off
- Standard10 pagesFrench languagesale 15% off
- Draft10 pagesEnglish languagesale 15% off
This document defines the XML Schema implementation of imagery sensor geopositioning models defined in ISO 19130-1 and ISO/TS 19130-2. It applies XML Schema inheritance and extension based on the OGC SensorML and OGC SWE Common Data Model. Instead of introducing an XML Schema based on the UML models defined in ISO 19130-1 and ISO/TS 19130-2, it leverages the existing OGC SensorML by first introducing a semantic mapping from the model elements defined in ISO 19130-1 and ISO/TS 19130-2 to OGC SensorML, and then defining the detailed schema inheritance and extensions based on OGC SensorML to fully support encoding of the imagery sensor models for geopositioning defined in ISO 19130-1 and ISO/TS 19130-2.
- Technical specification36 pagesEnglish languagesale 15% off
- Draft36 pagesEnglish languagesale 15% off
- Amendment9 pagesEnglish languagesale 10% offe-Library read for1 day
- Draft6 pagesEnglish languagesale 10% offe-Library read for1 day
This document specifies the behaviour of Web APIs that provide access to features in a dataset in a manner independent of the underlying data store. This document defines discovery and query operations.
Discovery operations enable clients to interrogate the API, including the API definition and metadata about the feature collections provided by the API, to determine the capabilities of the API and retrieve information about available distributions of the dataset.
Query operations enable clients to retrieve features from the underlying data store based upon simple selection criteria, defined by the client.
- Standard64 pagesEnglish languagesale 10% offe-Library read for1 day
- Draft61 pagesEnglish languagesale 10% offe-Library read for1 day
- Amendment8 pagesEnglish languagesale 10% offe-Library read for1 day
- Draft6 pagesEnglish languagesale 10% offe-Library read for1 day
This document 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, as feature catalogues are often derived from feature concept dictionaries, this document does specify a schema for a hierarchical register of feature concept dictionaries and feature catalogues. These registers are in accordance with ISO 19135‑1.
- Standard58 pagesEnglish languagesale 10% offe-Library read for1 day
- Draft40 pagesEnglish languagesale 10% offe-Library read for1 day
This document specifies a conceptual schema for locations relative to a one-dimensional object as measurement along (and optionally offset from) that object. It defines a description of the data and operations required to use and support linear referencing.
This document is applicable to transportation, utilities, environmental protection, location-based services and other applications which define locations relative to linear objects. For ease of reading, most examples discussed in this document come from the transportation domain.
- Standard109 pagesEnglish languagesale 10% offe-Library read for1 day
- Draft102 pagesEnglish languagesale 10% offe-Library read for1 day
- Amendment10 pagesEnglish languagesale 10% offe-Library read for1 day
- Draft10 pagesEnglish languagesale 10% offe-Library read for1 day
- Amendment8 pagesEnglish languagesale 10% offe-Library read for1 day
- Draft6 pagesEnglish languagesale 10% offe-Library read for1 day
- Amendment9 pagesEnglish languagesale 10% offe-Library read for1 day
- Draft6 pagesEnglish languagesale 10% offe-Library read for1 day
This document specifies the behaviour of Web APIs that provide access to features in a dataset in a
manner independent of the underlying data store. This document defines discovery and query
operations.
Discovery operations enable clients to interrogate the API, including the API definition and metadata
about the feature collections provided by the API, to determine the capabilities of the API and retrieve
information about available distributions of the dataset.
Query operations enable clients to retrieve features from the underlying data store based upon simple
selection criteria, defined by the client.
- Standard64 pagesEnglish languagesale 10% offe-Library read for1 day
- Draft61 pagesEnglish languagesale 10% offe-Library read for1 day
This document 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, as feature catalogues are often derived from feature concept dictionaries, this
document does specify a schema for a hierarchical register of feature concept dictionaries and feature
catalogues. These registers are in accordance with ISO 19135-1.
- Standard58 pagesEnglish languagesale 10% offe-Library read for1 day
- Draft40 pagesEnglish languagesale 10% offe-Library read for1 day
- Amendment11 pagesEnglish languagesale 10% offe-Library read for1 day
- Draft8 pagesEnglish languagesale 10% offe-Library read for1 day
- Standard3 pagesEnglish languagesale 15% off
- Standard2 pagesFrench languagesale 15% off
- Draft3 pagesEnglish languagesale 15% off