Page Comparison

...

• Spatial table allows nil geometry but you wish to enforce geometry creation
  • Add <requireGeometry>geometryType</requireGeometry> where geometryType matches the underlying spatial table
• Spatial table allows multi part geometry but you wish to enforce creation of single part geometry
  • Add <supportGeometry>geometryType</supportGeometry> where geometryType matches the underlying spatial table
• The spatial engine supports multiple geometry types in a single table, for example Oracle Spatial, and you wish to limit the geometry
  • Add <supportedGeometry>geometryType</supportedGeometry> to limit the available geometry types, otherwise options all will be available

Custom attributes

If the default attribute editing setup isn't suitable you can directly specify the attributes that the user can edit and how they appear to the user, by doing this you'll completely replace the attributes that the Weave automatically generated from the underlying spatial tables.

This is done by adding one or more parameter items to the edit configuration, where each parameter specified one input parameter. The format of the parameter items in an edit config are an extension of those available for search parameters.