Book Image

GeoServer Beginner's Guide - Second Edition

By : Stefano Iacovella
Book Image

GeoServer Beginner's Guide - Second Edition

By: Stefano Iacovella

Overview of this book

GeoServer is an opensource server written in Java that allows users to share, process, and edit geospatial data. This book will guide you through the new features and improvements of GeoServer and will help you get started with it. GeoServer Beginner's Guide gives you the impetus to build custom maps using your data without the need for costly commercial software licenses and restrictions. Even if you do not have prior GIS knowledge, you will be able to make interactive maps after reading this book. You will install GeoServer, access your data from a database, and apply style points, lines, polygons, and labels to impress site visitors with real-time maps. Then you follow a step-by-step guide that installs GeoServer in minutes. You will explore the web-based administrative interface to connect to backend data stores such as PostGIS, and Oracle. Going ahead, you can display your data on web-based interactive maps, use style lines, points, polygons, and embed images to visualize this data for your web visitors. You will walk away from this book with a working application ready for production. After reading GeoServer Beginner's Guide, you will be able to build beautiful custom maps on your website using your geospatial data.
Table of Contents (20 chapters)
Title Page
Credits
About the Author
About the Reviewer
www.PacktPub.com
Customer Feedback
Preface
Index

Setting Caching Defaults


As mentioned previously, the included GeoWebCache comes with a default configuration. Although the default configuration is ready to use, you can manage almost all parameters from the web interface.

The Caching Defaults form includes general parameters. The first section is about services used to expose tiles:

Direct integration

The first option is disabled by default. Direct integration is about the endpoint used in the WMS GetMap requests. If you go with the default option, you will have to use a custom endpoint to tell GeoServer that you want to retrieve a map from the cache if there are tiles available to fulfill your request:

    http://localhost:8080/geoserver/gwc/service/wms? 

Enabling direct integration lets you use the same syntax you would use against a non-cached layer:

    http://localhost:8080/geoserver/<workspace>/wms?tiled=true 

The endpoint is not the only condition required to use cache. Any WMS request has to meet several other conditions in order...