We're sorry but this page doesn't work properly without JavaScript enabled. Please enable it to continue.
Feedback

I’ve got geodata – How do I get out there (on the web)?

Formal Metadata

Title
I’ve got geodata – How do I get out there (on the web)?
Title of Series
Number of Parts
295
Author
Contributors
License
CC Attribution 3.0 Germany:
You are free to use, adapt and copy, distribute and transmit the work or content in adapted or unchanged form for any legal purpose as long as the work is attributed to the author in the manner specified by the author or licensor.
Identifiers
Publisher
Release Date
Language

Content Metadata

Subject Area
Genre
Abstract
GIS systems and ICT technologies are often at odds with each other for historical reasons. GIS software has developed in niches, predominantly through monolithic and proprietary systems. The growing need to expose geodata on the web, e.g. sparked through open data policies, leaves developers with a range of options. Clients may request server-side solutions such as OGC services such as Web Map Service, Web Feature Service and the likes. These solutions require a map server. Another option for instance is a direct database query that requests relational data through PHP. Since almost all big database management systems are spatially enabled today (Oracle Spatial, MS SQL Server, PostgreSQL/PostGIS, MySQL) there is per se no need to implement a map server at all. A third option is to use web clients’ native data formats such as JSON/GEOJSON. This may either be requested by a REST API, a JSON-capable DB (e.g. MongoDB) or through flat files. Which of these options serves my purposes best? This very much depends on the advantages of each of these choices and what your infrastructure is trying to achieve.
Keywords