Contents 1 GML model 1.1 Profile 1.1.1 GML Simple Features Profile 1.1.2 Subset tool 1.2 Application schema 1.3 GML and KML 1.4 GML geometries 1.5 Features 1.6 Coordinates 1.7 Coordinate reference system 2 Examples 2.1 Features using geometries 2.2 Point Profile 3 History 3.1 Initial Work - to OGC Recommendation Paper 3.2 Moving to XML Schema - Version 2. 3.3 GML and G-XML (Japan) 3.4 Towards ISO - GML 3.0 broadens the scope of GML 4 Standards 4.1 ISO 19136 5 See also 6 References 7 External links

GML model[edit] GML contains a rich set of primitives which are used to build application specific schemas or application languages. These primitives include: Feature Geometry Coordinate reference system Topology Time Dynamic feature Coverage (including geographic images) Unit of measure Directions Observations Map presentation styling rules The original GML model was based on the World Wide Web Consortium's Resource Description Framework (RDF). Subsequently, the OGC introduced XML schemas into GML's structure to help connect the various existing geographic databases, whose relational structure XML schemas more easily define. The resulting XML-schema-based GML retains many features of RDF, including the idea of child elements as properties of the parent object (RDFS) and the use of remote property references. Profile[edit] GML profiles are logical restrictions to GML, and may be expressed by a document, an XML schema or both. These profiles are intended to simplify adoption of GML, to facilitate rapid adoption of the standard. The following profiles, as defined by the GML specification, have been published or proposed for public use: A Point Profile for applications with point geometric data but without the need for the full GML grammar; A GML Simple Features profile supporting vector feature requests and transactions, e.g. with a WFS; A GML profile for GMLJP2 (GML in JPEG 2000); A GML profile for RSS. Note that Profiles are distinct from application schemas. Profiles are part of GML namespaces (Open GIS GML) and define restricted subsets of GML. Application schemas are XML vocabularies defined using GML and which live in an application-defined target namespace. Application schemas can be built on specific GML profiles or use the full GML schema set. Profiles are often created in support for GML derived languages (see application schemas) created in support of particular application domains such as commercial aviation, nautical charting or resource exploitation. The GML Specification (Since GML v3.) contains a pair of XSLT scripts (usually referred to as the "subset tool") that can be used to construct GML profiles. GML Simple Features Profile[edit] The GML Simple Features Profile is a more complete profile of GML than the above Point Profile and supports a wide range of vector feature objects, including the following: A reduced geometry model allowing 0d, 1d and 2d linear geometric objects (all based on linear interpolation) and the corresponding aggregate geometries (gml:MultiPoint, gml:MultiCurve, etc.). A simplified feature model which can only be one level deep (in the general GML model, arbitrary nesting of features and feature properties is not permitted). All non-geometric properties must be XML Schema simple types – i.e. cannot contain nested elements. Remote property value references (xlink:href) just like in the main GML specification. Since the profile aims to provide a simple entry point, it does not provide support for the following: coverages topology observations value objects (for real time sensor data) dynamic features Nonetheless it supports a good variety of real world problems. Subset tool[edit] In addition, the GML specification provides a subset tool to generate GML profiles containing a user-specified list of components. The tool consists of three XSLT scripts. The scripts generate a profile that a developer may extend manually or otherwise enhance through schema restriction. Note that as restrictions of the full GML specification, application schemas that a profile can generate must themselves be valid GML application schemas. The subset tool can generate profiles for many other reasons as well. Listing the elements and attributes to include in the resultant profile schema and running the tool results in a single profile schema file containing only the user-specified items and all of the element, attribute and type declarations on which the specified items depend. Some Profile schemas created in this manner support other specifications including IHO S-57 and GML in JPEG 2000. Application schema[edit] In order to expose an application's geographic data with GML, a community or organization creates an XML schema specific to the application domain of interest (the application schema). This schema describes the object types whose data the community is interested in and which community applications must expose. For example, an application for tourism may define object types including monuments, places of interest, museums, road exits, and viewpoints in its application schema. Those object types in turn reference the primitive object types defined in the GML standard. A list of known publicly available GML Application Schemas is being assembled. Some other markup languages for geography use schema constructs, but GML builds on the existing XML schema model instead of creating a new schema language. GML and KML[edit] KML, made popular by Google, complements GML. Whereas GML is a language to encode geographic content for any application, by describing a spectrum of application objects and their properties (e.g. bridges, roads, buoys, vehicles etc.), KML is a language for the visualization of geographic information tailored for Google Earth. KML can be used to render GML content, and GML content can be “styled” using KML for the purposes of presentation. KML is first and foremost a 3D portrayal transport, not a data exchange transport. As a result of this significant difference in purpose, encoding GML content for portrayal using KML results in significant and unrecoverable loss of structure and identity in the resulting KML. Over 90% of GML's structures (such as, to name a few, metadata, coordinate reference systems, horizontal and vertical datums, geometric integrity of circles, ellipses, arcs, etc.) cannot be transformed to KML without loss or non-standard encoding. Similarly, due to KML's design as a portrayal transport, encoding KML content in GML will result in significant loss of KML portrayal structures such as regions, level of detail rules, viewing and animation information, as well as styling information and multiscale representation. The ability to portray placemarks at multiple levels of details distinguishes KML from GML, since portrayal is outside the scope of GML.[3] GML geometries[edit] GML encodes the GML geometries, or geometric characteristics, of geographic objects as elements within GML documents according to the "vector" model. The geometries of those objects may describe, for example, roads, rivers, and bridges. The key GML geometry object types in GML 1.0 and GML 2.0, are the following: Point LineString Polygon GML 3.0 and higher also includes structures to describe "coverage" information, the "raster" model, such as gathered via remote sensors and images, including most satellite data. Features[edit] GML defines features distinct from geometry objects. A feature is an application object that represents a physical entity, e.g. a building, a river, or a person. A feature may or may not have geometric aspects. A geometry object defines a location or region instead of a physical entity, and hence is different from a feature. In GML, a feature can have various geometry properties that describe geometric aspects or characteristics of the feature (e.g. the feature's Point or Extent properties). GML also provides the ability for features to share a geometry property with one another by using a remote property reference on the shared geometry property. Remote properties are a general feature of GML borrowed from RDF. An xlink:href attribute on a GML geometry property means that the value of the property is the resource referenced in the link. For example, a Building feature in a particular GML application schema might have a position given by the primitive GML geometry object type Point. However, the Building is a separate entity from the Point that defines its position. In addition, a feature may have several geometry properties (or none at all), for example an extent and a position. Coordinates[edit] Coordinates in GML represent the coordinates of geometry objects. Coordinates can be specified by any of the following GML elements: <gml:coordinates> <gml:pos> <gml:posList> GML has multiple ways to represent coordinates. For example, the <gml:coordinates> element can be used, as follows: <gml:Point gml:id="p21" srsName=""> <gml:coordinates>45.67, 88.56</gml:coordinates> </gml:Point> Note that, when expressed as above, the individual coordinates (e.g. 88.56) are not separately accessible through the XML Document Object Model since the content of the <gml:coordinates> element is just a single string. To make GML coordinates accessible through the XML DOM, GML 3.0 introduced the <gml:pos> and <gml:posList> elements. (Note that although GML versions 1 and 2 had the <gml:coord> element, it is treated as a defect and is not used.) Using the <gml:pos> element instead of the <gml:coordinates> element, the same point can be represented as follows: <gml:Point gml:id="p21" srsName=""> <gml:pos srsDimension="2">45.67 88.56</gml:pos> </gml:Point> The coordinates of a <gml:LineString> geometry object can be represented with the <gml:coordinates> element: <gml:LineString gml:id="p21" srsName=""> <gml:coordinates>45.67, 88.56 55.56,89.44</gml:coordinates> </gml:LineString > The <gml:posList> element is used to represent a list of coordinate tuples, as required for linear geometries: <gml:LineString gml:id="p21" srsName=""> <gml:posList srsDimension="2">45.67 88.56 55.56 89.44</gml:posList> </gml:LineString > For GML data servers (WFS) and conversion tools that only support GML 1 or GML 2 (i.e. only the <gml:coordinates> element), there is no alternative to <gml:coordinates>. For GML 3 documents and later, however, <gml:pos> and <gml:posList> are preferable to <gml:coordinates>. For more information on the srsName attribute, see coordinate reference system below. Coordinate reference system[edit] Main article: coordinate reference system A coordinate reference system (CRS) determines the geometry of each geometry element in a GML document. Unlike KML or GeoRSS, GML does not default to a coordinate system when none is provided. Instead, the desired coordinate system must be specified explicitly with a CRS. The elements whose coordinates are interpreted with respect to such a CRS include the following: <gml:coordinates> <gml:pos> <gml:posList> An srsName attribute attached to a geometry object specifies the object's CRS, as shown in the following example: <gml:Point gml:id="p1" srsName="#srs36"> <gml:coordinates>100,200</gml:coordinates> </gml:Point> The value of the srsName attribute is a Uniform Resource Identifier (URI). It refers to a definition of the CRS that is used to interpret the coordinates in the geometry. The CRS definition may be in a document (i.e. a flat file) or in an online web service. Values of EPSG codes can be resolved by using the CRS Registry Service operated by the Oil and Gas Producers Association (OGP at The srsName URI may also be a Uniform Resource Name (URN) for referencing a common CRS definition. The OGC has developed a URN structure and a set specific URNs to encode some common CRS. A URN resolver resolves those URNs to GML CRS definitions.

