1Generalise Release Notes

A logout button has been added to the “smart” UI.

1.2.11

No new enhancements.

1.2.10

No new enhancements.

1.2.9

The Oracle data store supports selecting a savepoint within a workspace. When a generaliseRegion SOAP request specifies a sourceInfo with both workspace and savepoint defined, the savepoint will be selected when the connection underlying the classification is of type Oracle data store. Previously, this worked only with the Contextual data store.

1.2.8

No new enhancements.

1.2.7

No new enhancements.

1.2.6

Sort schemas in classification and profile data stores.

Reinstate create_building_partitions and snap_features builtins. These are unsupported demonstration capabilities.

1.2.5

New builtin operation split_at_junctions that makes a network fully noded as required by some 1Generalise algorithms.

New builtin function set_null_attributes that sets one or more attribute values to null, allowing the attribute names to be parameterized.

Simplification retries generate intersecting edges.

The simplification retry operations – e.g. “process_douglas_peucker_simplification_retries” – applies a number of strategies in order to try to achieve good results:

1. Retry the original simplification in case modifications to nearby features allow it to succeed.

2. Simplify the edge that failed, and then find all other edges that intersect the result, then validate the result. This can achieve a better result when two edges are approximately parallel.

3. Split the edge into half and simplify each half independently. If a half-edge intersects no other nodes or edges and the result does not change topological relationships with any nodes or isolated edges, the result is used. If simplifying the half-edge would break topology, the algorithm is applied recursively to bisect the half-edge.

Intersecting edges were created because strategy #2, the intersecting edge simplifier, relies on the topology engine to determine whether the result is valid. Crossing edges are valid unless an “edges split edges” rule is defined. The reported session used only a “share nodes” rule, so crossing edges are considered valid.

An edges split edges rule is recommended for most uses of 1Generalise. However, the simplification failures processor has been changed to exclude the intersecting edge simplifier if there is no edges split edges rule. The recursive simplifier will generate a valid result.

The logout button in the 1Generalise admin interface now works if the user logged in via the “smart” UI.

It is no longer possible to reproduce a session hanging if the pause button is pressed as it is starting. This was fixed in a recent update to 1Integrate.

1.2.7

Complete the short edge removal fixes started in release 1.2.5.

1.2.6

Further fixes to special cases in buildings short edge removal.

1.2.5

The short edge removal algorithm has been enhanced to achieve greater simplification of areas with inner rings where short edge removal on one of the rings generated self-intersections.

New Cache Viewer available for any task: Can step through state of each task, improved UI for seeing non-conformances and selecting features. The Cache Viewer is available from the Sessions tab in the admin UI.

Configurable styling of cache viewer

Session description button to document contents of session including details of all rules and actions run.

New timings summary page for session

Switch to garbage collection of the session data cache. This means that paused sessions can be deleted via the API or UI immediately, without having to stop each one.

Remove grid parameters from WebLogic installation files included in the release

Remove JDK selection from the installer and update the supported JDK check. All servers will use the JDK configured when the domain was created.

Prevent building_stellate_short_edges from producing sharp angles.

Fix a bug where buffering partitions for National Load child job creation could fail, reporting “MultiPolygon cannot be cast to Polygon”.

Fix a bug where line features that extend a very short distance outside the partition boundary were not written to the target dataset.

Buildings with spikes.

Output from the buildings subflow resulted in 'triangular' buildings or obvious spikes. A number of scenarios have been resolved:

• Where one source building touches another at an angle

• Where one generalised building touches another at an angle

• Where a source building is not square; i.e. has angular sides within the building outline

• Some other rare cases

Resolve rare cases where building simplification generated spikes (short_edge_removal and stellate_short_edges).

Fix a bug where building_remove_short_edges sometimes generated an error: “failed to invoke building_remove_short_edges Caused by: Lines do not intersect”.

Ensure that the ms-generalise-client application includes all required dependent jars (a regression introduced in version 1.1.100).

Extend the 1Generalise Algorithm for snapping Landcover features (or any area features) to handle impassable classes - a feature should not be extended if it interacts with a feature of one of these classes.

Snap areas fails when the snapping should produce a very thin polygon.

Snap Area fails when the area touches the line it needs to snap to.

In very rare cases building simplification enters an infinite loop, resulting in an out of memory error.

When loading an existing classification into the classification UI, filter on attributes which contain several values with space in it could become corrupted, and will need fixing manually.

Manual fix: edit all filter rules that use values with space in it, check that they appear correctly and fix those which are wrong.