In some cases however, a spatial link might result in the creation of new business information.
Let's consider the following example. From time to time, heavy rainfall causes parcels near watercourses to flood. These floods cause damage to the crops that farmers grow on these parcels. In order to compensate the farmers, we determine which areas are flooded, how big they are, and what crops were grown. In business terms, we have two entities of data:
- A collection of parcels, including information about ownership and crop growth.
- A flooded area that is either digitized or modeled, containing information about the date, time and nature of the flood.
On the left, the parcels. On the right, the flooded area. |
Both entities have a spatial attribute with its location, which in both cases are polygons. In a map, they look like this.
Data model for floods |
Data vault model for floods |
But in this particular case, the parcels and flood are not just on the same location, but they can interact with eachother. When we intersect the flood contour with the parcels, we get the areas of each parcel that is actually flooded.
Flooded areas (in red) |
These new business entities can be modeled as a link with satellite or as a new hub with a satellite attached to the exisiting link. There's currently some debate about the validity of the link satellite that centers around this question. I'm not going to weigh in on that debate here though. Either way, the resulting geometry of the intersection (the red polygons) are stored as new geometries in the satellite of either the link or the newly created hub. The resulting new geometry is called INTERSECTION_GEOMETRY. Below I've modeled both scenarios to give you an idea of how this looks, so you can take your pick.
New business entity modeled as link satellite |
New business entity modeled as a hub |
Comments or questions? Please let me know.
Geen opmerkingen:
Een reactie posten