is an implementation of a RESTful Geographic Feature Service using standard HTTP methods
FeatureServer is an implementation of a RESTful Geographic Feature Service. Using standard HTTP methods, you can fetch a representation of a feature or a collection of features, add new data to the service, or delete data from the service. Use it as an aggregator -- post your GeoRSS feeds to it, and then browse them using WFS. Use it as a translator: use the OGR DataSource to load a shapefile and open it in Google Earth.
| Datasource | Description | Support | Example |
|---|---|---|---|
| DBM | The DBM datasource uses anydbm combined with pickle to store features in a file on disk. This works on any platform, and works right out of the box. Info The BerkleyDB datasource is a subclass of the DBM datasource. It uses a BerkleyDB module for storage. |
config | |
| Flickr | Load images from flickr. | config | |
| GeoAlchemy | GeoAlchemy is an extension of SQLAlchemy, the python database toolkit, for spatial databases. GeoAlchemy datasource for FeatureServer allows you to access features stored in one of the supported spatial databases. As the moment GeoAlchemy supports PostGIS, MySQL and Spatialite. | config | |
| OGR | The OGR datasource allows you to take any OGR datasource -- such as a shapefile, PostGIS database, GML file, or other formats supported by OGR -- and use it as a backend for a FeatureServer layer. | config | |
| OSM | Load streets from OpenStreetMap by area, id, or key/value pair. | config | |
| PostGIS | The PostGIS datasource implements a direct connection to PostGIS, allowing for full featured editing/updating. | WFS WFS-T FE |
config |
| SpatialLite new | SpatiaLite is an open source library intended to extend the SQLite core to support fully fledged Spatial SQL capabilities. | WFS WFS-T FE |
config |
| SQLite | A simple SQLite datasource that can be used on any website with Python support for SQLite. Creates 2 tables for each layer: one for the features, and one for any attributes/properties pertaining to those features. | config | |
| Powered by Twittervision, the twitter datasource lets you use twittervision's API to display the current location of a user. | config | ||
| WFS | The WFS datasource implements read-only access to WFS servers. | config |
| Service | Description | Exception/Error Output new |
|---|---|---|
| CSV | Outputs each attribute of a feature as a separate column and the geomtry as WKT. | example |
| DXF (AutoCAD) new | Compatible with release 11 and 12, points, polyline (linestring), polygon | not supported |
| GeoJSON | input and output in the emerging GeoJSON specification. FeatureServer supports GeoJSON Points, Lines, and Polygons with Rings, as both input and output. | example |
| GeoRSS Atom (Simple) | input and output of Points/Lines/Polygons (no rings/holes) in GeoRSS Simple (Atom). This allows one to take any GeoRSS Simple Atom feed and feed it to FeatureServer for storage. | example |
| GML/WFS | Output-only support of WFS/GML. | example |
| GPX new | GPX (the GPS Exchange Format) is a light-weight XML data format for the interchange of GPS data (waypoints, routes, and tracks) between applications and Web services on the Internet. E.g. it can be used for Garmin devices. Info Points are converted to wpt and LineStrings to trkseg. Polygons are first converted to LineString and then treated as LineString. |
not supported if you think it is needed please leave a message on the mailing list. |
| HTML | Output-only support of features as HTML files, powered by Cheetah templates. | example |
| KML | Input and output of Points, Lines, and Polygons from KML. | not supported if you think it is needed please leave a message on the mailing list. |
| OSM | Output-only support of features as OpenStreetMap '.osm' files. (These files can be opened using JOSM and posted to the OSM server.) | not supported if you think it is needed please leave a message on the mailing list. |
| OV2 new | TomTom Points of Interest Database | not supported |
| Shapefile new | The Esri shapefile or simply a shapefile is a popular geospatial vector data format for geographic information systems software. It is developed and regulated by Esri as a (mostly) open specification for data interoperability among Esri and other software products. | not supported |
| SQLite/SpatiaLite new | SpatiaLite is an open source library intended to extend the SQLite core to support fully fledged Spatial SQL capabilities. | not supported |