Examples[edit] Polygons, Points, and LineString objects are encoded in GML 1.0 and 2.0 as follows: <gml:Polygon> <gml:outerBoundaryIs> <gml:LinearRing> <gml:coordinates>0,0 100,0 100,100 0,100 0,0</gml:coordinates> </gml:LinearRing> </gml:outerBoundaryIs> </gml:Polygon> <gml:Point> <gml:coordinates>100,200</gml:coordinates> </gml:Point> <gml:LineString> <gml:coordinates>100,200 150,300</gml:coordinates> </gml:LineString> Note that LineString objects, along with LinearRing objects, assume linear interpolation between the specified points. Also the coordinates of a Polygon have to be closed. Features using geometries[edit] The following GML example illustrates the distinction between features and geometry objects. The Building feature has several geometry objects, sharing one of them (the Point with identifier p21) with the SurveyMonument feature: <abc:Building gml:id="SearsTower"> <abc:height>52</abc:height> <abc:position xlink:type="Simple" xlink:href="#p21"/> </abc:Building> <abc:SurveyMonument gml:id="g234"> <abc:position> <gml:Point gml:id="p21"> <gml:posList>100,200</gml:posList> </gml:Point> </abc:position> </abc:SurveyMonument> Note that the reference is to the shared Point and not to the SurveyMonument, since any feature object can have more than one geometry object property. Point Profile[edit] The GML Point Profile contains a single GML geometry, namely a <gml:Point> object type. Any XML Schema can use the Point Profile by importing it and referencing the subject <gml:Point> instance: <PhotoCollection xmlns="" xmlns:gml="" xmlns:xsi="" xsi:schemaLocation=" MyGoodPhotos.xsd"> <items> <Item> <name>Lynn Valley</name> <description>A shot of the falls from the suspension bridge</description> <where>North Vancouver</where> <position> <gml:Point srsDimension="2" srsName=""> <gml:pos>49.40 -123.26</gml:pos> </gml:Point> </position> </Item> </items> </PhotoCollection> Note that when using the Point Profile, the only geometry object is the '<gml:Point>' object. The rest of the geography is defined by the photo-collection schema.

