XOMGL

Last updated

XOMGL (eXtensible Open Municipal Geodata Language) is an XML-based open standard for the exchange of large amounts of government data between a municipal agency and regular citizens and developers creating web-based mapping applications. It is part of the OMG Standard, which seeks to promote the free flow of information between government agencies and citizens by establishing a common set of technical standards for organizing and sharing public data. [1]

Contents

Types of data

The XOMGL format is good for organizing and distributing digitally many types of government data, including crime, building permits, restaurant health reviews, pollution sources, political contributions, property values, traffic accidents, sex offenders, and historic sites.

Fields

It has just enough required fields to allow easy updates and the plotting of data on online maps. It also has enough optional data to allow categorization, filtering, date ranges, images, external links, and latitude and longitude. It provides all of this without overwhelming the end user, providing too much irrelevant data, and displays in an easy to read and manage format.

Usage examples

A government agency would make data available on its website with either static links to files in this format, or queryable versions that allow users to filter the data by last updated date, date range, category, etc.

The XML and JSON versions can be used to automate data importing into web-based software applications, while the CSV version allows regular people to browse, filter, sort, edit, and re-purpose the information with only spreadsheet software knowledge.

Formats vs. Standards

Note there is a distinction between data standards and data formats. A data format like KML, GeoRSS, JSON, XML, CSV, and others describe how to format data to make it machine readable by specific applications. A data standard defines which fields/columns are needed to make raw data usable in these formats. Information in the XOMGL standard can be machine-output to any of the above listed data formats. [2]

Example XOMGL format

<?xml version="1.0" encoding="utf-8"?><datasetname=""><!-- * name:string - name of the dataset --><metadata><!-- * metadata about the dataset --><sourcename><!-- * string: name of the source of the data --></sourcename><sourceurl><!-- string: full path to the page that has the source data --></sourceurl><sourcecity><!-- string: name of the originating city --></sourcecity><sourcestateid><!-- int: id of the originating state --></sourcestateid><sourcecountryid><!-- int: id of the originating country --></sourcecountryid><description><!-- string: text description of source of the data --></description><updatefrequency><!-- string: frequency of data updates, daily, monthly, weekly, etc --></updatefrequency><lastupdated><!-- datetime: stamp of last update to this dataset --></lastupdated><startdatetime><!-- datetime: earliest date of data coverage --></startdatetime><enddatetime><!-- datetime: latest date of data coverage --></enddatetime></metadata><locationdata><!-- * location-based information --><centercity><!-- string: name of the city of the data center --></centercity><centerstateid><!-- int: id of the state of the data center --></centerstateid><centercountryid><!-- int: id of the country of the data center --></centercountryid><centerlatitude><!-- float: latitude of center --></centerlatitude><centerlongitude><!-- float: longitude of center --></centerlongitude><coveragecity><!-- string: city of the dataset coverage area. Leave out if coverage area is greater --></coveragecity><coveragestateid><!-- int: id of the state of the dataset coverage area. Leave out if coverage area is greater --></coveragestateid><coveragecountryid><!-- * int: id of the country of the dataset coverage area. --></coveragecountryid><minlatitude><!-- float: based on data coverage area --></minlatitude><maxlatitude><!-- float: based on data coverage area --></maxlatitude><minlongitude><!-- float: based on data coverage area --></minlongitude><maxlongitude><!-- float: based on data coverage area --></maxlongitude></locationdata><itemdata><!-- data concerning all items --><externalurl><!-- full path to more info with [ExternalID] in place of item->id in a url --></externalurl></itemdata><item><!-- * one item of data. there can be many of these --><id><!-- * string: unique id of this item based on internal system id. used for updating data later --></id><name><!-- * string: name of the item --></name><description><!-- string: html formatted or plain text full description of item --></description><categories><!-- one or more categories the item can be classified as. id links to other xml formatted data that shows category name--><categoryid><!-- int: id of categorization of item. --></categoryid></categories><location><!-- string: full text string of location. this can be used instead of address, city, state, zip --></location><address><!-- string: street address with house number --></address><address2><!-- string: more detailed street address info or location description --></address2><city><!-- string: city of item location --></city><state><!-- string: state of item location --></state><zip><!-- string: zip code of item location --></zip><date><!-- date: date associated with item --></date><latitude><!-- float: latitude of item location --></latitude><longitude><!-- float: longitude of item location --></longitude><fullurl><!-- string: full path to more information about this item --></fullurl><imagepath><!-- string: full path to location of image on a server --></imagepath><detaillink><!-- boolean: if true, will us item->id to link to another XML dataset with full details --></detaillink></item></dataset>

Related Research Articles

Geography Markup Language used to describe geographical features

The Geography Markup Language (GML) is the XML grammar defined by the Open Geospatial Consortium (OGC) to express geographical features. GML serves as a modeling language for geographic systems as well as an open interchange format for geographic transactions on the Internet. Key to GML's utility is its ability to integrate all forms of geographic information, including not only conventional "vector" or discrete objects, but coverages and sensor data.

ISO 6709 International standard for representation of geographic location

ISO 6709Standard representation of geographic point location by coordinates is the international standard for representation of latitude, longitude and altitude for geographic point locations.

SDXF is a data serialization format defined by RFC 3072. It allows arbitrary structured data of different types to be assembled in one file for exchanging between arbitrary computers.

The PBCore metadata standard was created by the public broadcasting community in the United States of America for use by public broadcasters and related communities that manage audiovisual assets, including libraries, archives, independent producers, etc. PBCore is organized as a set of specified fields that can be used in database applications, and it can be used as a data model for media cataloging and asset management systems. As an XML schema, PBCore enables data exchange between media collections, systems and organizations.

