...
There can be circumstances where there is no link between the Mapping and Spatial Engines. For example, if you were serving static images or have a Mapping Engine that serves static images ( e.g. Image Web Server) then there is no need for such a link to be defined. If the Entities are setup correctly in the Weave configuration, then a user can select features on the map, either spatially or a-spatially and have Weave render them on top of the image that is then sent to the Weave client.
| Gliffy |
|---|
| baseUrl | https://cohgawiki.atlassian.net/wiki |
|---|
| size | L600 |
|---|
| name | unlinked spatial map engines |
|---|
| containerId | 3246678 |
|---|
|
Entity
An entity provides a basic reference to an item that will be searched and report on within Weave. Its relationships within Weave are shown in the diagram below.
| Gliffy |
|---|
| baseUrl | https://cohgawiki.atlassian.net/wiki |
|---|
| name | entity universe |
|---|
| containerId | 3246678 |
|---|
|
Relationships
All the building blocks of Weave can be brought together and their relationships shown in the diagram below.
| Gliffy |
|---|
| baseUrl | https://cohgawiki.atlassian.net/wiki |
|---|
| name | Weave Relationships |
|---|
| containerId | 3246678 |
|---|
|