History[edit] Initial Work - to OGC Recommendation Paper[edit] Ron Lake started work on GML in the fall of 1998, following earlier work on XML encodings for radio broadcasting. Lake presented his early ideas to an OGC meeting in Atlanta, Georgia, in February 1999, under the title xGML. This introduced the idea of a GeoDOM, and the notion of Geographic Styling Language (GSL) based on XSL. Akifumi Nakai of NTT Data also presented at the same meeting on work partly underway at NTT Data on an XML encoding called G-XML, which was targeted at location–based services.[4] In April 1999, Galdos created the XBed team (with CubeWerx, Oracle Corporation, MapInfo Corporation, NTT Data, Mitsubishi, and Compusult as subcontractors). Xbed was focused on the use of XML for geospatial. This led to the creation of SFXML (Simple Features XML) with input from Galdos, US Census, and NTT Data. Galdos demonstrated an early map style engine pulling data from an Oracle-based "GML" data server (precursor of the WFS) at the first OGC Web Map Test Bed in September 1999. In October 1999, Galdos Systems rewrote the SFXML draft document into a Request for Comment, and changed the name of the language to GML (Geography Markup Language). This document introduced several key ideas that became the foundation of GML, including the 1) Object-Property-Value rule, 2) Remote properties (via rdf:resource), and 3) the decision to use application schemas rather than a set of static schemas. The paper also proposed that the language be based on the Resource Description Framework (RDF) rather than on the DTDs used to that point. These issues, including the use of RDF, were hotly debated within the OGC community during 1999 and 2000, with the result that the final GML Recommendation Paper contained three GML profiles – two based on DTD, and one on RDF – with one of the DTD’s using a static schema approach. This passed as a Recommendation Paper at the OGC in May 2000.[5] Moving to XML Schema - Version 2.[edit] Even before the passage of the Recommendation Paper at the OGC, Galdos had started work on an XML Schema version of GML, replacing the rdf:resource scheme for remote references with the use of xlink:href, and developing specific patterns (e.g. Barbarians at the Gate) for handling extensions for complex structures like feature collections. Much of the XML Schema design work was done by Mr. Richard Martell of Galdos who served as the document editor and who was mainly responsible for the translation of the basic GML model into an XML Schema. Other important inputs in this time frame came from Simon Cox (CSIRO Australia), Paul Daisey (US Census), David Burggraf (Galdos), and Adrian Cuthbert (Laser-Scan). The US Army Corps of Engineers (particularly Jeff Harrison) were quite supportive of the development of GML. The US Army Corp of Engineers sponsored the “USL Pilot” project, which was very helpful in exploring the utility of linking and styling concepts in the GML specification, with important work being done by Monie (Ionic) and Xia Li (Galdos). The XML Schema specification draft was submitted by Galdos and was approved for public distribution in December 2000. It became a Recommendation Paper in February 2001 and an Adopted Specification in May of the same year. This version (V2.0) eliminated the “profiles” from version 1. and established the key principles, as outlined in the original Galdos submission, as the basis of GML. GML and G-XML (Japan)[edit] As these events were unfolding, work was continuing in parallel in Japan on G-XML under the auspices of the Japanese Database Promotion Center under the direction of Mr. Shige Kawano. G-XML and GML differed in several important respects. Targeted at LBS applications, G-XML employed many concrete geographic objects (e.g. Mover, POI), while GML provided a very limited concrete set and built more complex objects by the use of application schemas. At this point in time, G-XML was still written using a DTD, while GML had already transitioned to an XML Schema. On the one hand G-XML required the use of many fundamental constructs not at the time in the GML lexicon, including temporality, spatial references by identifiers, objects having histories, and the concept of topology-based styling. GML, on the other hand, offered a limited set of primitives (geometry, feature) and a recipe to construct user defined object (feature) types. A set of meetings held in Tokyo in January 2001, and involving Ron Lake (Galdos), Richard Martell (Galdos), OGC Staff (Kurt Buehler, David Schell), Mr. Shige Kawano (DPC), Mr. Akifumi Nakai (NTT Data) and Dr. Shimada (Hitachi CRL) led to the signing of an MOU between DPC and OGC by which OGC would endeavour to inject the fundamental elements required to support G-XML into GML, thus enabling G-XML to be written as a GML application schema. This resulted in many new types entering GML’s core object list, including observations, dynamic features, temporal objects, default styles, topology, and viewpoints. Much of the work was conducted by Galdos under contract to NTT Data. This laid the foundation for GML 3, although a significant new development occurred in this time frame, namely the intersection of the OGC and ISO/TC 211. Towards ISO - GML 3.0 broadens the scope of GML[edit] While a basic coding existed for most of the new objects introduced by the GML/G-XML agreement, and for some introduced by Galdos within the OGC process (notably coverages), it soon became apparent that few of these encodings were compliant with the abstract specifications developed by the ISO TC/211, specifications which were increasingly becoming the basis for all OGC specifications. GML geometry, for example, had been based on an earlier and only partly documented geometry model (Simple Features Geometry) and this was insufficient to support the more extensive and complex geometries described in TC/211. The management of GML development was also altered in this time frame with the participation of many more individuals. Significant contributions in this time frame were made by Milan Trninic (Galdos) (default styles, CRS), Ron Lake (Galdos) (Observations), Richard Martell (Galdos) (dynamic features). On June 12, 2002, Mr. Ron Lake was recognized by the OGC for his work in creating GML by being presented the Gardels award.[6] The citation on the award reads “In particular, this award recognizes your great achievement in creating the Geography Markup Language, (GML), and your uniquely sensitive and effective work to promote the reconciliation of national differences to promote meaningful standardization of GML on a global level.” Simon Cox (CSIRO)[7] and Clemens Portele (Interactive Instruments)[8] also subsequently received the Gardels award, in part for their contributions to GML.

