All Topics

A B C D E F G H I K L M N O P R S T U V W
AM-54 - Landscape Metrics

Landscape metrics are algorithms that quantify the spatial structure of patterns – primarily composition and configuration - within a geographic area. The term "landscape metrics" has historically referred to indices for categorical land cover maps, but with emerging datasets, tools, and software programs, the field is growing to include other types of landscape pattern analyses such as graph-based metrics, surface metrics, and three-dimensional metrics. The choice of which metrics to use requires careful consideration by the analyst, taking into account the data and application. Selecting the best metric for the problem at hand is not a trivial task given the large numbers of metrics that have been developed and software programs to implement them.

GS-04 - Location Privacy

How effective is this fence at keeping people, objects, or sensitive information inside or outside? Location Privacy is concerned with the claim of individuals to determine when, how, and to what extent information about themselves and their location is communicated to others. Privacy implications for spatial data are growing in importance with growing awareness of the value of geo-information and the advent of the Internet of Things, Cloud-Based GIS, and Location Based Services.  

In the rapidly changing landscape of GIS and public domain spatial data, issues of location privacy are more important now than ever before. Technological trailblazing tends to precede legal safeguards. The development of GIS tools and the work of the GIS&T research and user community have typically occurred at a much faster rate than the establishment of legislative frameworks governing the use of spatial data, including privacy concerns. Yet even in a collaborative environment that characterizes the GIS&T community, and despite progress made, the issue of location privacy is a particularly thorny one, occurring as it does at the intersection of geotechnology and society.

AM-46 - Location-allocation modeling

Location-allocation models involve two principal elements: 1) multiple facility location; and 2) the allocation of the services or products provided by those facilities to places of demand. Such models are used in the design of logistic systems like supply chains, especially warehouse and factory location, as well as in the location of public services. Public service location models involve objectives that often maximize access and levels of service, while private sector applications usually attempt to minimize cost. Such models are often hard to solve and involve the use of integer-linear programming software or sophisticated heuristics. Some models can be solved with functionality provided in GIS packages and other models are applied, loosely coupled, with GIS. We provide a short description of formulating two different models as well as discuss how they are solved.

CP-12 - Location-Based Services

Location-Based Services (LBS) are mobile applications that provide information depending on the location of the user. To make LBS work, different system components are needed, i.e., mobile devices, positioning, communication networks, and service and content provider. Almost every LBS application needs several key elements to handle the main tasks of positioning, data modeling, and information communication. With the rapid advances in mobile information technologies, LBS have become ubiquitous in our daily lives with many application fields, such as navigation and routing, social networking, entertainment, and healthcare. Several challenges also exist in the domain of LBS, among which privacy is a primary one. This topic introduces the key components and technologies, modeling, communication, applications, and the challenges of LBS.

DM-35 - Logical Data Models

A logical data model is created for the second of three levels of abstraction, conceptual, logical, and physical. A logical data model expresses the meaning context of a conceptual data model, and adds to that detail about data (base) structures, e.g. using topologically-organized records, relational tables, object-oriented classes, or extensible markup language (XML) construct  tags. However, the logical data model formed is independent of a particular database management software product. Nonetheless such a model is often constrained by a class of software language techniques for representation, making implementation with a physical data model easier. Complex entity types of the conceptual data model must be translated into sub-type/super-type hierarchies to clarify data contexts for the entity type, while avoiding duplication of concepts and data. Entities and records should have internal identifiers. Relationships can be used to express the involvement of entity types with activities or associations. A logical schema is formed from the above data organization. A schema diagram depicts the entity, attribute and relationship detail for each application. The resulting logical data models can be synthesized using schema integration to support multi-user database environments, e.g., data warehouses for strategic applications and/or federated databases for tactical/operational business applications.