On Wed, Oct 6, 2010 at 6:47 PM, Ottofaro, Jack <jack.ottof...@lmco.com> wrote: > 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?
If you're dealing with vector data a custom datastore is the way to go. Have a look at: http://docs.geotools.org/latest/tutorials/advanced/datastore.html (mind, it requires GeoTools 2.7.x so it will work on GeoServer 2.1.x) Cheers Andrea ----------------------------------------------------- Ing. Andrea Aime Senior Software Engineer GeoSolutions S.A.S. Via Poggio alle Viti 1187 55054 Massarosa (LU) Italy phone: +39 0584962313 fax: +39 0584962313 http://www.geo-solutions.it http://geo-solutions.blogspot.com/ http://www.linkedin.com/in/andreaaime http://twitter.com/geowolf ----------------------------------------------------- ------------------------------------------------------------------------------ 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 Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users
