Interface IFeatureModel
- All Superinterfaces:
Model
- All Known Subinterfaces:
IHierarchicalFeatureModel
See article for more details on how to use and how to implement this class.
Using a model
A user of a model:
- Can use the query method on any thread
- Can expect model change events on any thread. This means that the user of a model is responsible for creating a thread-safe observer implementation, and for possible rescheduling of the model events on a different thread if needed.
Implementing a model
The model implementation has multiple responsibilities.
- Access the data uniformly. I.e. translate data storage entries into
Featureinstances. - Filter the data. When a user of the model queries the model, he can specify a filter. The model implementation must make sure that data is correctly filtered, as efficiently as possible.
- All model implementations must be thread safe for reading, to allow multiples queries in parallel.
- Make sure dynamic data (i.e. data that changes over time) is updated in a thread-safe way.
- Make sure that notifications are sent when dynamic data changes.
- Make sure that the data is presented in a consistent way. That is, after the model sends out a change event for a
Feature, thequery()method must also reflect that change. This can be guaranteed by making sure that model updates (internal updates + firing model change notifications) and calls to the query method are never executed simultaneously. Notifications must not be sent while thequery()method is executing.
Persisting changes
Feature models can add support for persisting model changes. See this article for more information.
Performance considerations
In order to optimize feature loading, it is recommended to follow these rules when creating a model:
- The model should have bounds.
- The features should contain a property whose value is a geometry.
Featuredata types should have aGeometryDataAnnotation.- The reference used should not be geocentric.
-
Method Summary
Modifier and TypeMethodDescriptionvoidaddObserver(IFeatureModelObserver modelObserver) Adds an observer that allows to receive change events from this feature model.Returns the feature model meta data.Returns theFeatureModelPersistenceManagerthat is used to persist in-memory changes made throughIFeatureModelUpdater.Returns theIFeatureModelUpdaterthat is used to make changes to the model.voidquery(FeatureQuery query, IFeatureQueryCallback callback) Queries the model, and passes the result to the given callback.voidremoveObserver(IFeatureModelObserver modelObserver) Removes the given observer.Methods inherited from interface com.luciad.models.Model
getModelMetadata, queryBounds
-
Method Details
-
query
Queries the model, and passes the result to the given callback.The callback can return false to indicate that the query can stop. This method passes
Featureinstances to the given callback. These instances contain a copy of the original data (structured according to theDataModelof this model). The ownership of these features is passed to the caller of this method (through the callback). This means that the model is not allowed to modify/deleted theseFeatureinstances, once they are passed to the callback function.This method is thread-safe, and can be called on any thread.
This method is synchronous and blocking. In other words, as soon as this function returns
- the given callback must have been called for each resulting feature
- no more calls to the callback can be done anymore
Implementations of this method have the responsibilities described in the class documentation.
When implementing this method you may want to use the existing evaluation support which you can find in
FeatureExpressionEvaluatorandFeatureExpressionEvaluatorFactory.Example to query the model for a
Featurewith a specific id.FeatureQuery query = FeatureQuery.newBuilder().featureIds(List.of(featureId)).build(); model.query(query, feature -> { System.out.println(feature.getId()); return false; });- Parameters:
query- the querycallback- a callback which can handle the result of the query operation
-
addObserver
Adds an observer that allows to receive change events from this feature model.Adding the same observer twice is forbidden, and will cause an exception to be thrown.
- Parameters:
modelObserver- an observer- Throws:
IllegalArgumentException- when the observer was already added.
-
removeObserver
Removes the given observer.If the given observer was never added, an exception is thrown.
- Parameters:
modelObserver- an observer- Throws:
IllegalArgumentException- when the observer is not known.
-
getFeatureModelMetadata
Returns the feature model meta data.It provides information about the types of features one can expect within the model.
- Returns:
- the feature model meta data.
-
getUpdater
Returns theIFeatureModelUpdaterthat is used to make changes to the model.When a model can't be updated,
nullmust be returned.Typically,
IFeatureModelimplementations implement these changes as in-memory changes.FeatureModelPersistenceManagercan then be used to persist those changes (if persisting changes is supported). AnIFeatureModelcan however choose to immediately persist any of these changes immediately, if persisting changes doesn't imply a large performance overhead for example. In that case aFeatureModelPersistenceManageris not needed, andgetPersistenceManagermust returnnull.- Returns:
- the updater that can be used for this model.
-
getPersistenceManager
Returns theFeatureModelPersistenceManagerthat is used to persist in-memory changes made throughIFeatureModelUpdater.When a model doesn't support (or doesn't need) saving functionality,
nullmust be returned.If persisting changes is not supported by the model, or if it is not needed because
IFeatureModelUpdateralready automatically persists its changes, this method must returnnull.- Returns:
- the
FeatureModelPersistenceManagerthat can be used for this model. - Since:
- 2023.1
-