The City of Red Deer Open Data Catalogue is using OGDI DataLab version 6.
The OGDI framework is written using C# and the .NET Framework, targeted for Microsoft's
The DataService exposes a RESTful Web service for programmatic access via a number of formats, including Open Data Protocol (OData) - an extension to Atom Publishing Protocol (AtomPub), Keyhole Markup Language (KML), JSON and JSONP.
The Data Browser is written in ASP.NET MVC and uses jQuery and a variety of other open source components which enables users to browse and query published datasets.
The Data Loader is a desktop client tool that includes both GUI-based and console-based data loader tools. This allows a developer to load data from .csv or .kml formats directly into Azure table storage.
The Red Deer Catalogue exposes data through REST web services using OGDI. The basic format of an OGDI service call is http://reddeer.cloudapp.net:8080/v1/container/dataset?query, where:
Note that OGDI DataLab v6 currently only supports the $filter and $top query options in the WCF Data Services query syntax.
Also note that if a property has a null value for a particular entity in the data set, it will be omitted entirely from the result set returned by OGDI DataLab. For example, in the Attractions data set, the "name" property is only returned for records that have a "name" value in the underlying data set. Your application design should take this into account and handle potentially missing properties.
http://reddeer.cloudapp.net:8080/v1/RedDeerCatalogue/Attractions?$filter=NAME eq 'Enmax Centrium'&format=json
Many of the data sets in the Red Deer Catalogue also include geospatial data, which is returned in the Keyhole Markup Language (KML) format. This format is compatible with popular desktop and Web-based mapping technologies including Microsoft Bing Maps, Google Maps, Yahoo! Maps, and Google Earth.
To return geospatial data in KML format, append the format=kml parameter to your query. For example, to retrieve geospatial points in KML format for Attractions in Red Deer that are named "Enmax Centrium":
http://reddeer.cloudapp.net:8080/v1/RedDeerCatalogue/Attractions?$filter=NAME eq 'Enmax Centrium'&format=kml
Note that if the data set that you are using does not include any geospatial data, a KML query to OGDI DataLab will return an empty result set.
OGDI DataLab and the underlying Azure Table Storage service support paging through large sets of query results. The documentation for Query Timeout and Pagination in the Azure Table Storage service provides a complete description of how OGDI and the underlying Azure platform support paging. You can also refer to the "C#/ASP.NET Paging" sample on the Data Browser page, which demonstrates how to perform paged queries using the WCF Data Services client library.