Shapefile¶
A shapefile is a popular geospatial vector data format.
Note
While GeoServer has robust support for the shapefile format, it is not the recommended format of choice in a production environment. Databases such as PostGIS are more suitable in production and offer better performance and scalability. See the section on Running in a production environment for more information.
Adding a shapefile¶
A shapefile is actually a collection of files (with the extensions: .shp, .dbf, .shx, .prj, and sometimes others). All of these files need to be present in the same directory in order for GeoServer to accurately read them. As with all formats, adding a shapefile to GeoServer involves adding a new store to the existing Stores through the Web administration interface.
Warning
The .prj file, while not mandatory, is strongly recommended when working with GeoServer as it contains valuable projection info. GeoServer may not be able to load your shapefile without it!
To begin, navigate to .
Adding a shapefile as a store¶
Option |
Description |
Workspace |
Name of the workspace to contain the store. This will also be the prefix of the layer created from the store. |
Data Source Name |
Name of the shapefile as known to GeoServer. Can be different from the filename. The combination of the workspace name and this name will be the full layer name (ex: topp:states). |
Description |
Description of the shapefile/store. |
Enabled |
Enables the store. If unchecked, no data in the shapefile will be served. |
URL |
Location of the shapefile. Can be an absolute path (such as |
namespace |
Namespace to be associated with the shapefile. This field is altered by changing the workspace name. |
create spatial index |
Enables the automatic creation of a spatial index. |
charset |
Character set used to decode strings from the |
memory mapped buffer Cache and reuse memory maps |
Enables the use of memory mapped I/O, improving caching of the file in memory. Turn off on Windows servers. |
When finished, click Save.