SOLAP.Issues,.Challenges,.and.Recommendations
Although there remain computing challenges for SOLAP, our geomatics engineering
perspective leads us to see the most crucial issues as the ones that relate to the
management and processing of spatial referencing. We need to facilitate the flow
of spatial data from the geospatial data sources to the datacubes. When compared
to traditional GIS research, research in spatial data warehousing, spatial OLAP, and
spatial datacubes requires to deal with more complex issues like:
??? Integrating time (which is ubiquitous in datacubes) with space: Very few GIS
databases are temporal, and when they are, they suffer from the same complexity
issues as traditional DBMS (versionings, querying versions) but they
must also deal with the evolution and tracing of the position of objects (e.g.,
a moving point representing a vehicle in real-time) as well as the evolution
of their shape (e.g., a forest fire, a building which has been enlarged), and
their mergings/splittings (e.g., many country boundaries have changed since
the late 1980s). Furthermore, it is not rare to see spatial datacubes where the
temporal resolution of the measures is finer (e.g., monthly values) than that of
the available cartographic data (e.g., annual maps), creating new challenges
especially with using the proper metadata and user warnings.
Pages:
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572