I posted an earlier question about the use of WFS within GeoServer to store
dynamic feature data, for example a fire, that is created by another legacy
application that already stores the data in our database. It seems the
"straightforward" approach would be to have the other application also use a
GeoServer REST based WFS to create the feature, correct? Another proposed
approach however is to extend GeoServer with some GeoTools based code
(AbstractDataStore, FeatureReader, etc) that would actually pull the data from
the database and internally create the corresponding feature within GeoServer.
Does anyone have experience with such an approach or can someone comment as to
which approach may be superior or more in line with how GeoServer should be
used?
Thanks in advance,
Jack Ottofaro
------------------------------------------------------------------------------
Beautiful is writing same markup. Internet Explorer 9 supports
standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 & L3.
Spend less time writing and rewriting code and more time creating great
experiences on the web. Be a part of the beta today.
http://p.sf.net/sfu/beautyoftheweb
_______________________________________________
Geoserver-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-users
