Open MathiasBaumgartinger opened 4 years ago
Further discussed resulted in following structure:
This will also be relevant for #237 and #235.
Classes are described as follows (in German):
Configurator (Superclass):
Layers (Singleton):
LayerConfigurator:
Layer:
GeoLayer:
LayerRenderers : Configurator:
new RenderedLayer
LayerRenderer:
LayerUI : Configurator:
new UILayer
For a deeper understanding we have defined three "user-stories":
d693969fcf29eb1c3e53e9921ead36e3b0677f32 provided a basic implementation for most of these classes.
We should move these descriptions and images to the wiki.
Same as #248: rather than the Wiki, we'll use Markdown documents within the project source for this.
As mentioned in #235, we will restructure the the whole node-tree. In more detail, the new structure should have a layer-based system. A LayerContainer which will handle every additional geo-information. This can for instance be raster-data, such as vegetation (grass, trees, ...) but also vector-data, such as assets (existing wind-turbines).
Layers should also be able to be grouped (sublayers), for example there will be different street sublayers grouped in one street-layer. Layers will be instanced by a
WorldConfigurator
according to information from the configuration node (at issue #230). A layer's sole purpose will be display of geodata. It will access the geodata via a global distributor of geodata.A general idea was to have super-class
Layer
and then distinguish between anObjectLayer
and anAreaLayer
.