In a conventional Geospatial Information Systems (GIS) architecture, spatial data is stored as a single representation that essentially models the humble map. Each feature is referenced by a single coordinate system using a common unit system. For applications that require simple map-like functions such as quick navigation, simple spatial queries and rudimentary analysis, this is an adequate approach. However, in the enterprise GIS environment this is an inflexible solution. Many assets have more than one representation: perhaps a geographic one that specifies its location and an additional representation that models its intricate internal workings. This kind of asset is difficult to model using a conventional GIS architecture.
|
GIS Weekly Magazine
Susan Smith
 |
Look for the next issue of GIS Weekly Magazine on May 28, 2012.
Each GISWeekly Review delivers to its readers news concerning the latest developments in the GIS industry, along with a selection of other articles that we feel you might find interesting. |
|
|
|
