OGC blogs http://wwwdev.opengeospatial.org/blog en What is an Open API? http://wwwdev.opengeospatial.org/blog/4511 <div class="field field-name-body field-type-text-with-summary field-label-hidden"><div class="field-items"><div class="field-item even"><p>ProgrammableWeb, an online news and directory for web-based application programming interfaces (APIs) references more than 13,900 APIs, which is up from 6,000 registered APIs in May 2012. This phenomenal growth! The number one category of web APIS by far is Mapping with more than 4,500 APIs. This is more than Social, Mobile or Finance! Perhaps this is why over the last 6 months there has been considerable discussion in the Open Geospatial Consortium (OGC) concerning APIs: What is an API, is there an ontology for classifying APIs, does the OGC develop APIs, and so forth. A critical element of these discussions is the concept of what is an Open API. There are those in the geospatial community that an Open API is, well, completely open. The API is free, unencumbered by any IPR, has a non-restrictive license, is open source, and most importantly does not require a proprietary software stack to actually use the API. While most anyone in the geospatial and broader IT world would agree on most of the listed aspects of an Open API, the last “requirement” of not accessing a proprietary software stack is counter to current IT best practices.</p> <p>Current IT best practices define an Open API as a <u>freely</u> available API that provides a developer with programmatic access to a software application or service. The programmatic access is typically to proprietary software stacks but can also be to open source software, or a combination of both. These APIs use sets of technologies that enable websites and/or client applications to interact with each other by using REST, SOAP, JavaScript and other web technologies.  These APIs have allowed web communities to create an open architecture for sharing content and data between communities and applications.  A very typical application for an Open API is to access data: tweets, geolocation(s), maps, stock quotes, weather sensors, and so forth. An Open API is published on the internet and is free to use by anyone – including a company’s competitors. Further, the licenses for most Open APIs tend to be unrestrictive – such as similar to Creative Commons or the Apache license. Do not confuse the API license with the Terms of Use/Service (ToS) related to any data accessed by the API!! This is a very important distinction. ToS related to data accessed by the API tend to be very restrictive – just check out the Twitter or Google ToS.</p> <p>Why do companies and organizations publish Open APIs that can be used by anyone including competitors? <em>Innovation is fostered wherever APIs are available. </em>Open APIs, because they are accessible to developers outside of an individual business, can attract new and often unexpected innovation by enabling your core business service to be “remixed” by others outside of an organization. A company might publish APIs to encourage third-party developers in vertical industries to be innovative and figure out new ways to use the startup’s software product. In this way, a company can increase market reach without the traditional major investments required to open new markets.</p> <p>Apigee, a builder of API management platform software, (<a href="http://apigee.com/about/blog/technology/why-and-how-apis-open-api-model">http://apigee.com/about/blog/technology/why-and-how-apis-open-api-model</a> ) summarizes these  Open API value propositions as:</p> <p><strong>Breakthrough innovation</strong><strong>:  </strong>Innovation by leveraging the creativity and know-how of hundreds of thousands of developers around the world using your API to create cool apps and make big breakthroughs.</p> <p><strong>Niche markets</strong><strong>:</strong> A company may have a geographical or demographic niche that represents a nice new value proposition for the business. But it may not have the resources or the budget to get the value proposition into those niches. Taking advantage of an open API program, any developer can create an app that generates new value for both themselves and the API provider.</p> <p><strong>Direct incentives</strong><strong>:</strong> A directed approach may be to run a contest or a hackathon and an incentive to build against your API. Google does this on a regular basis. This approach extends R&amp;D budgets and resources beyond the borders of your business and spurs innovation on a broad scale.</p> <p>There is also an interesting value proposition that is not often documented.  Any developer can take an API definition and implement the same interfaces defined in the existing Open API as part of their own software stack. Sure, they would be giving credit to your competitor but why spend significant R&amp;D dollars to replicate a well-designed and successful API? If your core software provides better and faster functionality, this approach makes it very easy for a developer to switch platforms. This brings us back to standards and the OGC. Standardized APIs can be implemented on any proprietary platform.</p> <p>Most Open APIs have a strong reliance on standards: OATH (authentication), OpenSearch (share search results), JSON, SOAP, ISO 8601 (date and time), and many more. From an OGC perspective, there are many (hundreds?) of APIs that reference OGC interface and encoding standards. These API implementations of OGC standards are providing new requirements into the OGC standards process – and the ongoing discussions in the OGC about the role of APIs in the OGC standards development process. In another blog I will talk about what makes a good API.</p> <p>In future blogs on Open APIs, I will address topics such as the relationship between Open APIs and open source, how to determine if an Open SPI is any good or not, and any topics suggested by the readers of this blog.</p> </div></div></div><div class="field field-name-field-contributor field-type-text field-label-above"><div class="field-label">Contributed by:&nbsp;</div><div class="field-items"><div class="field-item even">Carl Reed</div></div></div><div class="field field-name-field-contributor-image field-type-image field-label-above"><div class="field-label">Contributor picture:&nbsp;</div><div class="field-items"><div class="field-item even"><img src="http://wwwdev.opengeospatial.org/sites/www.opengeospatial.org/files/contributor_pictures/Carl%20Reed%20thumbnail%202015.png" width="79" height="80" /></div></div></div><div class="field field-name-taxonomy-vocabulary-13 field-type-taxonomy-term-reference field-label-above"><div class="field-label">Tags:&nbsp;</div><div class="field-items"><div class="field-item even"><div id="taxonomy-term-753" class="taxonomy-term vocabulary-vocabulary-13"> <h2><a href="/taxonomy/term/753">Open API</a></h2> <div class="content"> </div> </div> </div></div></div> Tue, 15 Sep 2015 19:49:22 +0000 Lance McKee 4511 at http://wwwdev.opengeospatial.org http://wwwdev.opengeospatial.org/blog/4511#comments Web3D City Model Contest Winners Announced http://wwwdev.opengeospatial.org/blog/2351 <div class="field field-name-body field-type-text-with-summary field-label-hidden"><div class="field-items"><div class="field-item even"><p><span> </span></p><p dir="ltr"><span style="line-height: 1.6;">The 2015 Web3D City Model Contest award winners were announced in June at the 20th Annual Web3D Conference in Crete, Greece.</span><a href="http://web3d2015.web3d.org/" style="line-height: 1.6;"> http://web3d2015.web3d.org/</a></p> <p dir="ltr"><span>In late 2014, The Web3D Consortium and the Open Geospatial Consortium (OGC) announced to their members the Web3D City Model Contest competition for the best browser-based 3D rendering of a city. The contest was organized to encourage development of software solutions to stream to a client large 3D city models including textured buildings, terrain, and sensor data. The aim of the competition was to demonstrate the state of the art of browser-based 3D visualization of city models as well as to provide a starting point to compare different streaming solutions. The results provide valuable insights for the ongoing development of the OGC’s 3D Portrayal Service (3DPS) candidate standard and its interoperability with Web3D standards.</span></p> <p dir="ltr"><span>As a minimum requirement, the implementation had to operate as a Web Service. The client was required to be browser-based and to have the capability to select individual features (e.g. a building) and display further information about the selected feature. Further, the Web Service and the streaming protocol had to be documented and open. All competitors were provided the same source data:the open data </span><a href="http://www.rotterdam.nl/links_rotterdam_3d"><span>CityGML model of Rotterdam</span></a><span>, and terrain data. Any freely accessible data (water level, weather forecast, or other sensor/model data), maps and other features could be added at the implementer’s discretion. (</span><span>See the submission instructions at</span><a href="http://web3d2015.web3d.org/competition.html"><span> </span><span>http://web3d2015.web3d.org/competition.html</span></a><span>).</span></p> <p dir="ltr"><span>This year’s winners received their awards at the 20th International ACM-SIGGRAPH Conference on 3D Web Technology in Heraklion, Crete, Greece. The winners received financial support to attend the conference. They were recognized for their creativity in addressing a 3D geospatial use case with solutions characterized by high performance in data loading, interactivity in the client, diversity of data rendered, and interoperability and openness. The winners were:</span></p> <ul><li dir="ltr"> <p dir="ltr"><span>GeoPlex GmbH: Hannes Gräuler and Frederik Hilling -- attended and accepted their award in the Industry Solutions category.</span></p> </li> <li dir="ltr"> <p dir="ltr"><span>Technical University of Munich: Kanishk  Chaturvedi  and Zhihang Yao -- accepted their award in the Student category.</span></p> </li> </ul><p dir="ltr"><span>The GeoPlex solution is implemented in pure WebGL (Java-Script), based on a heavily modified </span><span>OpenWebGlobe (</span><a href="http://www.openwebglobe.org/"><span>http://www.openwebglobe.org/</span></a><span>) </span><span>codebase. The server side consists of a GeoDjango application and a PostgreSQL database with PostGIS support. All tile types (image, terrain, geometry) use the same TMS-like </span><a href="http://wiki.openstreetmap.org/wiki/Slippy_map_tilenames"><span>slippy map convention</span></a><span>. The tile types contain neither distinctive geometries nor feature attributes. In order to enable the client to query individual features, the solution follows the FeatureInfoByRay concept of OGC’s 3D Portrayal Service Standard. Two points are sent to the server: the current camera position and the direction of the mouse click. Thus it is possible to generate a ray and return the first building that is hit by that ray, highlighting the geometry and showing the attributes to the user. OpenStreetMap data (OSM) was integrated to generate 3D symbols for bus stops and parking spots.</span></p> <p dir="ltr">The solution can be explored at <a href="http://rotterdam.b.geoplex.de/">http://rotterdam.b.geoplex.de/</a>.</p> <p dir="ltr"><span>The TU Munich solution </span><span>utilizes the Cesium JavaScript framework on top of HTML5 which allows for performing Ajax requests to access remote data hosted in a cross domain. The 3DCityDB was used to generate tiles stored in KML/COLLADA files from the CityGML data. Furthermore, the tiling manager in the web client was developed to support the tiling of large 3D city models and dynamic loading of the tiles. Utilizing multi-threading capabilities of HTML5, the time-costly operations such as parsing of multiple 3D objects are delegated to background threads running in parallel. At the same time, another thread monitors the interactions with the virtual camera and takes care of loading and unloading the data tiles according to their visibility. In addition, the user can control the dynamic elements of 3D building models using JavaScript commands embedded within Cesium JavaScript API. Cesium was extended to support KML network links, caching, dynamic loading and unloading of tiles, and 3D object highlighting.</span></p> <p dir="ltr"><span>The solution is accessible at: </span><a href="http://www.3dcitydb.net/3dcitydb/fileadmin/3DWebClient/index.html"><span>http://www.3dcitydb.net/3dcitydb/fileadmin/3DWebClient/index.html</span></a><span> .</span></p> <p dir="ltr"><span>The student award was co-sponsored by the 3D city model Working Group of the German Cartographic Society (DGfK) and the </span><a href="http://www.3d-stadtmodelle.org/"><span>German Society for Photogrammetry, Remote Sensing and Geoinformation (DGPF)</span></a><span>.</span></p> <p dir="ltr"><span><img src="https://lh6.googleusercontent.com/T40wc0MbPAzgb-8Px9FWCCwS8qoIJce5s8DmvuTFtKb0mql-GnqbBPkEWMldn6VB12nE8eBMRmbcK-4O7QI11J-nnQu5PyB6OMeQe-wEtj5sbysIeghuMljeHpcxHfbYuoypfa3k" border="0" width="643px;" height="427px;" /></span></p> <p dir="ltr"><span>Hannes Gräuler and Frederik Hilling of GeoPlex</span><span> </span><span>receive their award from the Web3D Consortium. From left to right: </span><span> </span><span>Nicolas Polys of the Web3D Consortium</span><span>, </span><span>Hannes Gräuler,</span><span> </span><span>Frederik Hilling and Mike McCann of the Web3D Consortium</span><span>. Missing: Volker Coors, HFT Stuttgart / OGC who was in hurry to catch his flight back home.</span></p> <p dir="ltr"><span>The OGC and the Web3D Consortium have both been working to address the need for interoperability as well as the content challenges of volume, access speed, and diversity of devices. The Web3D Consortium has focused on open standards for real-time 3D visualization, including streaming. Their members developed a Geospatial Component extension for X3D. The OGC has focused on developing a service interface to provide interoperable access to 3D geospatial data servers. In 2013, the OGC, building on work done in both organizations, initiated a standards working group to develop a 3D Portrayal Service Standard.</span></p> <p></p> <p dir="ltr"><br /><span style="line-height: 1.6;">Volker Coors is a <span>Professor at Hochschule für Technik Stuttgart and Anita Havele is <span>Executive Director at Web3D Consortium.</span></span></span></p> <p> </p> <p><span> </span></p><div><span><br /></span></div> <p></p></div></div></div><div class="field field-name-field-contributor-gravatar field-type-email field-label-above"><div class="field-label">Contributor Gravatar:&nbsp;</div><div class="field-items"><div class="field-item even"><a href="mailto:"></a></div></div></div> Thu, 27 Aug 2015 19:06:38 +0000 Lance McKee 2351 at http://wwwdev.opengeospatial.org http://wwwdev.opengeospatial.org/blog/2351#comments New! i-locate extends OpenStreetMap editor for indoor navigation graph editing! http://wwwdev.opengeospatial.org/blog/2350 <div class="field field-name-body field-type-text-with-summary field-label-hidden"><div class="field-items"><div class="field-item even"><p><span> </span></p> <p dir="ltr"><span style="line-height: 1.6;">i-locate (see our recent <a href="http://www.opengeospatial.org/blog/2263">OGC Blog post</a> and our <a href="http://www.i-locate.eu">website</a>)</span><span style="line-height: 1.6;"> is a project funded through Europe’s ICT-PSP program. i-locate provides the first reference implementation of the <a href="http://www.opengeospatial.org/standards/indoorgml">OGC IndoorGML Encoding Standard</a>. The project has recently released a plug-in for JOSM, the popular cross-platform editor for OpenStreetMap written in Java. The plug-in allows visualisation of navigation graphs encoded as IndoorGML.</span></p> <p dir="ltr"><span>The plug-in automatically recognises files with the .igml extension, that is, XML files describing connection graphs encoded as IndoorGML. By parsing .ignl files, the plug-in can create a georeferenced graph representing connectivity between different indoor areas (or cells, in IndoorGML terms). The plug-in builds the various nodes and arcs of the graph which respectively represent IndoorGML “states” and “transitions” for each floor inside a given building. Thanks to specific attributes used within the IndoorGML file, it is possible to filter out different types of nodes, which are then rendered in a different way for improved visualisation (e.g. doors, "anchor nodes" connecting indoor and outdoor graphs, connections between floors, etc.).</span></p> <p dir="ltr"><img src="https://portal.opengeospatial.org/files/?artifact_id=64636" border="0" alt="i-locate plug-in fig 1" width="650" height="474" /></p> <p dir="ltr"><span>The first version of the plug-in only supported visualisation of graphs. The latest release supports basic editing of the graph, allowing users to save changes as IndoorGML files. This capability extends the scope of the plug-in from a simple visualiser to a more comprehensive editor of IndoorGML graphs.</span></p> <p dir="ltr"><span><img src="https://portal.opengeospatial.org/files/?artifact_id=64637" border="0" alt="i-locate plug-in fig 2" width="650" height="474" /><br /></span></p> <p dir="ltr"><span>The current interface allows a user to customize the colors and names (usually the ID) of each IndoorGML “transition". To address “states”, the interface uses different rendering styles to differentiate “regular” nodes from anchor nodes (i.e. connections to outdoor graphs), or to show nodes representing rooms, doors, etc. This way it becomes very easy for users to appreciate the different semantics of the various parts of the IndoorGML graph.</span></p> <p dir="ltr"><span>Whenever a building features more than one level (that is, more than one floor or storey), the system allows selecting the level of interest, hiding all the elements belonging to other levels, therefore facilitating comprehension of the graph.</span></p> <p dir="ltr"><span>The plug-in uses the official IndoorGML schema to which a few minor extensions have been introduced. These extensions address requirements identified in pilot projects carried on within the i-locate project. All the extensions have been officially submitted to the IndoorGML SWG for their possible adoption in the future release of the standard.</span></p> <p dir="ltr">The i-locate project, coordinated by <a href="http://www.trilogis.it/">Trilogis Srl </a>based in Rovereto, Italy, is co-funded by the European Commission in the framework of the ICT-PSP (Information and Communication Technology Program).</p> <div>Giuseppe Conti is CTO at Trilogis and chair of the OGC Domain Working Group for Mobile Location Services. </div> <p dir="ltr"> </p></div></div></div><div class="field field-name-field-contributor-gravatar field-type-email field-label-above"><div class="field-label">Contributor Gravatar:&nbsp;</div><div class="field-items"><div class="field-item even"><a href="mailto:"></a></div></div></div> Mon, 24 Aug 2015 16:54:19 +0000 Lance McKee 2350 at http://wwwdev.opengeospatial.org http://wwwdev.opengeospatial.org/blog/2350#comments Indoor/outdoor location and asset management through open geodata – i-locate! http://wwwdev.opengeospatial.org/blog/2349 <div class="field field-name-body field-type-text-with-summary field-label-hidden"><div class="field-items"><div class="field-item even"><p><span> </span></p> <p dir="ltr"><span style="line-height: 1.6;">i-locate, a project of Europe’s </span><span style="line-height: 1.6;">ICT-PSP program,</span><span style="line-height: 1.6;"> provides the first reference implementation</span><span style="line-height: 1.6;"> of IndoorGML. The i-locate portal provides an indoor counterpart to OpenStreetMap (OSM).</span></p> <p dir="ltr"><span>S</span><span>tudies have shown that on average we spend about 90% of our time indoors, often in unfamiliar environments. Location Based Services (LBS), however, are  limited to outdoor scenarios because they are based almost entirely on GPS location, which doesn’t work well indoors. The potential social and economic value of indoor LBS applications to people and businesses is obviously very great. Applications include navigation but also activities such as asset management and hospital patient management.</span></p> <p dir="ltr"><span><img src="https://lh3.googleusercontent.com/zZWLxuNnE8rvXusADHDHOKQjy3effPwbQsGTvlJPPDHROM9ua_IU5uV0Wwg7fH_JinL9o9Zx7G-DQwuhXcsu0Qkxh-f4WsFzBxsbq58mlXUqYDbkejHBIZCT9J2tUJeVsq1Ncl0" border="0" width="644px;" height="428px;" /></span></p> <p dir="ltr"><span>The i-locate portal provides means to enter, select and view in-building data encoded using the OGC IndoorGML Encoding Standard.</span></p> <p dir="ltr"><span>The indoor LBS market is set to grow in the next 4 years to a multi-billion dollar market. Over the past few years, increasingly accurate indoor location determination technologies based on technologies such as Bluetooth, ZigBee, Wi-Fi and optical ranging have expanded the scope of LBS to include indoor spaces. Players such as Google, Apple, Nokia and a multitude of SMEs (Small-Medium Enterprises) are investing significant resources to create indoor mapping databases and services. Nevertheless, the development of seamless indoor/outdoor location services still must overcome three major barriers:</span></p> <p dir="ltr"><span>1)</span><span>   </span><span>Lack of indoor spatial data</span><span>. While much outdoor map data can be easily accessed as open data – a notable example being OpenStreetMap (OSM) – openly accessible indoor spatial data is not available except in isolated cases. In the case of publicly-accessible buildings, such as hospitals, stations, airports, shopping malls, and public offices, having open access to indoor spatial data would support new business activities and bring a number of social and economic benefits.</span></p> <p dir="ltr"><span>2)</span><span>   </span><span>Isolated technological ecosystems.</span><span> Technological fragmentation binds location based services to specific vendor-native technologies and limits the services to particular functions.</span></p> <p dir="ltr"><span>3)</span><span>   </span><span>Lack of standards-based indoor/outdoor LBS integration.</span><span> Standards exist that support seamless indoor/outdoor navigation, but no effort to date has successfully integrated these standards.</span></p> <p dir="ltr"><span>i-locate means to overcome these barriers by providing an open platform for innovation in integrated indoor and outdoor localisation of people and objects. i-locate has been engineered to address these market requirements provided by a core of specialised European SMEs:</span></p> <p dir="ltr"><span>·</span><span>  </span><span><span> </span></span><span>Create a public geoportal, the so-called “virtual hub”, that collects, makes discoverable, and provides access to indoor geographic information as open data: an indoor counterpart to OpenStreetMap.</span></p> <p dir="ltr"><span>·</span><span>  </span><span><span> </span></span><span>Adopt and extend open standards in the field of indoor/outdoor LBS.</span></p> <p dir="ltr"><span>·</span><span>  </span><span><span> </span></span><span>Create a open source software developer “toolkit” (technically middleware) that allows integrated indoor-outdoor LBS based on the aforementioned open standards.</span></p> <p dir="ltr"><span>·</span><span>  </span><span><span> </span></span><span>Ensure that such a toolkit is built on sound privacy and security policies, for the highest protection of personal/critical data.</span></p> <p dir="ltr"><span>·</span><span>  </span><span><span> </span></span><span>Develop a template for standards-based client software (apps) for mobile devices, addressing real world scenarios.</span></p> <p dir="ltr"><span>·</span><span>  </span><span><span> </span></span><span>Test – for more than one year – the virtual hub, the developer toolkit, and the final applications in real operational scenarios with real users and stakeholders within 14 pilot sites in 8 EU countries.</span></p> <p dir="ltr"><span>·</span><span>  </span><span><span> </span></span><span>Engage large industrial players and also SMEs to ensure i-locate’s viability.</span></p> <p dir="ltr"><span>i-locate began with a comprehensive analysis and design phase, undertaken by a consortium of Spanish organizations that provided in-depth analysis of many use cases. The use cases were developed in pilots – demonstration projects – involving real downstream users (e.g. technicians, doctors, public officials, etc.). The pilots included analysis of international, national, and local regulatory constraints, with particular attention to privacy, ethical, and security issues.</span></p> <p dir="ltr"><span>Concurrently, the consortium identified technical requirements. This phase benefitted from the involvement of a few key experts from the industrial and standardisation world, in particular experts employed by organizations and businesses involved in the OGC. These experts were formally engaged as members of the consortium’s advisory board.</span></p> <p dir="ltr">At that time, <a href="http://www.opengeospatial.org/standards/indoorgml">IndoorGML</a> was a candidate OGC standard, specifically designed for indoor navigation services (IndoorGML was officially voted as OGC standard in September 2014). The results of the pilots indicated that the current modular core of the standard needs to be extended with an additional module to address asset management in addition to navigation. This asset management extension of IndoorGML was proposed as a result of i-locate. The extension is currently under development in the OGC IndoorGML Standards Working Group. The extension is designed to follow the principles of the recent (2014) ISO 55000 abstract standard specifications on asset management. Other standards selected for some of the core features included the ISO/IEC 24730-1:2014 standard on “Information technology — Real-time locating systems (RTLS)”. This attention to open standards was essential to ensure widespread industrial uptake of i-locate. </p> <p dir="ltr"><span>The standards platform provided a necessary foundation for the definition of a comprehensive system architecture comprising a number of complex services such as localisation, geofencing, and spatial analytics. At this phase it become clear that i-locate would become the first reference implementation of IndoorGML, a new and innovative standard within the LBS market.</span></p> <p dir="ltr"><span>Other early activities included a detailed survey of the data available to the various pilot sites. Work included documenting the adjustments necessary before loading the data into the central database that was being deployed as part of on-going development of the core virtual hub indoor geoportal.</span></p> <p dir="ltr"><span>The portal has been progressively extended with connectors that provide real-time access to other open data repositories, such as repositories of 3D city models that implement the OGC CityGML standard. Additionally, a service needed to be developed that allowed geometrical and topological validation of data against the requirements specified in IndoorGML. The hub provides graphical user interface capabilities that allow ingestion of indoor mapping data as well as interactive drawing of indoor graphs encoded as IndoorGML. A result has been the early public deployment of a first version of the i-locate portal, which is already being used in pilot preparation activities.</span></p> <p dir="ltr"><span>After the first release of the system architecture, software development started. This led to the successful public release, at the end of i-locate’s first year, of the first version of the open source toolkit.</span></p> <p dir="ltr"><span>During the first year, the consortium has also defined a detailed deployment and validation plan and created an infrastructure for online training (available from the project website) and related interactive training material. The deployment and validation plan and the training infrastructure will be important to ensure widespread implementation and uptake of i-locate.</span></p> <p dir="ltr"><span>For more information about i-locate, see</span><a href="http://www.i-locate.eu/"><span> </span><span>www.i-locate.eu</span></a><span>. You can also download the promotional video from: </span><a href="https://www.dropbox.com/s/6d9c9vud22qhobe/i-locate%20promo.mp4?dl=0"><span>https://www.dropbox.com/s/6d9c9vud22qhobe/i-locate%20promo.mp4?dl=0 .</span></a></p> <p> </p> <p dir="ltr"><span>The </span><span>i-locate</span><span> project, coordinated by </span><a href="http://www.trilogis.it/"><span>Trilogis Srl</span><span> </span></a><span>based in Rovereto, Italy, is </span><span>co-funded by the European Commission in the framework of the ICT-PSP (Information and Communication Technology Program).</span><span> </span></p> <div><span><span>Giuseppe Conti is CTO at Trilogis and chair of the OGC Domain Working Group for Mobile Location Services. Co-authors include Nicola Dorigatti, </span></span><span style="line-height: 1.6;">Senior Software Analyst &amp; Developer at <span>Trilogis, and Stefano Piffer, <span>Technical Manager at </span>Trilogis. </span></span></div></div></div></div><div class="field field-name-field-contributor-gravatar field-type-email field-label-above"><div class="field-label">Contributor Gravatar:&nbsp;</div><div class="field-items"><div class="field-item even"><a href="mailto:"></a></div></div></div> Mon, 03 Aug 2015 18:12:06 +0000 Lance McKee 2349 at http://wwwdev.opengeospatial.org http://wwwdev.opengeospatial.org/blog/2349#comments First results of the OGC - W3C “Spatial Data on the Web” collaboration http://wwwdev.opengeospatial.org/blog/2348 <div class="field field-name-body field-type-text-with-summary field-label-hidden"><div class="field-items"><div class="field-item even"><p><span> </span></p> <p dir="ltr"><span style="line-height: 1.6;">Despite all the temptations of summer, a recently formed OGC - W3C collaboration, the Spatial Data on the Web Working Group, has progressed to releasing the first results of its work. The </span><a href="http://docs.opengeospatial.org/dp/15-074/15-074.html" style="line-height: 1.6;">Spatial Data on the Web Use Cases and Requirements (UCR) Document</a><span style="line-height: 1.6;"> is being released jointly as a W3C First Public Working Draft and as an OGC Public Discussion Paper. The documented use cases are an effort to put a human face on where and for whom the group’s work should be useful. Some of the use cases include: Meteorological Data Rescue, Harvesting of Local Search Content, Locating a Thing, and Linked Data for Tax Assessment - a very diverse collection. The derived requirements will serve to guide the subsequent standards work and put some reasonable bounds on the scope of that work.</span></p> <p dir="ltr"><span>The document also represents the first few months of cultural and technical “acclimatization” within a group that has dual standing as both a W3C and an OGC unit. Many of the group's members have substantial experience in both standards organizations, most have worked with spatial data, and all are familiar with Web technologies. Even so, there are distinct differences in how the two organizations work, whom they see as their constituents, and what their priorities are in bringing forward the Web of Data. From getting familiar with Zakim (the W3C IRC "bot") to bridging some of the documentary differences (Word-centric vs HTML-all-the-time), we have had some interesting learning experiences.</span></p> <p dir="ltr"><span>Even more than the cultural differences, though, the diversity of technical outlooks has been a challenge for the group to work through in its mainly remote (email, chat, and teleconference) interactions. Everyone lives in space and time, but not everyone has concerned themselves with the geodetic, geometric and semantic details of how to design high-quality data to represent features of space and time. Do we make sure that every human and machine operating on the Web has access to these details, or do we hide the details and try to make spatial data as much like any other data as possible?</span></p> <p dir="ltr"><span>The group has at least come together in the view that there are few easy answers but lots of interesting questions. Our challenge is how to make spatial data as ubiquitous and natural on the Web as possible without putting too many people in danger in those cases where perception created by data clashes with the hard reality of the world we move about in. As a group participant, I'm excited to see what a wider audience will make of the ground rules we've developed in the UCR document. I'm also excited to move forward from this point toward some spatial data practices that make spatial only as "special" on the Web as needed and not more so.</span></p> <p> </p></div></div></div><div class="field field-name-field-contributor-gravatar field-type-email field-label-above"><div class="field-label">Contributor Gravatar:&nbsp;</div><div class="field-items"><div class="field-item even"><a href="mailto:"></a></div></div></div> Thu, 23 Jul 2015 15:49:39 +0000 Lance McKee 2348 at http://wwwdev.opengeospatial.org http://wwwdev.opengeospatial.org/blog/2348#comments The First OGC Client Test: WMS 1.3 http://wwwdev.opengeospatial.org/blog/2347 <div class="field field-name-body field-type-text-with-summary field-label-hidden"><div class="field-items"><div class="field-item even"><p><span> </span></p> <p class="normal"><b>OGC now provides a WMS 1.3 Client Test that client developers can use to confirm that their clients correctly implement the OGC Web Map Service 1.3 Interface Standard.</b></p> <p class="normal">OGC develops standards that make spatial information easy to discover and use on the Web, in wireless and location-based services, and in mainstream IT. For some OGC standards, the <a href="http://www.opengeospatial.org/compliance">OGC Compliance Program</a> provides compliance tests that implementers can use to validate that their implementations of OGC standards conform to the rules specified in the standards.</p> <p class="normal">To provide potential customers with assurance that the product correctly implements the standard, implementers can ask OGC to certify that the product correctly implements the standard. OGC certified products are listed in the <a href="http://www.opengeospatial.org/resource/products/compliant">OGC Compliant Products Database</a>. Organizations procuring or using software use the OGC Compliant Products Database to find software that OGC has tested and certified for correct implementation of OGC standards.</p> <p class="normal"> </p> <p class="normal"><img src="http://www.opengeospatial.org/pub/www/files/client-wms13.jpg" border="0" title="wms 13 client" width="600" height="400" style="border: 1px solid black;" /></p> <p class="normal"><i>Figure: WMS 1.3 Client test interaction showing the OGC validator and uDIG performing the WMS 1.3 client test.</i></p> <p class="normal">For many years, the OGC Compliance Program has provided only tests for service interfaces and tests for encodings. Now, for the first time there is a test for clients. The OGC membership recently approved the OGC’s first client test, which is used to certify that clients correctly implement WMS 1.3.</p> <p class="normal"><span style="line-height: 1.6;">The WMS 1.3 Client test provides a way  to verify that a client sends a valid request to a WMS 1.3 server. The </span><a href="http://cite.opengeospatial.org/teamengine/about/wms-client/1.3.0/site/" style="line-height: 1.6;">overview page</a><span style="line-height: 1.6;"> of the test provides a detailed description of the test. The test follows the rules for testing (conformance classes) documented in the OpenGIS® Web Map Server Implementation Specification (</span><a href="http://portal.opengeospatial.org/files/?artifact_id=14416" style="line-height: 1.6;">OGC 06-042</a><span style="line-height: 1.6;"> Annex A.1.1).</span></p> <p class="normal"><span style="line-height: 1.6;">The process to test and certify a WMS 1.3 client is as follows:</span></p> <ol><li>Go the <a href="http://cite.opengeospatial.org/teamengine/">OGC Validator</a>.</li> <li>When you log in and start the test you will be provided a URL.</li> <li>Use the URL in your client, as if you were importing data from a WMS server. Make sure the client performs the following requests:<ol><li>GetCapabilities: Perform <b>at least</b> one valid request.</li> <li>GetMap: Perform <b>all</b> get map request for all the layers advertised in the server’s GetCapabilities document.</li> <li>GetFeatureInfo: Perform <b>at least</b> one GetfeatureInfo valid request.</li> </ol></li> <li>Finish the test session.</li> <li>If your client passes the test, go to step 6. If not, send a question to the <a href="http://cite.opengeospatial.org/forum">cite-forum</a> so experts can help you pass the test.</li> <li>Go to the OGC implementation portal, register your product and link to the session information (from step  4) to get OGC certification.</li> </ol><p class="normal">In the test engine, the server interacting with the client is a <a href="http://cite.deegree.org/deegree-webservices-3.3.14-2">deegree server  WMS 1.3 reference implementation.</a> The WMS 1.3 client reference implementation is <a href="http://udig.refractions.net">uDig</a>,  updated by LisaSoft in 2012. The code is available at <a href="https://github.com/opengeospatial/ets-wms-client13">Github</a>, as are all the other OGC tests. </p> <p class="normal">A video describing how to use the test has been posted to <a href="https://youtu.be/mNJUl1lhL-s">YouTube.</a></p> <p class="normal"> </p> <p> <iframe frameborder="0" src="https://www.youtube.com/embed/mNJUl1lhL-s" height="315" width="560"></iframe></p> <p class="normal"> </p> <p class="normal">Enjoy!</p></div></div></div><div class="field field-name-field-contributor-gravatar field-type-email field-label-above"><div class="field-label">Contributor Gravatar:&nbsp;</div><div class="field-items"><div class="field-item even"><a href="mailto:"></a></div></div></div> Mon, 29 Jun 2015 10:42:24 +0000 Luis Bermudez 2347 at http://wwwdev.opengeospatial.org http://wwwdev.opengeospatial.org/blog/2347#comments World Ozone & Ultraviolet Radiation Data Centre provides data discovery and access through interfaces implementing OGC standards http://wwwdev.opengeospatial.org/blog/2346 <div class="field field-name-body field-type-text-with-summary field-label-hidden"><div class="field-items"><div class="field-item even"><p>The <a href="http://woudc.org/home.php">World Ozone and Ultraviolet (UV) Radiation Data Centre (WOUDC)</a> is one of six World Data Centres which are part of the Global Atmosphere Watch programme of the World Meteorological Organization. </p> <p><img src="https://portal.opengeospatial.org/files/?artifact_id=64068" border="0" alt="WOUDC Data Search " width="680" height="412" /></p> <p>The WOUDC data centre is operated by the Meteorological Service of Canada, a branch of Environment Canada. The Centre has been archiving ozone data since 1960 and solar ultraviolet (UV) radiation data since 1992.</p> <p>WOUDC makes it possible to discover, visualize and access ground-based ozone and UV radiation data from a global archive. Data from 500 registered <a href="http://woudc.org/data/stations">stations</a> in the archive has been provided from over 150 <u><a href="http://woudc.org/contributors">contributors.</a></u></p> <p>WOUDC's delivery of data has advanced with the advance of storage media and Internet and web technologies such as FTP, CD ROM and DVD ROM. This year the <a href="http://woudc.org/about/data-access.php#web-services">website</a> was updated, providing modernized mechanisms that support discovery, visualization, access and management of ozone and UV data. All WOUDC data are available using the Centre’s <u><a href="http://woudc.org/data/explore.php">data search / download,</a></u> or web accessible folder (WAF) access. In addition, web services based on Open Geospatial Consortium (OGC) web service interface standards now provide standards-based search and on-demand access to the archive as described below.</p> <p>1. Catalogue Service for the Web (CSW)</p> <p>The <a href="http://www.opengeospatial.org/standards/cat">OGC Catalogue Service</a> provides a common interface to discover, browse and query discovery metadata (data about data). The WOUDC CSW provides a catalogue of all WOUDC data available in the archive. Metadata records are formatted using the ISO 19115/19139 geospatial metadata standards. WOUDC provides OGC CSW (version 2.0.2) at the following endpoint:</p> <p><a href="http://geo.woudc.org/csw?service=CSW&amp;version=2.0.2&amp;request=GetCapabilities">http://geo.woudc.org/csw?service=CSW&amp;version=2.0.2&amp;request=GetCapabilities</a></p> <p>2. Web Map Service (WMS)</p> <p>The <a href="http://www.opengeospatial.org/standards/wms">OGC Web Map Service</a> provides a common interface to access visualizations of geospatial data layers. Common web or desktop GIS applications deliver these visualizations in web friendly image formats such as PNG or JPEG. WOUDC provides OGC WMS (versions 1.1.1 - 1.3.0) at the following endpoint:</p> <p><a href="http://geo.woudc.org/ows?service=WMS&amp;version=1.3.0&amp;request=GetCapabilities">http://geo.woudc.org/ows?service=WMS&amp;version=1.3.0&amp;request=GetCapabilities</a></p> <p>3. Web Feature Service (WFS)</p> <p>The <a href="http://www.opengeospatial.org/standards/wfs">OGC Web Feature Service</a> provides a common interface to access geospatial data. Typical use of WFS includes custom query / raw access to geospatial features. The WOUDC WFS implementation provides WOUDC archive data in numerous formats, including Extended CSV, KML, CSV, GML, ESRI Shapefile, MapInfo, and GeoJSON.<span style="line-height: 1.6;"> </span></p> <p>The WFS has a server side limit of a maximum of 25000 features to ensure quality of service and availability. WOUDC provides access to data through OGC WFS (versions 1.0.0 - 1.1.0) compliant interface at the following endpoint:</p> <p><a href="http://geo.woudc.org/ows?service=WFS&amp;version=1.1.0&amp;request=GetCapabilities">http://geo.woudc.org/ows?service=WFS&amp;version=1.1.0&amp;request=GetCapabilities</a></p> <p><span style="line-height: 1.6;">For more information, please refer to the WOUDC </span><u style="line-height: 1.6;"><a href="http://woudc.org/about/data-access.php">data access </a></u><span style="line-height: 1.6;">page.</span></p> <p> </p></div></div></div><div class="field field-name-field-contributor-gravatar field-type-email field-label-above"><div class="field-label">Contributor Gravatar:&nbsp;</div><div class="field-items"><div class="field-item even"><a href="mailto:"></a></div></div></div> Tue, 09 Jun 2015 18:00:30 +0000 Lance McKee 2346 at http://wwwdev.opengeospatial.org http://wwwdev.opengeospatial.org/blog/2346#comments Point Cloud ad hoc meeting outcomes http://wwwdev.opengeospatial.org/blog/2345 <div class="field field-name-body field-type-text-with-summary field-label-hidden"><div class="field-items"><div class="field-item even"><p>Thank you to everyone who participated in the Point Cloud ad hoc meeting on Monday 1st June. There were over 60 people registered for the event with approximately half that calling in via the goto meeting session.</p> <p><span style="line-height: 1.6;">The meeting was very constructive and, despite some technical hurdles, we were able to get the two remote presenters dialed into the session. Multiple presenters offered concrete proposals for activities for the OGC to consider and spurred very useful discussions amongst participants. Everything was recorded, however please bear with us as we get the recording processed and uploaded. This is one meeting in a very busy schedule of meetings this week.</span></p> <p><span style="line-height: 1.6;">Key outcomes from the meeting:</span></p> <p> <span style="line-height: 1.6;">1. The representative from Intergraph moved to create a Point Cloud Domain Working Group in the OGC. This motion was supported by a number of other members including Envitia, Oracle, ESRI, NASA, OSGeo and a number of others. The charter will be drafted during the course of the week. The Domain Working Group will be open to public participation. First work items for consideration will be the authoring of a Best Practice on the use of the current standards / de facto standards in the LiDAR community and a possible Interoperability Experiment.</span></p> <p> <span style="line-height: 1.6;">2. Commitment to explore the creation of a Standards Working Group for work with the LAS format as highlighted in Michael Gerlek's presentation. However, participants agreed that this must be undertaken in collaboration with ASPRS. OGC staff will take the action to follow up with ASPRS and determine the next steps.</span></p> <p><span style="line-height: 1.6;">The presentations from the day are available at the links below:</span></p> <p>•<a href="https://portal.opengeospatial.org/files/?artifact_id=63716" title="Scott Simmons">Scott Simmons</a>, OGC: Introduction to Point Cloud discussion and summary of standards efforts <br /> •Jeff Young, ASPRS: ASPRS activities with LiDAR data (please note this was a verbal presentation, therefore there are no slides)<br /> •<a href="https://portal.opengeospatial.org/files/?artifact_id=63729" title="Chris Little">Chris Little</a>, UK Met Office: What (where and when) is the Point in Meteorology <br /> •<a href="https://portal.opengeospatial.org/files/?artifact_id=63711" title="Keith Ryden">Keith Ryden</a>, Esri: Enterprise community requirements for point clouds  <br /> •<a href="https://portal.opengeospatial.org/files/?artifact_id=63715" title="Jason Smith">Jason Smith</a>, Exelis (NGA): Sensor Independent Point Cloud (SIPC) data format, a profile of HDF5 <br /> •<a href="https://portal.opengeospatial.org/files/?artifact_id=63713" title="Michael Gerlek">Michael Gerlek</a>, RadiantBlue: Current situation and future work for point clouds <br /> •<a href="https://portal.opengeospatial.org/files/?artifact_id=63727" title="Peter Baumann">Peter Baumann</a>: Point clouds in coverages   <br /> •<a href="https://portal.opengeospatial.org/files/?artifact_id=63712" title="Martin Isenburg">Martin Isenburg</a>, OSGeo: Open Source community drivers for point cloud standards <br /> •<a href="https://portal.opengeospatial.org/files/?artifact_id=63714" title="Doug O'Brien">Doug O’Brien</a>, IDON Technologies: ISO and point cloud standards </p></div></div></div><div class="field field-name-field-contributor-gravatar field-type-email field-label-above"><div class="field-label">Contributor Gravatar:&nbsp;</div><div class="field-items"><div class="field-item even"><a href="mailto:"></a></div></div></div> Tue, 02 Jun 2015 15:39:58 +0000 Denise McKenzie 2345 at http://wwwdev.opengeospatial.org http://wwwdev.opengeospatial.org/blog/2345#comments A letter about Point Cloud & LiDAR http://wwwdev.opengeospatial.org/blog/2344 <div class="field field-name-body field-type-text-with-summary field-label-hidden"><div class="field-items"><div class="field-item even"><p>For the past few months there have been discussions across a range of geospatial organizations about Point Cloud data, and in particular, LiDAR. </p> <p><span style="line-height: 1.6;">Last week the OSGeo Board put forward an Open Letter to OGC, ASPRS and ESRI. The letter can be found here </span><a href="http://wiki.osgeo.org/wiki/LIDAR_Format_Letter" target="_blank" style="line-height: 1.6;">http://wiki.osgeo.org/wiki/LIDAR_Format_Letter</a><span style="line-height: 1.6;">.</span></p> <p><span style="line-height: 1.6;">Below is the response from the OGC sent to the OSGeo Board.</span></p> <p style="padding-left: 30px;"><i style="line-height: 1.6;">Dear Members of the OSGeo Board, Dr Anand:</i></p> <p style="padding-left: 30px;"><i>Thank you for your letter on behalf of the open source community highlighting need for interoperability in LiDAR standards.  In recent months there has been a growing interest from the OGC membership and the global geospatial community in the interoperability of point cloud data, including LiDAR. As result, the OGC scheduled a Point Cloud ad hoc meeting on this topic as part of our upcoming Technical Committee meetings in Boulder, Colorado, USA.  The meeting will occur on 1 June from 1300-1445 Mountain / 1900-2045 UTC, and is open to the public. We hope that this meeting will result in a chartered working group in short order. An initial agenda for this meeting is posted at:  <a href="https://portal.opengeospatial.org/files/?artifact_id=63241" target="_blank">https://portal.opengeospatial.org/files/?artifact_id=63241</a>, and additional detail on the Boulder TC meeting is available at:  <a href="http://www.opengeospatial.org/event/1506tc" target="_blank" title="http://www.opengeospatial.org/event/1506tc">http://www.opengeospatial.org/event/1506tc</a>.   Remote access to the meeting will be provided.  <br /><br /> To ensure broad community representation and effective exchange of ideas, we strongly encourage interested members of the OSGeo to participate in the upcoming OGC Point Cloud ad hoc meeting for technical discussion on LIDAR and other related point cloud standards interoperability interests. This process is guided by OGC’s consensus process, which help to ensure an environment of mutual respect and trust in which technical ideas for interoperability can be exchanged freely and fairly.  We understand that representatives from the ASPRS will also participating in the meeting as part of our ongoing partnership with this organization.</i></p> <p style="padding-left: 30px;"><i style="line-height: 1.6;">Some time ago, a Memorandum of Understanding was formalized between OSGeo and the OGC with a goal of improving  communication and coordination between our organizations.  In the spirit of this agreement, we look forward to further developing our working relationship to address geospatial interoperability opportunities and challenges.</i></p> <p style="padding-left: 30px;"><i style="line-height: 1.6;">The OGC staff contact for the Point Cloud ad hoc meeting is Scott Simmons, Executive Director for the OGC Standards Program ssimmons@opengeospatial.org. Please contact him directly for further information on the meeting.</i></p> <p style="padding-left: 30px;"><i style="line-height: 1.6;">Sincerely, Mark</i></p> <address style="padding-left: 30px;"><i style="line-height: 1.6;">Mark E. Reichardt</i></address><address style="padding-left: 30px;"><i style="line-height: 1.6;"> </i><i style="line-height: 1.6;">President &amp; CEO</i></address><address style="padding-left: 30px;"><i> Open Geospatial Consortium (OGC)</i></address> <p><br /> The Point Cloud ad hoc meeting referenced in Mark's letter is open to public participation. We welcome all who wish to contribute to this important meeting to contact Scott Simmons (ssimmons@opengeospatial.org) and join the discussions in June. Scott will be publishing a blog later this week on Point Clouds to summarise the issues that will be discussed at the June meeting.</p></div></div></div><div class="field field-name-field-contributor-gravatar field-type-email field-label-above"><div class="field-label">Contributor Gravatar:&nbsp;</div><div class="field-items"><div class="field-item even"><a href="mailto:"></a></div></div></div> Tue, 12 May 2015 12:13:15 +0000 Denise McKenzie 2344 at http://wwwdev.opengeospatial.org http://wwwdev.opengeospatial.org/blog/2344#comments Information Sharing and Safeguarding – Collaboration is the Key http://wwwdev.opengeospatial.org/blog/2343 <div class="field field-name-body field-type-text-with-summary field-label-hidden"><div class="field-items"><div class="field-item even"><p><span style="line-height: 1.6;">When it comes to advancing information sharing and interoperability within and between organizations, jurisdictions, and geographies, collaboration across the public and private sectors is relied upon to help provide answers through a combination of technology, best practices and standards. Professional associations and standards development organizations (SDOs) are continually finding ways to reach across their mission boundaries to drive coordinated outcomes that benefit users nationally and internationally.  While the alliance partnership between the IJIS Institute and the Open Geospatial Consortium (OGC) represents an effective point-to-point relationship to cooperatively address increasingly tough interoperability challenges, I am writing today to update you on a broader collaborative in which the OGC, the IJIS Institute, OMG, OASIS and many other organizations are engaged to advance  responsible information sharing and safeguarding solutions. </span></p> <p>The organizations noted above are part of a  Standards Coordinating Council (SCC) - a group chartered by the White House Information Sharing and Access Interagency Policy Committee (ISA IPC) that consists of  Standards Development Organizations (SDOs) and industry organizations working collectively to improve information sharing and safeguarding through the application of open standards and related best practices (see <a href="http://www.standardscoordination.org">www.standardscoordination.org</a>).  The ultimate goal of the SCC is to help achieve a broad and pervasive implementation of a <a href="https://www.whitehouse.gov/sites/default/files/docs/2012sharingstrategy_1.pdf">National Strategy for Information Sharing and Safeguarding</a>, and to coordinate the capabilities of the SCC that will lead to an enduring standards-based interoperability environment across the public and private sectors.  While the SCC was launched as part of a governmental Information Sharing Environment (ISE) program in the USA (see <a href="http://www.ise.gov">www.ise.gov</a>), the focus areas and challenges being addressed in this process are very much international as noted by the scoping illustration for the ISE:</p> <p> <img src="https://portal.opengeospatial.org/files/?artifact_id=63207" border="0" alt="ISE diagram" title="ISE diagram" width="690" height="301" /></p> <p>A major part of the SCC’s mission is to provide comprehensive and coordinated advice on standards and interoperability best practices and to bring issues and solutions back to its constituents for action.  This includes supporting the operationalization of interoperability architecture models like the: <a href="https://www.google.com/url?sa=t&amp;rct=j&amp;q=&amp;esrc=s&amp;source=web&amp;cd=2&amp;cad=rja&amp;uact=8&amp;ved=0CCMQFjAB&amp;url=http%3A%2F%2Fwww.ise.gov%2Fsites%2Fdefault%2Ffiles%2FFINAL%2520-%2520ISE_I2F_v0%25205.pdf&amp;ei=VDdKVZW0Ia-1sAT2oYGgAg&amp;usg=AFQjCNEpTjHCAFsITHBioJTITUdy3sCNKg&amp;sig2=rajEJ8ymoLV1vRKNAGOV_A&amp;bvm=bv.92765956,d.cWc">ISE Interoperability Framework (I2F)</a>, <a href="http://www.ise.gov/sites/default/files/GIRA.pdf">Geospatial Interoperability Reference Architecture (GIRA)</a>, and other resources and tools that are taking shape under the guidance of the SCC.  This body of knowledge serves to define common approaches for standards and interoperability from policy, process, data and services perspectives. There are major crosscutting functions of the Framework that are integral parts of the I2F including: </p> <ul><li>identity credentialing and access management,</li> <li>geospatial information technologies,</li> <li>cybersecurity and threat monitoring, and</li> <li>device independent secure mobility.  </li> </ul><p>As a step in furthering the SCC mission and broadening its audience, IJIS and the OGC recently facilitated a workshop at OGC’s Technical Committee Meetings in Barcelona, Spain, to provide an overview of SCC activities, including background on the ISE, a discussion on the role of the SCC, and an overview of key documents available and in process by the SCC.  The workshop also featured a discussion of a <i>pipeline</i> of information sharing and safeguarding programs underway at the federal, state and local level.  Some of these pipeline projects will be “mapped” at a very detailed level to the I2F, thus operationalizing I2F standards and interoperability guidance via real-world implementation examples.   This work is being advanced under a program known as <a href="http://project-interoperability.github.io/"><i>Project Interoperability</i></a>.    </p> <p>The international significance of this work was affirmed by the attendees of the Barcelona workshop. Similar interoperability frameworks to those being advanced by the SCC for the USA are under development in Europe and other regions. Workshop attendees agreed that there are potential opportunities for advancing requirements and use cases into the SCC process as a way to further stimulate improved international coordination. Further, workshop attendees saw value in cross-linking the I2F, the GIRA and other work products of the SCC with similar international programs.  This would broaden the availability of useful interoperability resources for all.   </p> <p>One of the more fundamental realizations from the Barcelona SCC workshop was that geospatial permeates the range of topics being advanced under the SCC and Project Interoperability. Further, OGC and IJIS members attending the workshop agreed that there is ample opportunity to leverage the SCC process to advance coordinated activities – interoperability testbeds, pilot initiatives, experiments, compliance testing and certification and other activities <u>across SDOs</u> in a way that encourages efficiencies and alignment of standards and best practice work at a much larger scale. These realizations are also reflected in the work of the IJIS Institute’s Geospatial Task Force, where IJIS Members representing law enforcement, public safety, and justice are adding the expertise of industry to strengthen these efforts. </p> <p>For more about the SCC and upcoming events at which the SCC has a role, please visit <a href="http://www.standardscoordination.org">www.standardscoordination.org</a>. At the website you can also ask questions about the SCC, find ways to participate in the SCC activities, and submit projects for consideration in Project Interoperability. Representatives from member organizations of the SCC such as the OGC, the IJIS Institute, OMG, OASIS and others have participatory access to SCC activities.  Member representatives should take the time to learn about and follow the SCC and its work – You have the ability to help influence the progress of standards information sharing and interoperability markets. </p> <p>Finally, it's important to think of the OGC as a unique node in the valuable SCC network. Participation in the OGC provides opportunities to influence the SCC process through our SCC representatives.  Perhaps more important, because the issues are global, OGC stakeholders in all regions of the world have access through SCC to a large but very select international group of innovators and decision makers. The OGC offers OGC members a very special opportunity to leverage the value of this network.</p> <p>For more information, please contact OGC’s lead staff point of contact for the SCC, Dr. Scott Serich, <a href="mailto:"></a><a href="mailto:sserich@opengeospatial.org">sserich@opengeospatial.org</a> </p> <p> </p> <p> </p></div></div></div><div class="field field-name-field-contributor-gravatar field-type-email field-label-above"><div class="field-label">Contributor Gravatar:&nbsp;</div><div class="field-items"><div class="field-item even"><a href="mailto:"></a></div></div></div> Thu, 07 May 2015 16:54:05 +0000 Mark Reichardt 2343 at http://wwwdev.opengeospatial.org http://wwwdev.opengeospatial.org/blog/2343#comments