Standards[edit] The Open Geospatial Consortium (OGC) is an international voluntary consensus standards organization whose members maintain the Geography Markup Language standard. The OGC coordinates with the ISO TC 211 standards organization to maintain consistency between OGC and ISO standards work. GML was adopted as an International Standard (ISO 19136:2007) in 2007. GML can[clarification needed] also be included in version 2.1 of the United States National Information Exchange Model (NIEM). ISO 19136[edit] ISO 19136 Geographic information – Geography Markup Language, is a standard from the family ISO - of the standards for geographic information (ISO 191xx). It resulted from unification of the Open Geospatial Consortium definitions and Geography Markup Language (GML) with the ISO-191xx standards. Earlier versions of GML were not ISO conformal (GML 1, GML 2) with GML version 3.1.1. ISO conformity means in particular that GML is now also an implementation of ISO 19107. The Geography Markup Language (GML) is an XML encoding in compliance with ISO 19118 for the transport and storage of geographic information modelled according to the conceptual modelling framework used in the ISO 19100-series and including both the spatial and nonspatial properties of geographic features. This specification defines the XML Schema syntax, mechanisms, and conventions that: Provide an open, vendor-neutral framework for the definition of geospatial application schemas and objects; Allow profiles that support proper subsets of GML framework descriptive capabilities; Support the description of geospatial application schemas for specialized domains and information communities; Enable the creation and maintenance of linked geographic application schemas and datasets; Support the storage and transport of application schemas and data sets; Increase the ability of organizations to share geographic application schemas and the information they describe.

