An example of CarbonArc PRO 1.6 using WFS-T is now available on YouTube

http://www.youtube.com/watch?v=wVrcr_zI9e8

Regards,
The Carbon Project

CarbonArc PRO provides a sophisticated set of WFS-T editing tools. But before using transactions CarbonArc needs to to know a little something about the WFS-T server, the transactional feature layers and all properties associated with the transacted features.

The Manage Transaction Sources tool allows the management and editing of the required information. In addition, this tool can auto-generate property types and rules for WFS Transactions using the appropriate GML schema.

For example, in order to add a new feature CarbonArc must know what layers in the map have actual Insert capability, what are the properties the feature can have, what rules apply to these properties and what types of geometries are allowed for the feature. Without this knowledge at hand, discovering and applying this information for each operation will make feature editing slow and cumbersome, unfit for a productive, user-friendly environment. CarbonArc resolves this by asking the user to set (just once) the information about the used transaction layers. The information is saved in a transactions cache file. Once a layer is registered to the transactions cache file any changes to its settings and rule will be updated in the managed file and will be available to all future CarbonArc sessions.

Question - it sounds like you may have set up “Manage Transaction Sources” for your WFS-T but we wanted to confirm.

Regards,
The Carbon Project

We have successfully used CarbonArc’s WFS-T (transaction) capability in a project here in Canada to insert, update and delete features from a framework data WFS server.

Can you describe the nature of the problems you ran into? I am curious myself to see what specific issues you had.

Ciao.