GTK GeoKernel and Data Management. Material from Niina Ahtonen, Esa Kauniskangas and Tero Rönkkö

Transcription

1 GTK GeoKernel and Data Management Esa Kauniskangas Material from Niina Ahtonen, Esa Kauniskangas and Tero Rönkkö 1

2 GTK s operational areas Northern Finland Office Rovaniemi Western Finland Office Kokkola Kuopio Eastern Finland Office Outokumpu Loppi Espoo Southern Finland Office 2

3 GTK / Eastern Finland Office, Information Services Projects Geodata systems development, GeoKernel Geological data digitizing and prosessing (Internal) Services GIS Services, graphical Services and map production Geological image processing Scientific library 3

4 The subsystems of GeoKernel (Geotietoydin)

5 GeoKernel in Data Menu (ArcView) 5

6 Advantages and requirements of GeoKernel information system Common information system architecture for all data capture processes Secure and centralized databases Data in its s real geometry map databases All data processes under the same information system architecture, workflows should be well described before system engineering starts Coherent architecture good opportunities for developers Data delivery and geoprocessing services Re-usable application framework professional environment for software developers Requirement analysis is very important (and very difficult) Component based software engineering leads to results Finding of essential features for implementation Training courses for each end-user group are needed for successful mobilisation GIS development challenges: metadata, new coordinate system implementation (Euref-FIN), geophysical data (ground geophysics), geochemical data, harmonization at o of web map services 6

7 Field data capture with tablet PC - geological mapping 7

8 Challenges Data migration from old systems to new one Requirements management processes specifications Complicated data models several layers and tables one feature can have dozens of attributes database tables have many relationships Resources human time 8

9 Case Mire In the office: planning of investigations lines with ArcMap and custom tools In the field pocket PC or tablet PC and GPS ArcPad shape and dbf files derived from central ArcSDE-geodatabase correct data structures forms and all functionality maintaining data integrity are custom made by GTK In the office: peat amount and energy content calculations peat profiles 9

10 Case Mire 10

11 Case Bedrock Rugged tablet PC:s (Panasonic) All base maps, geophysical maps, previously made observations etc. are in digital format and are fully usable use in the GIS-software during fieldwork Bedrock observations are stored using standard ArcMap geometry tools and custom editors programmed in GTK Editors use the database structure, which is extracted from the central ArcSDEgeodatabase Data model for bedrock observation covers all the sub processes belonging to bedrock mapping such as basic bedrock mapping, exploration of metallic ores, natural stone investigations and detailed mapping needed for infrastructure projects 11

12 12

13 Case Bedrock 13

14 Case Bedrock 14

15 GTK Metadata system architecture Geological Survey of Finland, Rönkkö Tero, Ahtonen Niina, Kuronen Eija, Pietilä Raija 15

16 Screenshot: Resource identification Geological Survey of Finland, Rönkkö Tero, Ahtonen Niina, Kuronen Eija, Pietilä Raija 16

17 Geological Map Production System Layout defining (wysiwyg) 17

18 Geological Map Production System Cartographic editing (wysiwyg) Transparent masking 18

19 Bedrock Map 1:

20 Finnish Stratigraphic Units Database 20

21 21

22 Quaternary Deposits Map Gravel and Sand Areas Clay Areas 22

23 Old Quaternary Map (1000K) New Quaternary Map 1: (DigiMP 200) 23

24 GTK s Web Portal (g geo.fi ) GTK s service model is based on ArcGIS Server 9.x for vector data (Advanced Enterprise version) ErMapper Image Web Server (IWS) for raster/matrix data Service and data can be used with web browser (basic users) with GIS software (advanced users) on OGC (Open Geospatial Consortium) interfaces (WMS, WFS) Geological spatial data comes from GTK s GeoKernel central database Airborne geophysical data, height models and other raster-themes come from IWS-servers Metadata from xml-files (stored in Oracle database) Basemaps are uploaded to services via WMS-interface from Finnish National Land Survey / Logica Reports and other documents are readable or downloadable in Adobe.pdf format Data downloads in different formats AutoCAD, Mapinfo, ESRI shapefiles, etc. Data Interoperability Extension (ESRI DIE) build in the system Ordering services available for printed documents and maps (on paper or GIS files) Mineral deposit databases and other data have been published also through Google Earth 24

25 WMS = Web Map Services WFS = Web Feature Services 25

26 Bedrock Map, WMS-interface OneGeology, OneGeologyEurope, INSPIRE, ProMine 26