Towards an open architecture for vector GIS

R. I. Dunfey, Bruce Gittings, James K. Batcheller

Research output: Contribution to journalArticlepeer-review

Abstract / Description of output

A range of open source software tools are now available to the Geographical Information Systems (GIS) analyst. However these tools are not necessarily interoperable and rarely significantly interoperable with proprietary systems. The open architectures, which have been developed for web-oriented systems, together with those proposed by the Open Geospatial Consortium (OGC), suggest that an open GIS architecture could be developed as an alternative to proprietary systems. The architecture would use open source components to store, translate, analyse, render and visualise GI data and would escape many of the problems of monolithic systems. Particularly what is proposed permits the loose coupling of any number of components and data stores in a manner that is both open and flexible. This paper proposes such an architecture and focuses on determining the suitability of Scalable Vector Graphics (SVG), an open vector-oriented eXtensible Markup Language (XML) grammar, as a significant component of such architecture. SVG is shown as an effective means of rendering GI data, not least because of its compatibility with the WC3 Document Object Model (DOM), permitting GIS-specific client tools to be written and transmitted to the web browser along with the SVG pages. While realising that the technology is in its infancy, the conclusion reached is that SVG currently provides a powerful solution and has enormous future potential.
Original languageEnglish
Pages (from-to)1720-1732
Number of pages13
JournalComputers and Geosciences
Volume32
Issue number10
DOIs
Publication statusPublished - Dec 2006

Keywords / Materials (for Non-textual outputs)

  • Open architecture
  • SVG
  • Web GIS
  • JavaScript
  • Web interface

Fingerprint

Dive into the research topics of 'Towards an open architecture for vector GIS'. Together they form a unique fingerprint.

Cite this