The commercialization of GIS applications refers to the process of bringing a software solution to market. The process involves three broad categories of tasks: identifying a problem or aspect of a problem that a GIS application can solve or address; designing and creating a GIS application to address the problem; and developing and executing a marketing plan to reach those with the problem, the potential users. Ideally these categories would be addressed in this order, but in practice, aspects of each are likely to be addressed and iterated throughout the commercialization process.

Bringing a GIS application to market requires expertise in 1) the target industry or market (e.g., forestry); 2) software development (how to design and build a product); 3) law (licenses, contracts, taxes); and 4) business (how to fund development, guide the process, evaluate success, marketing). A single individual or organization, referred to as the provider in this discussion, may lead or execute all three categories of tasks, or engage third parties when specific expertise is required.

Figure 1. Group movement patterns as illustrated in this coordinated escape behavior of a group of mountain goat (Rubicapra rubicapra) evading approaching hikers on the Fuorcla Trupchun near the Italian/Swiss border are at the core of computational movement analysis. Once the trajectories of moving objects are collected and made accessible for computational processing, CMA aims at a better understanding of the characteristics of movement processes of animals, people or things in geographic space.

Computational Movement Analysis (CMA) develops and applies analytical computational tools aiming at a better understanding of movement data. CMA copes with the rapidly growing data streams capturing the mobility of people, animals, and things roaming geographic spaces. CMA studies how movement can be represented, modeled, and analyzed in GIS&T. The CMA toolbox includes a wide variety of approaches, ranging from database research, over computational geometry to data mining and visual analytics.

Within an initial phase of database design, a conceptual data model is created as a technology-independent specification of the data to be stored within a database. This specification often times takes the form of a formalized diagram.  The process of conceptual data modeling is meant to foster shared understanding among data modelers and stakeholders when creating the specification.  As such, a conceptual data model should be easily readable by people with little or no technical-computer-based expertise because a comprehensive view of information is more important than a detailed view. In a conceptual data model, entity classes are categories of things (person, place, thing, etc.) that have attributes for describing the characteristics of the things.  Relationships can exist between the entity classes.  Entity-relationship diagrams have been and are likely to continue to be a popular way of characterizing entity classes, attributes and relationships.  Various notations for diagrams have been used over the years. The main intent about a conceptual data model and its corresponding entity-relationship diagram is that they should highlight the content and meaning of data within stakeholder information contexts, while postponing the specification of logical structure to the second phase of database design called logical data modeling.