UseCases/SDWUseCasesAndRequirements.html

<!DOCTYPE html>
<html lang="en" dir="ltr" typeof="bibo:Document " prefix="bibo: http://purl.org/ontology/bibo/ w3p: http://www.w3.org/2001/02pd/rec54#">
<head>
  <meta charset="utf-8" />
  <meta lang="en" property="dc:language" content="en" />
  <meta name="viewport" content="width=device-width, initial-scale=1, shrink-to-fit=no" />
  <title>Spatial Data on the Web Use Cases &amp; Requirements</title>
  <script src='https://www.w3.org/Tools/respec/respec-w3c-common' async class='remove'></script>
  <style type="text/css">
  .contributor:before {
    content: "Contributed by: ";
    font-weight: bold;
  }
  .relatedDeliverables:before {
    content: "Related deliverables: ";
    font-weight: bold;
  }
  .relatedRequirements:before {
    content: "Related requirements: ";
    font-weight: bold;
  }
  .relatedUseCases:before {
    content: "Related use cases: ";
    font-weight: bold;
  }
  .hidden {
    display: none;
  }
  .visible {
    display: block;
  }
  .toggleVis {
    text-decoration: none;
    font-weight: bold;
  }
  .expandOrCollapse {
    font-weight: bold;
  }
  </style> 
  <script type="text/javascript">
    // This is the script that hides/shows the full descriptions of the use cases
    // The default is visible so that they're accessible without scripting
    // Init makes them all hidden and writes in the toggle link

