CSDI Information

Datasets to be released through the CSDI portal are required to meet the CSDI standards, which include geo-tagging of non-spatial data, documentation of data specifications and metadata, conversion of spatial data to an open and machine-readable format and establishment of Application Programming Interface (API).

(1) Geo-tagging of non-spatial data

Geo-tagging of non-spatial data usually involves the adding of geographical identification such as latitude, longitude and grid coordinates, or administrative boundaries and addresses.

(2) Data Specification

Spatial data on CSDI must meet the established data specifications with detailed description of the data, including the data definition, content and structure, quality, workflow, maintenance, delivery and exchange.

(3) Metadata

Spatial data released on CSDI will contain metadata, describing the source and definition of the dataset, update time and contact information, etc.

(4) Open and machine readable format

Open and machine readable format refers to data formats that can be read and processed automatically by free and open-source softwares without human intervention to facilitate programming and spurring community innovation. Spatial data released on CSDI will be in GeoJSON, GML, KML and CSV formats which are commonly used by the industry.

(5) Application Programming Interface (API)

An API is a tool that enables a software application to share its functionalities and data with other software applications. It can greatly facilitate application development by allowing application developers to integrate specific functionalities and data to their applications without having to “reinvent the wheel” and spending time to create functionalities and data that already exist.

To facilitate users from public and private sectors to realise the benefits of using spatial data, four quick win projects have been implemented.

(1) Map Application Programming Interface (API)

The Map API is an API for the CSDI portal to share map data with the public and private sectors to support their applications requiring map display. It enables the community to build innovative applications enriched with locational and other features such as virtual city navigation;

(2) Geo-tagging Tool

It is an enabling tool to convert non-spatial data (e.g. demographic data or ground features) into a form of spatial data for display on a map. For example, a user can use the tool to convert the demographic data of different districts, which is textual and non-spatial in nature, into spatial data which can then be shown on a digital map rendering the map with the spatialised demographic data more informative;

(3) Address Data Infrastructure (ADI) (GeoAddress)

It is an enabling tool to standardise location identifiers across departments facilitating interoperability of address information across departments. The standardisation can help B/Ds improve public services, such as postal delivery, assessment of rateable value, planning of emergency services and management of complaint cases (e.g. calling by 1823); and

(4) District-based Spatial Information Dashboard

It is a web-based application that uses charts, gauges, maps, and other visual elements to display spatial datasets in an easily readable form and provide public and private sectors with consistent, up-to-date and consolidated district-based spatial information. In short, a dashboard assimilates different online information and provides data analytics. For example, a dashboard can be used to display a summary of the number, size, core facilities and management responsibility of public open spaces in a district. Overseas experience shows that dashboards can be used for city management as well as an understanding of public opinions and trends.