Module 1: Learning the basic concepts of GeoDMS

From ObjectVision

(Difference between revisions)
Jump to: navigation, search
Line 4: Line 4:
Every data item has a [[domain unit]], which defines its entity. For example, we have a geographic data set with provinces in the Netherlands. The Netherlands has 12 provinces, so you could say that the [[domain unit]] has 12 rows, one row for each province. Within this [[domain]] we have information about each province: name, number of inhabitants, and geometry. Each information field is called an [[attribute]]: an [[attribute]] of the [[domain unit]] provinces.  
Every data item has a [[domain unit]], which defines its entity. For example, we have a geographic data set with provinces in the Netherlands. The Netherlands has 12 provinces, so you could say that the [[domain unit]] has 12 rows, one row for each province. Within this [[domain]] we have information about each province: name, number of inhabitants, and geometry. Each information field is called an [[attribute]]: an [[attribute]] of the [[domain unit]] provinces.  
-
Each of those [[attributes]] holds information, and this can be numbers, text, or coordinates. We must tell GeoDMS what kind of information is being stored for each [[attribute]], this is called the [[values unit]].  
+
Each of those attributes holds information, and this can be numbers, text, or coordinates. We must tell GeoDMS what kind of information is being stored for each [[attribute]], this is called the [[values unit]].  
 +
 
 +
So, if we would see a dataset as a table, the number of rows (and its fixed order) are called the domain unit and the collumns represent attributes of that domain unit.
 +
 
 +
=='''GeoDMS GUI lay-out'''==
 +
 
 +
 
-
* Domain units
 
-
* Attributes
 
* Parameters
* Parameters
-
* Value units
 
* Units
* Units
* Expressions
* Expressions

Revision as of 15:30, 7 April 2020

Key concepts

Before we dig into the practical part, let's discuss some key concept which are fundamental to understanding GeoDMS and enables you to perform analyses.

Every data item has a domain unit, which defines its entity. For example, we have a geographic data set with provinces in the Netherlands. The Netherlands has 12 provinces, so you could say that the domain unit has 12 rows, one row for each province. Within this domain we have information about each province: name, number of inhabitants, and geometry. Each information field is called an attribute: an attribute of the domain unit provinces.

Each of those attributes holds information, and this can be numbers, text, or coordinates. We must tell GeoDMS what kind of information is being stored for each attribute, this is called the values unit.

So, if we would see a dataset as a table, the number of rows (and its fixed order) are called the domain unit and the collumns represent attributes of that domain unit.

GeoDMS GUI lay-out

  • Parameters
  • Units
  • Expressions
  • Properties
  • Containers


Configuring an item always consists of several components.

attribute<value type> name (domain) := expression;
Personal tools