Glenn,

MapServer itself does not read in GeoRSS feeds yet, although I'm sure there are mapscript and XSLT + OGR based solutions deployed out there. I've written about one that uses a little bit of Python mapscript:

  http://zcologia.com/news/336/cartography-data-georss/

Speaking of feeds, there are a bunch of us experimenting with using the Atom Publishing Protocol as a replacement for WFS-T. The nexus for this discussion is

  http://groups.google.com/group/geo-web-rest

One live example is at

  http://labs.metacarta.com/atompub/app-demo.html

The displayed features are posted to FeatureServer using Atompub, not WFS-T. Another live example of GIS + Atompub is at

  http://zcologia.com/hammock/places.html

(I almost wrote "Feeds FTW" here, but that seemed a bit silly.)

Cheers,
Sean


Glenn Brooks wrote:
HI,

I am working on distributing GIS attribute information (and some other 
non-spatial data) to a simple business intellegence/reporting dashboard.  The 
dashboard which will also include a transactional Cartoweb-Mapserver WMS/WFS 
for data entry into the underlying data bases.  Viewable by very non-technical 
people.

I would like to ask if anyone has explored outputting (or automatically 
updating) GIS layers from Postgis to  mapserver or cartoweb WFS clients using 
RSS feeds?  Is this practicable/more simple/or a nightmare?? It seems like it 
would be a

Also, would like to find more documentation about mapserver methods for connecting to Cartoweb and other clients- particularily how to decide whether and when Cartoweb/clients should request data layers directly from data sources then send to Mapserver, versus Mapserver connecting directly to Postgres/postgis or native formats. I am unsure how this should be organized. (The goal here is field-based browser based data editing ( ie create a new point in an existing layer, populate with attribute data- update the master database. I get the transactional side from the user, just don't understand all the linkages between WFS-T and Mapserver)
thanks much,

Glenn Brooks

Reply via email to