Modeling emergency management data by UML as an extension of geographic data sharing model: ASAT approach

Abstract

Applying GIS functionality provides a powerful decision support in various application areas and the basis to integrate policies directed to citizens, business, and governments. The focus is changing toward integrating these functions to find optimal solutions to complex problems. As an integral part of this approach, geographic data sharing model for Turkey were developed as a new approach that enables using the data corporately and effectively. General features of this model are object-oriented model, based on ISO/TC211 standards and INSPIRE Data Specifications, describing nationwide unique object identifiers, and defining a mechanism to manage object changes through time. The model is fully described with Unified Modeling Language (UML) class diagram. This can be a starting point for geographic data providers in Turkey to create sector models like Emergency Management that has importance because of the increasing number of natural and man-made disasters. In emergency management, this sector model can provide the most appropriate data to many "Actors" that behave as emergency response organizations such as fire and medical departments. Actors work in "Sectors" such as fire department and urban security. Each sector is responsible for "Activities" such as traffic control, fighting dire, emission, and so on. "Tasks" such as registering incident, fire response, and evacuating area are performed by actors and part of activity. These tasks produce information for emergency response and require information based on the base data model. By this way, geographic data models of emergency response are designed and discussed with "Actor-Sector-Activity-Task" classes as an extension of the base model with some cases from Turkey.

Cite this work

No public copy is stored for this record, so only the metadata is cited.

Stored only when both papers are in the corpus — 4 citations exist upstream.

Papers that cite the same references — the relational fallback while embeddings are still backfilling.