See also[edit] GML Application Schemas CityGML Geographic Data Files (GDF) SOSI Well-known text ISO/TS 19103 – Conceptual Schema Language (units of measure, basic types), ISO 19108 – Temporal schema (temporal geometry and topology objects, temporal reference systems), ISO 19109 – Rules for application schemas (features), ISO 19111 – Spatial referencing by coordinates (coordinate reference systems), ISO 19123 – Coverages GeoSPARQL – GML for geospatially-linked data and the Semantic Web

References[edit] ^ Open Geospatial Consortium Inc. (2010-02-08), Technical Committee Policies and Procedures: MIME Media Types for GML (PDF)  ^ "OpenGIS Geography Markup Language (GML) Encoding Standard". Retrieved 2011-03-25.  ^ ^ "G-XML". Archived from the original on 2009-12-17.  ^ "GML in JPEG 2000 for Geographic Imagery (GMLJP2) Encoding Specification".  ^ award citation for Ron Lake ^ award citation for Simon Cox ^ award citation for Clemens Portele

External links[edit] ISO 19136:2007 - Geographic information -- Geography Markup Language (GML) GML specifications v t e Standards of the Open Geospatial Consortium (OGC) CSW GeoPackage GeoRSS GeoSPARQL GML KML O&M OGC Reference Model SensorML SOS SFA SLD SRID TransducerML TMS WaterML WCS WFS WMS WMTS WPS WRS v t e ISO standards by standard number List of ISO standards / ISO romanizations / IEC standards 1–9999 1 2 3 4 5 6 7 9 16 31 -0 -1 -2 -3 -4 -5 -6 -7 -8 -9 -10 -11 -12 -13 128 216 217 226 228 233 259 269 302 306 428 518 519 639 -1 -2 -3 -5 -6 646 690 732 764 843 898 965 1000 1004 1007 1073-1 1413 1538 1745 1989 2014 2015 2022 2047 2108 2145 2146 2240 2281 2709 2711 2788 2848 2852 3029 3103 3166 -1 -2 -3 3297 3307 3602 3864 3901 3977 4031 4157 4217 4909 5218 5428 5775 5776 5800 5964 6166 6344 6346 6385 6425 6429 6438 6523 6709 7001 7002 7098 7185 7200 7498 7736 7810 7811 7812 7813 7816 8000 8178 8217 8571 8583 8601 8632 8652 8691 8807 8820-5 8859 -1 -2 -3 -4 -5 -6 -7 -8 -8-I -9 -10 -11 -12 -13 -14 -15 -16 8879 9000/9001 9075 9126 9293 9241 9362 9407 9506 9529 9564 9594 9660 9897 9899 9945 9984 9985 9995 10000–19999 10005 10006 10007 10116 10118-3 10160 10161 10165 10179 10206 10218 10303 -11 -21 -22 -28 -238 10383 10487 10585 10589 10646 10664 10746 10861 10957 10962 10967 11073 11170 11179 11404 11544 11783 11784 11785 11801 11898 11940 (-2) 11941 11941 (TR) 11992 12006 12182 12207 12234-2 13211 -1 -2 13216 13250 13399 13406-2 13450 13485 13490 13567 13568 13584 13616 14000 14031 14224 14289 14396 14443 14496 -2 -3 -6 -10 -11 -12 -14 -17 -20 14644 14649 14651 14698 14750 14764 14882 14971 15022 15189 15288 15291 15292 15398 15408 15444 -3 15445 15438 15504 15511 15686 15693 15706 -2 15707 15897 15919 15924 15926 15926 WIP 15930 16023 16262 16612-2 16750 16949 (TS) 17024 17025 17100 17203 17369 17442 17799 18000 18004 18014 18245 18629 18916 19005 19011 19092 (-1 -2) 19114 19115 19125 19136 19439 19500 19501 19502 19503 19505 19506 19507 19508 19509 19510 19600:2014 19752 19757 19770 19775-1 19794-5 19831 20000+ 20000 20022 20121 20400 21000 21047 21500 21827:2002 22000 23270 23271 23360 24517 24613 24617 24707 25178 25964 26000 26300 26324 27000 series 27000 27001 27002 27006 27729 28000 29110 29148 29199-2 29500 30170 31000 32000 38500 40500 42010 55000 80000 -1 -2 -3 Category Retrieved from "" Categories: XML markup languagesIndustry-specific XML-based standardsGIS file formatsOpen Geospatial ConsortiumISO/TC 211ISO standardsHidden categories: Pages using deprecated image syntaxWikipedia articles needing clarification from November 2012

