Hi,
I'm looking into extending the RSS/atom output to actually support GML3.
By the looks of it the code is simply not there, the GML object is available
but the
public void encode(Geometry g, GeoRSSTranslatorSupport translator) {
}
for it has not been implemented.
Now, GeoServer can do GML3 encoding, but the Encoder cannot take
a GeoRSSTranslatorSupport object to do it... so I'm wondering what's
the best way to handle this: shall we recode the geometry encoding
using the GeoRSSTranslatorSupport api (does not look like a daunting
task since we support only a limited number of geometries) or is there
any way to bridge the two worlds and use the Encoder to do it
sparing us from code duplication?
Cheers
Andrea
--
-------------------------------------------------------
Ing. Andrea Aime
GeoSolutions S.A.S.
Tech lead
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 962313
mob: +39 333 8128928
http://www.geo-solutions.it
http://geo-solutions.blogspot.com/
http://www.youtube.com/user/GeoSolutionsIT
http://www.linkedin.com/in/andreaaime
http://twitter.com/geowolf
-------------------------------------------------------
------------------------------------------------------------------------------
Free Software Download: Index, Search & Analyze Logs and other IT data in
Real-Time with Splunk. Collect, index and harness all the fast moving IT data
generated by your applications, servers and devices whether physical, virtual
or in the cloud. Deliver compliance at lower cost and gain new business
insights. http://p.sf.net/sfu/splunk-dev2dev
_______________________________________________
Geoserver-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
