org.geotools.validation
Interface IntegrityValidation
- All Superinterfaces:
- Validation
- All Known Implementing Classes:
- AddressGapValidation, AddressOverlapValidation, AngleSizeValidation, ContainsIntegrity, CrossesIntegrity, DefaultIntegrityValidation, DisjointIntegrity, IntersectsIntegrity, LineAbstractValidation, LineCoveredByFeatureLineValidation, LineCoveredByPolygonBoundaryValidation, LineCoveredByPolygonValidation, LineEndPointCoveredByLineValidation, LineIntersectsLineWithNodeValidation, LineLineAbstractValidation, LineNoDanglesValidation, LineNoPseudoNodeValidation, LineNotTouchingPolygonInteriorValidation, LinePointAbstractValidation, LinePolygonAbstractValidation, LinesNotIntersectValidation, LinesNotOverlapValidation, OrphanNodeValidation, OverlapsIntegrity, PointCoveredByEndPointOfLineValidation, PointCoveredByLineValidation, PointCoveredByPolygonBoundaryValidation, PointCoveredByPolygonValidation, PointInsidePolygonValidation, PointLineAbstractValidation, PointPolygonAbstractValidation, PolygonBoundaryCoveredByPolygonValidation, PolygonCoveredByFeaturePolygonValidation, PolygonCoveredByPolygonValidation, PolygonLineAbstractValidation, PolygonNotCoveredByPolygonValidation, PolygonNotOverlappingLineValidation, PolygonNotOverlappingPolygonValidation, PolygonPointAbstractValidation, PolygonPolygonAbstractValidation, RelateIntegrity, RelationIntegrity, StarNodeValidation, TouchesIntegrity, UniqueFIDValidation, UniquityValidation, WithinIntegrity
public interface IntegrityValidation
- extends Validation
Used to check geospatial information for integrity.
Each ValidationPlugIn is very specific in nature: it performs one test
extermly well. This simplifies design decisions, documenation
configuration and use.
Following the lead the excelent design work in the JUnit testing framework
validation results are collected by a ValidationResults object. This
interface for the ValidationResults object also allows it to collect
warning information.
The PlugIn is also required to supply some metadata to aid in its
deployment, scripting, logging and execution and error recovery:
-
name: user's name of validation test
-
description: user's description of validation test
-
priority: used to schedule validation test
-
typeNames: used to connect validaiton test to transaction opperation
Capabilities:
-
Uses FeatureResults to allow environment to gather error/warning information
as required (transaction XML document, JTable, logging system, etc...)
-
Primiarly used as part of processing the Transaction opperation of a Web
Feature Server. Used to ensure that the DataStore is consistent before
commiting a Transaction.
- Author:
- Jody Garnett, Refractions Research
- Module:
modules/extension/validation (gt-validation.jar)
validate
boolean validate(Map layers,
ReferencedEnvelope envelope,
ValidationResults results)
throws Exception
- Used to check features against this validation rule.
The layers Map is still under developement, current thinking involves
storing a FeatureSource of the correct typeName requested by
getTypeNames(), using the current geotools2 Transaction as the
opperation being validated.
We may need to extend this information to provide:
-
FeatureTypeMetaData: we may with to configure against metadata
-
Networks: networks are expensive to produce, we may be able to have the
ValidationProcessor cache a network for later.
- Parameters:
layers
- Map of FeatureSource by "dataStoreID:typeName"envelope
- The bounding box that encloses the unvalidated dataresults
- Used to coallate results information
- Returns:
true
if all the features pass this test.
- Throws:
Exception
Copyright © 1996-2010 Geotools. All Rights Reserved.