Navigation menu Personal tools Not logged inTalkContributionsCreate accountLog in Namespaces ArticleTalk Variants Views ReadEditView history More Search Navigation Main pageContentsFeatured contentCurrent eventsRandom articleDonate to WikipediaWikipedia store Interaction HelpAbout WikipediaCommunity portalRecent changesContact page Tools What links hereRelated changesUpload fileSpecial pagesPermanent linkPage informationWikidata itemCite this page Print/export Create a bookDownload as PDFPrintable version Languages DanskDeutschEspañolFrançaisItalianoNederlands日本語NorskPolskiPortuguêsSlovenčinaSlovenščinaSuomiTiếng Việt中文 Edit links This page was last edited on 21 January 2018, at 19:08. Text is available under the Creative Commons Attribution-ShareAlike License; additional terms may apply. By using this site, you agree to the Terms of Use and Privacy Policy. Wikipedia® is a registered trademark of the Wikimedia Foundation, Inc., a non-profit organization. Privacy policy About Wikipedia Disclaimers Contact Wikipedia Developers Cookie statement Mobile view (window.RLQ=window.RLQ||[]).push(function(){mw.config.set({"wgPageParseReport":{"limitreport":{"cputime":"0.220","walltime":"0.301","ppvisitednodes":{"value":1235,"limit":1000000},"ppgeneratednodes":{"value":0,"limit":1500000},"postexpandincludesize":{"value":58325,"limit":2097152},"templateargumentsize":{"value":2633,"limit":2097152},"expansiondepth":{"value":21,"limit":40},"expensivefunctioncount":{"value":1,"limit":500},"entityaccesscount":{"value":0,"limit":400},"timingprofile":["100.00% 203.231 1 -total"," 34.63% 70.370 1 Template:Infobox_file_format"," 29.89% 60.747 1 Template:Infobox"," 25.22% 51.254 1 Template:Reflist"," 19.45% 39.532 1 Template:Clarify"," 17.53% 35.631 1 Template:Fix-span"," 14.97% 30.415 1 Template:Citation"," 12.14% 24.671 1 Template:Longitem"," 10.26% 20.842 1 Template:Start_date_and_age"," 9.47% 19.248 2 Template:Navbox"]},"scribunto":{"limitreport-timeusage":{"value":"0.072","limit":"10.000"},"limitreport-memusage":{"value":3411929,"limit":52428800}},"cachereport":{"origin":"mw1252","timestamp":"20180218073156","ttl":1900800,"transientcontent":false}}});});(window.RLQ=window.RLQ||[]).push(function(){mw.config.set({"wgBackendResponseTime":83,"wgHostname":"mw1239"});});

ISO_19136 - Photos and All Basic Informations

ISO_19136 More Links