Geotagging Act of associating geographic coordinates to digital media

Geotagging, or GeoTagging, is the process of adding geographical identification metadata to various media such as a geotagged photograph or video, websites, SMS messages, QR Codes or RSS feeds and is a form of geospatial metadata. This data usually consists of latitude and longitude coordinates, though they can also include altitude, bearing, distance, accuracy data, and place names, and perhaps a time stamp.

Geocoding is the process of taking input text, such as an address or the name of a place, and returning a latitude/longitude location on the Earth's surface for that place. Reverse geocoding, on the other hand, converts geographic coordinates to a description of a location, usually the name of a place or an addressable location. Geocoding relies on a computer representation of address points, the street / road network, together with postal and administrative boundaries.

Learning object metadata Data model

Learning Object Metadata is a data model, usually encoded in XML, used to describe a learning object and similar digital resources used to support learning. The purpose of learning object metadata is to support the reusability of learning objects, to aid discoverability, and to facilitate their interoperability, usually in the context of online learning management systems (LMS).

Shapefile package of file formats which together define geographic features

The shapefile format is a geospatial vector data format for geographic information system (GIS) software. It is developed and regulated by Esri as a mostly open specification for data interoperability among Esri and other GIS software products. The shapefile format can spatially describe vector features: points, lines, and polygons, representing, for example, water wells, rivers, and lakes. Each item usually has attributes that describe it, such as name or temperature.

Entity–attribute–value model (EAV) is a data model to encode, in a space-efficient manner, entities where the number of attributes that can be used to describe them is potentially vast, but the number that will actually apply to a given entity is relatively modest. Such entities correspond to the mathematical notion of a sparse matrix.

The Metadata Object Description Schema (MODS) is an XML-based bibliographic description schema developed by the United States Library of Congress' Network Development and Standards Office. MODS was designed as a compromise between the complexity of the MARC format used by libraries and the extreme simplicity of Dublin Core metadata.

GeoRSS is a specification for encoding location as part of a Web feed. (Web feeds are used to describe feeds of content, such as news articles, Audio blogs, video blogs and text blog entries. These web feeds are rendered by programs such as aggregators and web browsers.) The name "GeoRSS" is derived from RSS, the most known Web feed and syndication format.

C-squares is a system of spatially unique, location-based identifiers (geocodes) for areas on the surface of the earth, represented as cells from a Discrete Global Grid at a hierarchical set of resolution steps. The identifiers incorporate literal values of latitude and longitude in an interleaved notation, together with additional digits that support intermediate grid resolutions of 5, 0.5, 0.05 degrees, etc. The system was initially designed to represent data "footprints" or spatial extents in a more flexible manner than a standard minimum bounding rectangle, and to support "lightweight", text-based spatial querying; it can also provide a set of identifiers for grid cells used for assembly, storage and analysis of spatially organised data. Dataset extents expressed in c-squares notation can be visualised using a web-based utility, the c-squares mapper, an online instance of which is currently provided by CSIRO Oceans and Atmosphere in Australia. C-squares codes and associated published software are free to use and the software is released under version 2 of the GNU General Public License (GPL), a licence of the Free Software Foundation.

The Open Packaging Conventions (OPC) is a container-file technology initially created by Microsoft to store a combination of XML and non-XML files that together form a single entity such as an Open XML Paper Specification (OpenXPS) document. OPC-based file formats combine the advantages of leaving the independent file entities embedded in the document intact and resulting in much smaller files compared to normal use of XML.

A document-oriented database, or document store, is a computer program designed for storing, retrieving and managing document-oriented information, also known as semi-structured data.

The FAO geopolitical ontology is an ontology developed by the Food and Agriculture Organization of the United Nations (FAO) to describe, manage and exchange data related to geopolitical entities such as countries, territories, regions and other similar areas.

EMML, or Enterprise Mashup Markup Language, is an XML markup language for creating enterprise mashups, which are software applications that consume and mash data from variety of sources, often performing logical or mathematical operations as well as presenting data. Mashed data produced by enterprise mashups are presented in graphical user interfaces as mashlets, widgets, or gadgets. EMML can also be considered a declarative mashup domain-specific language (DSL). A mashup DSL eliminates the need for complex, time-consuming, and repeatable procedural programming logic to create enterprise mashups. EMML also provides a declarative language for creating visual tools for enterprise mashups.

In computing, Open Data Protocol (OData) is an open protocol which allows the creation and consumption of queryable and interoperable RESTful APIs in a simple and standard way. Microsoft initiated OData in 2007. Versions 1.0, 2.0, and 3.0 are released under the Microsoft Open Specification Promise. Version 4.0 was standardized at OASIS, with a release in March 2014. In April 2015 OASIS submitted OData v4 and OData JSON Format v4 to ISO/IEC JTC 1 for approval as an international standard.

Additive manufacturing file format (AMF) is an open standard for describing objects for additive manufacturing processes such as 3D printing. The official ISO/ASTM 52915:2016 standard is an XML-based format designed to allow any computer-aided design software to describe the shape and composition of any 3D object to be fabricated on any 3D printer. Unlike its predecessor STL format, AMF has native support for color, materials, lattices, and constellations.

References

  1. "Open Municipal Geodata Standard Website". OMG Standard. 2008-03-01. Retrieved 2008-07-24.
  2. "OMG Standard Technical Specifications". OMG Standard. 2008-03-01. Retrieved 2008-07-24.