[postgis-users] PostGIS and ADO.NET

[Jeff Dege]

If we were using WFS, we'd be using MapServer to serve it, so it looks
like WFS-T is out.
 
So far, we've been doing everything web-based. A desktop editor would be
a nice fit for some problems, but it's not a must-have.
 
If we can put and get WKT from the database using the PostGress drivers
that may be our solution.
 
Thanks for the help.

________________________________

	From: postgis-users-bounces at postgis.refractions.net
[mailto:postgis-users-bounces at postgis.refractions.net] On Behalf Of Obe,
Regina
	Sent: Thursday, April 26, 2007 12:38 PM
	To: PostGIS Users Discussion
	Subject: RE: [postgis-users] PostGIS and ADO.NET
	
	
	I believe that WFS-T spec which I think GeoServer supports is
designed for transactional editing via WFS.  Mapserver unfortunately
does not support WFS-T to my knowledge. 
	 
	I haven't played around with WFS-T so don't know much about it
and am not too familar with many client apps that can use it directly
except for uDig (which can edit PostGIS directly anyway I think but is a
Java app) and OpenLayers which seems to support WFS-T but can't comment
on how good that support is.  
	 
	The PostGreSQL ADO.NET drivers can manipulate the attribute data
easily.  I do that all the time.
	 
	Are you looking for a web-based editor or a desktop editor?
	 
	If you are looking to have your users edit data from an ASP.NET
page and have the ASP.NET page update the database, then one thought
that comes to mind is to use the WKT driver in OpenLayers (don't know
how robust it is, but looks like its designed to both read and edit WKT
data)
	 
	
http://trac.openlayers.org/browser/sandbox/tschaub/wkt/lib/OpenLayers/Fo
rmat/WKT.js?rev=2902
	
http://trac.openlayers.org/browser/sandbox/tschaub/wkt/examples/wkt.html
?rev=2902
	 
	Then you can use the AsText() function and GeomFromText()
functions built into PostGIS to dish out WKT data and consume the WKT
data.  With that you can get by with just the npgsql ADO.NET driver for
editing and dishing out selected regions, your mapserver/KaMap for heavy
map rendering, and openLayers for bridging the gaps.
	 
	Hope that helps,
	Regina
	 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/postgis-users/attachments/20070426/220b2204/attachment.html>