Configuration Steps
From Geoikia-english
> Main Page > Configuring Services
Contents |
Introduction
The following steps show how to build a Geoide application:
- 1. Loading (spatial) source data into a spatial database
- 2. Configuring WFS, WMS using deegree/OpenJump
- 3. Configuring the Geoide Server (GI) using deegree/OpenJump
- 4. Configuring the Geoide Viewer (Geoide Author).
If you have configured services already, or you have access to WMS, WFS or Geoide Services, then you may continue with:
Steps
Next diagram shows the various configuration steps. For each step specific tools are available to execute the configuration successfully.
(1) Loading Source data into Spatial Database
- Here we assume that spatial data is already available in spatial databases.Sourcedata can be for instance ESRI shape files
The conversion of source data to spatial databases lies beyond the scope of this documentation. > Further information on Spatial Databases
(2) Configuring WFS, WMS, WMTS and TMS
- WFS = Web Feature Service > What is a WFS?
- WMS = Web Map Service > What is a WMS?
- WMTS =Web Map Tile Service
- TMS =Tile Map Service
WMS
- If you already have access to WMS services, then you can use these services directly and continue with step 4 (Configuring the Geoide Viewer).
- If you only have data in a database and you want these data to be accessible by the Geoide Viewer then you have to configure a WMS service first. You can find more information in Workshop deegree Web Services.
WFS
- If you want to use the Geoide Service (for instance for using the edit-functionality) then you have to configure first a WFS and Geoide Server (step 3).
- You can use OpenJump to configure services
- The configuration of a WFS will be explained using the use case "Agroportal":
- > Step 2: configuring WFS: (Example Agroportal)
WMTS en TMS
- Geoide supports tile map services working with protocols OGC:WMTS (Web Map Tile Service) and TMS (Tile Map Service) based on HTTP Key-ValuePair en RESTful.
(3) Configuring Geoide Server (GI) using deegree/OpenJump
- Geoide Server (giservlet) combines the functionality of a WFS and WMS:
- GetMap request results in a flash file (swf). This is not just a plain image, but contains objects which can be manipulated (for instance edited) in the Geoide Client environment (Geoide Viewer).
- GetFeature request resulteert in het ophalen van informatie van een object (feature) vergelijkbaar met een WFS GetFeature response
(4) Configuring Geoide Viewer (Geoide Author)
- You can configure the Geoide Viewer with the Geoide Author.
- > Step 4a: Configuring the Geoide Viewer with the Geoide Author
- If you want to use the report functionality in the Geoide Viewer, then you can use iReport and the Geoide Author.
Diagram: Tools
Next diagram shows the available tools for each step (example: Agroportal):
Diagram: files
Next diagram shows the files which are manipulated during each step (Example: Agroportal):
| ad (4)
GIContext.xml: Describes the structure of the geographic data (map layers) in the application. > See also Hierarchy GIClientConfig.xml: Describes the lay-out of the Geoide Viewer such as: Colors, Buttons, Screens etc. |
| ad (3)
Geoide.xml: Describes the layers served by the Geoide Server. Results are shown in the Get Capabilities response sld.xml: Describes the appearance of map layers. SLD = Styled Layer Descriptor | |
| ad (2)
*.xsd: Describes a feature type in the sense of:
| |