//    window.onload = init;

    function init() {
	    var divs = document.getElementsByTagName("div");
      for (var i = 0; i < divs.length - 1; i++ ) {
        if ((divs[i+1]) && (divs[i+1].className=='visible')) {
          divs[i+1].className = 'hidden';
	 				divs[i].innerHTML = '&#9654; Full use case description (click to expand):';
        }
      }
    }

    // And here's the toggle function

		function toggleVisibility(elem) {	// expand or collapse the next div
			var divs = document.getElementsByTagName("div");
			for(var i = 0; i < divs.length;i++) // find the next div element
				if(divs[i] == elem) {
					var item = divs[i + 1];
				}
			if (item) {
				if (item.className=='hidden') {
					item.className = 'visible';
					elem.innerHTML = '&#9650; Full use case description (click to collapse):';
				}	else {
					item.className = 'hidden';
					elem.innerHTML = '&#9654; Full use case description (click to expand):';
				}
			}
		}

  </script>
  <script class='remove'>
    var respecConfig = {
      specStatus: "ED",
      shortName: "sdw-ucr",
      publishDate:  "2016-10-10",
      previousPublishDate: "2015-12-17",
      previousMaturity: "NOTE",
//      previousURI: "http://www.w3.org/TR/2015/NOTE-sdw-ucr-20150723/",
      edDraftURI: "http://w3c.github.io/sdw/UseCases/SDWUseCasesAndRequirements.html",
      // lcEnd: "3000-01-01",
      // crEnd: "3000-01-01",
      editors: [
      {
        name: "Frans Knibbe",
        company: "Geodan",
        companyURL: "http://www.geodan.com/"
      },
      {
        name: "Alejandro Llaves",
        company: "OEG, Universidad Polit&eacute;cnica de Madrid",
        companyURL: "http://www.oeg-upm.net/"
      }],
      wg: "Spatial Data on the Web Working Group",
      wgURI: "http://www.w3.org/2015/spatial/",
      wgPublicList: "public-sdw-wg",
      wgPatentURI: "http://www.w3.org/2004/01/pp-impl/75471/status",
      inlineCSS: true,
      issueBase: "https://www.w3.org/2015/spatial/track/issues/",
      noIDLIn: true,
      noLegacyStyle: false,
      logos: [
      {
        src: "http://www.w3.org/Icons/w3c_home",
        alt: "W3C",
        height: "48",
        width: "72",
        url: "http://www.w3.org/"
      },
      {
        src: "http://www.w3.org/2015/01/ogc_logo.jpg",
        alt: "OGC",
        height: "48",
        width: "115",
        url: "http://www.opengeospatial.org/"
      }
      ],
      otherLinks: [{
      key: "OGC Document Number",
        data: [{
          value: "OGC 15-074 R1"
            }]
      }, {
      key: "Repository",
        data: [{
          value: "We are on GitHub",
          href: "https://github.com/w3c/sdw"
            }]
      }, {
      key: "Changes",
        data: [{
          value: "Change log",
          href: "#ChangeHistory"
        }, {
          value: "Diff to previous version",
          href: "diff-20151217.html"
        }, {
          value: "Commit history",
           href: "https://github.com/w3c/sdw/commits/gh-pages/UseCases"
       }]
      
    }],
      noRecTrack: true,
      overrideCopyright: "<p class='copyright'><a href='http://www.w3.org/Consortium/Legal/ipr-notice#Copyright'>Copyright</a> &copy; 2015 <a href='http://www.opengeospatial.org/'>OGC</a> &amp; <a href='http://www.w3.org/'> <abbr title='World Wide Web Consortium'>W3C</abbr> </a><sup>&reg;</sup> (<a href='http://www.csail.mit.edu/'><abbr title='Massachusetts Institute of Technology'>MIT</abbr></a>, <a href='http://www.ercim.eu/'><abbr title='European Research Consortium for Informatics and Mathematics'>ERCIM</abbr></a>, <a href='http://www.keio.ac.jp/'>Keio</a>, <a href='http://ev.buaa.edu.cn/'>Beihang</a>), <abbr title='World Wide Web Consortium'>W3C</abbr> <a href='http://www.w3.org/Consortium/Legal/ipr-notice#Legal_Disclaimer'>liability</a>, <a href='http://www.w3.org/Consortium/Legal/ipr-notice#W3C_Trademarks'>trademark</a> and <a href='http://www.w3.org/Consortium/Legal/copyright-documents'>document use</a> rules apply.</p>"
    };
  </script>

  <body>
    <section id='abstract'>
      <p>
        This document describes use cases that demand a combination of geospatial and non-geospatial
        data sources and techniques. It underpins the collaborative work of the 
        <a href="http://www.w3.org/2015/spatial/">Spatial Data on the Web Working Group</a>s operated
        by both <a href="http://www.w3.org/">W3C</a> and <a href="http://www.opengeospatial.org/">OGC</a>. 
      </p>
    </section>
    <section id='sotd'>
      <p><strong>For OGC</strong> This is a Public Draft of a document prepared by the Spatial Data on the Web Working Group (SDWWG) - a joint W3C-OGC project (see <a href="https://portal.opengeospatial.org/files/61610">charter</a>). The document is prepared following W3C conventions. The document is released at this time to solicit public comment. </p>
    </section>
    <section>
      <h2>Introduction</h2>
      <p>
        The mission of the <a href="http://www.w3.org/2015/spatial/">Spatial Data on the Web Working Group</a>, as described in its <a href="http://www.w3.org/2015/spatial/charter">charter</a>, is to clarify and to formalize standards on spatial data on the Web. In particular:</p>
        <ol>
        <li>to determine how spatial information can best be integrated with other data on the Web;</li>
        <li>to determine how machines and people can discover that different facts in different datasets relate to the same place, especially when 'place' is expressed in different ways and at different levels of granularity;</li>
        <li>to identify and assess existing methods and tools and then create a set of best practices for their use;</li>
        <li>where desirable, to complete the standardization of informal technologies already in widespread use.</li>
        </ol>
        <p>This document describes the results of the first steps of working towards these goals. Members of the Working Group and other stakeholders have come up with a number of <a href="#UseCases">use cases</a> that describe how spatial data on the Web could work. From these use cases, a number of <a href="#Requirements">requirements</a> for further work are derived. In this document, use cases, requirements and their relationships are described. Requirements and use cases are also related to the <a href="#Deliverables">deliverables</a> of the Working Group.</p>
      <p>The requirements described in this document will be the basis for development of the other four deliverables of the Working Group.</p>
    </section>

    <section id="Deliverables">
      <h2>Deliverables</h2>
      <p>The deliverables of this Working Group are described in the <a href="http://www.w3.org/2015/spatial/charter">Working Group Charter</a>. For convenience those deliverables are replicated in this chapter. The charter remains the authoritative source of the definition of deliverables.</p>
      <section id="UseCasesAndRequirements">
        <h3>Use Cases and Requirements</h3>
        <p>A document setting out the range of problems that the Working Groups are trying to solve (this document).</p>
      </section>
      <section id="BestPractices">
        <h3>Spatial Data on the Web Best Practices</h3>
        <p>This will include:</p>
        <ul>
        <li>an agreed spatial ontology conformant to the ISO 19107 abstract model and based on existing available ontologies such as GeoSPARQL, NeoGeo and the ISA Core Location vocabulary;</li>
        <li>advice on use of URIs as identifiers in geographic information systems;</li>
        <li>advice on providing different levels of metadata for different usage scenarios (from broad sweep metadata to metadata about individual coordinates in a polygon);</li>
        <li>develop advice on, or possibly define, RESTful APIs to return data in a variety of formats including those defined elsewhere, such as GeoJSON, GeoJSON-LD and TopoJSON.</li>
        </ul>
      </section>
      <section id="TimeOntologyInOWL">
        <h3>Time Ontology in OWL</h3>
        <p>The WG will work with the authors of the existing Time Ontology in OWL to complete the development of this widely used ontology through to Recommendation status. Further requirements already identified in the geospatial community will be taken into account.</p>
      </section>
      <section id="SSN">
        <h3>Semantic Sensor Network Vocabulary</h3>
        <p>The WG will work with the members of the former Semantic Sensor Network Incubator Group to develop its ontology into a formal Recommendation, noting the work to split the ontology into smaller sections to offer simplified access.</p>
      </section>
      <section id="CoverageInLinkedData">
        <h3>Coverage in Linked Data</h3>
        <p>The WG will develop a formal Recommendation for expressing discrete coverage data conformant to the ISO 19123 abstract model. Existing standard and de facto ontologies will be examined for applicability; these will include the RDF Data Cube. The Recommendation will include provision for describing the subset of coverages that are simple timeseries datasets - where a time-varying property is measured at a fixed location. OGC's WaterML 2 Part 1 - Timeseries will be used as an initial basis.</p>
        <p>Given that coverage data can often be extremely large in size, publication of the individual data points as Linked Data may not always be appropriate. The Recommendation will include provision for describing an entire coverage dataset and subsets thereof published in more compact formats using Linked Data. For example where a third party wishes to annotate a subset of a large coverage dataset or a data provider wishes to publish a large coverage dataset in smaller subsets to support convenient reuse.</p>
        <div class="note">
          <p>The OGC is currently working on refinements of ISO 19123 (in particular, the OGC Coverage Implementation Schema 1.1), which could result in specifications that allow a higher level of interoperability of implementations. The Working Group will also consider these forthcoming standards.</p>
       </div>
      </section>
    </section>

    <section id="Methodology">
      <h2>Methodology</h2>
      <p>In order to find out the requirements for the deliverables of the Working Group, use cases were collected. For the purpose of the Working Group, a use case is a story that describes challenges with respect to spatial data on the Web for existing or envisaged information systems. It does not  need to adhere to certain standardized format. Use cases are primarily used as a source of requirements, but a use case could be revisited near the time the work of the Working Group will reach completion, to demonstrate that it is now possible to make the use case work.</p> 
      <p>The Working Group has derived requirements from the collected use cases. A requirement is something that needs to be achieved by one or more deliverables and is phrased as a specification of functionality. Requirements can lead to one or more tests that can prove whether the requirement is met.</p>
      <p>Care was taken to only derive requirements that are considered to in scope for the further work of the Working Group. The scope of the Working Group is determined by the <a href="http://www.w3.org/2015/spatial/charter">charter</a>. To help keeping the requirements in scope, the following questions were applied:</p>
      <ol>
      <li>Is the requirement specifically about spatial data on the Web?</li>
      <li>Is the use case including data published, reused, and accessible via Web technologies?</li>
      <li>Has a use case a description that can lead to a testable requirement?</li>
      </ol>
    </section>

    <section id="UseCases">
      <!--A HTML template for use cases can be found at the end of this section -->
      <h2>Use Cases</h2>
        <p>Use cases that describe current problems or future opportunities for spatial data on the Web have been gathered as a first activity of the Working Group. They were mainly contributed by members of Working Group, but there were also contributions from other interested parties. In this chapter these use cases are listed and identified. Each use case is related to one or more Working Group <a href="#Deliverables">deliverables</a> and to one or more <a href="#Requirements">requirements</a> for future deliverables.</p>
        <section id="MeteorologicalDataRescue">
          <h3>Meteorological data rescue</h3>
          <p class="contributor">Chris Little, based on scenarios used for the WMO infrastructure requirements.</p>
          <div class="expandOrCollapse" onclick="toggleVisibility(this)">&#9654; Full use case description (click to expand):</div>
          <div class="visible">
          <p>This is really one of several future, but realistic, meteorological scenarios to aim at.</p>
          <p>National Hydro-Meteorological Services around the world are coordinated via the WMO (World Meteorological Organization), part of the United Nations system. WMO has the same status as ISO, and its standards and regulatory materials applies to all its 193 national meteorological services and are available in the six working languages ( &#1593;&#1585;&#1576;&#1610; | &#20013;&#25991; | Fr | Ru | Es | En). WMO has embarked on a long-term (think a decade or so) program to update the global meteorological operational infrastructure. This is known as the WIS (WMO Information System). The global infrastructure also has aviation, oceanographic, seismic and other users. The WIS includes a global, federated, synchronized, geospatial catalog, envisaged to encompass all hydro-meteorological data and services. Currently several nodes are operational, cataloging mainly routinely exchanged observations and forecasts.</p>
          <p>Envisage an environmental scientist in Cambodia, researching the impact of deforestation in Vietnam as part of investigating the regional impacts of climate change. She submits her search keywords, in Cambodian, and receives responses indicating there is some data from the 1950s, printed in a 1960 pamphlet, in the Biblioth&egrave;que Nationale, a library in Paris, France, in French. She receives an abstract of some form that enables her to decide that the data are worth accessing, and initiates a request for a digital copy to be sent.</p>
          <p>She receives the pamphlet as a scanned image of each page, and she decides that the quantitative information in the paper is useful, so she arranges transcription of the tabular numerical data and their summary values into a digital form and publishes the dataset, with a persistent identifier, and links it to a detailed coverage extent, the original paper source, the scanned pages and her paper when it is published. She also incorporates scanned charts and graphs from the original pamphlet into her paper. Her organization creates a catalog record for her research paper dataset and publishes it in the WIS global catalog, which makes it also visible to the GEO System of Systems broker portal.</p>
          </div>
          <p class="relatedDeliverables"><a href="#BestPractices"></a>, <a href="#TimeOntologyInOWL"></a>, <a href="#SSN"></a>, <a href="#CoverageInLinkedData"></a></p>
          <p class="relatedRequirements"><a href="#SpatialMetadata"></a>, <a href="#CoverageTemporalExtent"></a>, <a href="#CRSDefinition"></a>, <a href="#DateTimeDuration"></a>, <a href="#DifferentTimeModels"></a>, <a href="#Discoverability"></a>, <a href="#GeoreferencedData"></a>, <a href="#Linkability"></a>, <a href="#MultilingualSupport"></a>, <a href="#NominalTemporalReferences"></a>, <a href="#ObservedPropertyInCoverage"></a>, <a href="#Provenance"></a>, <a href="#QualityPerSample"></a>, <a href="#ReferenceDataChunks"></a>, <a href="#SensingProcedure"></a>, <a href="#SensorMetadata"></a>, <a href="#SpaceTimeMultiScale"></a>, <a href="#SpatialVagueness"></a>, <a href="#TemporalReferenceSystem"></a>, <a href="#UncertaintyInObservations"></a>, <a href="#Crawlability"></a></p>
        </section>
        <section id="HabitatZoneVerification">
          <h3>Habitat zone verification for designation of Marine Conservation Zones</h3>
          <p class="contributor">Jeremy Tandy</p>
          <div class="expandOrCollapse" onclick="toggleVisibility(this)">&#9654; Full use case description (click to expand):</div>
          <div class="visible">
            <p>The <a href="http://jncc.defra.gov.uk/page-5230">Marine and Coastal Access Act 2009</a> allows for the creation of a type of Marine Protected Area (MPA), called a Marine Conservation Zone (MCZ). MCZs protect a range of nationally important marine wildlife, habitats, geology and geomorphology and can be designated anywhere in English and Welsh inshore and UK offshore waters.</p>
            <p>The designation of a MCZ is dependent on a detailed analysis of the marine environment which results in the definition of geometric areas where a given habitat type is deemed to occur and is published as a habitat map.</p>
            <p>Being a policy statement, it is important to be able to express the provenance of information that was used to compile the habitat map. Moreover, because the marine environment is always changing, it is important to express the time at which this information was collected.</p>
            <p>The information includes:</p>
            <ul>
              <li>acoustic survey</li>
              <li>video (from a video camera towed behind a survey boat)</li>
              <li>biota observations (based on what is observed in the video and from physical collection)</li>
              <li>particle size (sand/mud)</li>
              <li>water column data</li>
              <li>seabed character map: discrete seabed features and backscatter information (from sonar) to determine bottom type</li>
            </ul>
            <p>These information types are varied in type and size. In particular, the acoustic survey (e.g. side-scan sonar) is difficult to manage as these survey results can be many gigabytes in size and cover large areas. A way is needed to refer to just a small part of these coverage data sets that are relevant to a particular habitat zone analysis.</p>
          </div>
          <p class="relatedDeliverables"><a href="#BestPractices"></a>, <a href="#TimeOntologyInOWL"></a>, <a href="#SSN"></a>, <a href="#CoverageInLinkedData"></a></p>
          <p class="relatedRequirements"><a href="#GeoreferencedData"></a>, <a href="#IdentifyCoverageType"></a>, <a href="#Provenance"></a>, <a href="#ReferenceDataChunks"></a>, <a href="#SensorMetadata"></a>, <a href="#CRSDefinition"></a>,  <a href="#MobileSensors"></a>, <a href="#Linkability"></a>, <a href="#NominalObservations"></a>, <a href="#HumansAsSensors"></a>, <a href="#3DSupport"></a>, <a href="#ExSituSampling"></a>, <a href="#SensingProcedure"></a>, <a href="#SpatialRelationships"></a></p>
        </section>
        <section id="RealtimeWildfireMonitoring">
          <h3>Real-time wildfire monitoring</h3>
          <p class="contributor">Manolis Koubarakis</p>
          <div class="expandOrCollapse" onclick="toggleVisibility(this)">&#9654; Full use case description (click to expand):</div>
          <div class="visible">
            <p>This use case is about the wildfire monitoring service of the National Observatory of Athens (NOA) as studied in the <a href="http://www.earthobservatory.eu/">TELEIOS</a> project. The wildfire monitoring service is based on the use of satellite images originating from the SEVIRI (Spinning Enhanced Visible and Infrared Imager) sensor on top of the Meteosat Second Generation satellites MSG-1 and MSG-2. Since 2007, NOA operates an MSG/SEVIRI acquisition station, and has been systematically archiving raw satellite images on a 5 and 15 minutes basis, the respective temporal resolutions of MSG-1 and MSG-2.</p>
            <p>The service active in NOA before TELEIOS can be summarized as follows:</p>
            <ol>
              <li> The ground-based receiving antenna collects all spectral bands from MSG-1 and MSG-2 every 5 and 15 minutes respectively.</li>
              <li>The raw datasets are decoded and temporarily stored in the METEOSAT Ground Station as wavelet compressed images.</li>
              <li>A Python program manages the data stream in real-time by offering the following functionality:
              <ol>
                <li>Extract and store the raw file metadata in an SQLite database. This metadata describes the type of sensor, the acquisition time, the spectral bands captured, and other related parameters. Such a step is required as one image comprises multiple raw files, which might arrive out-of-order.</li>
                <li>Filter the raw data files, disregarding non-applicable data for the fire monitoring scenario, and dispatch them to a dedicated disk array for permanent storage.</li>
                <li>Trigger the processing chain by transferring the appropriate spectral bands via FTP to a dedicated machine and initiating the following steps: (i) cropping the image to keep only the area of interest, (ii) georeferencing to the geodetic reference system used in Greece (HGRS 87), (iii) classifying the image pixels as "fire" or "non-fire" using appropriate algorithms, and finally (iv) exporting the final product to raster and vector formats (ESRI shapefiles).</li>
                <li>Dispatch the derived products to the disk array and additionally store them in a PostGIS database system.</li>
              </ol></li>
            </ol>
            <p>It would be interesting for NOA to see how to use the standards developed by this Working Group to achieve the following:</p>
            <ul>
            <li>Improve the thematic accuracy of generated products.</li>
            <li>Generate thematic maps by combining the generated products with other kinds of data such as: Corine Land Cover, the Administrative Geography of Greece, OpenStreetMap data and Geonames.</li>
            </ul>
            <p>This use case is further discussed in <a href="http://cgi.di.uoa.gr/~koubarak/publications/edbt2013.pdf">Real-Time
            Wildfire Monitoring Using Scientific Database and Linked Data Technologies</a>.
            Some of the data used in the operational service is <a href="http://linkedopendata.gr/">available separately</a>.</p>
          </div>
          <p class="relatedDeliverables"><a href="#BestPractices"></a>, <a href="#TimeOntologyInOWL"></a>, <a href="#SSN"></a></p>
          <p class="relatedRequirements"><a href="#CRSDefinition"></a>, <a href="#DeterminableCRS"></a>, <a href="#Georectification"></a>, <a href="#Linkability"></a>, <a href="#IdentifyCoverageType"></a>, <a href="#Provenance"></a>, <a href="#SensorMetadata"></a>, <a href="#DynamicSensorData"></a>, <a href="#SSNLikeRepresentation"></a></p>
        </section>
        <section id="DiachronicBurntScarMapping">
          <h3>Diachronic burnt scar Mapping</h3>
          <p class="contributor">Manolis Koubarakis</p>
          <div class="expandOrCollapse" onclick="toggleVisibility(this)">&#9654; Full use case description (click to expand):</div>
          <div class="visible">
          <p>This use case was studied by the National Observatory of Athens (NOA) in the <a href="http://www.earthobservatory.eu/">TELEIOS</a> project. The burnt scar mapping service is dedicated to the accurate mapping of burnt areas in Greece after the end of the summer fire season, using Landsat 5 TM satellite images. The processing chain of this service is divided into three stages, each one containing a series of modules.</p>
          <p>The pre-processing stage is dedicated to (i) identification of appropriate data, downloading and archiving, (ii) georeferencing of the received satellite images, and (iii) cloud masking process to exclude pixels &ldquo;contaminated&rdquo; by clouds from the subsequent processing steps.</p>
          <p>The core processing stage comprises (i) a classification algorithm which identifies burnt and non-burnt sets of pixels, (ii) a noise removal process that is necessary to eliminate isolated pixels that have been classified wrongfully as burnt, and (ii) converting the raster intermediate product to vector format.</p>
          <p>Finally, the post-processing stage consists of (i) a visual refinement step to ensure product thematic accuracy and consistency, (ii) attribute enrichment of the product by overlaying the polygons with geoinformation layers and finally (iii) generation of thematic maps. It would be interesting for NOA to see where the standards to be developed in this Working Group could be used.</p>
<!--          <p>The <a href="http://ocean.space.noa.gr/seviri_u/fend_new/index.php">burnt scar mapping service</a> is operational.</p> -->
          </div>
          <p class="relatedDeliverables"> <a href="#BestPractices"></a>, <a href="#TimeOntologyInOWL"></a>, <a href="#SSN"></a></p>
          <p class="relatedRequirements"> <a href="#CRSDefinition"></a>, <a href="#DeterminableCRS"></a>, <a href="#Georectification"></a>, <a href="#Linkability"></a>, <a href="#IdentifyCoverageType"></a>, <a href="#Provenance"></a>, <a href="#SensorMetadata"></a>, <a href="#SSNLikeRepresentation"></a> </p>
        </section>
        <section id="HarvestingLocalSearchContent">
          <h3>Harvesting of Local Search Content</h3>
          <p class="contributor">Ed Parsons</p>
          <div class="expandOrCollapse" onclick="toggleVisibility(this)">&#9654; Full use case description (click to expand):</div>
          <div class="visible">
          <p>This is a rather generic and broad use case, relevant to Google but clearly also relevant to anyone interested in machine processing of HTML referring to about locations and activities that take place at those locations. Local search providers spend much time and effort creating databases of local facilities, businesses and events.</p>
          <p>Much of this information comes from Web pages published on the public Web, but in an unstructured form. Previous attempts at harvesting this information automatically have met with only limited success. Current alternative approaches involve business owners manually adding structured data to dedicated portals. This approach, although clearly an improvement, does not really scale and there are clearly issues in terms of data sharing and freshness.</p>
          <p>The information of interest includes:</p>
          <ul>
          <li>the facility's address;</li>
          <li>the type of business/activity;</li>
          <li>opening hours;</li>
          <li>date, time and duration of events;</li>
          <li>telephone, e-mail and Web site details.</li>
          </ul>
          <p>Complexities to this include multiple address standards, the differences between qualitative representations of place, and precise spatial co-ordinates, definitions of activities etc.</p>
          <p>Ultimately these Web pages should become the canonical source of local data used by all Web users and services.</p>
          </div>
          <p class="relatedDeliverables"><a href="#BestPractices"></a>, <a href="#TimeOntologyInOWL"></a>,</p>
          <p class="relatedRequirements"><a href="#AvoidCoordinateTransformations"></a>, <a href="#CoordinatePrecision"></a>, <a href="#Crawlability"></a>, <a href="#DateTimeDuration"></a>, <a href="#DeterminableCRS"></a>, <a href="#Discoverability"></a>, <a href="#LinkingCRS"></a></p>
        </section>
        <section id="LocatingAThing">
          <h3>Locating a thing</h3>
          <p class="contributor">Ed Parsons</p>
          <div class="expandOrCollapse" onclick="toggleVisibility(this)">&#9654; Full use case description (click to expand):</div>
          <div class="visible">
          <p>With the increasing availability of small, mobile location aware devices the requirement to identify a location human terms is becoming more important. While the determination of sensor in space to a high level of precision is a largely solved problem we are less able to express the location in terms meaningful to humans. The fact that the Bluetooth-LE tracker attached to my bag is at 51.4256853,-0.3317991,4.234500 is much less useful than the description, "Under your bed at home". At others times the location descriptions "24 Bridgeman Road, Teddington, TW11 8AH, UK" might be equally valid, as might "Teddington", "South West London", "England", "UK", "Inside", "Where you left it Yesterday", "Upstairs", "45 minutes from here" or "150 meters from the Post Office".</p>
          <p>A better understanding of how we describe places in human terms, the hierarchical nature of places and the fuzzy nature of many geographical entities will be needed to make the "Internet of Things" manageable. A new scale of geospatial analysis may be required using a reference frame based on the locations of individuals rather than a global spherical co-ordinate, allowing a location of your keys and their attached bluetooth tag to be described as "in the kitchen".</p>
          </div>
          <p class="relatedDeliverables"><a href="#BestPractices"></a></p>
          <p class="relatedRequirements"><a href="#DeterminableCRS"></a>, <a href="#IndependenceOnReferenceSystems"></a>, <a href="#LinkingCRS"></a>, <a href="#TimeDependentCRS"></a>, <a href="#MachineToMachine"></a>, <a href="#SpatialRelationships"></a></p>
        </section>
        <section id="PublishingGeographicalData">
          <h3>Publishing geographical data</h3>
          <p class="contributor">Frans Knibbe</p>
          <div class="expandOrCollapse" onclick="toggleVisibility(this)">&#9654; Full use case description (click to expand):</div>
          <div class="visible">
            <p>This use case is for representing the perspective of a party that is interested in publishing data on the Web and wants to do it right with respect to the geographical component of the data. The point of this use case is that it would be good to remove barriers that stand in the way of more spatial data becoming available on the Web.</p>
            <p>A data publisher could have the following questions:</p>
            <ol>
              <li>How should I publish vector data? What is the best encoding to use?</li>
              <li>How should I publish raster data?</li>
              <li>How do I make the CRS(s) known?</li>
              <li>How do I make the spatial resolution/level of detail/accuracy known?</li>
              <li>Which data publishing software has good support of geographical data types and geographical functions?</li>
              <li>Which data publishing software has good performance when it comes to spatial operations on data?</li>
             </ol>
            <p>From the last two questions it follows that the WG could also be involved in enabling conformance testing and stimulating development of benchmarks for software.</p>
          </div>
          <p class="relatedDeliverables"><a href="#BestPractices"></a></p>
          <p class="relatedRequirements"><a href="#3DSupport"></a>, <a href="#BoundingBoxCentroid"></a>, <a href="#Compatibility"></a>, <a href="#LinkingCRS"></a>, <a href="#MultipleCRS"></a>, <a href="#SpatialRelationships"></a></p>
        </section>
        <section id="ConsumingGeographicalDataInAWebApplication">
          <h3>Consuming geographical data in a Web application</h3>
          <p class="contributor">Frans Knibbe</p>
          <div class="expandOrCollapse" onclick="toggleVisibility(this)">&#9654; Full use case description (click to expand):</div>
          <div class="visible">
          <p>This use case is somewhat complementary to use case <a href="#PublishingGeographicalData">Publishing GeographicalD ata</a>. It takes the consumer perspective, specifically that of a developer of a Web application that should visualize data and allow some kind of user interaction. The hypothetical Web application has little or no prior knowledge about the data it will encounter on the Web, but should be able to do something meaningful with any spatial data that are encountered, like drawing data on a map or rendering the data in a 3D cityscape.</p>
          <p>The point of this use case is that in order for spatial data on the Web to be successful, supply and demand must be balanced to create a positive feedback loop. High quality data must be available in high quantities but those data must also be highly usable for experts as well as non-experts.</p>
          <p>A Web application developer could have the following questions:
          <ol>
            <li>How do I find geographical data on the Web?</li>
            <li>How can I tell what kind of spatial data I will get? Raster or vector? 2D or 3D?</li>
            <li>Which encoding of vector data can I expect?</li>
            <li>Which encoding of raster data can I expect?</li>
            <li>Can I get the data with coordinates that match the coordinate system of my map?</li>
            <li>What is the spatial extent of this dataset/collection of resources/resource?</li>
            <li>How can I filter data to get the most appropriate spatial representation of a resource/collection of resources?</li>
            <li>How can I use spatial data on the Web without having to take a four year academic course first?</li>
            <li>Which spatial operations does this SPARQL endpoint support?</li>
            <li>Can I use spatial operations in federated queries?</li>
            <li>How can I ensure responsiveness of my application (low wait times when accessing data)?</li></ol>
          </div>
          <p class="relatedDeliverables"><a href="#BestPractices"></a></p>
          <p class="relatedRequirements"><a href="#AvoidCoordinateTransformations"></a>, <a href="#BoundingBoxCentroid"></a>, <a href="#Compressible"></a>, <a href="#Crawlability"></a>, <a href="#DeterminableCRS"></a>, <a href="#IndependenceOnReferenceSystems"></a>, <a href="#LinkingCRS"></a>, <a href="#TilingSupport"></a></p>
        </section>
        <section id="EnablingPublicationDiscoveryAndAnalysisOfSpatiotemporalDataInTheHumanities">
          <h3>Enabling publication, discovery and analysis of spatiotemporal data in the humanities</h3>
          <p class="contributor">Frans Knibbe, Karl Grossner</p>
          <div class="expandOrCollapse" onclick="toggleVisibility(this)">&#9654; Full use case description (click to expand):</div>
          <div class="visible">
          <p>Note this use case shares characteristics with <a href="#PublishingCulturalHeritageData">Publishing Cultural Heritage Data</a>.</p>
          <p>A research endeavor that has just started tries to stimulate researchers in various fields of the humanities to make research data available in such a way that the data are and remain usable by other researchers, and that the data may be used for purposes other than those envisaged by the original researcher. The emphasis lies on spatiotemporal data because they are nice to visualize (a map with a time slider) and because it is thought that it would be interesting to try to discover patterns in time and/or space in interlinked distributed data sets.</p>
          <p>This project has the following aspects that seem relevant to this Working Group:</p>
          <ol>
          <li>Technologies must be easy to implement for people that generally do not have a high affinity with IT. This goes for data publishing as well as data consumption.</li>
          <li>References to time and space are often inexact or have shifting frames of reference, so simple encodings like basic geo or ISO 8601 do not suffice.</li>
          <li>References to time and space do need to be as exact as possible, to enable automatic discovery of spatiotemporal patterns.</li>
          <li>Datasets do not just need to be published, they need to be easily discovered too, using spatial and/or temporal filters.</li>
          </ol>
          <p>Adding examples below relevant to items 2 and 3 above, from one existing scholarly Web application case, which may contribute to a more general (i.e. not necessarily historical) requirement for representing several types of uncertainty: imprecision, probability, confidence. Standards for gazetteers -particularly historical (temporal) ones- are non-existent, although several projects with potentially global reach are underway. It will be helpful to have this Working Group in dialog with developers for such projects as <a href="http://pelagios-project.blogspot.com/p/about-pelagios.html">Pelagios</a>, <a href="http://loc.gazetteer.us/">Library of Congress</a>, <a href="http://pleiades.stoa.org/">Pleiades</a>, and Past Place (cf. <a href="http://www.port.ac.uk/department-of-geography/staff/humphrey-southall.html">Humphrey Southall</a>).
          <h4>Spatial</h4>
          <ul>
            <li>A set of life path data were developed for a kinship network of 30,000 individual Britons linked by birth and marriage. Spatial data for the locations of life events has several levels of granularity, from street address (10 Downing Street) to country (China). How can spatial containment relationships for places be expressed so that spatial-temporal contemporaneity be calculated?</li>
            <li>References to places in historical works are often limited to toponyms (i.e. absent geometry or precise spatial relations), and qualified by such terms as "near," and "north of." How can these be indexed spatially so as to be discoverable?</li>
          </ul>
          <h4>Temporal</h4>
          <ul>
            <li>As with spatial data, historical sources contain temporal references at varying granularity. A single data set may contain expressions for exact dates, months, or years -- or ranges containing a mix of any of those.</li>
            <li>Temporal references are frequently inexact, or relational with variable precision. The above referenced data set has a mix, including "around March 1832," "before 1750," "after WW II."</li>
          </ul>
          </div>
          <p class="relatedDeliverables"><a href="#BestPractices"></a>, <a href="#TimeOntologyInOWL"></a></p>
          <p class="relatedRequirements"><a href="#AvoidCoordinateTransformations"></a>, , <a href="#CoordinatePrecision"></a>, <a href="#DateTimeDuration"></a>, <a href="#DeterminableCRS"></a>, <a href="#LinkingCRS"></a>, <a href="#MultipleCRS"></a>, <a href="#NominalTemporalReferences"></a>, <a href="#SpaceTimeMultiScale"></a>, <a href="#TemporalVagueness"></a>, <a href="#TimeDependentCRS"></a>, <a href="#IndependenceOnReferenceSystems"></a>, <a href="#SpatialRelationships"></a></p>
        </section>
        <section id="PublishingGeospatialReferenceData">
          <h3>Publishing geospatial reference data</h3>
          <p class="contributor">Clemens Portele</p>
          <div class="expandOrCollapse" onclick="toggleVisibility(this)">&#9654; Full use case description (click to expand):</div>
          <div class="visible">
          <p><i>This use is based on the <a href="http://www.elfproject.eu/documentation">European Location Framework (ELF)</a>.</i></p>
          <p>Mapping and cadastral authorities maintain datasets that provide geospatial reference data. Reference data is data that a user/developer uses to provide location for her own data (by linking to it), by providing context information about a location (overlaying his data over a background map), etc.</p>
          <p>A key part of this is persistent identifiers for the published data to allow linking to the reference data. Let's assume that http URIs following the <a href="http://www.w3.org/TR/cooluris/">Cool URI note</a> are used as identifiers.</p>
          <p>In ELF &mdash; and <a href="http://inspire.ec.europa.eu/"><abbr title="Infrastructure for Spatial Information in the European Community">INSPIRE</abbr></a> &mdash; reference data is typically published using a Web service by the national authority. In ELF this is an OGC Web Feature Service. To provide access to the different datasets via a single entry point, all the national services are made available via a proxy Web service that also handles authentication etc. In addition, it is foreseen to publish the reference data in other commonly used Web-based platforms for geospatial data to simplify the use of the data - developers and users can use the tools and APIs they are familiar with.</p>
          <p>As a result, the same administrative unit (to pick an example) is basically available via multiple (document) URIs: via the national Web service, the ELF proxy Web service and Web services of the other platforms. Different services will support different representations (GML, JSON, etc.). The Web services may not be accessible by everyone and different users will have access to different document URIs.</p>
          <p>Which real-world object and document URIs for the administrative unit should be maintained and what does a GET return in order:</p> <ul>
          <li>to support linking other data to the administrative unit;</li>
          <li>to deliver the document and representation that the user expects when dereferencing the link?</li>
          </ul>
          <p>A related challenge is that today such links are often implicit. For example, a post code or a statistical unit code is a property in the other data, but the link is not explicit like an HTTP URI. What is a good practice to make use of such implicit links? Should they be converted to HTTP URIs to be explicit or are there better ways (e.g. additional context that provide information about the semantics and a pattern how to construct dereferenceable URIs)?</p>
          </div>
          <p class="relatedDeliverables"><a href="#BestPractices"></a></p>
          <p class="relatedRequirements"><a href="#Validation"></a>, <a href="#Linkability"></a>, <a href="#SpatialOperators"></a>, <a href="#GeoreferencedData"></a></p>
        </section>
        <section id="IntegrationOfGovernmentalAndUtilityDataToEnableSmartGrids">
          <h3>Integration of governmental and utility data to enable smart grids</h3>
          <p class="contributor">Frans Knibbe</p>
          <div class="expandOrCollapse" onclick="toggleVisibility(this)">&#9654; Full use case description (click to expand):</div>
          <div class="visible">
          <p>The research project <a href="http://www.cerise-project.nl/index.php?lang=en">CERISE-SG</a> aims to integrate data from different domains: government, energy utilities and geography, in order to enable establishment of smart energy grids.</p>
          <p>The project has recognized Linked Data as an appropriate concept for integration of data from separate semantic domains. One approach of achieving cross-domain interoperability is to switch from domain-specific semantics to common semantics. For example, the concept of an address has its own definitions in governmental standards and utility standards. Using a common definition improves interoperability.</p><p>An example of a domain model that is an international standard in electric utilities is the <a href="https://en.wikipedia.org/wiki/Common_Information_Model_(electricity)">Common Information Model (CIM)</a>. Its data model provides definitions for an important entity: the electricity meter. These meters provide useful data on consumption and production of energy. If it is possible to view these devices as sensors, it could be possible to move from domain specific semantics (CIM) to common semantics (SSN), and to have ready linkage to geographical semantics (location and network topology). What is required in this case is a low-threshold way of using sensor semantics, because people involved in integration of data from multiple domains should not be burdened with having to grasp the full complexity of each domain.</p>
          </div>
          <p class="relatedDeliverables"><a href="#BestPractices"></a>, <a href="#SSN"></a></p>
          <p class="relatedRequirements"> <a href="#DeterminableCRS"></a>, <a href="#Discoverability"></a>, <a href="#Linkability"></a>, <a href="#SensorMetadata"></a>, <a href="#SpatialMetadata"></a>, <a href="#SSNExamples"></a></p>
        </section>
        <section id="UsingSpatialDataDuringEmergencyResponseOperations">
          <h3>Using spatial data during emergency response operations</h3>
          <p class="contributor">Bart van Leeuwen</p>
          <div class="expandOrCollapse" onclick="toggleVisibility(this)">&#9654; Full use case description (click to expand):</div>
          <div class="visible">
          <p>Emergency response services in the Netherlands use Spatial Data Infrastructures (SDI) to help manage large scale incidents. Predefined geographical data from their GIS warehouses can be used, but incidents and accidents are by nature unpredictable so it is impossible to determine beforehand which data are needed. In-house data need to be supplemented with data from other sources based on ad-hoc requirements. Typically, supplemental data are available through WxS services. This poses several problems:</p>
          <ol>
          <li>Third party data lack semantics in the sense of the Web of data. Under the umbrella of various projects a first attempt has been made to at least share definitions of the terminology used by various emergency response services, both national and cross border. This resulted in the start of a project called the <a href="http://www.firebrary.com/">Firebrary</a>. Now the terminology and definitions are available on the Web as linked data as SKOS. Still linking from the spatial data to these definitions and vice versa is not standardized. Publication of Web semantics with spatial data would improve discoverability of applicable data and facilitate linking data from separate sources.</li>
          <li>It is not possible to predefine relationships between Web data and data exposed through WxS services (rdfs:seeAlso is considered by many to be too limited).</li>
          <li>It is not easy to share all data related to an incident as Web data.</li>
          </ol>
          <p>Being able to plot and exchange data about active incidents through the Web and visualize them in GIS tools with open standards would be a huge leap forward for emergency response services.</p>
          </div>
          <p class="relatedDeliverables"><a href="#BestPractices"></a></p>
          <p class="relatedRequirements"><a href="#AvoidCoordinateTransformations"></a>, <a href="#Compatibility"></a>, <a href="#DeterminableCRS"></a>, <a href="#Discoverability"></a>, <a href="#Linkability"></a>, <a href="#LinkingCRS"></a>, <a href="#SpatialMetadata"></a>, <a href="#SpatialRelationships"></a>, <a href="#SubjectEquality"></a></p>
        </section>
        <section id="PublicationOfAirQualityDataAggregations">
          <h3>Publication of air quality data aggregations</h3>
          <p class="contributor"> Alejandro Llaves, Miguel Angel Garc&iacute;a-Delgado (OEG-UPM), Rub&eacute;n Notivol, Javier Celma (Ayuntamiento de Zaragoza)</p>
          <div class="expandOrCollapse" onclick="toggleVisibility(this)">&#9654; Full use case description (click to expand):</div>
          <div class="visible">
          <p><b>What:</b> The local authorities of Zaragoza (Spain) want to publish the air quality data of the city. Each observation station has a spatial location described with an address. The dataset contains hourly observations and daily aggregations of different gases, e.g. SO<sub>2</sub>, NO<sub>2</sub>, O<sub>3</sub>, CO, etc.</p>
          <p><b>How:</b> We use the <a href="http://www.w3.org/ns/locn">Location Core vocabulary</a> to model the address, e.g. :station locn:address "C/ Gran V&iacute;a (Paraninfo)"^^xsd:string. We use xsd:dateTime to represent hourly observations, e.g. :obs ssn:observationResultTime "2003-03-08T11:00:00Z"^^xsd:dateTime.</p>
          <p><b>Open challenges:</b> The combination of hourly observations and daily aggregations in the same dataset may cause confusion because the granularity of the observation is not explicit. For daily aggregations, we suggest using time:Interval from the Time Ontology. To make the temporal modeling more homogeneous, time:Instant could be used for the hourly observations.</p>
          <p>A description of the data set, including its SPARQL endpoint, can be found at <a href="https://www.zaragoza.es/ciudad/risp/detalle_Risp?id=131">https://www.zaragoza.es/ciudad/risp/detalle_Risp?id=131</a>.</p>
          </div>
          <p class="relatedDeliverables"><a href="#SSN"></a>, <a href="#TimeOntologyInOWL"></a></p>
          <p class="relatedRequirements"><a href="#DateTimeDuration"></a>, <a href="#ObservationAggregations"></a></p>
        </section>
        <section id="PublicationOfTransportCardValidationAndRechargingData">
          <h3>Publication of transport card validation and recharging data</h3>
          <p class="contributor">Alejandro Llaves (OEG-UPM)</p>
          <div class="expandOrCollapse" onclick="toggleVisibility(this)">&#9654; Full use case description (click to expand):</div>
          <div class="visible">
          <p><b>What:</b> The Regional Transport Consortium of Madrid (CRTM) wants to make available data about transport card validations and transport card recharging. In the case of transport card validations, the NFC sensors are located on buses, and at the entrance and (some) exit points of metro stations. The observation value of a validation includes data related to the transport card, such as the card identifier and the user profile. The sensors for transport card recharging are ATMs and ticket selling points distributed around Madrid. The observation value of a recharging includes the card identifier and the type of recharging.</p>
          <p><b>How:</b> To model transport card validations, we consider two observed properties: user entry (EntradaUsuario) and user exit (SalidaUsuario). Validation sensors at metro stations have a fixed location and a unique identifier, e.g. 02_L12_P2. A bus validation sensor is moving continuously, so for the sake of pragmatism, there is a unique sensor identifier for each bus stop in every line, e.g. 03_L20_P837. Those identifiers point to an address and geographic coordinates. The observed property when a user adds money to her transport card is the act of recharging (CargaTTP). In both cases, validation and recharging observations, the feature of interest is the transport card.</p>
          </div>
          <p class="relatedDeliverables"><a href="#BestPractices"></a>, <a href="#SSN"></a></p>
          <p class="relatedRequirements"><a href="#TimeDependentCRS"></a>, <a href="#SSNExamples"></a></p>
        </section>
        <section id="CombiningSpatialRDFDataForIntegratedQueryingInATriplestore">
          <h3>Combining spatial RDF data for integrated querying in a triplestore</h3>
          <p class="contributor">Matthew Perry (Oracle)</p>
          <div class="expandOrCollapse" onclick="toggleVisibility(this)">&#9654; Full use case description (click to expand):</div>
          <div class="visible">
          <p>RDF datasets with spatial components are becoming more common on the Web. Many applications could benefit from the ability to combine, analyze and query this data with an RDF triplestore (or across triplestores with a federated query). Challenges arise, however, when trying to integrate such datasets.</p>
          <ul>
            <li>Inconsistent, incomplete, and non-standard metadata descriptions of spatial data</li>
            <li>Different representations of geometry data across different datasets</li>
            <li>Different spatial reference systems used across different datasets</li>
            <li>Different scales used across different datasets</li>
          </ul><p>For example, <a href="http://data.ordnancesurvey.co.uk/">Ordnance Survey</a> linked data uses British National Grid CRS and represents geometries with an Ordnance Survey-developed ontology, and <a href="http://linkedgeodata.org/Datasets">LinkedGeoData</a> uses WGS84 longitude latitude and represents geometries as GeoSPARQL WKT literals.</p>
          <p>Best practices in the following areas would help make integration more straightforward.</p>
          <ul>
            <li>Agreed-upon vocabulary for metadata about spatial datasets</li>
            <li>Agreed-upon URIs for common coordinate reference systems</li>
            <li>Recommendations for a default, canonical coordinate reference system for spatial data published on the Web</li>
            <li>Recommendations for serializing geometries as RDF</li>
          </ul><p>Consistent metadata descriptions about spatial datasets will take out a lot of guess work when combining datasets, and standard URIs for coordinate reference systems will be an important part of this metadata description. A recommended canonical CRS would make combining datasets more efficient by eliminating the coordinate transformation step, which would make federated GeoSPARQL queries more feasible.</p>
          </div>
          <p class="relatedDeliverables"><a href="#BestPractices"></a></p>
          <p class="relatedRequirements"><a href="#AvoidCoordinateTransformations"></a>, <a href="#DeterminableCRS"></a>, <a href="#EncodingForVectorGeometry"></a>, <a href="#LinkingCRS"></a>, <a href="#SpatialMetadata"></a></p>
        </section>
        <section id="DutchBaseRegistry">
          <h3>Dutch Base Registry</h3>
          <p class="contributor">Linda van den Brink</p>
          <div class="expandOrCollapse" onclick="toggleVisibility(this)">&#9654; Full use case description (click to expand):</div>
          <div class="visible">
          <p>Dutch government data is for a large part open data. However, at the moment the data is difficult to find, and it cannot be easily linked to other data. It is not helping that most registrations are making use of their heavy backoffice standards for opening their data. These problems are counteracted by copying data of others, involving heavy expenses for collecting, converting and synchronizing the data, or by building expensive national provisions. The result is an abundance of copies and much doubt regarding the authenticity of the information.</p>
          <p>A better solution would be to make the authentic data permanently available as linked data, so that everyone can use it and the datasets can be interlinked, resulting in more coherence and improved traceability and no more need for copying and synchronization.</p>
          <p>There are now 13 Dutch &lsquo;base registries&rsquo; containing government reference data: e.g.</p>
          <ul>
            <li>BAG (buildings and addresses)</li>
            <li>NHR (businesses, organizations)</li>
            <li>BRP (citizens)</li>
            <li>BGT (large scale topography)</li>
            <li>BRT (small scale topography)</li>
            <li>BRK (cadastre)</li>
            <li>WOZ (building tax)</li>
          </ul>
          <p>A lot of these have geospatial content or refer to geospatial resources in other base registries (such as addresses). At the moment these references are informal and often incorrect or outdated. This means there is a need to express geospatial content in linked data (i.e. a standard vocabulary) and to perform spatial queries over linked data.</p>
          <p>Geometries, especially lines and polygons, may contain many coordinates. For example, a municipal boundary could easily contain more than 1500 coordinate pairs. Compared to non-geometric properties, this can result in large amounts of data to transfer and process. The coordinates can easily be 95% of all data of an object when using polygons. The question rises whether there is a need for performance optimization and/or compression techniques for large amounts of coordinates. If so, there could also be a need to standardize such a technique, similar to the PNG format for encoding images.</p>
          <p>Coordinate reference systems (CRS) are to geo-information what character encodings are to text. If you don&rsquo;t know which CRS is used, you can&rsquo;t use the coordinates. Different CRSs exist for a reason: localized CRSs provide more precise coordinates for a certain part of the globe. It is not possible for a global CRS to be as precise, for example because the continental plates move a few centimeters every year. For large scale data and applications this continental drift could be very relevant over time. Take for example the boundary of cadastral parcels. If this drift is not taken into account, there could be issues if parcel boundaries that were established e.g. 10 years ago are overlaid over recently acquired aerial imagery with high accuracy (e.g. 10 cm). There could be visual differences, while the actual situation did not change.</p>
          <p>While the possibility to use different CRSs hinders interoperability (datasets using different CRSs cannot be easily combined, a complex transformation is necessary), on the other hand this option is perhaps needed for use cases where a high precision of coordinates is important. The BGT (large scale topography) is an example of such a use case.</p>
          <p>A prototype application, based on linked data, where BGT, BAG, NHR and WOZ data is combined, is <a href="http://almere.pilod.nl/bgtld">here</a>. BAG linked data is <a href="http://bag.kadaster.nl">here</a> (&ldquo;Begrippen&rdquo;: the vocabulary; &ldquo;BAG Data&rdquo;: the data)</p>
          </div>
          <p class="relatedDeliverables"><a href="#BestPractices"></a></p>
          <p class="relatedRequirements"><a href="#AvoidCoordinateTransformations"></a>, <a href="#Compressible"></a>, , <a href="#CoordinatePrecision"></a>, <a href="#DeterminableCRS"></a>, <a href="#Linkability"></a>, <a href="#LinkingCRS"></a>, <a href="#MultipleCRS"></a></p>
        </section>
        <section id="PublishingCulturalHeritageData">
          <h3>Publishing Cultural heritage data</h3>
          <p class="contributor">Lars G. Svensson</p>
          <div class="expandOrCollapse" onclick="toggleVisibility(this)">&#9654; Full use case description (click to expand):</div>
          <div class="visible">
          <p>Cultural Heritage Data such as library authority files are increasingly being published as Linked (Open) Data. Those datasets contain, among other entities, descriptions of spatio-temporal events such as <i>World War I</i>, the <i>Birth of Albert Einstein</i> (date and place) or <i>Martin Luther's pinning of his 95 theses</i>. The problem is that most of the spatio-temporal information is inexact. This inexactness ranges from time spans (<i>second quarter of the 9th century</i>, e.g. approx. 825-850, which also could be 823 or 852) to geographic entities such as <i>Renaissance Italy</i> (what did Italy look like at that time, and to what extent is the Italian renaissance as a time period different from the English?).</p>
          <p>When cultural heritage institutions put their data on the Web, the staff members mapping their data to Web standards often do not have expertise in temporal or geospatial data formats. Formats such as WKT are standardized but it is difficult to know if the mapping from the local data source is done correctly. A validator for commonly used formats such as WKT or GeoJSON would prove helpful.</p>
          <p>Challenges include:</p>
          <ol>
          <li>There is no framework available to describe fuzzy temporal information. ISO 8601 and the related XSD datatypes assume a precision that cannot be supplied by the data publishers.</li>
          <li>In addition to that, OWL reasoning over cultural heritage datasets is severely hampered since OWL only accepts the datatypes xsd:dateTime and xsd:dateTimeStamp as temporal datatypes (cf. <a href="http://www.w3.org/TR/owl2-syntax/#Time_Instants">Time Instants</a>).</li>
          <li>Little or no possibilities to perform validation of temporal and/or spatial data formats (e.g. WKT).</li>
          </ol>
          <p>Note: This use case has similarities to <a href="#EnablingPublicationDiscoveryAndAnalysisOfSpatiotemporalDataInTheHumanities"></a>.</p>
          </div>
          <p class="relatedDeliverables"><a href="#BestPractices"></a>, <a href="#TimeOntologyInOWL"></a>, <a href="#CoverageInLinkedData"></a></p>
          <p class="relatedRequirements"><a href="#CoverageTemporalExtent"></a>, <a href="#DateTimeDuration"></a>, <a href="#GeoreferencedData"></a>, <a href="#NominalTemporalReferences"></a>, <a href="#IndependenceOnReferenceSystems"></a>, <a href="#UpdateDatatypes"></a>, <a href="#SpaceTimeMultiScale"></a>, <a href="#TemporalVagueness"></a>, <a href="#SpatialVagueness"></a>, <a href="#Validation"></a></p>
        </section>
        <section id="DisseminationOf3DGeologicalData">
          <h3>Dissemination of 3D geological data</h3>
          <p class="contributor">Rachel Heaven</p>
          <div class="expandOrCollapse" onclick="toggleVisibility(this)">&#9654; Full use case description (click to expand):</div>
          <div class="visible">
            <p>The British Geological Survey (BGS), like all Geological Survey Organizations (GSOs), has as one of its principal roles to be the primary provider of geoscience information within its national territory. Increasingly the information provided is digital and dissemination is over the internet, and there is a trend towards making more information freely available. For BGS&rsquo;s 2D information this requirement has been met by the provision of <a href="http://bgs.ac.uk/data/services/wms.html">various OGC Web map services</a>.</p>
            <p>However, geological units and structures are three-dimensional bodies and their traditional depiction on two-dimensional geological maps leads to a loss of information and the requirement of quite a high level of geological understanding on the part of the user to interpret them. The geoscience data user community includes scientific users, but also includes many other stakeholders such as exploration companies, civil engineers, local authority planners, as well as the general public. It is therefore the aim of many Geological Surveys, including BGS, to move towards the provision of geological information as spatial 3D datasets on the Web that are accessible and usable by non-experts.</p>
            <p>We have implemented a few ways of disseminating the 3D data on the Web (<a href="http://www.bgs.ac.uk/services/3Dgeology/lithoframeSamples.html">http://www.bgs.ac.uk/services/3Dgeology/lithoframeSamples.html</a>, <a href="http://www.bgs.ac.uk/services/3Dgeology/virtualBoreholeViewer.html">http://www.bgs.ac.uk/services/3Dgeology/virtualBoreholeViewer.html</a>,<a href="http://earthserver.bgs.ac.uk/">http://earthserver.bgs.ac.uk/</a>, investigation of augmented reality smartphone application) but the remaining issues are</p>
            <ul>
              <li>user should not need any special software for discovery and assessment purposes</li>
              <li>user can subset the data by x,y,z limits</li>
              <li>user can overlay their own area/volume of interest on the model (e.g. for tunneling projects)</li>
              <li>user may have to overlay their own (or an open data) DTM if the model is built using a non-open data DTM</li> 
              <li>to represent complex geology (folding, faulting, intrusions etc) and varying data resolution the delivery method must be able to handle triangulated irregular networks (TINs) and heterogeneous resolution voxel grids.</li>
            </ul>
            <p>If there existed a best practice or standard way of publishing this sort of data then it would encourage development of applications on the Web to handle them. The datasets that BGS is generating are:</p>
            <ul>
              <li>3D spatial models of rock type and/or lithology currently represented as stacks of 2d subsurface grids representing the interfaces between different layers.</li>
              <li>3D voxel datasets of x,y,z grid cell and geological, physical or chemical property (+ associated uncertainty).</li>
              <li>3D LIDAR point cloud data e.g. of retreating cliff faces, underground mine structures.</li>
            </ul>
          </div>
          <p class="relatedDeliverables"><a href="#BestPractices"></a>, <a href="#CoverageInLinkedData"></a></p>
          <p class="relatedRequirements"><a href="#Discoverability"></a>, <a href="#GeoreferencedData"></a>, <a href="#IdentifyCoverageType"></a>, <a href="#LinkingCRS"></a>, <a href="#ObservedPropertyInCoverage"></a>, <a href="#QualityPerSample"></a>, <a href="#ReferenceDataChunks"></a>, <a href="#3DSupport"></a>, <a href="#UseInComputationalModels"></a>, <a href="#SpatialMetadata"></a>, <a href="#TilingSupport"></a>, <a href="#Compressible"></a>, <a href="#Linkability"></a></p>
        </section>
        <section id="PublicationOfRawSubsurfaceMonitoringData">
          <h3>Publication of raw subsurface monitoring data</h3>
          <p class="contributor">Rachel Heaven</p>
          <div class="expandOrCollapse" onclick="toggleVisibility(this)">&#9654; Full use case description (click to expand):</div>
          <div class="visible">
          <p>The UK Government is funding a new Energy Security and Innovation Observing System for the Subsurface (ESIOS). ESIOS will consist of a group of science research facilities where new subsurface activities such as fracking (hydraulic fracturing) for shale gas can be tested and monitored under controlled conditions. This research will address many of the environmental issues that need to be answered for the development of the UK&rsquo;s home-grown, secure energy solutions. This includes carbon capture and storage, geothermal energy, nuclear waste disposal, underground coal gasification and underground gas storage.</p>
          <p>Data will be collected from monitoring boreholes and from surface, airborne and satellite sensors. The raw scientific data will be published freely online, possibly in real-time or near real-time, to encourage transparency and public confidence in the industry, and to provide underpinning science for regulation.</p>
          <p>The scientific data will consist of:</p>
          <ul>
            <li>location data for the sensor facilities;</li>
            <li>time series data consisting of x,y,z (depth), time, and an observed property (e.g. porosity, resistivity, density, methane content, fracture orientation, groundwater flow direction, seismic ground motion).</li>
          </ul>
          <p>We want to be able to publish this raw data on the Web in such a way that it can be easily consumed by third party Web applications for visualization, spatio-temporal filtering, statistical analysis and alerts.</p>
          <p>(Another similar use case is for publication of geomagnetic monitoring data, for which the primary outputs are time series tables or graphs, and the location data for the observation station is relatively simple and low accuracy)</p>
          </div>
          <p class="relatedDeliverables"><a href="#BestPractices"></a>, <a href="#TimeOntologyInOWL"></a>, <a href="#SSN"></a>, <a href="#CoverageInLinkedData"></a></p>
          <p class="relatedRequirements"><a href="#HumansAsSensors"></a>, <a href="#CRSDefinition"></a>, <a href="#DynamicSensorData"></a>, <a href="#GeoreferencedData"></a>, <a href="#IdentifyCoverageType"></a>, <a href="#Linkability"></a>, <a href="#LinkingCRS"></a>, <a href="#4DModelSpaceTime"></a>, <a href="#NominalObservations"></a>, <a href="#ObservationAggregations"></a>, <a href="#SamplingTopology"></a>, <a href="#SensingProcedure"></a>, <a href="#SensorMetadata"></a>, <a href="#SpatialMetadata"></a>, <a href="#SpatialVagueness"></a>, <a href="#3DSupport"></a>, <a href="#SpaceTimeMultiScale"></a>, <a href="#SSNExamples"></a>, <a href="#TimeSeries"></a>, <a href="#UncertaintyInObservations"></a>, <a href="#VirtualObservations"></a></p>
        </section>
        <section id="UseOfAPlaceNameOntologyForGeo-parsingTextAndGeo-enablingSearches">
          <h3>Use of a place name ontology for geo-parsing text and geo-enabling searches</h3>
          <p class="contributor">Rachel Heaven</p>
          <div class="expandOrCollapse" onclick="toggleVisibility(this)">&#9654; Full use case description (click to expand):</div>
          <div class="visible">
          <p>The British Geological Survey (BGS) has valuable geoscience data in text form dating back 180 years, which is gradually being scanned and OCR to make it more accessible and searchable. Much of the information in the reports concerns observations or interpretations made at a location or about a named geological feature. We would like the relevant information in those documents to be retrievable from a Web search using coordinate limit criteria or using a place name criteria, so this use case requires a place name ontology (or federated ontologies).</p>
          <p>For BGS's purposes the ontology should contain historical place names, named subsurface geological features (e.g. Widmerpool Gulf), palaeogeographic place names, and named submarine features (e.g. <a href="http://www.gebco.net/data_and_products/undersea_feature_names/">GEBCO undersea feature names </a>).</p>
          <p>To extend the capabilities into the vertical dimension then the ontology should also contain the names of qualitative earth realms (vertical divisions within the atmosphere, ocean and solid earth &ndash; such as in <a href="https://sweetontology.net">the SWEET ontology</a>).</p>
          <p>To extend the capabilities into the time dimension then the ontology should also contain the names of historical and geological time periods (e.g. <a href="https://www.seegrid.csiro.au/wiki/CGIModel/GeologicTime#GeologicTime_XML">https://www.seegrid.csiro.au/wiki/CGIModel/GeologicTime#GeologicTime_XML</a>, used in a recent example of geological age name parser at <a href="http://www.agenames.org">http://www.agenames.org</a>)</p>
          <p>With a resource like this, all text resources could be parsed to locate them in time and space.</p>
          <p>Each named feature should have a spatial attribute, either as topological relations to other named features, or as spatial-temporal extent appropriate for various scales and with appropriate uncertainties (i.e. fuzzy definitions of geometry and time periods). Versioning will be important e.g. for administrative boundaries that change frequently.</p>
          <p>(NB <a href="http://www.geonames.org/">Geonames</a> goes much of the way to meeting this requirement)</p>
          </div>
          <p class="relatedDeliverables"><a href="#BestPractices"></a>, <a href="#TimeOntologyInOWL"></a>, <a href="#SSN"></a></p>
          <p class="relatedRequirements"><a href="#DifferentTimeModels"></a>, <a href="#DateTimeDuration"></a>, <a href="#3DSupport"></a>, <a href="#NominalTemporalReferences"></a>, <a href="#TemporalReferenceSystem"></a>, <a href="#TemporalVagueness"></a>, <a href="#SpatialVagueness"></a>, <a href="#SpatialRelationships"></a>, <a href="#ValidTime"></a>, <a href="#SpatialMetadata"></a></p>
        </section>
        <section id="DrivingToWorkInTheSnow">
          <h3>Driving to work in the snow</h3>
          <p class="contributor">Cory Henson (Bosch RTC)</p>
          <div class="expandOrCollapse" onclick="toggleVisibility(this)">&#9654; Full use case description (click to expand):</div>
          <div class="visible">
            <p>Consider the following wildly-fictional scenario: Sue is driving to work in the snow on a cold Pittsburgh morning. On entry, her car recognizes the cold weather and automatically heats the interior to Sue's preferred temperature and turns on the defrost to clear the frost from the wind-shield. On the way, the snow causes significant traffic delay on her route forcing her to re-schedule an early morning meeting. In response, the car suggests she stop at her favorite nearby coffee shop for a Flat White until the roads are clear.</p>
            <p>The scenario above requires access to multiple types of observation, spatial, and temporal data which may be local to the car or available on the Web.</p>
            <p>The different types of observation data may include:</p>
            <ul>
              <li>sensed environmental observations (e.g,. freezing-temperature, frost-on-windshield);</li>
              <li>user behavior observations (e.g., Sue sets the thermostat to 75F, Sue stops at the coffee shop, Sue updates her calendar);</li>
              <li>observations on the Web (e.g., current weather conditions, traffic conditions).</li>
            </ul>
            <p>The different types of spatial data may include:</p>
            <ul>
              <li>points-of-interest (e.g., home, work, coffee shop);</li>
              <li>spatial relations (e.g., coffee shop is NEAR Sue's current location).</li>
            </ul>
            <p>The different types of temporal data may include:</p>
            <ul>
              <li>calendar events (e.g., Sue's meeting on calendar);</li>
              <li>schedules (e.g., schedule when the coffee-shop is open);</li>
              <li>temporal relations (e.g., the predicted time to reach work occurs after the beginning of a scheduled meeting).</li>
            </ul>
            <p>In addition, the car uses light-weight communication protocols, such as CoAP and/or MQTT, to exchange data (i.e., observations, spatial, and temporal data) between networked components.</p>
            <p>This scenario may face the following general challenges for representing, managing, and querying observation data:</p>
            <ul>
              <li>discover observation streams within a given spatial context (and matching some criteria);</li>
              <li>query for observations within a given spatiotemporal context (and matching some criteria);</li>
              <li>publish and subscribe to an observation stream within a given spatial context (and matching some criteria);</li>
              <li>filter an observation stream based on given set of criteria (e.g., quality, feature-of-interest, observed-property);</li>
              <li>represent data with a small syntactic footprint (for exchange between resource-constrained devices);</li>
              <li>integration of SSN with existing, well-known, IoT protocols (CoAP, MQTT, etc.);</li>
              <li>represent "high-level" qualitative observations (such as observations of user behavior, e.g., Sue stopped at the coffee shop).</li>
            </ul>
          </div>
          <p class="relatedDeliverables"><a href="#BestPractices"></a>, <a href="#TimeOntologyInOWL"></a>, <a href="#SSN"></a>, <a href="#CoverageInLinkedData"></a></p>
          <p class="relatedRequirements"><a href="#HumansAsSensors"></a>, <a href="#DateTimeDuration"></a>, <a href="#DeterminableCRS"></a>, <a href="#Discoverability"></a>, <a href="#DynamicSensorData"></a>, <a href="#GeoreferencedData"></a>, <a href="#LightweightAPI"></a>, <a href="#ModelActuation"></a>, <a href="#MovingFeatures"></a>, <a href="#NominalObservations"></a>, <a href="#NominalTemporalReferences"></a>, <a href="#SensorMetadata"></a>, <a href="#MachineToMachine"></a>, <a href="#Compressible"></a></p>
        </section>
        <section id="IntelligentTransportationSystem">
          <h3>Intelligent Transportation System</h3>
          <p class="contributor">Antoine Zimmermann</p>
          <div class="expandOrCollapse" onclick="toggleVisibility(this)">&#9654; Full use case description (click to expand):</div>
          <div class="visible">
          <p>Intelligent Transportation Systems (ITS) can be defined as the application of advanced information and communications technology to surface transportation in order to achieve enhanced safety and mobility while reducing the environmental impact of transportation. The addition of wireless communications offers a powerful and transformative opportunity to establish transportation connectivity that further enables cooperative systems and dynamic data exchange using a broad range of advanced systems and technologies. - See more at: <a href="http://www.its.dot.gov/standards_strategic_plan/">http://www.its.dot.gov/standards_strategic_plan</a></p>
          <p>ITS do so by exploiting information from various origins, especially the Web. Several Web sites, Web services, datasets related to public transport services, traffic, road network structure, localized incidents, and so on have to be exploited in order to convey users with the best decisions, in real time. All of these information sources rely considerably on spatio-temporal data. The challenge is to model dependency in both space and time seamlessly and simultaneously so that the accuracy of analysis can be improved (for instance for regulation of multimodal transportation network) or the processing of aggregated information can be simplified (for instance for multimodal traveler information system). For such systems to work well in a pervasive way, it is also important that the system can easily discover relevant datasets/services based on the user current location.</p>
          <p>Consequently, such systems would greatly benefit from standardized formats, standard practices for publishing or making spatial data available online. A standard way of indicating time and time frames would also help correlate several temporally situated entities such as bus schedules, real time bus position, and traffic light durations.</p>
          <p>A specific type of ITS is Advanced Traveler Information System (ATIS) that computes an accurate travel duration. To do so, ATIS should be able to combine data following different spatio-temporal scales. These data could be related to the current or anticipated network traffic (the congestion level), the network topology (number of lines on the routes, presence of traffic lights, etc.), the presence of expected events (which can be static, like work on the road, or dynamic like demonstrations), the weather state (the presence of rain or mist on a part of the itinerary), and so on.</p>
          <p>ITSs can also be dedicated to the management of parking spots. For a driver, the choice of its parking spot is a multi-criteria decision process that takes into account static data given by the description of the infrastructure (whether the spot is private or public, reserved for disabled, etc.), dynamic data given by sensors (like traffic) and personal data (destination, budget).</p>
          </div>
          <p class="relatedDeliverables"><a href="#BestPractices"></a>, <a href="#TimeOntologyInOWL"></a>, <a href="#SSN"></a>, <a href="#CoverageInLinkedData"></a></p>
          <p class="relatedRequirements"><a href="#DateTimeDuration"></a>, <a href="#MobileSensors"></a>, <a href="#ModelActuation"></a>, <a href="#MovingFeatures"></a>, <a href="#NominalObservations"></a>, <a href="#SpaceTimeMultiScale"></a>, <a href="#SSNExamples"></a>, <a href="#TemporalReferenceSystem"></a></p>
        </section>
        <section id="OptimizingEnergyConsumptionProductionSalesAndPurchasesInSmartGrids">
          <h3>Optimizing energy consumption, production, sales and purchases in Smart Grids</h3>
          <p class="contributor">Antoine Zimmermann</p>
          <div class="expandOrCollapse" onclick="toggleVisibility(this)">&#9654; Full use case description (click to expand):</div>
          <div class="visible">
            <p>In smart grids, energy management has to take into account the fact that any energy consumer may also be a producer (they are thus "prosumers"). This leads to new load balancing problems as well as new forms of economic exchanges regarding selling and buying energy. In order to take an informed decision on what amount of energy to buy from whom at what cost, or to sell, decision algorithms must use information that can be local (their own consumption and production), global (statistical data on seasonal household energy consumption), and possibly external to grid (meteorological data). In such context, reliance on Web data from several sources adds real value to the decision process.</p>
            <p>The kind of data that has to be considered are, for the most part, highly fluctuating: weather for assessing heating needs, stock exchange for pricing appropriately, current and future offer and demand, etc.</p>
            <p>There is a need for a temporal model that covers historical data for statistical analysis, short term timestamped sensed data, and data about future predictions.</p>
            <p>The need for spatio-temporal information is even increased if the smart grid is including electric vehicles that can serve as energy producers when they are not consuming electricity for recharging.</p>
          </div>
          <p class="relatedDeliverables"><a href="#TimeOntologyInOWL"></a>, <a href="#SSN"></a></p>
          <p class="relatedRequirements"><a href="#Linkability"></a>, <a href="#ModelActuation"></a>, <a href="#SSNExamples"></a></p>
        </section>
        <section id="LinkedDataForTaxAssessment">
          <h3>Linked Data for tax assessment</h3>
          <p class="contributor">Luigi Selmi (via <a href="https://lists.w3.org/Archives/Public/public-sdw-comments/">public-sdw-comments)</a></p>
          <div class="expandOrCollapse" onclick="toggleVisibility(this)">&#9654; Full use case description (click to expand):</div>
          <div class="visible">
            <p>Tax assessments are based on the comparison of what is due by a citizen in a year for her ownership of real estates in the area administered by a municipality and what has been paid. The tax amount is regulated by laws and based on many criteria like the size of the real estate, the area in which it is located, its type: house, office, farm, factory and others. Taxpayers can save money from the original due depending on the usage of the estate. A family that owns the house in which they live can save the entire amount. Many other regulations lighten in different ways the burden of the tax for other categories of taxpayers. Furthermore the situation about a taxpayer changes over the years in relation to her properties share and family status. Due to the many different situations met, an employee in charge of performing tax assessments on behalf of a municipality must collect many information before being able to assert with a good degree of confidence that a difference between the original amount and what has been paid is not justified and an advice has to be sent to the taxpayer starting a long and expensive process to recover the difference. Currently each single assessment requires the employee to collect information from different public administrations Web sites, archives, registries, documents. Data scattered in so many silos and formats dramatically reduce employees productivity and assessment effectiveness at the point that it is not always clear whether the money recovered is worth the cost of the assessment. A Linked Data approach for sharing spatial and temporal data would certainly increase the productivity of the assessor.</p>
          </div>
          <p class="relatedDeliverables"><a href="#BestPractices"></a></p>
          <p class="relatedRequirements"><a href="#DeterminableCRS"></a>, <a href="#Discoverability"></a>, <a href="#Linkability"></a>, <a href="#LinkingCRS"></a></p>
        </section>
        <section id="ImagesEGATimeSeriesOfAWaterCourse">
          <h3>Images, e.g. a time series of a water course</h3>
          <p class="contributor">Kerry Taylor (on behalf of Jamie Baker, Australian Commonwealth Department of Communications)</p>
          <div class="expandOrCollapse" onclick="toggleVisibility(this)">&#9654; Full use case description (click to expand):</div>
          <div class="visible">
            <p>This use case is provided to extend three primary use cases already before the Working Group:</p>
            <ul>
              <li><a href="#PublishingGeographicalData"></a></li>
              <li><a href="#ConsumingGeographicalDataInAWebApplication"></a></li>
              <li><a href="#PublishingGeospatialReferenceData"></a></li>
            </ul>
            <p>More broadly the Commonwealth of Australia has developed a National Map Web platform which is currently making available authoritative national datasets. There is a need to recognize that data can an image (e.g. an image-based tile set for example) and therefore in itself also create a time series-based resource (for example, the change in a water course over time which can be visualized as time series layers). Indeed both the ISO and OGC have recognized this in their standards. It is the Australian Government Department of Communication&rsquo;s view, as the lead agency stewarding spatial data policy, that image-based resources should also be included in the consideration of this Working Group as it relates to geographic and spatial features geometries. Wherever possible the Commonwealth view is to maintain the highest applicability of a standard or best practice guide and not limit conformance options for data holdings (especially of public origin). This also applies to cadastral and other data at the state/territory level which could show the change in land parcel, development or other property and built environment features over time. In terms of our future cities, sensors and other data sources may also need linkage to image-based resources for citizen use. As such:</p>
            <ol>
              <li>Image-based data needs to be recognized and discoverable as it too tells a story;</li>
              <li>Time series data can be visual and therefore visualized as a data layer or an image in time or both;</li>
              <li>Linking of data whether image-based or not should be discoverable and mix or match just as easily as data of a similar or dissimilar type;</li>
              <li>Metadata conformance is crucial to support discoverability, interoperability and provide information on the nature of a data resource (e.g. Time series image or time series data).</li>
              <li>A challenge exists in maximizing the interoperability of geographic and/or spatial data both above and below ground level. (An example may be subsurface water imaging data combined with sensor data).</li>
            </ol>
            <p>This additional information supports a broader need for SSN, Coverage and Time considerations for the above three current use cases.</p>
          </div>
          <p class="relatedDeliverables"><a href="#BestPractices"></a>, <a href="#TimeOntologyInOWL"></a>, <a href="#SSN"></a>, <a href="#CoverageInLinkedData"></a></p>
          <p class="relatedRequirements"><a href="#Discoverability"></a>, <a href="#GeoreferencedData"></a>, <a href="#IdentifyCoverageType"></a>, <a href="#ReferenceDataChunks"></a>, <a href="#SpaceTimeMultiScale"></a>, <a href="#TimeSeries"></a>, <a href="#3DSupport"></a>, <a href="#SensorMetadata"></a>, <a href="#CRSDefinition"></a>,  <a href="#Linkability"></a>, <a href="#Provenance"></a>, <a href="#SamplingTopology"></a>, <a href="#DateTimeDuration"></a>, <a href="#QualityPerSample"></a>, <a href="#ValidTime"></a></p>
        </section>
        <section id="DroughtsInGeologicalComplexEnvironmentsWhereGroundwaterIsImportant">
          <h3>Droughts in geological complex environments where groundwater is important</h3>
          <p class="contributor">Chris Little (on behalf of Andrew G Hughes, British Geological Survey)</p>
          <div class="expandOrCollapse" onclick="toggleVisibility(this)">&#9654; Full use case description (click to expand):</div>
          <div class="visible">
            <p>During the period 2011-2013, the UK faced an extraordinary drought only to be saved from a likely major crisis by very high spring and summer rainfall (CEH, 2012). Government asked questions such as &ldquo;how much water is left in the tank?&rdquo;, at which point managers and regulators realized that they didn&rsquo;t know the answer with any certainty (EA, 2012). A National Drought Group of leading stakeholders was formed and led by the Chief Executive of the Environment Agency (EA) reporting to the Secretary of State for Environment, Food and Rural Affairs. The whole of the UK was affected, but the south-east most severely because of the lower rainfall and high water demand.</p>
            <p>When will London run out of water? How socially accepted is drought and associated water restrictions to the general public? When will water company groundwater sources begin to switch off? Questions like these are critical for drought management, but often the science is not sufficiently advanced to address them, and where it is, not fully integrated to satisfactorily answer them.</p>
            <p>The River Thames Basin is home to 13 Million people, considerable industry and valuable aquatic ecosystems all of which require the effective and sustainable management of the water environment in the basin to thrive. A thorough understanding of the hydrology of the basin is vital to underpin this management to ensure the best use of resources. This is particularly important given the twin pressures of increasing water consumption and climate change. The groundwater system of the Thames consists of around 12 aquifers most of which are not hydraulically connected, except via the River Thames and its tributaries. These aquifers are locally very important for water supply and their provision of base flow sustains the ecology of the river system in dry summer periods and droughts.</p>
            <p>To properly simulate the system then a good geological understanding has to be translated into a hydrogeological knowledge and then simulated. This is not a straight-forward task. The important elements of the system include: 3D geological understanding encapsulated into a geological model, dynamic model of the surface processes, groundwater and river systems along with a model of water supply (e.g. IRAS; Mastrosov et al., 2010). This will ultimately involve:</p>
            <ul>
              <li>Static data (updated as understanding increases);</li>
              <li>Data passed in a one way chain between models runs separately;</li>
              <li>Dynamically linked models to investigate feedbacks between different parts of the system.</li>
            </ul>
            <p>The aim would be to develop an integrated system that can address the question &ldquo;When will water company groundwater sources begin to switch off&rdquo; or similar.</p>
            <h3 id="references">References</h3>
            <ul>
              <li>CEH. (2012). Retrieved 9 Dec 2015, from <a href="http://www.ceh.ac.uk/news-and-media/news/drought-flood-dramatic-turnaround-uk-water-resources">From drought to flood: dramatic turnaround in UK water resources</a></li>
              <li>EA (2012). Review of the 2010-2012 drought and prospects for water resources in 2013. Environment Agency Report.</li>
              <li>Matrosov E.S., Harou, J.J. and Loucks D.P., 2010. A computationally efficient open-source water resource system simulator - Application to London and the Thames Basin. Environmental Modeling &amp; Software. Volume 26, Issue 12, December 2011, Pages 1599&ndash;1610.</li>
            </ul>
          </div>
          <p class="relatedDeliverables"><a href="#BestPractices"></a>, <a href="#TimeOntologyInOWL"></a>, <a href="#SSN"></a>, <a href="#CoverageInLinkedData"></a></p>
          <p class="relatedRequirements"><a href="#Linkability"></a>, <a href="#Provenance"></a>, <a href="#QualityPerSample"></a>, <a href="#NominalObservations"></a>, <a href="#3DSupport"></a>, <a href="#VirtualObservations"></a>, <a href="#DynamicSensorData"></a>, <a href="#UseInComputationalModels"></a>, <a href="#TimeSeries"></a> </p>
        </section>
        <section id="SoilDataApplications">
          <h3>Soil data applications</h3>
          <p class="contributor">Simon Cox (on behalf of Peter Wilson, Bruce Simons @ CSIRO)</p>
          <div class="expandOrCollapse" onclick="toggleVisibility(this)">&#9654; Full use case description (click to expand):</div>
          <div class="visible">
            <ol>
            <li>Farmer wants to know soil types and properties in an adjacent property which he is considering purchasing. ... the global soil community wants to be able to publish standardized soil site description/classification and soil analysis data which can then be collated (such as in the Harmonized World Soil Database) and used for modeling the spatial distribution of soil properties (digital soil mapping) (for example as part of the ISRIC 1kmSoilGirds or IUSS GlobalSoilMap projects). This would utilize our efforts with the SoilML (ISO28258) meta-model and the fully attributed implementable extension (currently ANZSoilML) to deliver the standardized soil data services.</li>
            <li>Compare similar soils and productivity responses to addition ... the IUSS GlobalSoilMap project wants to deliver high resolution estimates of functional soil properties as 90m raster data across the globe, constructed through bottom up, country delivery of standardized data. Our TERN Soil and Landscape Grid of Australia project has now developed the required data for Australia and we need to progress delivery as standardized services (using WMS,WFS and WCS) as a demonstrator of how to do this globally. The GlobalSoilMap project (maybe through the UN Global Soil Partnership, or via ISRIC the World Soil Data Centre) could develop a portal to allow discovery/display of all the contributing country data and to facilitate user (e.g. global climate or food security modelers) connection to the services from multiple sources.</li>
            <li>Agronomist needs observations of soil properties such as pH, Nitrogen, and soil-type and derive new properties using locally defined pedo-transfer functions ... Access observed and interpreted soil properties (by soil type and/or by spatial distribution) in a standard format that allows using algorithms/pedotransfer functions to use these properties to calculate additional interpreted soil properties.</li>
            </ol>
          </div>
          <p class="relatedDeliverables"><a href="#BestPractices"></a>, <a href="#SSN"></a>, <a href="#CoverageInLinkedData"></a></p>
          <p class="relatedRequirements"><a href="#Discoverability"></a>, <a href="#IdentifyCoverageType"></a>, <a href="#ObservationAggregations"></a>, <a href="#ObservedPropertyInCoverage"></a>, <a href="#QualityPerSample"></a>,  <a href="#SpaceTimeMultiScale"></a>, <a href="#VirtualObservations"></a>, <a href="#SensingProcedure"></a>, <a href="#HumansAsSensors"></a></p>
        </section>
        <section id="BushfireResponseCoordinationCentre">
          <h3>Bushfire response coordination centre</h3>
          <p class="contributor">Simon Cox (on behalf of Paul Box, Simon Cox and Ryan Fraser @ CSIRO)</p>
          <div class="expandOrCollapse" onclick="toggleVisibility(this)">&#9654; Full use case description (click to expand):</div>
          <div class="visible">
            <p>This user story covers a number of interrelated use cases:</p>
              <ul>
                <li>UC1 Search for place name</li>
                <li>UC2 Disambiguate place, based on type and provide</li>
                <li>UC3 Find the location of a place (centroid, representative location)&ndash; where is it?</li>
                <li>UC4 Find information about a place</li>
                <li>UC5 Find and use a suitable alternative geometric representations of a place &ndash; its shape, for a given scale and application</li>
                <li>UC6 Discover, access and use measurements relating to a place</li>
                <li>UC7.1 Discover related places - find synonyms</li>
                <li>UC7.2 Discover related places - topologically related places such as neighboring, or containing regions</li>
              </ul>
            <h4>User story</h4>
            <p>A bush-fire is underway in Blue Mountains NSW. An incident management team has been established, with an incident controller from NSW Fire and Rescue in charge, based in a coordination centre. She notices that the Twitter analytics feed has flagged a Tweet that mentions a fire in &lsquo;Springwood&rsquo;. The location of the Tweet shows on the incident map as being in the &lsquo;Blue Mountains&rsquo; &ndash; (this location is a geocode of place name used in the Tweeter&rsquo;s Profile). The watch officer enters &lsquo;Springwood&rsquo; [uc1] in a multi-gazetteer index and gets 41 hits for Springwood in Australia. She zooms to the Blue Mountains and sees there are 13 places called Springwood. These results include a school, a number of rural properties, and an official suburb named Springwood [uc2] near which most of the other places are located. The officer selects the suburb name in the National Gazetteer, and the map zooms to the bounding box for the selected place [uc3]. The controller wants to find more detailed information about the place and clicks on its identifier (a URI for the place). The user is provided with information about:</p>
            <ul>
              <li>Identity of the place and data sets/collection to which it belongs [uc4]&ndash; e.g. the national gazetteer.</li>
              <li>Available geometries for the place [uc5]- e.g. a feature-service for a gazetteer data source, hosted by Geosciences Australia.</li>
              <li>Existence of links to additional sources of information about the place [uc6] &ndash; e.g. links to data about the suburb provided by the local government.</li>
              <li>Synonyms for the place &ndash; alternative identifiers used for the place [uc7.1] &ndash; e.g. identifiers used for suburbs in the Australian Statistical Geographic Standard (ASGS).</li>
              <li>Related places [uc7.2] &ndash; e.g. a local government area that contains the suburb, or hydrological reporting units cover the suburb.</li>
              <li>information about related places e.g.:
                <ul>
                  <li>population profiles for the place codes using ASGS codes [uc7.1&amp;6]</li>
                  <li>nearby sensors providing hydro/met data that are in the containing hydrological reporting unit [7.2 &amp; 6]</li>
                </ul>
              </li>
            </ul>
            <p>An official report of the fire location now also appears on the screen, from a fire service operator on the ground. With the fire location now confirmed, the priority is to identify the areas at risk, and assess community impact, locate possible evacuation centers and set in place evacuation plans.</p>
            <p>A fire spread model has been run using reported fire location. An impact analysis and evacuation plan is being developed. The predicted fire spread polygon is shown on the incident map. To assess affected population the analyst needs to find population geography and data. [uc5]</p>
            <p>The Springwood place landing page has a link to get information about the data source [uc4]. This is the national gazetteer, which provides bounding box geometries only. This is not accurate enough for her analysis. Returning to the graph of linked resources, the analysis determines that the gazetteer entry has a synonym in the ASGS [uc7.1]. She clicks on this and sees it&rsquo;s the census geography for the same place (Springwood suburb) [uc4]. She finds the data source link which she discovers uses polygonal geometry and adds this as a service to her map.</p>
            <p>She is now able to see that Springwood suburb will be within the predicted fire polygon and will need to be evacuated. The analyst clicks linked information resources for Springwood (the synonym in the ASGS dataset) and a graph of related resources is displayed [uc 7.1, 7.2, 6]. This shows a link to a suburb profile based on the most recent national population and census data is available the analyst clicks on this and a query for predefined measurements (plus the place identifier) is passed to a census data cube service. The analyst visualizes and saves the result set locally.</p>
            <p>The analyst also notices that information resources are connected to Springwood (in the gazetteer dataset) [uc 7.1, 7.2, 6]. These include a link to a containing local government area (LGA) and links to LGA emergency management resources on the Website. This lists contact information and evacuation centers information which is used to inform development of the evacuation plan.</p>
          </div>
          <p class="relatedDeliverables"><a href="#BestPractices"></a>, <a href="#SSN"></a></p>
          <p class="relatedRequirements"><a href="#AvoidCoordinateTransformations"></a>, <a href="#Linkability"></a>, <a href="#SensorMetadata"></a>, <a href="#SpatialVagueness"></a>, <a href="#SSNExamples"></a></p>
        </section>
        <section id="ObservationsOnGeologicalSamples">
          <h3>Observations on geological samples</h3>
          <p class="contributor">Simon Cox</p>
          <div class="expandOrCollapse" onclick="toggleVisibility(this)">&#9654; Full use case description (click to expand):</div>
          <div class="visible">
            <p>Geological samples are retrieved from the field and then processed in the laboratory to determine various properties, including chemistry, mineralogy, age, and petrophysical properties like density, porosity, permeability.</p>
            <p>Samples obtained as part of economic activities, such as mineral exploration, are usually processed in commercial assay and chemistry labs. For QA/QC purposes, each batch of samples will have a number of control samples inserted, for which the concentration of particular chemical species are already known. For confidentiality reasons the location information associated with each sample is not provided to the lab, but must be re-attached during the interpretation phase. During processing, many derived samples will be generated by various physical and chemical procedures. In some cases the derived samples are strict sub-samples, whose intensive properties are intended to be the same as the parent. In other cases, the split is 'biased', with the derived sample intended to select a specific sub-sample, defined by a particular particle size, density, magnetic properties, etc. The link from the derived sample to the parent sample must be preserved, and the link from the parent to the location from which it was obtained also. In some cases the location is associated with another sampling artifact, such as a drill-hole or traverse or cruise, with the latter carrying the detailed location information.</p>
            <p>In a research context some samples have a particularly high-value, having been obtained by an expensive process (involving drilling or ships or spacecraft) or from a location that is hard to visit (remote, offshore, in space). These samples are sometimes sub-divided and distributed to multiple research teams or labs for different specialized observations. Each lab will run its own LIMS system, which will usually assign a local identifier for the sample. When the results of these observations are reported, it is necessary that observations from different labs can be correlated with each other, so that the complete picture around each sample can be assembled.</p>
            <p>These stories focus on sensing applications involving ex-situ sampling, where a location is visited and a specimen obtained using some sampling process, then transported to one or more laboratories where it is processed into one or more sub-samples and various observations made. Sample identity is usually key, and the relationships between samples, between samples and other artifacts of the sampling process, and also with other geographic features or locations. The sampling time and analysis and reporting time are all different.</p>
            <p>Similar process apply to botanical sampling, and to environmental sampling (water, air, dust).</p>
          </div>
          <p class="relatedDeliverables"><a href="#TimeOntologyInOWL"></a>, <a href="#SSN"></a></p>
          <p class="relatedRequirements"><a href="#DateTimeDuration"></a>, <a href="#DifferentTimeModels"></a>, <a href="#GeoreferencedData"></a>, <a href="#Linkability"></a>, <a href="#Provenance"></a>,  <a href="#SensorMetadata"></a>, <a href="#ExSituSampling"></a>, <a href="#SamplingTopology"></a>, <a href="#SensingProcedure"></a>, <a href="#SSNExamples"></a>, <a href="#HumansAsSensors"></a>, <a href="#TemporalReferenceSystem"></a></p>
        </section>
        <section id="SpatialSampling">
          <h3>Spatial sampling</h3>
          <p class="contributor">Simon Cox</p>
          <div class="expandOrCollapse" onclick="toggleVisibility(this)">&#9654; Full use case description (click to expand):</div>
          <div class="visible">
            <p>Most observations are made on <em>samples</em> that are selected to be somehow representative of the feature of ultimate interest which is being characterized. The sample may be statistical, or related to accessibility, or may be of a proxy phenomenon which can be related to the property of ultimate interest.</p>
            <p>In environmental observations, certain spatial distributions are commonly used across multiple disciplines, such as</p>
            <ul>
              <li>grids</li>
              <li>transects, cruises, flight-lines</li>
              <li>cross-sections</li>
              <li>physical sampling</li>
            </ul>
            <p>These may be related to each other (samples taken along a drill-hole, stations on a traverse, shots along a seismic section) and the relationships provide a kind of 'topology' of sampling which assists access and processing. Sampling features may also be associated with other organizational structures, such as cruises, field trips, campaigns, projects, missions, orbits, deployments, platforms, which are used for discovery and for navigation within a datasets. Sampling strategies are often combined with an observational procedure or instrument to define a standard 'protocol' for observations. The protocol may be identified by name.</p>
            <i>Additional comment by Rachel Heaven:</i>
            <p>The locations within a spatial distribution may have a different degree of certainty with respect to each other than the positional certainty of the spatial distribution as a whole e.g. the ends of a sampling traverse may be known in a national or global coordinate reference system to +/-5m accuracy; soil samples may be taken along the traverse at every 1m +/-0.01m interval, or species sightings that need to be re-visited may be described in real world terms such as "half way up the burn on the left hand bank". Similarly, measurements taken down a drill hole are known accurately in down hole depth with respect to the drilling datum, but less accurately in true vertical depth and with respect to a national vertical datum. If the hole deviates from vertical, the absolute location will be even more uncertain.</p>
          </div>
          <p class="relatedDeliverables"><a href="#BestPractices"></a>, <a href="#TimeOntologyInOWL"></a>, <a href="#SSN"></a>, <a href="#CoverageInLinkedData"></a></p>
          <p class="relatedRequirements"><a href="#CRSDefinition"></a>, <a href="#GeoreferencedData"></a>, <a href="#Linkability"></a>, <a href="#MobileSensors"></a>, <a href="#SensorMetadata"></a>, <a href="#SpaceTimeMultiScale"></a>, <a href="#SSNExamples"></a>, <a href="#SpatialVagueness"></a>, <a href="#SamplingTopology"></a>, <a href="#UncertaintyInObservations"></a>, <a href="#SpatialMetadata"></a></p>
        </section>
        <section id="SelectHierarchicalGeographicalRegionsForUseInDataAnalysisOrVisualisation">
          <h3>Select hierarchical geographical regions for use in data analysis or visualisation</h3>
          <p class="contributor">Bill Roberts (based on needs arising from Swirrl's own work)</p>
          <div class="expandOrCollapse" onclick="toggleVisibility(this)">&#9654; Full use case description (click to expand):</div>
          <div class="visible">
            <p>Statistical data is frequently referenced against geographical regions. A common requirement is to select a collection of non-overlapping regions with complete coverage of a 'parent' region (a 'Mutually Exclusive Collectively Exhaustive' - MECE - set). This might be used for data aggregation: given the population statistics for all council areas in Scotland, calculate the population of Scotland.</p>
            <p>Or it might be for data visualization: retrieve data on average house prices for all parliamentary constituencies in the UK, then combine this with polygons of the constituency boundaries and use it to draw a choropleth map.</p>
            <p>Although geographical data frequently includes 'contains' or 'within' relationships between larger and smaller areas, this is not sufficient for the above use cases. A larger area can be broken down into smaller areas in a variety of ways. Sometimes a combination of 'contains' relationships and knowledge of the 'type' of region can be enough: it may allow separating out a particular level in a geographical hierarchy. But that doesn't allow for cases where regions of a particular type don't have full coverage of the parent. An example is 'parishes' in England. The collection of all current parishes is non-overlapping, but it is not exhaustive. Some locations are not in any parish.</p>
            <p>The variation of administrative, statistical and political geography over time is also an issue. A particular division of a region into sub-regions may be valid only for a specific period. For example, council boundaries change from time to time. At any given time, there is a MECE set of council boundaries in a region, but the boundaries change occasionally, so if analyzing data on English councils from 2014, a different set of areas is required than would be needed for say 2012. 2012 might involve areas A,B,C,D,E,F whereas 2014 requires A,B,C,D,G,H. A similar issue arises when dividing Europe up into countries for example.</p>
            <p>These are common problems and there are probably many separate solutions already in active use. It would be useful however to have a standardized vocabulary to represent these kind of relationships, which would increase the interoperability of data analysis tools.</p>
          </div>
          <p class="relatedDeliverables"><a href="#BestPractices"></a>, <a href="#TimeOntologyInOWL"></a></p>
          <p class="relatedRequirements"><a href="#DateTimeDuration"></a>, <a href="#SpatialOperators"></a>, <a href="#SpatialRelationships"></a>, <a href="#ValidTime"></a></p>
        </section>
        <section id="SatelliteDataProcessing">
          <h3>Satellite data processing</h3>
          <p class="contributor">Kerry Taylor (informed by Matt Paget and Juan Guerschman, CSIRO)</p>
          <div class="expandOrCollapse" onclick="toggleVisibility(this)">&#9654; Full use case description (click to expand):</div>
          <div class="visible">
            <p><em>Vegetation fractional cover</em> is a key metric for monitoring land management, both in pastoral and agricultural settings. The aim is to estimate the fractions of photosynthetic and non-photosynthetic vegetation and the remaining fraction of bare soil. Fractional cover is computed from both Landsat and MODIS satellite surface reflectance products but calibration and validation via ground-based observations is also needed.</p>
            <p>The method for computing fractional cover was developed by comparing geo-aligned Landsat sensor and two MODIS-derived surface reflectance products. Scaling issues associated with different sensors and spatial resolutions were addressed, along with locally-measured effects of soil color and soil moisture.</p>
            <p>Source Data:</p>
            <ol>
              <li>Data from the TM (Landsat 5) and ETM+ (Landsat 7) sensors were downloaded from the United States Geological Survey (USGS) and corrected for atmosphere, topographic and bi-directional surface reflectance effects, standardized to a nadir view (i.e., satellite zenith angle is zero) and a solar zenith angle of 45&deg;)</li>
              <li>The MODIS 16-Day Nadir BRDF-Adjusted Reflectance product (MCD43A4) provides surface reflectance data as if they were taken from the nadir view and uses the solar angle calculated at local solar noon (Schaaf et al., 2002). MCD43A4 data were obtained from the Land Processes Distributed Active Archive Center (LPDAAC). These data were resampled to a geographic coordinate system.</li>
              <li>The MODIS surface reflectance products from the Terra satellite (MOD09) provide an estimate of the surface spectral reflectance as it would be measured at ground level in the absence of atmospheric scattering and absorption (Vermote et al, 2011; Vermote &amp; Kotchenova, 2008). The 8-day composite (MOD09A1) selects the best possible observation from an 8-day window, selected on the basis of high observation coverage, low viewing angle, cloud free and low aerosol loading, with a spatial resolution of 500 meters and seven spectral bands. The MOD09A1 surface reflectance data used here were subject to the same geometric processing as the MCD43A4 data.</li>
              <li>Field measurements of fractional cover were obtained at 913 sites across Australia (ABARES, 2013). Exactly 78 of those sites were sampled repeatedly, resulting in a total of 127 observations (a measurement taken at a given site on a specific date). The field observations did not systematically record soil color or soil moisture. Recent observations include soil color (Munsell Soil Color Charts, 1994), yet soil moisture is only subjectively measured (i.e., wet or dry). To derive these two soil properties consistently and objectively for the entire series we used information derived from other sources.</li>
            </ol>
            <p>As a result, a combined product is proposed which gives flexibility to use MODIS-derived estimates when large areas and high temporal repetition is desired, and Landsat-derived estimates when high spatial resolution is essential and/or when data prior to 2000 is needed. The algorithms needed for implementing a fractional cover product based on a blended Landsat-MODIS product are given <a href="#refGuerschman">[1]</a>.</p>
            <p>Now, this fractional cover coverage product over Australia is computed monthly and <a href="http://www.auscover.org.au/xwiki/bin/view/Product+pages/FC+Composites+MODIS+OEH">distributed by the NSW government</a>, where it is used for their <a href="http://www.environment.nsw.gov.au/dustwatch/">Dustwatch program</a> amongst other things. The Dustwatch program publishes monthly (PDF) reports of wind-related erosion and groundcover change.</p>
            <p><b id="refGuerschman">[1]</b> <a href="http://www.sciencedirect.com/science/article/pii/S0034425715000395">Guerschman et al, "Assessing the effects of site heterogeneity and soil properties when un-mixing photosynthetic vegetation, non-photosynthetic vegetation and bare soil fractions from Landsat and MODIS data", Remote Sensing of Environment, to appear 2015.</a>(Note that this paper provides several references to similar approaches to using multispectral coverages to determine vegetation).</p>
          </div>
          <p class="relatedDeliverables"><a href="#BestPractices"></a>, <a href="#SSN"></a>, <a href="#CoverageInLinkedData"></a></p>
          <p class="relatedRequirements"><a href="#CRSDefinition"></a>, <a href="#GeoreferencedData"></a>, <a href="#LinkingCRS"></a>, <a href="#MobileSensors"></a>, <a href="#IdentifyCoverageType"></a>, <a href="#Provenance"></a>, <a href="#SensorMetadata"></a>, <a href="#HumansAsSensors"></a>, <a href="#VirtualObservations"></a>, <a href="#SensingProcedure"></a>, <a href="#IndependenceOnReferenceSystems"></a>, <a href="#SpatialMetadata"></a>, <a href="#SSNProfiles"></a></p>
        </section>
        <section id="MarineObservationsEMII">
          <h3>Marine observations - eMII</h3>
          <p class="contributor">Simon Cox (on behalf of <a href="http://imos.org.au/emii.html">IMOS eMII</a>)</p>
          <div class="expandOrCollapse" onclick="toggleVisibility(this)">&#9654; Full use case description (click to expand):</div>
          <div class="visible">
            <section>
            <h4>Water column observations</h4>
            <p>I am a modeler and I want to find, filter and extract water column data that has been collected by profiling instruments (e.g. CTD, XBT, ARGO Floats, CTD&rsquo;s mounted on animals) so that I can prime my models. I want to easily be able to discover these data either by nominating the collection device type, or by nominating data parameters of interest. Once I can see which datasets meet my broad discovery criteria, and whilst still in the Portal, I want to be able to filter out data that is not of interest (e.g. those data outside of my region of interest, those not covering my features of interest, data which is unqualified, data below a certain depth and data from institutions I don&rsquo;t trust). I want to extract these data in a harmonized format (i.e. receive a single file of aggregated data expressed using common data fields, or in multiple files where each file has a similar syntactic and semantic encoding). I don&rsquo;t want to have to spend time transforming datasets with differing formats, nor guess which data fields in datasets from different sources are semantically covering the same information. I need to know what each field in the downloaded data represents.</p>
            </section>
            <section>
            <h4>Reconfiguring data ingestion process</h4>
            <p>I am an eMII Project Officer. I spend my day pulling data from partner services and transforming it so that it can be published through the 1-2-3 Portal. Just when I think I have tweaked all of the systems I need to in order to successfully ingest and publish provider data, the provider changes his/her data format, schema syntax or semantics. I then have to re-write or re-configure systems to obtain any new data. This happens very frequently. Even data providers who supply me with data from the same instruments use different data encodings and formats so I have to create individualized database tables to manage their incoming data. I would like data providers to agree on common schema for expressing similar data types and in collaboration develop some &lsquo;governance&rsquo; rules surrounding data publication to the Portal to reduce the time I spend on repetitive (and often unnecessary) tasks.</p>
            </section>
            <section>
            <h4>Observations along profiles</h4>
            <p>I am an eMII Project Officer and I manage multiple profile type datasets (e.g.: Argo profile, seals profile, XBT profile &hellip;). I want to be able to assess the quality of the data provided by partners before inclusion into the IMOS database and making it available through the IMOS portal. I want to set up a system whereby every new profile will be compared with existing profiles available in the IMOS database. The incoming profile will have to conform to a standard format so that it is relatively easy to implement and develop different set of rules to enable comparison with existing profiles. The system will send me an alert if one or multiple profiles failed some tests. Then I will be able to follow up more quickly with the corresponding partners to check if an error occurs during the processing of the data or if actually the data is correct. In the end, this process will enable an increase of the quality of the data provided to the end user.</p>
            </section>
          </div>
          <p class="relatedDeliverables"><a href="#BestPractices"></a>, <a href="#SSN"></a>, <a href="#CoverageInLinkedData"></a></p>
          <p class="relatedRequirements"><a href="#Discoverability"></a>, <a href="#MobileSensors"></a>, <a href="#ObservationAggregations"></a>, <a href="#ObservedPropertyInCoverage"></a>, <a href="#QualityPerSample"></a>, <a href="#SensorMetadata"></a>, <a href="#3DSupport"></a>, <a href="#SamplingTopology"></a></p>
        </section>
        <section id="MarineObservationsDataProviders">
          <h3>Marine observations - data providers</h3>
          <p class="contributor">Simon Cox (on behalf of <a href="http://imos.org.au/emii.html">IMOS eMII</a>)</p>
          <div class="expandOrCollapse" onclick="toggleVisibility(this)">&#9654; Full use case description (click to expand):</div>
          <div class="visible">
            <section>
            <h4>Atlas of Living Australia (ALA)</h4>
            <p>The ALA would like to integrate their data into the AODN. The ALA serves a range of Web services including WMS and corresponding ISO19115/MCP metadata. The ALA's use case is unusual in that it has tens of thousands of WMS layers and metadata records. This data cannot be added to version 2 of the AODN portal because it is too large to be harvested into the menu tree. ALA will need to be integrated with the 123 portal. Dave Martin's team has created a proof of concept integration. There would be a single metadata record for ALA, which will allow it to be discovered in Step 1 of the portal. After proceeding to Step 2 the user would see something like <a href="http://bl.ocks.org/nickdos/raw/119e3c16edeced2a9355/">this mockup</a>.</p>
            </section>
            <section>
            <h4>Reef Life Survey (RLS)</h4>
            <p>RLS have visited 2500+ coral and rocky reef sites and have conducted approx 6000 surveys across those sites. Each survey is conducted at a nominal &lsquo;site&rsquo;.
              <section>
              <h5>Methods 1 &amp; 2</h5>
              <p>During a survey observations are recorded of each of (1) vertebrate species abundance and biomass and (2) invertebrate species abundance.<p>
              </section>
              <section>
              <h5>Method 3</h5>
              <p>During a survey downward looking photographs are taken. The photographs are sequenced 1-20 for each site and are not geolocated. Subsequently, the photographs are scored at 5 points within each image. Each point is scored into one of 36 categories. Parameters are date, depth, resolution, major category, minor category, numerical value.</p>
              </section>
              <section>
              <h5>User Story 1</h5>
              <p>I&rsquo;m interested in ecosystems, reef assemblages and inter-species interactions. Show me what vertebrate and invertebrate species were found at this site (and any corresponding location/depth/habitat information).</p>
              <p>What I want to see:</p>
                <ul>
                  <li>By site, all vertebrate species abundance and biomass values (for each survey?)</li>
                  <li>By site, all invertebrate abundance values (for each survey?)</li>
                </ul>
              </section>
              <section>
              <h5>User Story 2</h5>
              <p>I have a large-scale question to ask about a particular species, for example, I am interested in broad distribution patterns of lobsters, plankton dispersal and settling rates. Show me all of the sites that were surveyed and the presence/absence of a particular species at each of those sites.</p>
              <p>What I want to see:</p>
                <ul>
                  <li>Across all sites that have been surveyed by RLS, the latitude, longitude, depth and presence/absence of a particular vertebrate or invertebrate species (no time component)</li>
                  <li>A time selector that shows changing or stable presence/absence values for repeat surveys at the same site</li>
                </ul>
              </section>
            </section>
            <section>
            <h4>Institute for Marine and Antarctic Studies (IMAS)</h4>
            <p>The IMAS use case includes a number of data collections. The main requirements is a mechanism to easily install the necessary applications. Ideally the AODN will host the applications (GeoNetwork, Geoserver etc) in the NeCTAR Cloud. This cloud based infrastructure will be managed by the AODN, but IMAS will have administrator accounts on each application and will be responsible for data content.</p>
            </section>
          </div>
          <p class="relatedDeliverables"><a href="#SSN"></a></p>
          <p class="relatedRequirements"><a href="#GeoreferencedData"></a>, <a href="#NominalObservations"></a>, <a href="#HumansAsSensors"></a>, <a href="#3DSupport"></a>, <a href="#SSNExamples"></a>, <a href="#UncertaintyInObservations"></a></p>
        </section>
        <section id="MarineObservationsDataConsumers">
          <h3>Marine observations - data consumers</h3>
          <p class="contributor">Simon Cox (on behalf of <a href="http://imos.org.au/emii.html">IMOS eMII</a>)</p>
          <div class="expandOrCollapse" onclick="toggleVisibility(this)">&#9654; Full use case description (click to expand):</div>
          <div class="visible">
            <section>
              <h4>Download Temperature and Velocity Data from NSW Moorings</h4>
              <p>The user would like to download temperature and velocity data from NSW moorings without downloading large numbers of NetCDF files, and without needing many clicks.</p><p>(Based on feedback from Robin Robertson).</p>
            </section>
            <section>
              <h4>Download Glider Data</h4>
              <p>The user would like an easy way to download the calibrated glider data. The user does not want the data delivered manually via drop box, or to face the difficulty of downloading NetCDF files in the way they are currently provided.</p><p>(Based on feedback from Robin Robertson).</p>
            </section>
            <section>
              <h4>Download ANMN Timor South moorings data</h4>
              <p>The user would like to download the ANMN Timor South moorings data - without needing 160 clicks.</p><p>(Based on feedback from Rebecca Cowley).</p>
            </section>
            <section>
              <h4>Download XBT data</h4>
              <p>The user would like to download XBT data from the portal. Not just the metadata - but the actual data.</p><p>(Based on feedback from Rebecca Cowley).</p>
            </section>
            <section>
              <h4>Download NRS data</h4><p>The user would like to be able to download NRS moorings data.</p><p>(Based on feedback by Peter Thompson)</p>
            </section>
            <section>
              <h4>Understandable by scientists from other fields</h4>
              <p>The user would like to be able to understand the portal even though she is from another field (e.g. genomics).</p><p>(Based on feedback from Levente Bodrossy).</p>
            </section>
            <section>
              <h4>Filter moorings data by deployment and instrument type</h4><p>The user would like to be able to filter moorings data by deployment and instrument type.</p><p>(Based on feedback from Craig Steinberg)</p>
            </section>
            <section>
              <h4>Download data as CSV</h4><p>The user would like to download sea surface temperature from the Bass Straight as a CSV file - not NetCDF</p><p>(Based on feedback from Andre Chiaradia)</p>
            </section>
            <section>
              <h4>Argo float data in a bounding box in the Southern Ocean.</h4><p>The user would like to download argo data from a particular region in the Southern Ocean.</p><p>(Based on feedback from Esmee)</p>
            </section>
            <p>Also see <a href="https://sites.google.com/site/aodntag/working-groups/use-cases/data-consumers">additional stories in un-edited emails</a>.</p>
          </div>
          <p class="relatedDeliverables"><a href="#BestPractices"></a>, <a href="#SSN"></a></p>
          <p class="relatedRequirements"><a href="#AvoidCoordinateTransformations"></a>, <a href="#DeterminableCRS"></a>, <a href="#LinkingCRS"></a>, <a href="#SensingProcedure"></a></p>
        </section>
        <section id="BuildingInformationManagementAndDataSharing">
          <h3>Building information management and data sharing</h3>
          <p class="contributor"> Linda van den Brink (with thanks to Henk Schaap - Gobar)</p>
          <div class="expandOrCollapse" onclick="toggleVisibility(this)">&#9654; Full use case description (click to expand):</div>
          <div class="visible">
            <p>The Dutch organization <a href="http://www.rws.nl/en">Rijkswaterstaat</a> is responsible for the practical execution of the public works and water management, including the construction and maintenance of waterways and roads, and flood protection and prevention in the Netherlands. The following is a use case about sharing Rijkswaterstaat information to support building processes.</p>
            <p>A part of a highway is in need of a new tarmac layer. This involves a lot of information sharing between the contractor (Rijkswaterstaat), the organization responsible for organizing the project and the organization responsible for carrying out the maintenance work. Building Information Management (BIM) is used for this and the data is published via a Webserver.</p>
            <p>The information being exchanged is asset management information, i.e. the location of the roads, tunnels, bridges, aqueducts, railway lines, surrounding terrain and water bodies involved (geometric information). In addition, non-spatial information is important, like the layers of material the road consists of, when it was last maintained etc. The spatial information is not only shared as 2D geometries: (detailed) 3D information is also used in the building process. The area involved contains about 9.000 relevant physical objects (about 100 different object types) and about 2.000 spatial objects that relate to the traffic network, about which information is exchanged.</p>
          </div>
          <p class="relatedDeliverables"><a href="#BestPractices"></a></p>
          <p class="relatedRequirements"><a href="#3DSupport"></a>, <a href="#DeterminableCRS"></a>, <a href="#LinkingCRS"></a>, <a href="#SpatialRelationships"></a>, <a href="#SpatialMetadata"></a>, <a href="#Validation"></a>, <a href="#DeterminableCRS"></a></p>
        </section>
        <section id="LandsatDataServices">
          <h3>Landsat data services</h3>
          <p class="contributor">Kerry Taylor (on behalf of Aaron Sedgmen of Geoscience Australia)</p>
          <div class="expandOrCollapse" onclick="toggleVisibility(this)">&#9654; Full use case description (click to expand):</div>
          <div class="visible">
            <p>Geoscience Australia (GA) maintains an archive of Landsat 5, 7 and 8 satellite imagery over the Australian continent from 1986 to present. The Australian Reflectance Grid 25 (ARG25) dataset produced from the Landsat archive is a collection of approximately 184,000 individual Landsat 5 and Landsat 7 scenes processed to the ARG25 specification. The ARG25 data are available to the public as file downloads and OGC Web services. The ARG25 collection can be searched using an OGC Catalog Service (CSW) containing ISO 19115 metadata for each scene. Note that the ARG25 data services are expected to be superseded by the Australian Geoscience Data Cube when it becomes publicly available.</p>
            <p>The ARG25 data services were promoted for use at the 2013 and 2014 Australian GovHack events, a competition aimed at mainstream (i.e. largely non geoscience/geospatial specialist) Web and application developers, to mashup, reuse, and remix open government data. The predominant use case for the ARG25 data at GovHack has been to perform spatiotemporal searches on the catalog for an area of interest, retrieve and subset/stitch scenes from the Web services, and provide an animated time sequence of the imagery to allow users to visualize changes in land cover over time, e.g. &ldquo;show me how my town has grown over the last 10 years&rdquo;.</p>
            <p>The relative complexity and richness of the OGC/ISO Web service APIs and data exchange formats presented a barrier to developers who were accustomed to lighter weight APIs and formats optimized for rapid integration and mashing up of data in mobile and browser based applications. As a result, uptake of the ARG25 data at GovHack was less than hoped for, and we see this as indicative of the mainstream Web app development community in the real world.</p>
            <p>GA has had much success with OGC and ISO standards in the sharing of data with government, research and industry partners and clients who are power users of spatial data and savvy in the standards. The less traditional users who are not spatial data specialists are less likely to access GA&rsquo;s data delivered using OGC and ISO standards, and this is a section of the user community that can potentially apply the data to highly innovative and entrepreneurial uses.</p>
            <p>GA does use proprietary and quasi-standard light weight data exchange formats (e.g. JSON) and Web APIs (e.g. ESRI RESTful API) for delivering some geospatial data, although, in accordance with government policy, it is GA&rsquo;s preference to adopt standards when possible to maximize interoperability.</p>
          </div>
          <p class="relatedDeliverables"><a href="#BestPractices"></a>, <a href="#TimeOntologyInOWL"></a>, <a href="#CoverageInLinkedData"></a></p>
          <p class="relatedRequirements"><a href="#DateTimeDuration"></a>, <a href="#Discoverability"></a>, <a href="#ReferenceDataChunks"></a>, <a href="#TimeSeries"></a>, <a href="#CoverageTemporalExtent"></a>, <a href="#TilingSupport"></a></p>
        </section>
        <section id="MetadataAndSearchGranularity">
          <h3>Metadata and search granularity</h3>
          <p class="contributor">Kerry Taylor (on behalf of Aaron Sedgmen of Geoscience Australia)</p>
          <div class="expandOrCollapse" onclick="toggleVisibility(this)">&#9654; Full use case description (click to expand):</div>
          <div class="visible">
            <p>Geoscience Australia (GA) collects and curates Australian national geoscience and geographic data sets, for use by government, industry and the community. Following is a typical requirement of a user of GA data - &ldquo;A mineral exploration company is collating published geological data for their mining lease. They are particularly interested in sample locations where gold ppm values are above 0.1ppm, occurring in greenstone, located on or near a fault line, and aged around 2.6 Ga&rdquo;.<p>
            <p>Users are able to perform structured searches for GA datasets at the collection level using catalogs of ISO 19115 metadata. The collection level metadata provides users with download links to the packaged datasets, and in limited instances, links for accessing the data via Web services and/or applications that provide visualization and GIS analysis capability.</p>
            <p>To perform fine grained searches within the dataset, such as feature level searches (e.g. show me sample locations in the OZCHEM database with gold ppm > 0.1), users must download the packaged datasets to their local environment and use their own tools to search through the data. Web services providing data access, e.g. WFS, and Web applications with GIS capability served by GA, e.g. the Rock Properties Explorer app, can provide some capability for searching within data collections.</p>
            <p>Usability of search and discovery systems would be enhanced by having standards that define the line between spatial data and metadata in the context of searches, and standard methodologies for searching across collection level and feature level data.</p>
          </div>
          <p class="relatedDeliverables"><a href="#BestPractices"></a>, <a href="#TimeOntologyInOWL"></a>, <a href="#SSN"></a></p>
          <p class="relatedRequirements"><a href="#DeterminableCRS"></a>, <a href="#DifferentTimeModels"></a>, <a href="#ExSituSampling"></a>, <a href="#NominalTemporalReferences"></a>, <a href="#SpatialVagueness"></a>, <a href="#3DSupport"></a>, <a href="#SpaceTimeMultiScale"></a>, <a href="#TemporalReferenceSystem"></a></p>
        </section>
        <section id="CrowdsourcedEarthquakeObservationInformation">
          <h3>Crowdsourced earthquake observation information</h3>
          <p class="contributor">Kerry Taylor (on behalf of Aaron Sedgmen of Geoscience Australia)</p>
          <div class="expandOrCollapse" onclick="toggleVisibility(this)">&#9654; Full use case description (click to expand):</div>
          <div class="visible">
            <p>Geoscience Australia (GA) collects earthquake observation information from the general public to improve its knowledge base of the impact of earthquakes across the Australian continent. An online HTML form is available on the GA Website for members of the public to report their experiences of earthquake events. Information collected includes the person&rsquo;s location (both geographic and within a building), time of event, perception of intensity and observed effects on the built environment. The information provided by the public is rated against the Modified Mercalli Intensity (MMI) Scale and is used to improve the accuracy of shake maps for earthquake prone regions of the country. This feeds into GA&rsquo;s understanding of exposure of the Australian built environment to natural disaster, and is used for disaster mitigation purposes including the determination of minimum building codes for various regions of the country.</p>
            <p>There is potential for GA to improve the efficiency by which it obtains earthquake observation information from the general public by leveraging popular social media services (such as Twitter), and adopting common standards and best practices for collecting crowdsourced information.</p>
          </div>
          <p class="relatedDeliverables"><a href="#BestPractices"></a>, <a href="#SSN"></a></p>
          <p class="relatedRequirements"> <a href="#Crawlability"></a>, <a href="#Discoverability"></a>, <a href="#DeterminableCRS"></a>, <a href="#EncodingForVectorGeometry"></a>, <a href="#LinkingCRS"></a>, <a href="#NominalObservations"></a>, <a href="#MultilingualSupport"></a>, <a href="#HumansAsSensors"></a>, <a href="#SpatialVagueness"></a>, <a href="#SensorMetadata"></a>, <a href="#GeoreferencedData"></a>, <a href="#ObservationAggregations"></a>, <a href="#MobileSensors"></a>, <a href="#3DSupport"></a>, <a href="#DynamicSensorData"></a>, <a href="#Streamable"></a>, <a href="#SpatialMetadata"></a>, <a href="#Linkability"></a>, <a href="#MachineToMachine"></a>, <a href="#SpatialOperators"></a>, <a href="#SSNExamples"></a></p>
        </section>
        <section id="TCGAMicroscopyImaging">
          <h3>TCGA / microscopy imaging</h3>
          <p class="contributor">Erich Bremer</p>
          <div class="expandOrCollapse" onclick="toggleVisibility(this)">&#9654; Full use case description (click to expand):</div>
          <div class="visible">
            <p>Studying the morphology of disease at the cellular and sub-cellular levels using high resolution tissue images is extremely important to help understand the nature of various cancers. <a href="http://cancergenome.nih.gov/">The Cancer Genome Atlas (TCGA)</a> contains over 32,000 de-identified whole-slide microscopy images (WSI) of over two dozen cancer types. These images can contain between 100K-1M nuclei each. Biomedical informatics researcher have developed (and continue to develop) software to automatically segment nuclei for study. The spatial features of each nucleus and groups of nuclei as it relates to other nuclei combined with other linked data such as other morphological features (crypts, ducts, etc.) and/or patient lab results are used in analyzing and categorizing tissues and patients into groups and in comparing such groupings to understand disease mechanisms in a particular cancer type as well as across cancer types.<p>
            <p>Representing nuclear segmentations is often done with binary masks or through polygon representations (e.g., the use of Well Known Text (WKT) representations) and also by leveraging work from the Geospatial community. However, in the case of nuclear segmentations, coordinate systems are 2D &amp; 3D Cartesian based. Although the majority of work is this area is 2D-based, a growing segment of microscopy is also 3D-based as the technology develops and become more sophisticated. As living tissue can change over time through growth, infection, cancer, damage, etc, (as well as its associated organism&rsquo;s various properties) it is important that spatial locations of features such as nuclear segmentation be also represented in a temporal aspect for proper comparisons.</p>
            <p>Samples of TCGA WSI data can be viewed at: <a href="http://cancer.digitalslidearchive.net">http://cancer.digitalslidearchive.net</a></p>
          </div>
          <p class="relatedDeliverables"><a href="#BestPractices"></a>, <a href="#CoverageInLinkedData"></a></p>
          <p class="relatedRequirements"><a href="#CoverageTemporalExtent"></a>, <a href="#DeterminableCRS"></a>, <a href="#LinkingCRS"></a>, <a href="#ReferenceDataChunks"></a>, <a href="#3DSupport"></a>, <a href="#Discoverability"></a>, <a href="#SpatialMetadata"></a>, <a href="#TilingSupport"></a>, <a href="#IndependenceOnReferenceSystems"></a>, <a href="#Provenance"></a>, <a href="#TimeSeries"></a>, <a href="#SpatialOperators"></a></p>
        </section>
        <section id="CropYieldEstimationUsingMultipleSatellites">
          <h3>Crop yield estimation using multiple satellites</h3>
          <p class="contributor">Kerry Taylor with Zheng-Shu Zhou, CSIRO</p>
          <div class="expandOrCollapse" onclick="toggleVisibility(this)">&#9654; Full use case description (click to expand):</div>
          <div class="visible">
            <p>Space-borne Synthetic Aperture Radar (SAR) observations are coming on line rapidly over the next few years. SAR signals are represented in 2D space but can be processed to point observations in 3D space, or to 3D triangulated surfaces using polarimetric and phase information. A compelling use case for SAR data is crop classification, i.e., identification of cereal crops (wheat, barley, rice etc.), through analysis of the radar backscatters and polarizations over the variable-height surface and volume of the crop.</p>
            <p>Multispectral (e.g. Landsat or MODIS) satellite imagery has been widely used to estimate vegetation cover and growth rates. It seems that combining SAR derived crop-type observations with Landsat-derived vegetation estimations could be used to estimate crop yields throughout the growth cycle. In principle, access to such data is open, but in practice it is difficult to get hold of and difficult to process for anyone other than well-connected scientists in developed nations. How could this data be opened up to a bigger community to help solve this problem, perhaps aided by reference to local knowledge?</p>
            <p>We might expect that this will be used to assist in logistics and market planning in developed countries, and for food security in developing and war-torn nations.</p>
          </div>
          <p class="relatedDeliverables"><a href="#BestPractices"></a>, <a href="#SSN"></a>, <a href="#CoverageInLinkedData"></a></p>
          <p class="relatedRequirements"><a href="#3DSupport"></a>, <a href="#AvoidCoordinateTransformations"></a>, <a href="#CoverageTemporalExtent"></a>, <a href="#LinkingCRS"></a>, <a href="#SSNLikeRepresentation"></a>, <a href="#VirtualObservations"></a>, <a href="#SensorMetadata"></a>, <a href="#GeoreferencedData"></a>, <a href="#Linkability"></a>, <a href="#SpaceTimeMultiScale"></a>, <a href="#UncertaintyInObservations"></a>, <a href="#QualityPerSample"></a>, <a href="#ObservedPropertyInCoverage"></a>, <a href="#IdentifyCoverageType"></a>, <a href="#ReferenceDataChunks"></a>, <a href="#UseInComputationalModels"></a>, <a href="#Provenance"></a>, <a href="#TimeSeries"></a>, <a href="#CRSDefinition"></a>, <a href="#TimeSeries"></a>, <a href="#SpatialOperators"></a>, <a href="#SSNExamples"></a></p>
        </section>
        <section id="EnablingCrossdomainSharingAndReuseOfGeospatialMetadata">
          <h3>Enabling cross-domain sharing and re-use of geospatial metadata</h3>
          <p class="contributor">Andrea Perego, <a href="https://ec.europa.eu/jrc/">European Commission, Joint Research Centre (JRC)</a></p>
          <div class="expandOrCollapse" onclick="toggleVisibility(this)">&#9654; Full use case description (click to expand):</div>
          <div class="visible">
            <p><a href="https://joinup.ec.europa.eu/asset/dcat_application_profile/">DCAT-AP</a> (DCAT application profile for data portals in Europe) is a metadata interchange format, based on and compliant with the <a href="http://www.w3.org/TR/vocab-dcat/">W3C Data Catalog vocabulary (DCAT)</a>, designed to ensure cross-domain and cross-border interoperability across European data portals.</p>
            <p>In order to achieve this, DCAT-AP consists of a "core" profile, including a set of metadata elements commonly used across domains, whereas domain-specific requirements are addressed by a set of "extensions". One of them, referred to as <a href="https://joinup.ec.europa.eu/node/139283">GeoDCAT-AP</a>, is specifically designed to provide a DCAT-AP compliant representation of geospatial metadata. More precisely, GeoDCAT-AP extends DCAT-AP in order to cover the set of metadata elements corresponding to the union of the <a href="http://eur-lex.europa.eu/eli/reg/2008/1205"><abbr title="Infrastructure for Spatial Information in the European Community">INSPIRE</abbr> metadata schema</a> and the core profile of <a href="http://www.iso.org/iso/catalogue_detail.htm?csnumber=26020">ISO 19115:2003</a>.</p>
            <p>Methodologically, GeoDCAT-AP has been designed based on the following requirements:
            <ol>
              <li>Agree on mappings with metadata elements available in DCAT-AP (e.g., title, abstract, license, distributions)</li>
              <li>Define alignment with elements not available in DCAT-AP, by using, whenever possible, popular RDF vocabularies</li>
            </ol>
            <p>The requirement for point (2) was to identify an RDF representation of elements missing in DCAT-AP that can be re-used, if relevant, in other domains - as those concerning data quality (e.g., conformity, topological consistency) and granularity (e.g., spatial / temporal resolution), two notions not supported in DCAT-AP (nor in DCAT). This implied that, in many cases, there has been the need of relaxing the ISO 19115 specification whenever it was a barrier to re-use.</p>
            <p>Another key design principle was related to the fact that GeoDCAT-AP is not meant to be a replacement of ISO 19115 / 19139, but an alternative representation, built on a set of harmonized mappings, enabling sharing and re-use of geospatial metadata. For this reason, any ISO 19115-conformant metadata record could be transformed into a GeoDCAT-AP one, but the opposite was not a requirement.</p>
            <p>Issues identified during the development of GeoDCAT-AP, highlighted that the effective cross-domain and cross-platform sharing and re-use of geospatial metadata is undermined by the lack of best practices concerning:</p>
            <ul>
              <li>The use of HTTP URIs for geospatial data and metadata</li>
              <li>The representation of geometries, and for the specification of bounding boxes, centroids, etc.</li>
              <li>The representation of spatial and temporal coverage</li>
              <li>The specification of spatial and temporal reference systems</li>
              <li>The specification of spatial and temporal resolution</li>
              <li>The representation of data quality and lineage (provenance)</li>
              <li>Support for multilingual metadata</li>
              <li>Metadata profile-based content negotiation</li>
            </ul>
            <p>Related use cases:</p>
            <ul>
              <li><a href="#CombiningSpatialRDFDataForIntegratedQueryingInATriplestore"></a></li>
              <li><a href="#PublishingGeospatialReferenceData"></a></li>
              <li><a href="#ImprovingDiscoveryOfSpatialDataOnTheWeb"></a></li>
            </ul>
          </div>
          <p class="relatedDeliverables"><a href="#BestPractices"></a></p>
          <p class="relatedRequirements"><a href="#BoundingBoxCentroid"></a>, <a href="#Crawlability"></a>, <a href="#DateTimeDuration"></a>, <a href="#DifferentTimeModels"></a>, <a href="#Discoverability"></a>, <a href="#EncodingForVectorGeometry"></a>, <a href="#IndependenceOnReferenceSystems"></a>, <a href="#Linkability"></a>, <a href="#LinkingCRS"></a>, <a href="#NominalTemporalReferences"></a>, <a href="#MachineToMachine"></a>, <a href="#MultilingualSupport"></a>, <a href="#Provenance"></a>, <a href="#QualityPerSample"></a>, <a href="#SpatialMetadata"></a>, <a href="#TemporalReferenceSystem"></a>, <a href="#SpatialVagueness"></a>, <a href="#TemporalVagueness"></a>, <a href="#TimeSeries"></a>, <a href="#ValidTime"></a></p>
        </section>
        <section id="ImprovingDiscoveryOfSpatialDataOnTheWeb">
          <h3>Improving discovery of spatial data on the Web</h3>
          <p class="contributor">Andrea Perego, <a href="https://ec.europa.eu/jrc/">European Commission, Joint Research Centre (JRC)</a></p>
          <div class="expandOrCollapse" onclick="toggleVisibility(this)">&#9654; Full use case description (click to expand):</div>
          <div class="visible">
            <p><i>Use case based on <a href="http://inspire.ec.europa.eu/events/conferences/inspire_2014/pdfs/19.06_4_11.00_Adam_Iwaniak.pdf">work presented at INSPIRE 2014</a> by Adam Iwaniak (Wroclaw University of Environmental and Life Sciences, Poland)</i><p>
            <p>Geoportals offer effective discovery functionalities for specialists. However, as in most data portals, using basic free text search is usually far from being a satisfactory experience. Actually, users (both non-experts and specialists), when searching for data, are frequently making use of popular search engines as a first step to get to the data they are looking for.</p>
            <p>Improving free text search in (geo)data portals is unlikely to address this issue. Moreover, it would not help users who do not know in which portal(s) the relevant data are available. Users will keep on using in any case search engines for this purpose.</p>
            <p>An option would be optimizing geoportals for Web discovery, by implementing consistently SEO (Search Engine Optimization) techniques. The advantages include (but are not limited to) the following:</p>
            <ul>
            <li>Increase visibility of spatial data - as well as of the geoportals giving access to them.</li>
            <li>Enabling queries not limited to free text fields (e.g., dataset title and description), but concerning also coordinates, spatial / temporal resolution, etc.</li>
            <li>Enabling users to find the data better satisfying their requirements (in terms of spatial and temporal coverage, granularity, formats, access and licensing conditions, etc.)</li>
            </ul>
            <p>Best practices for publishing geospatial metadata on the Web should be recommended. This includes, for example, standard serializations of geospatial metadata in formats and vocabularies used by search engines to index Web resources - e.g., RDFa, Microdata, Microformats</p>
            <p>Related use cases:</p>
              <ul>
                <li><a href="#ConsumingGeographicalDataInAWebApplication"></a></li>
                <li><a href="#EnablingCrossdomainSharingAndReuseOfGeospatialMetadata"></a></li>
              </ul>
          </div>
          <p class="relatedDeliverables"><a href="#BestPractices"></a></p>
          <p class="relatedRequirements"><a href="#Crawlability"></a>, <a href="#Discoverability"></a>, <a href="#DeterminableCRS"></a>, <a href="#EncodingForVectorGeometry"></a>, <a href="#IndependenceOnReferenceSystems"></a>, <a href="#Linkability"></a>, <a href="#MachineToMachine"></a>, <a href="#MultilingualSupport"></a>, <a href="#NominalTemporalReferences"></a>, <a href="#Provenance"></a>, <a href="#QualityPerSample"></a>, <a href="#SpatialMetadata"></a>, <a href="#SpatialVagueness"></a>, <a href="#TemporalVagueness"></a></p>
        </section>
        <section id="INSPIREComplianceUsingWebStandards">
          <h3>INSPIRE compliance using Web standards</h3>
          <p class="contributor">Erwin Folmer, <a href="http://www.kadaster.nl/web/english.htm">Dutch Cadastre</a> (via public-sdw-comments@w3.org)</p>
          <div class="expandOrCollapse" onclick="toggleVisibility(this)">&#9654; Full use case description (click to expand):</div>
          <div class="visible">
            <p>The European INSPIRE directive leads to the availability of many datasets with geographical aspects. Unfortunately the burden for data providers to comply with INSPIRE is high, which leads to the potential danger that the means (INSPIRE) becomes more important than the end (to have interoperable data). For many data providers the sole purpose is to state that they are INSPIRE compliant. This limited but understandable approach of data providers results in potential users being overlooked. Implementations of more user-friendly Web-related solutions will be very difficult and limited in the next few years, unless we find a (documented, proven and accepted) way to comply with INSPIRE by using Web standards (Linked Data).</p>
            <p>The Dutch Cadastre is a major provider of INSPIRE data in the Netherlands. It also maintains the portal <a href="https://www.pdok.nl/en/node">PDOK</a>, a central facility for making INSPIRE-compliant geographical data available in the Netherlands.</p>
          </div>
          <p class="relatedDeliverables"><a href="#BestPractices"></a></p>
          <p class="relatedRequirements"><a href="#Compatibility"></a></p>
        </section>
        <section id="EventlikeGeographicFeatures">
          <h3>Event-like geographic features</h3>
          <p class="contributor">Karl Grossner, Stanford Libraries</p>
          <div class="expandOrCollapse" onclick="toggleVisibility(this)">&#9654; Full use case description (click to expand):</div>
          <div class="visible">
            <p>Events are geographic phenomena. They comprise activity associated with particular locations on the Earth's surface, and their participants' locations and attributes over time are integral to their analysis as well as their indexing in information systems. Event participants may be human and agentive or not -including for example objects present at or resulting from activity, or natural phenomena like hurricanes or earthquakes.</p>
            <p>In addition to class or type, and the nature of their participants, essential descriptors for events include their static or dynamic location(s) and temporal extents, described with spatial and temporal reference systems. Location may be static or dynamic. Static events routinely modeled include crime, mortality, battles, performances, etc. Temporal extents may be modeled as instants or intervals, in cases aggregated as "multi-instants" or "multi-intervals."</p>
            <p>Although it is inherently difficult to model dynamic phenomena, there are many compelling reasons to do so. They can be conceived variously, as processes modeled as sequences of discrete events or as functions. Examples include: trajectories of people in commercial activity, journeys, battles, and biographical "life-paths."</p>
            <p>From a spatial perspective, many places are essentially dynamic and modeling these is a core challenge in historical and cultural heritage applications. The size and shape of political entities changes over time; they grow, shrink, split, merge, disappear, reappear, etc. The point being their spatial extent is directly bound to time. Historical periods are considered as 'place-at-period' - for example there is not a simple "Bronze Age" period, rather "Bronze Age Britain" and "Bronze Age Southern Levant."</p>
            <p>Taken together these share a requirement to consider space and time together.</p>
            <p>There is ongoing work in several research communities to arrive at better general models for representing and computing over such spatial-temporal and dynamic phenomena. One approach aims at 4-dimensional model of space-time (e.g. <a href ="http://www.cidoc-crm.org/docs/cidoc_crm_version_6.0.pdf">CIDOC-CRM E92-Spacetime Volume</a>). <a href="https://github.com/geojson/geojson-ld/issues?q=is%3Aissue+is%3Aclosed">Another</a> seeks to add a "when" component to the "where" (geometry) of GeoJSON and GeoJSON-LD.</p>
          </div>
          <p class="relatedDeliverables"><a href="#BestPractices"></a>, <a href="#TimeOntologyInOWL"></a></p>
          <p class="relatedRequirements"><a href="#DateTimeDuration"></a>, <a href="#4DModelSpaceTime"></a>, <a href="#SpaceTimeMultiScale"></a>, <a href="#TemporalReferenceSystem"></a>, <a href="#TemporalVagueness"></a>, <a href="#ValidTime"></a></p>
        </section>
        <section id="CreationOfVirtualObservationsfromAnalysisPhaseOfWeatherPredictionModel">
          <h3>Creation of &ldquo;virtual observations&rdquo; from &ldquo;analysis&rdquo; phase of weather prediction model</h3>
          <p class="contributor">Jeremy Tandy, <a href="http://www.metoffice.gov.uk/">Met Office</a></p>
          <div class="expandOrCollapse" onclick="toggleVisibility(this)">&#9654; Full use case description (click to expand):</div>
          <div class="visible">
            <p>National Meteorological Services (NMS), such as  <a href="http://www.metoffice.gov.uk/">Met Office</a>, maintain a network of weather observation sites within their region of responsibility in order, amongst other things, to provide input to their numerical weather prediction models. The cost of maintaining these weather observation sites means that their number is limited.</p>
            <p>Within the UK, and likely in other places too, there is a high demand for weather observations for specific locations. To meet this demand, the Met Office provides data for many more locations than the number of weather observation sites they maintain. In order to do this, &ldquo;virtual observations&rdquo; for these locations are derived from the &ldquo;analysis&rdquo; of the numerical weather prediction model. (&ldquo;Analysis&rdquo; is the term used to describe the initial state of the numerically modeled atmosphere from which the forecast is calculated; it incorporates real observations and provides a dynamically balanced representation of the atmosphere at a snapshot in time.)</p>
            <p>The metadata needed to provide context to a &ldquo;virtual observation" is identical to that for normal observations; albeit that the procedure used to create the observation involves a computational simulation rather than a physical sensor and stimulus. Clearly, it is important to provide information about the procedure used to create the observation so that &ldquo;real&rdquo; observations can be distinguished from &ldquo;virtual&rdquo; observations.</p>
          </div>
          <p class="relatedDeliverables"><a href="#BestPractices"></a>, <a href="#TimeOntologyInOWL"></a>, <a href="#SSN"></a></p>
          <p class="relatedRequirements"><a href="#Provenance"></a>, <a href="#VirtualObservations"></a>, <a href="#SensingProcedure"></a>, <a href="#UncertaintyInObservations"></a>, <a href="#SensorMetadata"></a>, <a href="#CRSDefinition"></a>, <a href="#GeoreferencedData"></a>, <a href="#ObservationAggregations"></a>, <a href="#SSNExamples"></a>, <a href="#TimeSeries"></a></p>
        </section>
        <section id="IncorporatingGeospatialDataIntoInteractive3DGraphicsOnTheWeb">
          <h3>Incorporating geospatial data (e.g. geo-referenced geometry) into interactive 3D graphics on the Web</h3>
          <p class="contributor">Stefan Lemme, DFKI/Saarland University</p>
          <div class="expandOrCollapse" onclick="toggleVisibility(this)">&#9654; Full use case description (click to expand):</div>
          <div class="visible">
            <p>This use case relates to <a href="#ConsumingGeographicalDataInAWebApplication"></a> and maintains the bridge to 3D-Web applications (without targeting the actual rendering process, which is out of scope for this Working Group).</p>
            <p>Visualizing geospatial data, such as geo-referenced 3D geometry of buildings, is a crucial capability even for Web applications. This use case targets Web developers that are using 3D graphics in their (existing) Web applications. To ease the pick up of 3D graphics for Web developers, since they are usually non-graphics experts, the <a href="https://www.w3.org/community/declarative3d/">Declarative 3D for the Web Architecture Community Group</a> of the <abbr title="World Wide Web Consortium">W3C</abbr> did previous work to determine the requirements, options, and use cases for integration of interactive 3D graphics capabilities into the <abbr title="World Wide Web Consortium">W3C</abbr> technology stack. Thereby, they propose a declarative approach to describe the 3D scene content as an extension of HTML5 rather than interfacing low-level APIs for rendering. Several implementations, such as <a href="http://www.web3d.org/x3d/what-x3d">X3D</a>/<a href="http://www.x3dom.org/">X3DOM</a> and <a href="http://xml3d.org/">XML3D</a> address this approach. However, Web developers are usually non-geospatial experts. Thus, to achieve a similar low-entrance barrier for them to incorporate geospatial data into interactive 3D graphics on the Web, any (Web)service providing geospatial data (including geometry) might consider a compatible content delivery format and API. Firstly, this implies none to only very little processing overhead on the client. In particular, when having mobile Web applications in mind an efficient content delivery (bandwidth-wise as well as client-side-processing-wise) is becoming important. Secondly, Web developers utilize established libraries, such as jQuery, to interface remote (RESTful) APIs. To ease interfacing geospatial services, Web developers tend to reuse their tools. Finally, existing best practices of the Web should be taken into account and applied to the access of geospatial data according, such as paging of result sets, caching of resources at several stages (server, browser), etc.</p>
          </div>
          <p class="relatedDeliverables"><a href="#BestPractices"></a></p>
          <p class="relatedRequirements"><a href="#Linkability"></a>, <a href="#Streamable"></a>, <a href="#Compressible"></a>, <a href="#3DSupport"></a>, <a href="#TilingSupport"></a></p>
        </section>
        <section id="SmartCities">
          <h3>Smart Cities</h3>
          <p class="contributor">Payam Barnaghi (on behalf of the EU FP7 CityPulse Project)</p>
          <div class="expandOrCollapse" onclick="toggleVisibility(this)">&#9654; Full use case description (click to expand):</div>
          <div class="visible">
            <p>The <a href="http://ict-citypulse.eu/">CityPulse project</a> has identified 101 smart city scenarios and related use-cases in cooperation with partner cities and the City Stakeholder Group in the project. The scenarios are made available online for the wider community to rank the use cases. The scenarios are <a href="http://www.ict-citypulse.eu/scenarios/">available online</a>. A Large set of semantically annotated datasets collected from partners of the CityPulse EU FP7 project and relevant resources for smart city data are <a href="http://iot.ee.surrey.ac.uk:8080/">also available</a>. The annotation tool for the datasets can be found <a href="http://iot.ee.surrey.ac.uk:8080/software.html">here</a>.</p>
            <p>In "101" Smart City use cases, each scenario is described in a short narrative and is ranked based on stakeholder needs and community groups by completing an online survey. The following lists top three ranked scenarios from the use cases. The complete list and details of the ranking and scenario evaluations are described in <a href="http://www.ict-citypulse.eu/page/sites/default/files/citypulse_d2.1_requirements_v1.0_0.pdf">M. Presser et al, Smart City Use-cases and Requirements</a>.</p>
            <ol>
              <li><b><a href="http://www.ict-citypulse.eu/scenarios/scenario/1">Context-aware multimodal real time travel planner</a>:</b> Tony needs to travel from home to work. Different means of transportation are generally available to him and include walking, biking, moped/scooter (own, shared, electric/petrol), car (own, pooling, ride sharing, taxi), public transportation (bus, metro, train, ferry/boat). Transportation can be optimized to Tony&rsquo;s preferred travel time, convenience (comfort, seating, crowdedness, safety, environmental quality), total cost, environmental impacts, scenic route, and personal health. Factors that impact this optimization include conditions of the different transportation modes (road, weather, maintenance works, traffic intensity, people density, parking availability, charging pole availability, pollution, air quality, irregularities in traffic schedules, road tolls, seating availability, accidents, availability of city bikes,...). Tony will be presented with his ideal route and will be able to select each leg of the journey based on concurrent and projected aggregated conditions. Recalculation of his chosen route(s) can happen if conditions or preferences change, and will adapt to any detour of own choice.</li>
              <li><a href="http://www.ict-citypulse.eu/scenarios/scenario/2"><b>Public parking space availability prediction:</b></a> Frank is having a hard time finding a public parking space. The city is increasingly reducing the amount of parking spaces per unit (e.g. apartments), and the difficulty of finding a parking space means Frank has to circulate his car looking for available parking spots. This is both annoying for him and results in negative environmental impacts (pollution, noise). By using multiple input sources of information a certain degree of probability of finding a parking spot in different locations can be provided, also including timed no parking zones, thus reducing circulation times. By knowing the current situation of other circulating cars, Frank can avoid congested hot spots by being rerouted towards different paths to even out the distribution. When Frank ends up leaving his spot he can also actively provide parking availability data via his smartphone.</li>
              <li><a href="http://www.ict-citypulse.eu/scenarios/scenario/3"><b>Stimulating green behavior:</b></a> The city council has an interest in making citizens aware of their own environmental impacts in an attractive way without forcing the issue. The council provides citizens and interested parties with a dashboard, so they can follow the "environmental heartbeat" of the city as well as their own impacts and contributions. Now citizens will be able to see and measure the environmental impact on the city as a whole as well as their own personal actions, indicating noise levels, air quality, waste index, recycling activities, fresh water quality, sea water quality etc. Anyone can now compare behavior and activities to that of other groups such as neighbors, neighborhoods or city districts, resulting in competitions between these to collect "Green Points". Not only the fun of competition is stimulating, but Green Points can be traded for rebates on public transport and other environmentally friendly actions which forms a "green economy" ("green coins").</li>
            </ol>
          </div>
          <p class="relatedDeliverables"><a href="#BestPractices"></a>, <a href="#SSN"></a></p>
          <p class="relatedRequirements"><a href="#Linkability"></a>, <a href="#DeterminableCRS"></a>, <a href="#DynamicSensorData"></a>, <a href="#HumansAsSensors"></a>, <a href="#MobileSensors"></a>, <a href="#ModelActuation"></a>, <a href="#NominalObservations"></a>, <a href="#LightweightAPI"></a>, <a href="#SSNExamples"></a></p>
        </section>
        <section id="ProvenanceOfClimateData">
          <h3>Provenance of climate data</h3>
          <p class="contributor">Bruce Bannerman (Australian Bureau of Meteorology)</p>
          <div class="expandOrCollapse" onclick="toggleVisibility(this)">&#9654; Full use case description (click to expand):</div>
          <div class="visible">
            <p>This use case is inspired by one of the conclusions of the UK Parliamentary inquiry into <a href="http://www.publications.parliament.uk/pa/cm201011/cmselect/cmsctech/444/44404.htm">ClimateGate</a> <i>"...It is not standard practice in climate science to publish the raw data and the computer code in academic papers. However, climate science is a matter of great importance and the quality of the science should be irreproachable. We therefore consider that climate scientists should take steps to make available all the data that support their work (including raw data) and full methodological workings (including the computer codes...)." </i> When a climate scientist publishes a paper, he needs to be able to refer reviewers to the source data and software source code that underpins the assertions made within the paper. Climate data are typically time-series and can be quite complex. Data can be sourced from a single National Meteorological and Hydrological Service (NMHS), or from a number of NMHS. Software source code is typically stored within a software revision control repository, such as git.</p>
            <p>Climate data may comprise all of the following:</p>
            <ol>
              <li>A time-series of observations of a specific phenomenon at a single sensor, including:
              <ul>
                <li>Estimations of the value of an observed property.</li>
                <li>A detailed understanding of the conditions under which the observation was made.<li>
                <li>Any changes that have been made to the observation (e.g. due to Quality Assurance processes).</li>
              </ul></li>
              <li>A collection of the time-series observations described at #1, of the same phenomenon, at the same time steps, perhaps in the form of a discrete coverage (time-series).</li>
              <li>A time-series representing the distribution of values of the collection of time-series observations represented as perhaps a:
              <ul>
                <li>Continuous two dimensional coverage.</li>
                <li>Continuous coverages as three dimensional cubes.</li>
                <li>Continuous coverage as n-dimensional models.</li>
                <li>An ensemble, comprising a number of models.</li>
                <li>The outputs of some analytical process as a time-series/coverage/cube/model.</li>
              </ul></li>
            </ol>
            <p>So using the description of climate data above, when a paper is published, the scientist needs to be able to refer viewers to:</p>
            <ul>
              <li>The analytical data which underpin the paper (perhaps the n-dimensional continuous coverage time-series at #3).</li>
              <li>The quality assured observations data that the continuous coverages at #3 were derived from at #2 and #1 (with details as to why each change to the Quality Assured observations described at #1 were made).</li>
              <li>The &lsquo;raw&rsquo; observations data described at #1, with details as to the conditions, sensors, etc., that the observation was made under.</li>
              <li>The version of the software source code that was used to manipulate the data at #1, #2, and #3.</li>
            </ul>
            <p>This is not a trivial data management problem to address, however its resolution will provide a solid data management grounding for future climate science and help address much spurious debate. Parts of the puzzle are currently being worked on, e.g.:</p>
            <ul>
              <li>The World Meteorological Organization (WMO) has published <a href="http://library.wmo.int/opac/index.php?lvl=notice_display&amp;id=16300">WMO No. 1131: Climate Data Management Systems Specifications</a> that provide a high level conceptual architecture to address much of the data management issues described above.</li>
              <li>WMO and OGC have developed and are developing relevant logical data models ISO 19156 Observations and Measurements, OGC Timeseries, and WMO METCE. The last two are based on Observations and Measurements.</li>
              <li>WMO has released a standard for describing Observations Metadata, called WIGOS Metadata.</li>
              <li>WMO is about to start work on a logical data model based on Observations and Measurements and Timeseries for describing WMO Observations. A future iteration of this model will need to cater for data provenance.</li>
              <li>W3C has developed PROV-O, which has considerable potential for describing data provenance.</li>
            </ul>
            <p>The missing part is: How can the provenance of the collection of climate data and the software used to manipulate it be best modeled and in the future, found via the Internet? The resolution of this issue will be of relevance to many domains.</p>
          </div>
          <p class="relatedDeliverables"><a href="#BestPractices"></a>, <a href="#SSN"></a>, <a href="#CoverageInLinkedData"></a></p>
          <p class="relatedRequirements"><a href="#Discoverability"></a>, <a href="#ObservationAggregations"></a>, <a href="#ObservedPropertyInCoverage"></a>, <a href="#Provenance"></a>, <a href="#QualityPerSample"></a>, <a href="#SensorMetadata"></a>, <a href="#SensingProcedure"></a>, <a href="#SpatialMetadata"></a>, <a href="#SSNExamples"></a>, <a href="#3DSupport"></a>, <a href="#TimeSeries"></a>, <a href="#VirtualObservations"></a></p>
        </section>
        <section id="smod">
          <h3>Representing geospatial data in RDF</h3>
          <p class="contributor">Phil Archer on behalf of the SmartOpendata project</p>
          <div class="expandOrCollapse" onclick="toggleVisibility(this)">&#9654; Full use case description (click to expand):</div>
          <div class="visible">
            <p>Beginning in late 2013, the EU-funded <a href="http://www.smartopendata.eu/">SmartOpenData project</a> carried out a number of pilots examining the potential of Linked Data for environmental and rural issues, particularly in National Parks. One aspect of the project required parts of the European Union's <a href="http://inspire.ec.europa.eu/data-model/approved/r4618-ir/html/">INSPIRE data model</a> to be represented in RDF and used across the different pilots.</p>

            <p>The INSPIRE data model is large, complex, and designed for use in a Geospatial Information System and not for Linked Data. Initially, the model was followed directly, creating classes and properties that exactly matched those in the original INSPIRE model. However, this produced cumbersome RDF that was hard to use, was difficult to link to other data points, and offered no advantage over the original. It was using Linked Data for the sake of it.</p>
            <p>As a result, the decision was taken not to attempt to replicate the whole model in RDF but to follow a more Linked Data centric approach, re-using concepts wherever necessary but simplifying it where possible, and making maximum use of external URI sets. An important reference in this work was the <a href="https://ies-svn.jrc.ec.europa.eu/documents/25">Study on RDF and <abbr title="persistent identifiers">PID</abbr>s for INSPIRE</a> by Diederik Tirry and Danny Vandenbroucke. It summarized work by three experts: Clemens Portele, Linda van den Brink and Stuart Williams. The establishment of the <a href="http://inspire.ec.europa.eu/registry/">INSPIRE Registry</a>, that provides stable URIs for many of the code lists was also a key development.</p>
          <p>As a result of the work by the European Commission and the SmartOpenData project, a <a href="http://www.w3.org/2015/03/inspire/" title="INSPIRE Vocabularies">set of small RDF vocabularies</a>  is available that represents a subset of the INSPIRE model. The desire to see these extended by future projects is stated explicitly.</p>
          </div>
          <p class="relatedDeliverables"><a href="#BestPractices"></a>, <a href="#CoverageInLinkedData"></a></p>
          <p class="relatedRequirements"><a href="#Compatibility"></a>, <a href="#Linkability"></a>, <a href="#MultilingualSupport"></a></p>
        </section>
        <section id="ModellingInTheConstructionSector">
          <h3>Modelling in the construction sector</h3>
          <p class="contributor">Sander Stolk (Semmtech)</p>
          <div class="expandOrCollapse" onclick="toggleVisibility(this)">&#9654; Full use case description (click to expand):</div>
          <div class="visible">
            <p>In civil engineering and asset management settings, data from different domains exist alongside each other. Such data typically overlap and complement each other. Think of design data (CAD), geospatial data (GIS), and data for systems engineering (SE). These are produced by different software, and use different perspectives - although they are quite possibly about the same subject (e.g. a specific office building or road).</p>
            <p>Problems arise when combining data about a single subject from different perspectives, in an attempt to complement information from one with that of another. This means terminology is needed to capture that resources may be about the same subject but use different perspectives. For example, here are three example perspectives on the same subject - an office building:</p>
            <ol>
            <li><b>Real-world perspective</b>. One way of describing the office building is to identify it directly with a URI and detail its properties. Ontologies specifically geared to capturing real-life objects in such a way, using a real-world perspective, are typically called object type libraries (or OTLs).</li>
            <li><b>Chart perspective</b>. Another way of describing the office building is to have a set of coordinates and describe what those coordinates on the map represent. In other words, the information is not about the office building itself but about coordinates that represent the building and how we should interpret those coordinates. In such a case, the building is captured in a charted representation.</li>
            <li><b>Format perspective</b>. A third way of describing the office building could be by having it arranged in a format of which the exact semantics is not yet made explicit in the Semantic Web, such as content arranged according to an XML structure.</li>
            </ol>
            <p>The perspectives above are not exhaustive. What they exemplify is that vastly different perspectives of the world and its real-life objects exist. Resources that are about the same subject and are captured using the same perspective, or representation, can often be considered equal or identical. Attributes captured for the one can then be said to also hold for the other. Resources captured using different perspectives, however, cannot be deemed equals. The one resource is then, for example, a registration of the other.</p>
            <p>If differences in perspective are not identified and made explicit, an attempt at integrating data from different perspectives is likely to lead to false conclusions. For instance, that a tangible office building in the real world is also a vector of coordinates, and that it has a filled out table cell called 'shape'.
It is exactly such relations between resources, signaling differences in perspective (e.g. that one resource is a registration of another), that should be able to be captured using explicit and standardized properties.</p>
            <p>This problem is present in several projects in the construction domain where integration of data from different perspectives plays a role. An example is <a href="http://www.rws.nl/english/about-us/doing-business-with-rijkswaterstaat/v-con/index.aspx">V-Con</a>. However, data from these projects are currently not open.</p>
          </div>
          <p class="relatedDeliverables"><a href="#BestPractices"></a></p>
          <p class="relatedRequirements"><a href="#SubjectEquality"></a></p>
        </section>
        <!-- Template for use cases
        <section id="">
          <h3></h3>
          <p class="contributor"></p>
          <div class="expandOrCollapse" onclick="toggleVisibility(this)">&#9654; Full use case description (click to expand):</div>
          <div class="visible">
            <p></p>
          </div>
          <p class="relatedDeliverables"><a href="#BestPractices"></a>, <a href="#TimeOntologyInOWL"></a>, <a href="#SSN"></a>, <a href="#CoverageInLinkedData"></a></p>
          <p class="relatedRequirements"></p>
        </section>
        -->
      </section>
      <br>
      <section id="Requirements">
      <h2>Requirements</h2>
      <p>This chapter lists the requirements for the deliverables of the Working Group, in alphabetical order.</p>
        <p class="note">In some requirements the expression 'recommended way' is used. This means that a single best way of doing something is sought. It does not say anything about the form this recommended  way should have, or who should make the recommendation. A recommended way could be a formal recommendation or standard from an authoritative standards body like the OGC or W3C, but it could just as well be a more informal specification, as long as it is arguably the best way of doing something.</p>
      <section id="4DModelSpaceTime">
        <h3>4D model of space-time</h3>
        <p>It should be possible to represent spatial extent directly bound to time, e.g. journey trajectories.</p>
        <p class="relatedDeliverables"><a href="#TimeOntologyInOWL"></a></p>
        <p class="relatedUseCases"><a href="#EventlikeGeographicFeatures"></a>, <a href="#PublicationOfRawSubsurfaceMonitoringData"></a></p>
      </section> 
      <section id="AvoidCoordinateTransformations">
        <h3>Avoid coordinate transformations</h3>
        <p> Data consumers should be helped in avoiding coordinate transformations when spatial data from multiple sources are combined.</p>
        <p class="note">When geometric data from different sources have no shared Coordinate Reference System (CRS), a data consumer will have to transform the coordinates of at least one data source to another CRS to spatially combine the data. Such a transformation takes time and could introduce errors in the output, so it is preferable to avoid it. Having multiple CRSs to choose from, and different data publishers using common CRSs can help in avoiding coordinate transformations.</p>
        <p class="relatedDeliverables"><a href="#BestPractices"></a>, <a href="#CoverageInLinkedData"></a></p>
        <p class="relatedUseCases"> <a href="#ConsumingGeographicalDataInAWebApplication"></a>, <a href="#HarvestingLocalSearchContent"></a>, <a href="#EnablingPublicationDiscoveryAndAnalysisOfSpatiotemporalDataInTheHumanities"></a>, <a href="#UsingSpatialDataDuringEmergencyResponseOperations"></a>, <a href="#CombiningSpatialRDFDataForIntegratedQueryingInATriplestore"></a>, <a href="#DutchBaseRegistry"></a>, <a href="#BushfireResponseCoordinationCentre"></a>, <a href="#MarineObservationsDataConsumers"></a>, <a href="#CropYieldEstimationUsingMultipleSatellites"></a></p>
      </section>
      <section id="BoundingBoxCentroid">
        <h3>Bounding box and centroid</h3>
        <p>There should be a recommended way for publishing and requesting the bounding box and centroid of a spatial thing.</p>
        <p class="relatedDeliverables"><a href="#BestPractices"></a></p>
        <p class="relatedUseCases"><a href="#PublishingGeographicalData"></a>, <a href="#EnablingCrossdomainSharingAndReuseOfGeospatialMetadata"></a></p>
      </section> 
      <section id="Compatibility">
        <h3>Compatibility with existing practices</h3>
        <p>Standards or recommendations for spatial data on the Web should be compatible with existing methods of making spatial data available (like WFS, WMS, CSW, WCS) and with existing information models.</p>
        <p class="relatedDeliverables"><a href="#BestPractices"></a>, <a href="#SSN"></a>, <a href="#CoverageInLinkedData"></a></p>
        <p class="relatedUseCases"><a href="#PublishingGeographicalData"></a>, <a href="#UsingSpatialDataDuringEmergencyResponseOperations"></a>, <a href="#PublicationOfAirQualityDataAggregations"></a>, <a href="#INSPIREComplianceUsingWebStandards"></a>, <a href="#DisseminationOf3DGeologicalData"></a>, <a href="#ObservationsOnGeologicalSamples"></a>, <a href="#PublicationOfRawSubsurfaceMonitoringData"></a>, <a href="#SoilDataApplications"></a>, <a href="#SpatialSampling"></a>, <a href="#MarineObservationsEMII"></a>, <a href="#CreationOfVirtualObservationsfromAnalysisPhaseOfWeatherPredictionModel"></a>, <a href="#ProvenanceOfClimateData"></a>, <a href="#smod"></a></p>        
      </section>    
      <section id="Compressible">
        <h3>Compressibility</h3>
        <p>Spatial data on the Web should be compressible (for optimization of data transfer).</p>
        <p class="relatedDeliverables"><a href="#BestPractices"></a></p>
        <p class="relatedUseCases"><a href="#DutchBaseRegistry"></a>, <a href="#DrivingToWorkInTheSnow"></a>, <a href="#IncorporatingGeospatialDataIntoInteractive3DGraphicsOnTheWeb"></a></p>
      </section> 
      <section id="CoordinatePrecision">
        <h3>Coordinate precision</h3>
        <p>The use of precision that matches uncertainty in coordinate data should be facilitated and encouraged.</p>
        <p class="relatedDeliverables"><a href="#BestPractices"></a>, <a href="#CoverageInLinkedData"></a></p>
        <p class="relatedUseCases"><a href="#DutchBaseRegistry"></a>, <a href="#SpatialSampling"></a>, <a href="#EnablingPublicationDiscoveryAndAnalysisOfSpatiotemporalDataInTheHumanities"></a></p>
      </section>
      <section id="CoverageTemporalExtent">
        <h3>Coverage temporal extent</h3>
        <p>It should be possible to add temporal references to spatial coverage data.</p>
        <p class="relatedDeliverables"><a href="#CoverageInLinkedData"></a></p><a href="#PublicationOfRawSubsurfaceMonitoringData"></a>, <a href="#RealtimeWildfireMonitoring"></a>, <a href="#SatelliteDataProcessing"></a>, <a href="#SpatialSampling"></a>, <a href="#HabitatZoneVerification"></a>, 
        <p class="relatedUseCases"><a href="#CropYieldEstimationUsingMultipleSatellites"></a>, <a href="#MeteorologicalDataRescue"></a>, <a href="#PublishingCulturalHeritageData"></a>, <a href="#TCGAMicroscopyImaging"></a>, <a href="#LandsatDataServices"></a>, <a href="#DrivingToWorkInTheSnow"></a></p>
      </section>  
      <section id="Crawlability">
        <h3>Crawlability</h3>
        <p>Spatial data on the Web should be crawlable, allowing data to be found and indexed by external agents.</p>
        <p class="relatedDeliverables"><a href="#BestPractices"></a></p>
        <p class="relatedUseCases"><a href="#MeteorologicalDataRescue"></a>, <a href="#HarvestingLocalSearchContent"></a>, <a href="#ConsumingGeographicalDataInAWebApplication"></a>, <a href="#CrowdsourcedEarthquakeObservationInformation"></a>, <a href="#EnablingCrossdomainSharingAndReuseOfGeospatialMetadata"></a>, <a href="#ImprovingDiscoveryOfSpatialDataOnTheWeb"></a></p>
      </section>
      <section id="CRSDefinition">
        <h3>CRS definition</h3>
        <p>There should be a recommended way of referencing a Coordinate Reference System (CRS) with a HTTP URI, and to get useful information about the CRS when that URI is dereferenced.</p>
        <p class="note">Useful things to know about a CRS are the extent of its applicability and its units of measurement.</p>
        <p class="relatedDeliverables"><a href="#SSN"></a>, <a href="#BestPractices"></a></p>
        <p class="relatedUseCases"><a href="#DiachronicBurntScarMapping"></a>, <a href="#MeteorologicalDataRescue"></a>, <a href="#ImagesEGATimeSeriesOfAWaterCourse"></a>, <a href="#CropYieldEstimationUsingMultipleSatellites"></a>, <a href="#CreationOfVirtualObservationsfromAnalysisPhaseOfWeatherPredictionModel"></a></p>
      </section>
      <section id="DateTimeDuration">
        <h3>Date, time and duration</h3>
        <p>It should be possible to represent dates, time and duration.</p>
        <p class="relatedDeliverables"><a href="#TimeOntologyInOWL"></a></p>
        <p class="relatedUseCases"><a href="#DrivingToWorkInTheSnow"></a>, <a href="#EnablingPublicationDiscoveryAndAnalysisOfSpatiotemporalDataInTheHumanities"></a>, <a href="#EventlikeGeographicFeatures"></a>, <a href="#HarvestingLocalSearchContent"></a>, <a href="#IntelligentTransportationSystem"></a>, <a href="#LandsatDataServices"></a>, <a href="#MeteorologicalDataRescue"></a>, <a href="#ObservationsOnGeologicalSamples"></a>, <a href="#PublicationOfAirQualityDataAggregations"></a>, <a href="#SelectHierarchicalGeographicalRegionsForUseInDataAnalysisOrVisualisation"></a>, <a href="#UseOfAPlaceNameOntologyForGeo-parsingTextAndGeo-enablingSearches"></a>, <a href="#PublishingCulturalHeritageData"></a>, <a href="#ImagesEGATimeSeriesOfAWaterCourse"></a>, <a href="#EnablingCrossdomainSharingAndReuseOfGeospatialMetadata"></a></p>
      </section>
      <section id="DeterminableCRS">
        <h3>Determinable CRS</h3>
        <p>For users of geometric spatial data it should always be possible to determine which coordinate reference system (CRS) is used.</p>
        <p class="relatedDeliverables"><a href="#BestPractices"></a></p>
        <p class="relatedUseCases"><a href="#RealtimeWildfireMonitoring"></a>, <a href="#DiachronicBurntScarMapping">, </a> <a href="#HarvestingLocalSearchContent"></a>, <a href=""></a>, <a href="#LocatingAThing"></a>, <a href="#ConsumingGeographicalDataInAWebApplication"></a>, <a href="#EnablingPublicationDiscoveryAndAnalysisOfSpatiotemporalDataInTheHumanities"></a>, <a href="#IntegrationOfGovernmentalAndUtilityDataToEnableSmartGrids"></a>,<a href="#UsingSpatialDataDuringEmergencyResponseOperations"></a>, <a href="#CombiningSpatialRDFDataForIntegratedQueryingInATriplestore"></a>, <a href="#DutchBaseRegistry"></a>, <a href="#DrivingToWorkInTheSnow"></a>, <a href="#LinkedDataForTaxAssessment"></a>, <a href="#MarineObservationsDataConsumers"></a>, <a href="#BuildingInformationManagementAndDataSharing"></a>, <a href="#MetadataAndSearchGranularity"></a>, <a href="#CrowdsourcedEarthquakeObservationInformation"></a>, <a href="#TCGAMicroscopyImaging"></a>, <a href="#ImprovingDiscoveryOfSpatialDataOnTheWeb"></a>, <a href="#SmartCities"></a></p>
      </section>
      <section id="DifferentTimeModels">
        <h3>Different time models</h3>
        <p>It should be possible to represent data using different time models, such as geological time and non-Gregorian calendars.</p>
        <p class="relatedDeliverables"><a href="#TimeOntologyInOWL"></a></p>
        <p class="relatedUseCases"><a href="#MetadataAndSearchGranularity"></a>, <a href="#MeteorologicalDataRescue"></a>, <a href="#ObservationsOnGeologicalSamples"></a>, <a href="#UseOfAPlaceNameOntologyForGeo-parsingTextAndGeo-enablingSearches"></a>, <a href="#EnablingCrossdomainSharingAndReuseOfGeospatialMetadata"></a></p>
      </section>
      <section id="Discoverability">
        <h3>Discoverability</h3>
        <p>It should be easy to find spatial data on the Web, e.g. by means of metadata aimed at discovery. When spatial data are published on the Web, both humans and machines should be able to discover those data.</p>
        <p class="relatedDeliverables"><a href="#BestPractices"></a>, <a href="#CoverageInLinkedData"></a></p>
        <p class="relatedUseCases"><a href="#BushfireResponseCoordinationCentre"></a>, <a href="#ConsumingGeographicalDataInAWebApplication"></a>, <a href="#CropYieldEstimationUsingMultipleSatellites"></a>, <a href="#DisseminationOf3DGeologicalData"></a>, <a href="#DrivingToWorkInTheSnow"></a>, <a href="#EnablingPublicationDiscoveryAndAnalysisOfSpatiotemporalDataInTheHumanities"></a>, <a href="#HarvestingLocalSearchContent"></a>, <a href="#ImagesEGATimeSeriesOfAWaterCourse"></a>, <a href="#ImprovingDiscoveryOfSpatialDataOnTheWeb"></a>, <a href="#IntegrationOfGovernmentalAndUtilityDataToEnableSmartGrids"></a>, <a href="#IntelligentTransportationSystem"></a>, <a href="#LandsatDataServices"></a>, <a href="#MarineObservationsEMII"></a>, <a href="#MeteorologicalDataRescue"></a>, <a href="#MetadataAndSearchGranularity"></a>, <a href="#SoilDataApplications"></a>, <a href="#UsingSpatialDataDuringEmergencyResponseOperations"></a>, <a href="#TCGAMicroscopyImaging"></a>, <a href="#CrowdsourcedEarthquakeObservationInformation"></a>, <a href="#EnablingCrossdomainSharingAndReuseOfGeospatialMetadata"></a>, <a href="#ProvenanceOfClimateData"></a></p>
      </section>
      <section id="DynamicSensorData">
        <h3>Dynamic sensor data</h3>
        <p>It should be possible to represent near real-time streaming sensor measurements.</p>
        <p class="relatedDeliverables"><a href="#SSN"></a></p>
        <p class="relatedUseCases"><a href="#CrowdsourcedEarthquakeObservationInformation"></a>, <a href="#RealtimeWildfireMonitoring"></a>, <a href="#DrivingToWorkInTheSnow"></a>, <a href="#DroughtsInGeologicalComplexEnvironmentsWhereGroundwaterIsImportant"></a>, <a href="#PublicationOfRawSubsurfaceMonitoringData"></a>, <a href="#SmartCities"></a></p>
      </section>
      <section id="EncodingForVectorGeometry">
        <h3>Encoding for vector geometry</h3>
        <p>There should be a recommended way of encoding vector geometry (an expression of spatial data that uses coordinates) when such data are published on the Web.</p>
        <p class="relatedDeliverables"><a href="#BestPractices"></a></p>
        <p class="relatedUseCases"><a href="#PublishingGeographicalData"></a>, <a href="#ConsumingGeographicalDataInAWebApplication"></a>, <a href="#CombiningSpatialRDFDataForIntegratedQueryingInATriplestore"></a>, <a href="#IntelligentTransportationSystem"></a>, <a href="#INSPIREComplianceUsingWebStandards"></a>, <a href="#PublishingCulturalHeritageData"></a>, <a href="#CrowdsourcedEarthquakeObservationInformation"></a>, <a href="#EnablingCrossdomainSharingAndReuseOfGeospatialMetadata"></a>, <a href="#ImprovingDiscoveryOfSpatialDataOnTheWeb"></a></p>
      </section>
      <section id="ExSituSampling">
        <h3>Ex-situ sampling</h3>
        <p>It should be possible to represent ex-situ (remote) sampling or sensing.</p>
        <p class="relatedDeliverables"><a href="#SSN"></a></p>
        <p class="relatedUseCases"><a href="#MetadataAndSearchGranularity"></a>, <a href="#ObservationsOnGeologicalSamples"></a>, <a href="#HabitatZoneVerification"></a></p>
      </section>
    <section id="Georectification">
        <h3>Georectification</h3>
        <p>The coverage data model should consider the inclusion of metadata to allow georectification to an arbitrary grid.</p>
        <p class="relatedDeliverables"><a href="#CoverageInLinkedData"></a></p>
        <p class="relatedUseCases"><a href="#DiachronicBurntScarMapping"></a>, <a href="#RealtimeWildfireMonitoring"></a></p>
      </section>
      <section id="GeoreferencedData">
        <h3>Georeferenced spatial data</h3>
        <p>It should be possible to georeference spatial data.</p>
        <p class="relatedDeliverables"><a href="#SSN"></a>, <a href="#CoverageInLinkedData"></a></p>
        <p class="relatedUseCases"><a href="#DisseminationOf3DGeologicalData"></a>, <a href="#HabitatZoneVerification"></a>, <a href="#ImagesEGATimeSeriesOfAWaterCourse"></a>, <a href="#MeteorologicalDataRescue"></a>, <a href="#PublishingCulturalHeritageData"></a>, <a href="#SatelliteDataProcessing"></a>, <a href="#CropYieldEstimationUsingMultipleSatellites"></a>, <a href="#CrowdsourcedEarthquakeObservationInformation"></a>, <a href="#HabitatZoneVerification"></a>, <a href="#DrivingToWorkInTheSnow"></a>, <a href="#ImagesEGATimeSeriesOfAWaterCourse"></a>, <a href="#ObservationsOnGeologicalSamples"></a>, <a href="#SpatialSampling"></a>, <a href="#SatelliteDataProcessing"></a>, <a href="#MarineObservationsDataProviders"></a>, <a href="#PublicationOfRawSubsurfaceMonitoringData"></a>, <a href="#CreationOfVirtualObservationsfromAnalysisPhaseOfWeatherPredictionModel"></a>, <a href="#PublishingGeospatialReferenceData"></a></p>
      </section>
      <section id="HumansAsSensors">
        <h3>Humans as sensors</h3>
        <p>It should be possible to represent observations taken by human individuals or communities acting as sensors perceiving the environment.</p>
        <p class="relatedDeliverables"> <a href="#SSN"></a></p>
        <p class="relatedUseCases"><a href="#DrivingToWorkInTheSnow"></a>, <a href="#SatelliteDataProcessing"></a>, <a href="#MarineObservationsDataProviders"></a>, <a href="#CrowdsourcedEarthquakeObservationInformation"></a>, <a href="#PublicationOfRawSubsurfaceMonitoringData"></a>, <a href="#ObservationsOnGeologicalSamples"></a>, <a href="#SoilDataApplications"></a>, <a href="#SmartCities"></a>, <a href="#HabitatZoneVerification"></a></p>
      </section>
      <section id="IdentifyCoverageType">
        <h3>Identify coverage type</h3>
        <p>Many different types of coverage exist. When coverage data are published on the Web it should be easy to identify the coverage type.</p>
        <p class="relatedDeliverables"><a href="#CoverageInLinkedData"></a></p>
        <p class="relatedUseCases"><a href="#HabitatZoneVerification"></a>, <a href="#DiachronicBurntScarMapping"></a>, <a href="#RealtimeWildfireMonitoring"></a>, <a href="#DisseminationOf3DGeologicalData"></a>, <a href="#ImagesEGATimeSeriesOfAWaterCourse"></a>, <a href="#SoilDataApplications"></a>, <a href="#SatelliteDataProcessing"></a>, <a href="#CropYieldEstimationUsingMultipleSatellites"></a></p>
      </section>
      <section id="IndependenceOnReferenceSystems">
        <h3>Independence on reference systems</h3>
        <p>Standards or recommendations for spatial data on the Web should be independent on the reference systems that are used for data.</p>
        <p class="note">This requirement reflects that spatial data incorporate geographical data, but can also be data that are not directly related to Earth or its scale.</p>
        <p class="relatedDeliverables"><a href="#BestPractices"></a>, <a href="#CoverageInLinkedData"></a>, <a href="#SSN"></a></p>
        <p class="relatedUseCases"><a href="#LocatingAThing"></a>, <a href="#ConsumingGeographicalDataInAWebApplication"></a>, <a href="#PublishingCulturalHeritageData"></a>, <a href="#EnablingPublicationDiscoveryAndAnalysisOfSpatiotemporalDataInTheHumanities"></a>, <a href="#SatelliteDataProcessing"></a>, <a href="#TCGAMicroscopyImaging"></a>, <a href="#EnablingCrossdomainSharingAndReuseOfGeospatialMetadata"></a>, <a href="#ImprovingDiscoveryOfSpatialDataOnTheWeb"></a></p>
      </section>
      <section id="LightweightAPI">
        <h3>Lightweight API</h3>
        <p>Show how the SSN ontology can be applied in the context of lightweight needs for the Internet of Things (IoT).</p>
        <p class="relatedDeliverables"><a href="#SSN"></a></p>
        <p class="relatedUseCases"><a href="#DrivingToWorkInTheSnow"></a>, <a href="#SmartCities"></a></p>
      </section>
      <section id="Linkability">
        <h3>Linkability</h3>
        <p>Spatial data on the Web should be linkable (by explicit relationships between different data in different data sets), to other spatial data and to or from other types of data.</p>
        <p class="relatedDeliverables"><a href="#SSN"></a>, <a href="#BestPractices"></a></p>
        <p class="relatedUseCases"><a href="#BushfireResponseCoordinationCentre"></a>, <a href="#CropYieldEstimationUsingMultipleSatellites"></a>, <a href="#DiachronicBurntScarMapping"></a>, <a href="#DroughtsInGeologicalComplexEnvironmentsWhereGroundwaterIsImportant"></a>, <a href="#ObservationsOnGeologicalSamples"></a>, <a href="#OptimizingEnergyConsumptionProductionSalesAndPurchasesInSmartGrids"></a>, <a href="#RealtimeWildfireMonitoring"></a>, <a href="#SpatialSampling"></a>, <a href="#EnablingPublicationDiscoveryAndAnalysisOfSpatiotemporalDataInTheHumanities"></a>, <a href="#PublishingGeospatialReferenceData"></a>, <a href="#DutchBaseRegistry"></a>, <a href="#MeteorologicalDataRescue"></a>, <a href="#PublicationOfRawSubsurfaceMonitoringData"></a>, <a href="#SmartCities"></a>, <a href="#HabitatZoneVerification"></a>, <a href="#ImagesEGATimeSeriesOfAWaterCourse"></a>, <a href="#CrowdsourcedEarthquakeObservationInformation"></a>, <a href="#EnablingCrossdomainSharingAndReuseOfGeospatialMetadata"></a>, <a href="#ImprovingDiscoveryOfSpatialDataOnTheWeb"></a>, <a href="#smod"></a>, <a href="#IncorporatingGeospatialDataIntoInteractive3DGraphicsOnTheWeb"></a></p>
      </section>
      <section id="LinkingCRS">
      <h3>Linking geometry to CRS</h3>
      <p>There should be a recommended way of linking vector geometry/geometries to the Coordinate Reference System (CRS) that is used for positions in the geometry/geometries.</p>
      <p class="relatedDeliverables"><a href="#BestPractices"></a></p>
      <p class="relatedUseCases"><a href="#HarvestingLocalSearchContent"></a>, <a href="#LocatingAThing"></a>, <a href="#PublishingGeographicalData"></a>, <a href="#ConsumingGeographicalDataInAWebApplication"></a>, <a href="#EnablingPublicationDiscoveryAndAnalysisOfSpatiotemporalDataInTheHumanities"></a>, <a href="#UsingSpatialDataDuringEmergencyResponseOperations"></a>, <a href="#CombiningSpatialRDFDataForIntegratedQueryingInATriplestore"></a>, <a href="#DutchBaseRegistry"></a>, <a href="#DisseminationOf3DGeologicalData"></a>, <a href="#PublicationOfRawSubsurfaceMonitoringData"></a>, <a href="#LinkedDataForTaxAssessment"></a>, <a href="#SatelliteDataProcessing"></a>, <a href="#MarineObservationsDataConsumers"></a>, <a href="#BuildingInformationManagementAndDataSharing"></a>, <a href="#CrowdsourcedEarthquakeObservationInformation"></a>, <a href="#TCGAMicroscopyImaging"></a>, <a href="#CropYieldEstimationUsingMultipleSatellites"></a>, <a href="#EnablingCrossdomainSharingAndReuseOfGeospatialMetadata"></a></p>
      </section>
      <section id="MachineToMachine">
        <h3>Machine to machine</h3>
        <p>Standards or recommendations for spatial data on the Web should work well in machine to machine environments.</p>
        <p class="relatedDeliverables"><a href="#BestPractices"></a>, <a href="#SSN"></a></p>
        <p class="relatedUseCases"><a href="#LocatingAThing"></a>, <a href="#DrivingToWorkInTheSnow"></a>, <a href="#CrowdsourcedEarthquakeObservationInformation"></a>, <a href="#ImprovingDiscoveryOfSpatialDataOnTheWeb"></a></p>
      </section>
      <section id="MobileSensors">
        <h3>Mobile sensors</h3>
        <p>It should be possible to represent sensors that change their location, as well as the current location of the sensor at the observation time.</p>
        <p class="relatedDeliverables"><a href="#SSN"></a></p>
        <p class="relatedUseCases"><a href="#CrowdsourcedEarthquakeObservationInformation"></a>, <a href="#DrivingToWorkInTheSnow"></a>, <a href="#IntelligentTransportationSystem"></a>, <a href="#MarineObservationsEMII"></a>, <a href="#PublicationOfAirQualityDataAggregations"></a>, <a href="#SpatialSampling"></a>, <a href="#SatelliteDataProcessing"></a>, <a href="#HabitatZoneVerification"></a>, <a href="#SmartCities"></a>, <a href="#EnablingCrossdomainSharingAndReuseOfGeospatialMetadata"></a></p>
      </section>  
      <section id="ModelActuation">
        <h3>Model actuation</h3>
        <p>It should be possible to model actuation functions of sensing devices.</p>
        <p class="note">Actuation of a sensing device is its ability to change something in its environment upon receiving a signal.</p>
        <p class="relatedDeliverables"><a href="#SSN"></a></p>
        <p class="relatedUseCases"><a href="#DrivingToWorkInTheSnow"></a>, <a href="#IntelligentTransportationSystem"></a>, <a href="#OptimizingEnergyConsumptionProductionSalesAndPurchasesInSmartGrids"></a>, <a href="#SmartCities"></a></p>
      </section>
      <section id="MovingFeatures">
        <h3>Moving features</h3>
        <p>It should be possible to refer to features that change their location.</p>
        <p class="relatedDeliverables"><a href="#SSN"></a></p>
        <p class="relatedUseCases"><a href="#DrivingToWorkInTheSnow"></a>, <a href="#IntelligentTransportationSystem"></a></p>
      </section>
      <section id="MultilingualSupport">
        <h3>Multilingual support</h3>
        <p>All vocabularies that will be developed or revised should have annotation in multiple languages.</p>
        <p class="note">We assume that is technically possible to have human readable annotation in multiple languages in vocabularies for spatiotemporal data on the Web. With English being the default language, as many other languages as possible should be supported. This will mean that in such cases we will have to call upon WG members that are fluent in languages other than English to provide annotation.</p>
        <p class="relatedDeliverables"><a href="#BestPractices"></a>, <a href="#SSN"></a>, <a href="#CoverageInLinkedData"></a>, <a href="#TimeOntologyInOWL"></a></p>
        <p class="relatedUseCases"><a href="#MeteorologicalDataRescue"></a>, <a href="#CrowdsourcedEarthquakeObservationInformation"></a>, <a href="#EnablingCrossdomainSharingAndReuseOfGeospatialMetadata"></a>, <a href="#ImprovingDiscoveryOfSpatialDataOnTheWeb"></a>, <a href="#smod"></a></p>
      </section>
      <section id="MultipleCRS">
        <h3>Multiple CRSs</h3>
        <p>There should be a recommended way of publishing geometric data with multiple Coordinate Reference Systems (CRSs).</p>
        <p class="relatedDeliverables"><a href="#BestPractices"></a></p>
        <p class="relatedUseCases"><a href="#DutchBaseRegistry"></a>, <a href="#EnablingPublicationDiscoveryAndAnalysisOfSpatiotemporalDataInTheHumanities"></a>, <a href="#PublishingGeographicalData"></a></p>
      </section>
      <section id="NominalObservations">
        <h3>Nominal observations</h3>
        <p>It should be possible to represent qualitative and nominal observations.</p>
        <p class="relatedDeliverables"><a href="#SSN"></a></p>
        <p class="relatedUseCases"> <a href="#CrowdsourcedEarthquakeObservationInformation"></a>, <a href="#PublicationOfRawSubsurfaceMonitoringData"></a>, <a href="#SatelliteDataProcessing"></a>, <a href="#SoilDataApplications"></a>, <a href="#HabitatZoneVerification"></a>, <a href="#SmartCities"></a></p>
      </section>
    <section id="NominalTemporalReferences">
        <h3>Nominal temporal references</h3>
        <p>It should be possible to refer to time intervals by nominal temporal references (e.g. January, a named event in a calendar, a geological period, a dynastic period).</p>
        <p class="relatedDeliverables"><a href="#TimeOntologyInOWL"></a></p>
        <p class="relatedUseCases"><a href="#DrivingToWorkInTheSnow"></a>, <a href="#EnablingPublicationDiscoveryAndAnalysisOfSpatiotemporalDataInTheHumanities"></a>, <a href="#MetadataAndSearchGranularity"></a>, <a href="#MeteorologicalDataRescue"></a>, <a href="#PublishingCulturalHeritageData"></a>, <a href="#UseOfAPlaceNameOntologyForGeo-parsingTextAndGeo-enablingSearches"></a>, <a href="#ImprovingDiscoveryOfSpatialDataOnTheWeb"></a></p>
      </section>
      <section id="ObservationAggregations">
        <h3>Observation aggregations</h3>
        <p>It should be possible to represent aggregations of observations.</p>
        <p class="relatedDeliverables"><a href="#SSN"></a></p>
        <p class="relatedUseCases"><a href="#CrowdsourcedEarthquakeObservationInformation"></a>, <a href="#MarineObservationsEMII"></a>, <a href="#PublicationOfAirQualityDataAggregations"></a>, <a href="#PublicationOfRawSubsurfaceMonitoringData"></a>, <a href="#SoilDataApplications"></a>, <a href="#CreationOfVirtualObservationsfromAnalysisPhaseOfWeatherPredictionModel"></a>, <a href="#ProvenanceOfClimateData"></a></p>
      </section>
      <section id="ObservedPropertyInCoverage">
        <h3>Observed property in coverage</h3>
        <p>It should be possible to describe the observed property represented by a coverage.</p>
        <p class="relatedDeliverables"><a href="#CoverageInLinkedData"></a></p>
        <p class="relatedUseCases"><a href="#CropYieldEstimationUsingMultipleSatellites"></a>, <a href="#DisseminationOf3DGeologicalData"></a>, <a href="#MarineObservationsEMII"></a>, <a href="#MeteorologicalDataRescue"></a>, <a href="#SoilDataApplications"></a>, <a href="#ProvenanceOfClimateData"></a></p>
      </section>
      <section id="Provenance">
        <h3>Provenance</h3>
        <p>Ensure alignment of models or vocabularies for describing provenance that exist in the geospatial and Semantic Web domains. Examples are the W3C provenance ontology (PROV-O) and the OGC metadata specification (ISO-19115).</p>
        <p class="relatedDeliverables"><a href="#BestPractices"></a>, <a href="#SSN"></a>, <a href="#CoverageInLinkedData"></a>, <a href="#TimeOntologyInOWL"></a></p> 
        <p class="relatedUseCases"><a href="#CreationOfVirtualObservationsfromAnalysisPhaseOfWeatherPredictionModel"></a>, <a href="#CropYieldEstimationUsingMultipleSatellites"></a>, <a href="#DiachronicBurntScarMapping"></a>, <a href="#DroughtsInGeologicalComplexEnvironmentsWhereGroundwaterIsImportant"></a>, <a href="#HabitatZoneVerification"></a>, <a href="#MeteorologicalDataRescue"></a>, <a href="#ObservationsOnGeologicalSamples"></a>, <a href="#RealtimeWildfireMonitoring"></a>, <a href="#SatelliteDataProcessing"></a>, <a href="#ImagesEGATimeSeriesOfAWaterCourse"></a>, <a href="#TCGAMicroscopyImaging"></a>, <a href="#EnablingCrossdomainSharingAndReuseOfGeospatialMetadata"></a>, <a href="#ImprovingDiscoveryOfSpatialDataOnTheWeb"></a>, <a href="#ProvenanceOfClimateData"></a></p>
      </section>
      <section id="QualityPerSample">
        <h3>Quality per sample</h3>
        <p>It should be possible to describe properties of data quality (e.g. uncertainty) per data sample.</p>
        <p class="relatedDeliverables"><a href="#CoverageInLinkedData"></a></p>
        <p class="relatedUseCases"><a href="#CropYieldEstimationUsingMultipleSatellites"></a>, <a href="#MeteorologicalDataRescue"></a>, <a href="#DisseminationOf3DGeologicalData"></a>, <a href="#DroughtsInGeologicalComplexEnvironmentsWhereGroundwaterIsImportant"></a>, <a href="#MarineObservationsEMII"></a>, <a href="#SoilDataApplications"></a>, <a href="#ImagesEGATimeSeriesOfAWaterCourse"></a>, <a href="#EnablingCrossdomainSharingAndReuseOfGeospatialMetadata"></a>, <a href="#ImprovingDiscoveryOfSpatialDataOnTheWeb"></a>, <a href="#ProvenanceOfClimateData"></a></p>
      </section>
      <section id="ReferenceDataChunks">
        <h3>Reference data chunks</h3>
        <p>It should be possible to identify and reference chunks of data, e.g. for processing, citation, provenance, cataloging.</p>
        <p class="relatedDeliverables"><a href="#CoverageInLinkedData"></a></p>
        <p class="relatedUseCases"><a href="#CropYieldEstimationUsingMultipleSatellites"></a>, <a href="#DisseminationOf3DGeologicalData"></a>, <a href="#HabitatZoneVerification"></a>, <a href="#ImagesEGATimeSeriesOfAWaterCourse"></a>, <a href="#LandsatDataServices"></a>, <a href="#MeteorologicalDataRescue"></a>, <a href="#TCGAMicroscopyImaging"></a></p>
      </section>
      <section id="SamplingTopology">
        <h3>Sampling topology</h3>
        <p>It should be possible to represent topological relationships between observation samples, e.g. specimens located along a borehole or probe spots found on a polished section of rocks.</p>
        <p class="relatedDeliverables"><a href="#SSN"></a></p>
        <p class="relatedUseCases"><a href="#SpatialSampling"></a>, <a href="#MarineObservationsEMII"></a>, <a href="#PublicationOfRawSubsurfaceMonitoringData"></a>, <a href="#ObservationsOnGeologicalSamples"></a>, <a href="#ImagesEGATimeSeriesOfAWaterCourse"></a></p>
      </section>
      <section id="SensorMetadata">
        <h3>Sensor metadata</h3>
        <p>It should be possible to include metadata about the sensors producing the observations.</p>
        <p class="relatedDeliverables"><a href="#SSN"></a></p>
        <p class="relatedUseCases"><a href="#CropYieldEstimationUsingMultipleSatellites"></a>, <a href="#CrowdsourcedEarthquakeObservationInformation"></a>, <a href="#MeteorologicalDataRescue"></a>, <a href="#RealtimeWildfireMonitoring"></a>, <a href="#DiachronicBurntScarMapping"></a>, <a href="#IntegrationOfGovernmentalAndUtilityDataToEnableSmartGrids"></a>, <a href="#DrivingToWorkInTheSnow"></a>, <a href="#BushfireResponseCoordinationCentre"></a>, <a href="#ObservationsOnGeologicalSamples"></a>, <a href="#SpatialSampling"></a>, <a href="#SatelliteDataProcessing"></a>, <a href="#MarineObservationsEMII"></a>, <a href="#PublicationOfRawSubsurfaceMonitoringData"></a>, <a href="#HabitatZoneVerification"></a>, <a href="#ImagesEGATimeSeriesOfAWaterCourse"></a>, <a href="#CreationOfVirtualObservationsfromAnalysisPhaseOfWeatherPredictionModel"></a>, <a href="#ProvenanceOfClimateData"></a></p>
      </section>
      <section id="SensingProcedure">
        <h3>Sensing procedure</h3>
        <p>It should be possible to attach the procedural description of a sensing method.</p>
        <p class="relatedDeliverables"><a href="#SSN"></a></p>
        <p class="relatedUseCases"><a href="#SatelliteDataProcessing"></a>, <a href="#CreationOfVirtualObservationsfromAnalysisPhaseOfWeatherPredictionModel"></a>, <a href="#MeteorologicalDataRescue"></a>, <a href="#PublicationOfRawSubsurfaceMonitoringData"></a>, <a href="#MarineObservationsDataConsumers"></a>, <a href="#ObservationsOnGeologicalSamples"></a>, <a href="#SoilDataApplications"></a>, <a href="#HabitatZoneVerification"></a>, <a href="#ProvenanceOfClimateData"></a></p>
      </section>
    <section id="SpaceTimeMultiScale">
        <h3>Space-time multi-scale</h3>
        <p>It should be possible to represent and integrate data over spatial and temporal scales.</p>
        <p class="relatedDeliverables"><a href="#SSN"></a>, <a href="#TimeOntologyInOWL"></a></p>
        <p class="relatedUseCases"><a href="#CropYieldEstimationUsingMultipleSatellites"></a>, <a href="#ImagesEGATimeSeriesOfAWaterCourse"></a>, <a href="#IntelligentTransportationSystem"></a>, <a href="#MeteorologicalDataRescue"></a>, <a href="#SoilDataApplications"></a>, <a href="#SpatialSampling"></a>, <a href="#EnablingPublicationDiscoveryAndAnalysisOfSpatiotemporalDataInTheHumanities"></a>, <a href="#EventlikeGeographicFeatures"></a>, <a href="#MetadataAndSearchGranularity"></a>, <a href="#PublishingCulturalHeritageData"></a>, <a href="#PublicationOfRawSubsurfaceMonitoringData"></a>, <a href="#ProvenanceOfClimateData"></a></p>
      </section>      
      <section id="SpatialMetadata">
        <h3>Spatial metadata</h3>
        <p>There should be recommended ways for describing the spatial characteristics of data (data objects, data sets or data services), like:</p>
        <ul>
        <li>number of dimensions (1D, 2D, 3D)</li>
        <li>data type (raster or vector)</li>
        <li>Coordinate Reference System(s)</li>
        <li>spatial extent</li>
        <li>spatial resolution</li>
        <li>positioning system used for acquiring location</li>
        </ul>
        <p class="relatedDeliverables"><a href="#BestPractices"></a></p>
        <p class="relatedUseCases"><a href="#MeteorologicalDataRescue"></a>, <a href="#HarvestingLocalSearchContent"></a>, <a href="#PublishingGeographicalData"></a>, <a href="#ConsumingGeographicalDataInAWebApplication"></a>, <a href="#UsingSpatialDataDuringEmergencyResponseOperations"></a>, <a href="#CombiningSpatialRDFDataForIntegratedQueryingInATriplestore"></a>, <a href="#PublicationOfRawSubsurfaceMonitoringData"></a>, <a href="#IntelligentTransportationSystem"></a>, <a href="#ImagesEGATimeSeriesOfAWaterCourse"></a>, <a href="#SoilDataApplications"></a>, <a href="#LandsatDataServices"></a>, <a href="#MetadataAndSearchGranularity"></a>, <a href="#EnablingCrossdomainSharingAndReuseOfGeospatialMetadata"></a>, <a href="#ImprovingDiscoveryOfSpatialDataOnTheWeb"></a>, <a href="#BuildingInformationManagementAndDataSharing"></a>, <a href="#INSPIREComplianceUsingWebStandards"></a>, <a href="#TCGAMicroscopyImaging"></a>, <a href="#DisseminationOf3DGeologicalData"></a>, <a href="#CrowdsourcedEarthquakeObservationInformation"></a></p>
      </section>
      <section id="SpatialRelationships">
        <h3>Spatial relationships</h3>
        <p>There should be a recommended way for expressing spatial relationships between spatial entities. These relationships can be topological, mereological (part-whole), directional or distance related.</p>
        <p class="relatedDeliverables"><a href="#BestPractices"></a></p>
        <p class="relatedUseCases"><a href="#HabitatZoneVerification"></a>, <a href="#LocatingAThing"></a>, <a href="#PublishingGeographicalData"></a>, <a href="#EnablingPublicationDiscoveryAndAnalysisOfSpatiotemporalDataInTheHumanities"></a>, <a href="#SelectHierarchicalGeographicalRegionsForUseInDataAnalysisOrVisualisation"></a>, <a href="#UseOfAPlaceNameOntologyForGeo-parsingTextAndGeo-enablingSearches"></a>, <a href="#BuildingInformationManagementAndDataSharing"></a></p>
      </section>
      <section id="SpatialOperators">
        <h3>Spatial operators</h3>
        <p>There should be a recommended way for the definition and use of spatial operators. Spatial things can have spatial relations: topological relations, directional or distance relations. Operators based on these relations (e.g. 'Contains'. 'Intersects', 'Nearest', 'within a radius of') should be well defined and easy to use.</p>
        <p class="relatedDeliverables"><a href="#BestPractices"></a></p>
        <p class="relatedUseCases"><a href="#ConsumingGeographicalDataInAWebApplication"></a>, <a href="#EnablingPublicationDiscoveryAndAnalysisOfSpatiotemporalDataInTheHumanities"></a>, <a href="#SelectHierarchicalGeographicalRegionsForUseInDataAnalysisOrVisualisation"></a>, <a href="#MetadataAndSearchGranularity"></a>, <a href="#ImprovingDiscoveryOfSpatialDataOnTheWeb"></a>, <a href="#PublishingGeospatialReferenceData"></a>, <a href="#TCGAMicroscopyImaging"></a>, <a href="#CropYieldEstimationUsingMultipleSatellites"></a>, <a href="#CrowdsourcedEarthquakeObservationInformation"></a></p>
      </section>
      <section id="SpatialVagueness">
        <h3>Spatial vagueness</h3>
        <p>It should be possible for vague or informal expressions of locations or spatial relationships to be useful as spatial data.</p>
        <p>Examples of vague or informal expressions of locations are:</p>
        <ul>
          <li>At the bottom of the hillside</li>
          <li>Downtown Los Angeles</li>
          <li>London (has multiple definitions, so just the name is not precise)</li>
          <li>The southwest boundary of the Roman Empire</li>        
        </ul>
        <p>Examples of vague or informal expressions of spatial relationships are:</p>
        <ul>
          <li>Near ...</li>
          <li>Across the street from ...</li>
          <li>Upstairs</li>
          <li>At walking distance from ...</li>        
        </ul>
        <p class="relatedDeliverables"><a href="#BestPractices"></a>, <a href="#SSN"></a>, <a href="#CoverageInLinkedData"></a></p>
        <p class="relatedUseCases"><a href="#BushfireResponseCoordinationCentre"></a>, <a href="#MetadataAndSearchGranularity"></a>, <a href="#MeteorologicalDataRescue"></a>, <a href="#SpatialSampling"></a>, <a href="#CrowdsourcedEarthquakeObservationInformation"></a>, <a href="#PublishingCulturalHeritageData"></a>, <a href="#PublicationOfRawSubsurfaceMonitoringData"></a>, <a href="#UseOfAPlaceNameOntologyForGeo-parsingTextAndGeo-enablingSearches"></a>, <a href="#EnablingCrossdomainSharingAndReuseOfGeospatialMetadata"></a>, <a href="#ImprovingDiscoveryOfSpatialDataOnTheWeb"></a></p>
      </section>
     <section id="SSNLikeRepresentation">
        <h3>SSN-like representation</h3>
        <p>It should be possible to represent satellite data using the SSN model, including sensor descriptions.</p>
        <p class="relatedDeliverables"><a href="#CoverageInLinkedData"></a></p>
        <p class="relatedUseCases"><a href="#CropYieldEstimationUsingMultipleSatellites"></a>, <a href="#DiachronicBurntScarMapping"></a>, <a href="#RealtimeWildfireMonitoring"></a></p>
      </section>   
      <section id="SSNProfiles">
        <h3>SSN profiles</h3>
        <p>There should be a recommended way for defining profiles (constrained subsets) of the SSN model and for checking compliance of profiles against the SSN model.</p>
        <p class="relatedDeliverables"><a href="#SSN"></a></p>
        <p class="relatedUseCases"><a href="#SatelliteDataProcessing"></a></p>
      </section>
      <section id="SSNExamples">
        <h3>SSN usage examples</h3>
        <p>There should be examples of how the SSN ontology can be used together with other vocabularies.</p>
        <p class="relatedDeliverables"><a href="#SSN"></a></p>
        <p class="relatedUseCases"><a href="#IntegrationOfGovernmentalAndUtilityDataToEnableSmartGrids"></a>, <a href="#PublicationOfTransportCardValidationAndRechargingData"></a>, <a href="#PublicationOfRawSubsurfaceMonitoringData"></a>, <a href="#IntelligentTransportationSystem"></a>, <a href="#OptimizingEnergyConsumptionProductionSalesAndPurchasesInSmartGrids"></a>, <a href="#BushfireResponseCoordinationCentre"></a>, <a href="#ObservationsOnGeologicalSamples"></a>, <a href="#SpatialSampling"></a>, <a href="#MarineObservationsDataProviders"></a>, <a href="#CrowdsourcedEarthquakeObservationInformation"></a>, <a href="#CropYieldEstimationUsingMultipleSatellites"></a>, <a href="#CreationOfVirtualObservationsfromAnalysisPhaseOfWeatherPredictionModel"></a>, <a href="#SmartCities"></a>, <a href="#ProvenanceOfClimateData"></a></p>
      </section>       
      <section id="Streamable">
        <h3>Streamable data</h3>
        <p>Data should be streamable, a consumer should be able to do something meaningful before the end of the data message is received.</p>
        <p class="note">This could be considered a general requirement for data on the Web, but it is recorded here because spatial data often consist of large chunks of data.</p>
        <p class="relatedDeliverables"><a href="#BestPractices"></a></p>
        <p class="relatedUseCases"><a href="#ConsumingGeographicalDataInAWebApplication"></a>, <a href="#IncorporatingGeospatialDataIntoInteractive3DGraphicsOnTheWeb"></a></p>
      </section>
      <section id="SubjectEquality">
        <h3>Subject equality</h3>
        <p>There should be a recommended way to express that data based on different models are about the same real world spatial thing.</p>
        <p class="relatedDeliverables"><a href="#BestPractices"></a></p>
        <p class="relatedUseCases"><a href="#ModellingInTheConstructionSector"></a>, <a href="#UsingSpatialDataDuringEmergencyResponseOperations"></a></p>
      </section>
      <section id="3DSupport">
        <h3>Support for 3D</h3>
        <p>Standards or recommendations for spatial data on the Web should be applicable to three-dimensional data.</p>
        <p class="relatedDeliverables"><a href="#BestPractices"></a>, <a href="#SSN"></a>, <a href="#CoverageInLinkedData"></a></p>
        <p class="relatedUseCases"><a href="#DisseminationOf3DGeologicalData"></a>, <a href="#PublishingGeographicalData"></a>, <a href="#PublicationOfRawSubsurfaceMonitoringData"></a>, <a href="#UseOfAPlaceNameOntologyForGeo-parsingTextAndGeo-enablingSearches"></a>, <a href="#ImagesEGATimeSeriesOfAWaterCourse"></a>, <a href="#DroughtsInGeologicalComplexEnvironmentsWhereGroundwaterIsImportant"></a>, <a href="#BuildingInformationManagementAndDataSharing"></a>, <a href="#CrowdsourcedEarthquakeObservationInformation"></a>, <a href="#TCGAMicroscopyImaging"></a>, <a href="#MarineObservationsEMII"></a>, <a href="#MarineObservationsDataProviders"></a>, <a href="#CropYieldEstimationUsingMultipleSatellites"></a>, <a href="#MetadataAndSearchGranularity"></a>, <a href="#HabitatZoneVerification"></a>, <a href="#ProvenanceOfClimateData"></a>, <a href="#IncorporatingGeospatialDataIntoInteractive3DGraphicsOnTheWeb"></a></p>
      </section>
      <section id="TilingSupport">
        <h3>Support for tiling</h3>
        <p>Standards or recommendations for spatial data on the Web should support tiling (for raster and vector data). Tiling of spatial data can drastically improve the speed of data retrieval and allows having simple caches of data around the Web.</p>
        <p class="relatedDeliverables"><a href="#BestPractices"></a>, <a href="#CoverageInLinkedData"></a></p>
        <p class="relatedUseCases"><a href="#ConsumingGeographicalDataInAWebApplication"></a>, <a href="#IncorporatingGeospatialDataIntoInteractive3DGraphicsOnTheWeb"></a></p>
      </section>
      <section id="TimeDependentCRS">
        <h3>Time dependencies in CRS definitions</h3>
        <p>It should be possible for Coordinate Reference Systems to have time dependent components such as the point of origin.</p>
        <p class="relatedDeliverables"><a href="#BestPractices"></a>
        <p class="relatedUseCases"><a href="#LocatingAThing"></a>, <a href="#EnablingPublicationDiscoveryAndAnalysisOfSpatiotemporalDataInTheHumanities"></a>, <a href="#PublicationOfTransportCardValidationAndRechargingData"></a></p>
      </section>
      <section id="TemporalReferenceSystem">
        <h3>Temporal reference system</h3>
        <p>If a temporal reference is used, the definition of the temporal reference system (e.g. Unix date, Gregorian Calendar, Japanese Imperial Calendar, Carbon Date, Geological Date) should be referenceable online.</p>
        <p class="relatedDeliverables"><a href="#TimeOntologyInOWL"></a></p>
        <p class="relatedUseCases"><a href="#EventlikeGeographicFeatures"></a>, <a href="#IntelligentTransportationSystem"></a>, <a href="#MetadataAndSearchGranularity"></a>, <a href="#MeteorologicalDataRescue"></a>, <a href="#UseOfAPlaceNameOntologyForGeo-parsingTextAndGeo-enablingSearches"></a>, <a href="#ObservationsOnGeologicalSamples"></a>, <a href="#EnablingCrossdomainSharingAndReuseOfGeospatialMetadata"></a></p>
      </section>
      <section id="TemporalVagueness">
        <h3>Temporal vagueness</h3>
        <p>It should be possible to describe time points and intervals in a vague, imprecise manner. For example:</p>
        <ul>
          <li>An event happened at the second quarter of the 9th century (the calendar used for this fact is unknown).</li>
          <li>Something occurred in the afternoon of July 1st, 2011 (the time interval 'afternoon' is not precisely defined).</li>
          <li>A photo is known to be taken on a Christmas Day (the year is unknown).</li>
          <li>An event took place in the later part of the Jurassic (with 'later part' being imprecise, as opposed to 'Late Jurassic')</li>
        </ul>
        <p class="relatedDeliverables"><a href="#TimeOntologyInOWL"></a></p>
        <p class="relatedUseCases"><a href="#EnablingPublicationDiscoveryAndAnalysisOfSpatiotemporalDataInTheHumanities"></a>, <a href="#EventlikeGeographicFeatures"></a>, <a href="#PublishingCulturalHeritageData"></a>, <a href="#UseOfAPlaceNameOntologyForGeo-parsingTextAndGeo-enablingSearches"></a>, <a href="#EnablingCrossdomainSharingAndReuseOfGeospatialMetadata"></a>, <a href="#ImprovingDiscoveryOfSpatialDataOnTheWeb"></a></p>
      </section>
      <section id="TimeSeries">
        <h3>Time series</h3>
        <p>It should be possible to represent time series of data.</p>
        <p class="relatedDeliverables"><a href="#TimeOntologyInOWL"></a>, <a href="#CoverageInLinkedData"></a>, <a href="#SSN"></a></p>
        <p class="relatedUseCases"><a href="#CropYieldEstimationUsingMultipleSatellites"></a>, <a href="#DroughtsInGeologicalComplexEnvironmentsWhereGroundwaterIsImportant"></a>, <a href="#ImagesEGATimeSeriesOfAWaterCourse"></a>, <a href="#LandsatDataServices"></a>, <a href="#PublicationOfRawSubsurfaceMonitoringData"></a>, <a href="#CreationOfVirtualObservationsfromAnalysisPhaseOfWeatherPredictionModel"></a>, <a href="#ImagesEGATimeSeriesOfAWaterCourse"></a>, <a href="#TCGAMicroscopyImaging"></a>, <a href="#EnablingCrossdomainSharingAndReuseOfGeospatialMetadata"></a>, <a href="#ProvenanceOfClimateData"></a></p>
      </section>
      <section id="UncertaintyInObservations">
        <h3>Uncertainty in observations</h3>
        <p>It should be possible to represent uncertainty in observations.</p>
        <p class="relatedDeliverables"><a href="#SSN"></a></p>
        <p class="relatedUseCases"><a href="#CropYieldEstimationUsingMultipleSatellites"></a>, <a href="#MarineObservationsDataProviders"></a>, <a href="#MeteorologicalDataRescue"></a>, <a href="#PublicationOfRawSubsurfaceMonitoringData"></a>, <a href="#SpatialSampling"></a>, <a href="#CreationOfVirtualObservationsfromAnalysisPhaseOfWeatherPredictionModel"></a></p>
      </section>
      <section id="UpdateDatatypes">
        <h3>Update datatypes in OWL Time</h3>
        <p>OWL Time should be updated to align with the 2012 update of OWL datatypes and 2012 update of xsd datatypes</p>
        <p class="relatedDeliverables"><a href="#TimeOntologyInOWL"></a></p>
        <p class="relatedUseCases"><a href="#PublishingCulturalHeritageData"></a></p>
      </section>
      <section id="UseInComputationalModels">
        <h3>Use in computational models</h3>
        <p>It should be possible to use coverage data as input or output of computational models, e.g. geological models.</p>
        <p class="relatedDeliverables"><a href="#CoverageInLinkedData"></a></p>
        <p class="relatedUseCases"><a href="#CropYieldEstimationUsingMultipleSatellites"></a>, <a href="#DisseminationOf3DGeologicalData"></a>, <a href="#DroughtsInGeologicalComplexEnvironmentsWhereGroundwaterIsImportant"></a></p>
      </section>
      <section id="Validation">
        <h3>Validation</h3>
        <p>It should be possible to validate spatial data on the Web; to automatically detect conflicts with standards or definitions.</p>
        <p class="note">Although data validation is a general topic, this requirement is included because validation of spatial data requires specialist spatial techniques.</p>
        <p class="relatedDeliverables"><a href="#BestPractices"></a></p>
        <p class="relatedUseCases"><a href="#PublishingGeospatialReferenceData"></a>, <a href="#PublishingCulturalHeritageData"></a>, <a href="#BuildingInformationManagementAndDataSharing"></a></p>
      </section>
    <section id="ValidTime">
        <h3>Valid time</h3>
        <p>Ensure alignment with existing methods for expressing the time in which data are valid (e.g. dcterms:valid). <!--<a href="http://purl.org/dc/terms/valid">http://purl.org/dc/terms/valid</a>)--></p>
        <p class="note">This requirement does not mean that the way expressions of time can be used is considered in scope for the Time Ontology, but it does mean that being able to express temporal validity using the Time Ontology is considered important for location data.</p>
        <p class="relatedDeliverables"><a href="#TimeOntologyInOWL"></a></p>
        <p class="relatedUseCases"><a href="#UseOfAPlaceNameOntologyForGeo-parsingTextAndGeo-enablingSearches"></a>, <a href="#ImagesEGATimeSeriesOfAWaterCourse"></a>, <a href="#SelectHierarchicalGeographicalRegionsForUseInDataAnalysisOrVisualisation"></a>, <a href="#EventlikeGeographicFeatures"></a>, <a href="#EnablingCrossdomainSharingAndReuseOfGeospatialMetadata"></a></p>
      </section>
      <section id="VirtualObservations">
        <h3>Virtual observations</h3>
        <p>It must be possible to represent synthetic observations made by computational procedures or inference.</p>
        <p class="relatedDeliverables"><a href="#SSN"></a></p>
        <p class="relatedUseCases"><a href="#DroughtsInGeologicalComplexEnvironmentsWhereGroundwaterIsImportant"></a>, <a href="#SoilDataApplications"></a>, <a href="#SatelliteDataProcessing"></a>, <a href="#CropYieldEstimationUsingMultipleSatellites"></a>, <a href="#CreationOfVirtualObservationsfromAnalysisPhaseOfWeatherPredictionModel"></a>, <a href="#PublicationOfRawSubsurfaceMonitoringData"></a>, <a href="#ProvenanceOfClimateData"></a></p>
      </section>
      <!-- Template for requirements:
       <section id="">
        <h3></h3>
        <p></p>
        <p class="relatedDeliverables"><a href=""></a>, <a href=""></a></p>
        <p class="relatedUseCases"><a href=""></a>, <a href=""></a></p>
      </section>
      -->
      <!-- Template for issues:
       <div class="issue" data-number="XX">
          <p>This requirement needs clarification.</p>
       </div>
      --> 
    </section>
    <section id="RequirementsByDeliverable">
      <h2>Requirements by deliverable</h2>
      <p>For convenience, this chapter lists requirements grouped by Working Group deliverable.</p>
<!--      <div id="table1"></div> -->
    </section>
    <section id="ack">
      <h2>Acknowledgments</h2>
      <p>The editors are grateful for all contributions made to this document. In particular we thank the people that have contributed use cases (their names are mentioned with each use case) and the Working Group members that helped in mining and refining the requirements.</p>
<!--      <p>Copyright &copy; 2015 by <a href="http://www.dfki.de/web/forschung/asr">DFKI</a> for examples in <a href="#IncorporatingGeospatialDataIntoInteractive3DGraphicsOnTheWeb">
Incorporating geospatial data into interactive 3D graphics on the Web</a>. The <a href="http://opensource.org/licenses/MIT">MIT License</a> applies.</p> -->
    </section>
    <section id="ChangeHistory">
      <h2>Appendix A: History of changes</h2>
      <section id="FPWD-SPWD">
        <h3>Changes between the First Public Working Draft and Second Public Working Draft</h3>
        <p>A summary of the main changes between the <a href="http://www.w3.org/TR/2015/NOTE-sdw-ucr-20150723/">First Public Working Draft</a> (published 2015-07-23) and the Second Public Working Draft (this version) of this document:</p>
        <ul>
        <li>A note was added to the description of the deliverable <a href="#CoverageInLinkedData">Coverage In Linked Data</a>.</li>
        <li>Two new use cases were added: <a href="#ProvenanceOfClimateData">Provenance of climate data</a> and <a href="#smod">Representing geospatial data in RDF</a>.</li>
        <li>A note was added to the <a href ="#Requirements">section listing accepted requirements</a>, to explain the term 'recommended way'.</li>
        <li>The <a href="#Provenance">Provenance requirement</a> was rephrased.</li>
        <li>The <a href="#ValidTime">Valid time requirement</a> was rephrased.</li>
        <li>The requirement 'Spatial meronymy' was renamed to <a href="#SpatialRelationships">Spatial relationships</a> and redefined.</li>
        <li>A new requirement for the deliverable <a href="#TimeOntologyInOWL">Time Ontology in OWL</a> was added: <a href="#UpdateDatatypes">Update datatypes in OWL Time</a>.</li>
        <li>A new section was added that lists <a href="#RequirementsByDeliverable">accepted requirements by deliverable</a>.</li>
        <li>A new section listing <a href="https://www.w3.org/TR/2015/NOTE-sdw-ucr-20151217/#DeferredRequirements">deferred requirements</a> was added.</li>
        </ul>
      </section>
      <section id="SPWD-TPWD">
        <h3>Changes between the Second Public Working Draft and Third Public Working Draft</h3>
        <p>A summary of the main changes between the <a href="https://www.w3.org/TR/2015/NOTE-sdw-ucr-20151217/">Second Public Working Draft</a> (published 2015-12-17) and the Third Public Working Draft (this version) of this document:</p>
        <ul>
        <li>The section <a href="https://www.w3.org/TR/2015/NOTE-sdw-ucr-20151217/#DeferredRequirements">Deferred requirements</a> was removed. The only requirement in that section, <a href="https://www.w3.org/TR/2015/NOTE-sdw-ucr-20151217/#Profiling">Definition of SSN profiles and checking compliance against the model</a>, was moved to the general requirements section and changed to <a href="#SSNProfiles">SSN profiles</a>.</li>
        <li>The requirement <a href="https://www.w3.org/TR/2015/NOTE-sdw-ucr-20151217/#ModelReuse">Model reuse</a> was removed.</li>
        <li>The SSN requirement <a href="https://www.w3.org/TR/2015/NOTE-sdw-ucr-20151217/#ReferenceExternalVocabularies">Reference external vocabularies</a> was removed.</li>
        <li>The requirement <a href="https://www.w3.org/TR/2015/NOTE-sdw-ucr-20151217/#NonGeographicReferenceSystem">Non-geographic reference system</a> was merged with the requirement <a href="#IndependenceOnReferenceSystems">Independence on reference systems</a>.</li>
        <li>The requirement <a href="https://www.w3.org/TR/2015/NOTE-sdw-ucr-20151217/#MultipleTypesOfCoverage">Mutliple types of coverage</a> was rephrased and renamed to <a href="#IdentifyCoverageType">Identify coverage type</a>.</li>
        <li>The <a href="https://www.w3.org/TR/2015/NOTE-sdw-ucr-20151217/#DefaultCRS">Default CRS requirement</a> was changed to <a href="#DeterminableCRS">Determinable CRS</a>.</li>
        <li>The use case <a href="#ModellingInTheConstructionSector">Modelling in the construction sector</a> was added.</li>
        <li>The requirement <a href="#SubjectEquality">Subject equality</a> was added.</li>
        <li>Use case <a href="https://www.w3.org/TR/2015/NOTE-sdw-ucr-20151217/#GeospatialExtensionsToDomainIndependentMetadataSchemas">Geospatial extensions to domain-independent metadata schemas</a> was updated and has become <a href="#EnablingCrossdomainSharingAndReuseOfGeospatialMetadata">Enabling cross-domain sharing and re-use of geospatial metadata</a>.</li>
        <li>Requirement Lightweight API was changed (<a href="https://www.w3.org/TR/2015/NOTE-sdw-ucr-20151217/#LightweightAPI">this</a> is the previous version and <a href="#LightweightAPI">this</a> is the current version).</li>
        <li>Examples were added to the <a href="#TemporalVagueness">Temporal vagueness requirement</a>.</li>
        <li>The use case <a href="https://www.w3.org/TR/2015/NOTE-sdw-ucr-20151217/#UsingSpatialDataFromTheWebInGISSystemsDuringEmergencyResponseOperations">Using spatial data from the Web in GIS systems during emergency response operations</a> was changed and given the new title <a href="#UsingSpatialDataDuringEmergencyResponseOperations">Using spatial data during emergency response operations</a>.</li>
        <li>The <a href="#TilingSupport">requirement for tiling support</a> was related to the deliverable <a href="#CoverageInLinkedData">Coverage in Linked Data</a>.</li>
        <li>The <a href="https://www.w3.org/TR/2015/NOTE-sdw-ucr-20151217/#SpatialVagueness">previous Spatial vagueness requirement</a> has been <a href="#SpatialVagueness">rephrased</a>.</li>
        <li>The requirement <a href="https://www.w3.org/TR/2015/NOTE-sdw-ucr-20151217/#QualityMetadata">Quality metadata</a> for the Coverage deliverable has been rephrased and is renamed to <a href="#QualityPerSample">Quality per sample</a>.</li>
        <li>A new requirement was added: <a href="#AvoidCoordinateTransformations">Avoid coordinate transformations</a>.</li>
        <li>A new requirement was added: <a href="#CoordinatePrecision">Coordinate precision</a>.</li>
        <li>A new requirement was added: <a href="#MultipleCRS">Multiple Coordinate Reference Systems</a>.</li>
        <li>A new SSN requirement was added: <a href="#ModelActuation">Model actuation</a>.</li>
        <li>A new requirement was added: <a href="#SSNExamples">SSN usage examples</a>.</li>
        </ul>
      </section>
    </section>
    <script class='remove'> 
      <!-- Create a list of deliverables with related requirements. -->
      var tab = document.getElementById("RequirementsByDeliverable");
      var deliverables = document.getElementById("Deliverables").getElementsByTagName("section");
      var requirements = document.getElementById("Requirements").getElementsByTagName("section");
      var relatedDelivs = [];
      var dId, rId, dLabel, rLabel, dp, dpb, dpbt1, dpbt2, dpba, dbpat, dpo, dpol, dpola, dpolat;
      for (i = 0; i < deliverables.length; i++) {
        dId = deliverables[i].id;
        if (dId == "UseCasesAndRequirements") {continue;}
        dLabel = deliverables[i].getElementsByTagName("h3")[0].innerText;
//        dp = document.createElement("p");
        dp = document.createElement("section");
        dp.id = 'ar'+dId ;
//        dpb = document.createElement("b");
        dpb = document.createElement("h3");
        dpbt1 = document.createTextNode("Requirements for deliverable ");
        dpb.appendChild(dpbt1);
        dpba = document.createElement("a");
        dpbat = document.createTextNode(dLabel);
        dpba.appendChild(dpbat);
        dpba.href = "#" + dId;
        dpb.appendChild(dpba);
        //dpbt2 = document.createTextNode(":");
        //dpb.appendChild(dpbt2);
        dp.appendChild(dpb);
        dpo = document.createElement("ol");
        for (j = 0; j < requirements.length; j++) {
          rId = requirements[j].id;
          rLabel = requirements[j].getElementsByTagName("h3")[0].innerText;
          relatedDelivs = requirements[j].getElementsByClassName("relatedDeliverables")[0].getElementsByTagName("a");
          for (k = 0; k < relatedDelivs.length; k++) {
            if (relatedDelivs[k].getAttribute("href") == "#" + dId) {
              dpol = document.createElement("li");
              dpola = document.createElement("a");
              dpolat = document.createTextNode(rLabel);
              dpola.appendChild(dpolat);
              dpola.href = "#" + rId;
              dpol.appendChild(dpola);
              dpo.appendChild(dpol);           
            }
          }
        }
        dp.appendChild(dpo);
        tab.appendChild(dp);
      }
    </script>
  </body>
</html>