featureserver
featureserver copied to clipboard
iocast
FeatureServer is as OGC web feature service and filter encoding Python server.
When a PostGIS column with ':' is selected to be used as attribute (or aliased as such) the consuming XML applications cannot handle the output. I created a small workaround...
See https://trac.osgeo.org/osgeo/ticket/1846#comment:5 Please speak up now or the data could be removed in a week or so.
First, `FeatureServer.DataSource.OGR:__init__` parses the `attribute_cols` [here](https://github.com/iocast/featureserver/blob/2e8c5937e67a9048dd28d2c567b868def466517a/FeatureServer/DataSource/OGR.py#L62). Then, `vectorformats.Formats.WFS` tries to parse them again [here](https://github.com/iocast/featureserver/blob/2e8c5937e67a9048dd28d2c567b868def466517a/vectorformats/Formats/WFS.py#L339). A very basic WFS query: ``` http://localhost:8080/?SERVICE=WFS&VERSION=1.0.0&TYPENAME=states&BBOX=-122.77458907062643334,47.22724615119393832,-121.86953238113640907,47.96610480588739023&REQUEST=DescribeFeatureType ``` results in an error: ``` An error occurred:...
It would be an awesome feature if we could serve tiled GeoJSON (clipped or not) like in Tilestache: http://tilestache.org/doc/TileStache.Goodies.Providers.PostGeoJSON.html so we can use them with HTML5 Canvas in Leaflet or...
Is it possible to set the maximum of features that a query may produce?
Hi, we've been using FeatureServer for a while and we just jumped from 1.12 to 1.15.2. We use it exclusively with Postgis and we've found out some problems using schema...
I have a timestamp field without timezones in the database and when feature server try to serialize it he is unable. There is no standards in JSON nor in GeoJSON...
Reading any WFS service as parameter and getting the same option as a service defined in the configuration file
if a numeric comparison is requested in the FE query, than do a numeric comparison on database instead of string comparison. To determine if numeric or not, a regular expression...