Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <blockquote> <p>GeoServer is an open source software server written in Java that allows users to share and edit geospatial data. Designed for interoperability, it publishes data from any major spatial data source using open standards.</p> <p>Being a community-driven project, GeoServer is developed, tested, and supported by a diverse group of individuals and organizations from around the world.</p> <p>GeoServer is the reference implementation of the Open Geospatial Consortium (OGC) Web Feature Service (WFS) and Web Coverage Service (WCS) standards, as well as a high performance certified compliant Web Map Service (WMS). GeoServer forms a core component of the Geospatial Web.</p> <p>(<a href="http://geoserver.org/display/GEOS/Welcome" rel="nofollow">http://geoserver.org/display/GEOS/Welcome</a> as it is on Jan 29th, 2014)</p> </blockquote> <p>A common use for geoserver is with two other componnets: Geowebcache and Openlayers. The first is an actually embed feature in Geoserver default installation. It avoids processing storing images that were generated by Geoserver once. The access to this cache is transparent to the user, using the same endpoint. Openlayers is a javascript library that handles the complexity of assembling the images given by geoserver into a usable map.</p> <p>More information can be found in the following links:</p> <p>Openlayers: </p> <ul> <li><a href="http://openlayers.org/" rel="nofollow">http://openlayers.org/</a></li> <li><a href="http://wiki.osgeo.org/wiki/Openlayers" rel="nofollow">http://wiki.osgeo.org/wiki/Openlayers</a></li> <li><a href="http://geoserver.geo-solutions.it/edu/en/use_ol/ol_map.html" rel="nofollow">http://geoserver.geo-solutions.it/edu/en/use_ol/ol_map.html</a> (creating a simple application with OL and Geoserver)</li> </ul> <p>Geowebcache: </p> <ul> <li><a href="http://docs.geoserver.org/latest/en/user/geowebcache/index.html" rel="nofollow">http://docs.geoserver.org/latest/en/user/geowebcache/index.html</a></li> <li><a href="http://docs.geoserver.org/latest/en/user/geowebcache/using.html" rel="nofollow">http://docs.geoserver.org/latest/en/user/geowebcache/using.html</a></li> </ul> <p>Geoserver is able to abstract many complex operations with geodesic data and can serve the application with many representations of it. The most used are the map images, but other formats like KML (used by Google Earth), JSON and XML are also available, making possible to offer a rich app to the user.</p> <p>It will also allow the administrator to style the map in many ways using defined styles for the layers, described in the format called SLD. Here you have how to:</p> <p>Compose styles (this is a very rich site): <a href="http://docs.geoserver.org/stable/en/user/styling/sld-cookbook/" rel="nofollow">http://docs.geoserver.org/stable/en/user/styling/sld-cookbook/</a> Import them into geoserver and many other operations: <a href="http://docs.geoserver.org/latest/en/user/styling/index.html" rel="nofollow">http://docs.geoserver.org/latest/en/user/styling/index.html</a></p> <p>The input formats will mostly be the Shapefiles or a data connection to the database that contains geospacial data, such as Postgres using the Postgis extension.</p> <p>A brief about the supported formats: <a href="http://docs.geoserver.org/latest/en/user/community/importer/formats.html?highlight=shapefile" rel="nofollow">http://docs.geoserver.org/latest/en/user/community/importer/formats.html?highlight=shapefile</a></p> <p>Importing a shapefile: <a href="http://docs.geoserver.org/latest/en/user/gettingstarted/shapefile-quickstart/index.html" rel="nofollow">http://docs.geoserver.org/latest/en/user/gettingstarted/shapefile-quickstart/index.html</a></p> <p>Connecting to a Postgres/postgis database: <a href="http://docs.geoserver.org/latest/en/user/gettingstarted/postgis-quickstart/index.html" rel="nofollow">http://docs.geoserver.org/latest/en/user/gettingstarted/postgis-quickstart/index.html</a></p> <p>Shapefiles (a format described by ESRI) definition and other useful information:</p> <ul> <li><a href="http://www.esri.com/library/whitepapers/pdfs/shapefile.pdf" rel="nofollow">http://www.esri.com/library/whitepapers/pdfs/shapefile.pdf</a></li> <li><a href="http://www.esri.com/news/arcuser/0401/topo.html" rel="nofollow">http://www.esri.com/news/arcuser/0401/topo.html</a></li> </ul> <p>Postgres and Postgis information:</p> <ul> <li><a href="http://www.postgresql.org/" rel="nofollow">http://www.postgresql.org/</a></li> <li><a href="http://postgis.net/" rel="nofollow">http://postgis.net/</a></li> <li><a href="http://www.postgresql.org/about/news/1387/" rel="nofollow">http://www.postgresql.org/about/news/1387/</a></li> </ul> <p>Geoserver uses the concept of endpoint to serve the information. The parameters are received via GET, making simple request powerfull tools of abstraction. An example with openlayers can be found here:</p> <p><a href="http://openlayers.org/dev/examples/getfeatureinfo-control.html" rel="nofollow">http://openlayers.org/dev/examples/getfeatureinfo-control.html</a></p> <p>The endpoint, in the example is the following:</p> <pre><code>var political = new OpenLayers.Layer.WMS("State Boundaries", "http://demo.opengeo.org/geoserver/wms", { 'layers': 'topp:tasmania_state_boundaries', transparent: true, format: 'image/gif' }, { isBaseLayer: true } ); </code></pre> <p>where - "<strong><a href="http://demo.opengeo.org/geoserver/wms" rel="nofollow">http://demo.opengeo.org/geoserver/wms</a></strong>" is the endpoint for wms serving - <strong>'layers': 'topp:tasmania_state_boundaries'</strong> - we want the *tasmania_state_boundaries* layer from <em>top</em> workspace - <strong>transparent: true</strong> informs the server to leave transparent the regions where there is no information. Otherwise they will be white. - <strong>format: 'image/gif'</strong> - The format of the images we want.</p> <p>It's that simple to access a black hole of geo information that, otherwise, would require too much time to do. Too much time.</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload