we are doing a small survey with regard to the features of several
Web
Feature Services, one of them is Geoserver.
I tried to fill in the following list of functionality as good as I
could
using the documentation available. Would be great if somebody on this
list
could comment on this. If you think some of the functionality that
Geoserver is good at is not in this list, then please indicate this.
You missed one datasource - arcsde is supported as well. I don't really
understand the 'possibility to define not supported' category. If you
could explain that better I could answer, but you probably can.
-is locking supported on all data sources?
Yes, locking is supported on all data sources. It's done in geotools,
so does not rely on the backend datastore (though there is a framework
to do that as well, to do stronger back end locking if needed).
-can I use namespaces for my typenames, as defined in the OGC WFS
spec?
Yep, namespaces are fully supported, will validate completely.
-is the FeatureIdentifier used in the response and with what kind of
information is it filled (primary key column?)
Yes, fid is definitely used. It is generally the primary key column,
but it is data source specific (there aren't fids in shapefiles, so we
use the line number), and can default to other stuff when there is no
primary key defined (like oid in postgis).
-is the OGC Filter fully supported on all datasources?
Yep. If the data source can handle the filtering itself we pass it off
to them, encode the filter in sql. If the data source can't then we do
it with geotools, in java. Which is a bit slower, but it's nice
becaues we can fully support filters for all datasources.
-are database views supported?
There is support for this, but it's rather new, so not super well
tested.
The big thing missing is the web admin interface. This is in 1.2-beta,
and we're getting it up to at least rc1 now, just need a few more
tweaks and then a bunch of cross platform testing to call it 1.2.0.
But it makes configuration a breeze, no files that you have to modify
by hand that may get parsed wrong, it's quite nice to use, all thanks
to the excellent team at refractions. And it also includes limited WMS
support, at least enough to visualize the data, in a variety of formats
(including svg). Oh yeah, and gzipped output, to cut down on bandwidth
of responses. And automatic generation of DescribeResponses, you don't
have to configure schema files for each featureType, it will just
figure them out on their own. And a pluggable datastore scheme that
makes it really easy to add your own new datasource. Ok, I'll stop now
WFS interface:
--------------
GetCapabilities supported
DescribeFeatureType supported
GetFeature supported
GetFeatureWithLock supported
Transaction supported
LockFeature supported
Maxfeatures supported
DCPType HTTP GET supported
DCPType HTTP POST supported
GML version 2.1.2
WFS version 1.0.0
namespace support
for typenames supported??
Possibility to define not supported??
GML profiles (like
the ESRI GML profile)
FeatureIdentifier unknown??
in response?
Data sources:
-------------
Oracle Spatial
Shapefile
PostGIS
Thanks in advance for any info.
Best regards,
Bart
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
----------------------------------------------------------
This mail sent through IMP: https://webmail.limegroup.com/