Filename ExtensionMedia TypeOpen Geospatial ConsortiumSoftware Release Life CycleGeographic Information SystemXMLInternational StandardXMLOpen Geospatial ConsortiumJPEG 2000Geometric PrimitiveGeospatial TopologyWorld Wide Web ConsortiumResource Description FrameworkXML Schema (W3C)XML Schema (W3C)Web Feature ServiceJpeg2000RSSNamespaceXSLTIHOIHOGML Application SchemasKeyhole Markup LanguageGoogle EarthCoordinate Reference SystemXMLDocument Object ModelWeb Feature ServiceCoordinate Reference SystemKeyhole Markup LanguageGeoRSSUniform Resource IdentifierUniform Resource NamePolygonPoint (geometry)XMLOpen Geospatial ConsortiumExtensible Stylesheet LanguageOracle CorporationMapInfo CorporationMitsubishiResource Description FrameworkDocument Type DefinitionXML Schema (W3C)ISO/TC 211Open Geospatial ConsortiumOpen Geospatial ConsortiumInternational Organization For StandardizationISO/TC 211Wikipedia:Please ClarifyUnited StatesNational Information Exchange ModelList Of ISO StandardsInternational Organization For StandardizationOpen Geospatial ConsortiumISO 19107ISO 19118ISO 19100-seriesXMLGML Application SchemasCityGMLGeographic Data FilesSOSIWell-known TextISO/TS 19103ISO 19108ISO 19109ISO 19111ISO 19123GeoSPARQLLinked DataSemantic WebTemplate:Open Geospatial Consortium StandardsTemplate Talk:Open Geospatial Consortium StandardsOpen Geospatial ConsortiumCatalog Service For The WebGeoPackageGeoRSSGeoSPARQLKeyhole Markup LanguageObservations And MeasurementsOGC Reference ModelSensorMLSensor Observation ServiceSimple Feature AccessStyled Layer DescriptorSRIDTransducerMLTile Map ServiceWaterMLWeb Coverage ServiceWeb Feature ServiceWeb Map ServiceWeb Map Tile ServiceWeb Processing ServiceWeb Registry ServiceTemplate:ISO StandardsTemplate Talk:ISO StandardsInternational Organization For StandardizationList Of International Organization For Standardization StandardsList Of ISO RomanizationsList Of IEC StandardsISO 1ISO 2Preferred NumberISO 4ISO 5ISO 6ISO 7ISO 9A440 (pitch Standard)ISO 31ISO 31-0ISO 31-1ISO 31-2ISO 31-3ISO 31-4ISO 31-5ISO 31-6ISO 31-7ISO 31-8ISO 31-9ISO 31-10ISO 31-11ISO 31-12ISO 31-13ISO 128ISO 216ISO 217ISO 226British Standard Pipe ThreadISO 233ISO 259EnvelopeKappa NumberVicat Softening PointISO 428ISO 518ISO 519ISO 639ISO 639-1ISO 639-2ISO 639-3ISO 639-5ISO 639-6ISO/IEC 646ISO 690ISO 732Antimagnetic WatchISO 843ISO 898ISO 965ISO 1000Magnetic Ink Character Recognition135 FilmOCR-A FontISO 1413ALGOL 60ISO 1745ISO 1989ISO 2014ISO 2015ISO/IEC 2022ISO 2047International Standard Book NumberISO 2145ISO 2146ISO 2240Water Resistant MarkISO 2709ISO 2711ISO 2788ISO 2848ISO 2852126 FilmISO 3103ISO 3166ISO 3166-1ISO 3166-2ISO 3166-3International Standard Serial NumberISO 3307Kunrei-shiki RomanizationISO 3864International Standard Recording CodeISO 3977ISO 4031ISO 4157ISO 4217ISO/IEC 4909ISO/IEC 5218ISO 5428ISO 5775ISO 5776ISO 5800ISO 5964ISO 6166ISO 6344ISO 6346ISO 6385Water Resistant MarkANSI Escape CodeISO 6438ISO 6523ISO 6709ISO 7001ISO 7002PinyinPascal (programming Language)ISO 7200OSI ModelISO 7736ISO/IEC 7810ISO/IEC 7811ISO/IEC 7812ISO/IEC 7813ISO/IEC 7816ISO 8000ISO 8178Fuel OilFTAMISO 8583ISO 8601Computer Graphics MetafileISO/IEC 8652ISO 8691Language Of Temporal Ordering SpecificationISO/IEC 8820-5ISO/IEC 8859ISO/IEC 8859-1ISO/IEC 8859-2ISO/IEC 8859-3ISO/IEC 8859-4ISO/IEC 8859-5ISO/IEC 8859-6ISO/IEC 8859-7ISO/IEC 8859-8ISO-8859-8-IISO/IEC 8859-9ISO/IEC 8859-10ISO/IEC 8859-11ISO/IEC 8859-12ISO/IEC 8859-13ISO/IEC 8859-14ISO/IEC 8859-15ISO/IEC 8859-16Standard Generalized Markup LanguageISO 9000SQLISO/IEC 9126File Allocation TableISO 9241ISO 9362Shoe SizeManufacturing Message SpecificationISO 9529ISO 9564X.500ISO 9660ISO 9897C (programming Language)POSIXISO 9984ISO 9985ISO/IEC 9995ISO 10005ISO 10006ISO 10007ISO/IEC 10116Whirlpool (cryptography)ISO 10160ISO 10161Guidelines For The Definition Of Managed ObjectsDocument Style Semantics And Specification LanguageISO 10206ISO 10218ISO 10303EXPRESS (data Modeling Language)ISO 10303-21ISO 10303-22ISO 10303-28STEP-NCISO 10383ISO 10487ArmSCIIIS-ISUniversal Coded Character SetTorxRM-ODPMultibusInternational Standard Music NumberISO 10962ISO/IEC 10967ISO/IEEE 11073ISO 11170ISO/IEC 11179ISO/IEC 11404JBIGISO 11783ISO 11784 & 11785ISO 11784 & 11785ISO/IEC 11801ISO 11898ISO 11940ISO 11940-2ISO/TR 11941ISO/TR 11941ISO 11992ISO 12006ISO/IEC TR 12182ISO/IEC 12207Tag Image File Format / Electronic PhotographyPrologPrologPrologIsofixTopic MapsISO 13399ISO 13406-2110 FilmISO 13485ISO 13490ISO 13567Z NotationISO 13584International Bank Account NumberISO 14000ISO 14031ISO 14224PDF/UAHorsepowerISO/IEC 14443MPEG-4MPEG-4 Part 2MPEG-4 Part 3Delivery Multimedia Integration FrameworkH.264/MPEG-4 AVCMPEG-4 Part 11MPEG-4 Part 12MPEG-4 Part 14MPEG-4 Part 14MPEG-4 Part 14ISO 14644STEP-NCISO 14651ISO 14698ISO 14750Software MaintenanceC++ISO 14971ISO 15022ISO 15189ISO/IEC 15288Ada Semantic Interface SpecificationISO 15292ISO 15398Common CriteriaJPEG 2000Motion JPEG 2000HTMLPDF417ISO/IEC 15504International Standard Identifier For Libraries And Related OrganizationsISO 15686ISO/IEC 15693International Standard Audiovisual NumberISO 15706-2International Standard Musical Work CodeISO 15897ISO 15919ISO 15924ISO 15926ISO 15926 WIPPDF/XMaxiCodeECMAScriptPDF/VTISO 16750ISO/TS 16949ISO/IEC 17024ISO/IEC 17025ISO 17100:2015Open Virtualization FormatSDMXLegal Entity IdentifierISO/IEC 27002ISO/IEC 18000QR CodeISO/IEC 18014ISO 18245Process Specification LanguagePhotographic Activity TestPDF/AISO 19011ISO 19092-1ISO 19092-2ISO 19114ISO 19115Simple Feature AccessISO 19136ISO 19439Common Object Request Broker ArchitectureUnified Modeling LanguageMeta-Object FacilityXML Metadata InterchangeUnified Modeling LanguageKnowledge Discovery MetamodelObject Constraint LanguageMeta-Object FacilityXML Metadata InterchangeBusiness Process Model And NotationISO 19600:2014ISO/IEC 19752RELAX NGISO/IEC 19770X3DISO/IEC 19794-5Cloud Infrastructure Management InterfaceISO/IEC 20000ISO 20022ISO 20121ISO 20400MPEG-21International Standard Text CodeISO 21500ISO/IEC 21827ISO 22000C Sharp (programming Language)Common Language InfrastructureLinux Standard BasePDF/ELexical Markup FrameworkISO-TimeMLCommon LogicISO 25178ISO 25964ISO 26000OpenDocumentDigital Object IdentifierISO/IEC 27000-seriesISO/IEC 27000ISO/IEC 27001ISO/IEC 27002ISO/IEC 27006International Standard Name IdentifierISO 28000ISO 29110Requirements EngineeringJPEG XROffice Open XMLRuby (programming Language)ISO 31000Portable Document FormatISO/IEC 38500Web Content Accessibility GuidelinesISO/IEC 42010ISO 55000ISO/IEC 80000ISO 80000-1ISO 80000-2ISO 80000-3Category:ISO StandardsHelp:CategoryCategory:XML Markup LanguagesCategory:Industry-specific XML-based StandardsCategory:GIS File FormatsCategory:Open Geospatial ConsortiumCategory:ISO/TC 211Category:ISO StandardsCategory:Pages Using Deprecated Image SyntaxCategory:Wikipedia Articles Needing Clarification From November 2012Discussion About Edits From This IP Address [n]A List Of Edits Made From This IP Address [y]View The Content Page [c]Discussion About The Content Page [t]Edit This Page [e]Visit The Main Page [z]Guides To Browsing WikipediaFeatured Content – The Best Of WikipediaFind Background Information On Current EventsLoad A Random Article [x]Guidance On How To Use And Edit WikipediaFind Out About WikipediaAbout The Project, What You Can Do, Where To Find ThingsA List Of Recent Changes In The Wiki [r]List Of All English Wikipedia Pages Containing Links To This Page [j]Recent Changes In Pages Linked From This Page [k]Upload Files [u]A List Of All Special Pages [q]Wikipedia:AboutWikipedia:General Disclaimer

view link view link view link view link view link