Dear Chris, dear list,
The following XML Schema describes my WFS layer (DescribeFeatureType):
xsd:complexType name=zonesType
xsd:complexContent
xsd:extension base=gml:AbstractFeatureType
xsd:sequence
xsd:element maxOccurs=1 minOccurs=0 name=geom
nillable=true
Dear list, dear Chris,
Sorry for posting so limited information, as I merely described the usage
scenario...
Below I pasted the verbose log, starting off with the actual WFS-T-request
posted by MapInfo (inserting a single feature; column names: geom,
sitename). Just before the massive stack
Can you post in the results of a describe feature type? And of a wfs get
feature from that table?
Could you try to re-insert one of the results you get from a get feature
request back in? To see if it's a mapinfo problem or a problem with all
transactions.
On Thu, Jan 20, 2011 at 4:15 AM,
Dear list,
I have a PostGIS table with just 8 geometries (polygons), each row having
only one data attribute (character(8) ).
Using MapInfo 10.5 as a client, I downloaded these through WFS. Then, I
added one feature by drawing a polygon and assigning some text to the new
records' single
You're going to need to provide some more info to give anyone the chance to
help solve the problem.
Can you get what the actual transaction request that MapInfo is sending?
Posting the logs with the logging level turned up also may help.
Chris
On Wed, Jan 19, 2011 at 11:20 AM, InterRob
