The iterator construct from the Collections api is well understood and loved, but breaks down for working with large GIS data volumes. By using a visitor we allow the implementor of a Feature Collection to make use of additional resources (such as multiple processors or tiled data) concurrently.
This interface is most often used for calculations and data transformations and an implementations may intercept known visitors (such as "bounds" or reprojection) and engage an alternate work flow. @author Cory Horner (Refractions Research, Inc) @source $URL$
|
|
|
|
|
|
|
|