Opened 15 years ago
Last modified 12 years ago
#85 new defect
Manage multi-polygons
Reported by: | yvesm | Owned by: | |
---|---|---|---|
Priority: | major | Milestone: | 1.8.0 |
Component: | server | Version: | |
Keywords: | Cc: |
Description
Currently, the only service that supports writing to PostGIS in GeoPrisma is FeatureServer. However, FS does not support multiple geometries, at least multipolygons and this is a drag because ETL tools (e.g. Talend) tend to create multipolygons to begin with. Even if multipolygons which really are polygons can be coerced into polygons in PostGIS (or using other tools), there are cases where features are true multipolygons. Those can be read fine, but cannot be edited. Would MapFish Server help here ?
Change History (8)
comment:1 by , 14 years ago
comment:2 by , 14 years ago
We could proxy to TinyOWS for sure. But for the record may I add that we haven't covered the use of MFS really seriously. MFS will run very efficiently under Apache's mod_wsgi (which is no big Java process either). In fact I'd be curious to test speed FS (mod_wsgi or mod_python), MFS (mod_wsgi) and TinyOWS (FCGI) for GeoJSON. MFS also has the possibility of returning only feature attributes (no geometry) so that could be very interesting in pop ups or to populate dropdownlists e.g. shortcut.
The support for OGC filters is something really cool though but http://mapfish.org/doc/2.0/framework/customizing-webservices.html#adding-filters looks cool too. Anyways, that's lots of new services for us to proxy to in the future :-)
comment:3 by , 13 years ago
Milestone: | → 1.0.0 |
---|
FeatureServer will never have this new feature. Is this still a valid issue ?
comment:4 by , 13 years ago
Milestone: | 1.0.0 → 1.2.0 |
---|
We should decide if we still want to support featureserver in 1.2
comment:5 by , 13 years ago
FeatureServer is marked for deprecation in 1.2, so we could forget this fix.
comment:6 by , 13 years ago
Milestone: | 1.2.0 → 1.4.0 |
---|
TinyOWS could be a nice solution too :