Geospatial Interoperability Demonstrator Project - PowerPoint PPT Presentation

1 / 26
About This Presentation
Title:

Geospatial Interoperability Demonstrator Project

Description:

Geospatial Interoperability Demonstrator Project. Gail Millin MIMAS ... Name 'png24', Mimetype 'image/png', Driver 'GD/PNG' Imagemode 'RGBA' Extension 'png' ... – PowerPoint PPT presentation

Number of Views:61
Avg rating:3.0/5.0
Slides: 27
Provided by: Gai56
Category:

less

Transcript and Presenter's Notes

Title: Geospatial Interoperability Demonstrator Project


1
Geospatial Interoperability Demonstrator Project
Gail Millin MIMAS Open Forum 29th June 2005
2
Introduction
  • Interoperability project aims and objective
  • Data preparation
  • Serving imagery
  • - University of Minnesota MapServer
  • - ER Mappers Image Web Server
  • Developing a web client
  • - RightWebMap 7.0
  • Future aims

3
Interoperability Team
http//www.mimas.ac.uk/ http//camber.mc.man.ac.u
k/iws/interoperability.htm
http//www.ge.ucl.ac.uk/ http//iceds.ge.ucl.ac.u
k/
http//www.edina.ac.uk/
http//www.nerc.ac.uk/
http//www.ccg.leeds.ac.uk/
4
Objectives of the Project
  • Aim to prove the feasibility of delivering
    geo-spatial data using OGC standards for GIS web
    services
  • Primary objective is to develop a set of
    demonstrator applications which promote
    interoperability between distributed data sources
  • Why? To maximize value and enhance interactivity
    between spatial datasets

5
Overall Project Outcomes
  • A range of OGC based web services (WMSWFSWCS)
    (MIMAS, UCL, EDINA and NERC)
  • A basic annotation web service (XIMA) (CCG, Leeds
    University)
  • A series of demonstrator clients (assigned to UCL
    but also developments at MIMAS and EDINA
    occurring). The clients will illustrate
  • Access to data
  • A teaching focused use case (Urban Expansion)
  • A research focused use case (Planimetric - based
    on dynamic image registration using web services)
  • A report on the utility and issues surrounding
    implementation of open standards for geospatial
    data within JISC, including an assessment of
    security and access authorisation issues

6
MIMAS Data Provision Preparation
  • Landsat 5, Landsat 7 (Pan and fused), SPOT,
    Ortholandsat 5/7 and Hillshade provided as part
    of Landmap Project http//www.landmap.ac.uk
  • Pyramiding 25m, 50m and 100m resolution for
    ortholandsat 5 and 7 stretched mosaics.
  • Tiling Shapefile index created for tiled data,
    improve server response time by requesting tiles
    that fall into the bounding box defined by the
    user.
  • Band Combinations Landsat 5 mosaic bands 7,4,2
    highlight urban areas in pinkish purple colour.

7
Serving Spatial Data - OGC Standards
  • Open Geospatial Consortium (OGC) - a non-profit,
    international, voluntary standards organization
    that is leading the development of standards for
    geospatial services
  • Their aim is to advance geo-processing
    interoperability across the GIS industry
  • Defines web service implementation specifications
    for
  • Web Map Services (WMS)
  • Web Feature Services (WFS)
  • Web Coverage services (WCS)
  • For documentation - http//www.opengeospatial.org/
    specs/

8
WMS, WFS and WCS
  • WMS web application which provides a portrayal
    of geographic data which is stored on the server.
  • WFS is an interface allowing requests for
    geographical features across the web using the
    XML based GML for data exchange.
  • WCS defines how to provide satellite data over
    the internet. This differs from WMS as actual
    data values are sent.
  • MIMAS is providing WMS and WCS at present.

9
University of Minnesota MapServer
  • MapServer is a freely available, open source
    development environment, offering support of WMS
    and WCS http//mapserver.gis.umn.edu/
  • Requires a variety of supporting libraries e.g.
  • - PROJ 4 for on-the-fly projection
  • - Geospatial Data Abstraction Library
    (GDAL) a translator library for raster data
  • MIMAS installed MapServer 4.4.1 on Windows Server
    2003 using IIS 6.0

10
Configuring MapServer for WMS
  • MIMAS MapFile Structure

11
WMS Layer Element of the MapFile
12
WMS GetMap Request
  • Once a MapFile has been created a GetMap request
    can be submitted to MapServer e.g.
  • http//camber.mc.man.ac.uk/cgi-bin/mapserv.exe?map
    c\Inetpub\wwwroot\MIMAS\wms_mimas_mosaic.mapVER
    SION1.1.1REQUESTGetMapSRSEPSG27700BBOX0,0,
    700005,1050000WIDTH700HEIGHT700LAYERSLandsat
    7Mosaic15mFORMATimage/jpeg
  • As part of the interoperability project GetMap
  • requests have been produced for the
  • Orthospot mosaic, Landsat 7 15m 25m
  • mosaics, Landsat 5 mosaics, Ortholandsat 5
  • and 7 stretched mosaics at 100m, 50m and
  • 25m resolution in tiff format and at 25m
  • resolution in ecw format.
  • .

13
WMS GetCapabilities Request
  • All the imagery being provided by MIMAS for the
    interoperability project can be listed using a
    GetCapabilities request
  • http//camber.mc.man.ac.uk/cgi-bin/mapserv.exe?map
    c\Inetpub\wwwroot\MIMAS\wms_mimas_mosaic.mapREQ
    UESTGetCapabilities
  • This request is useful to discover information
    about a WMS, the layers contained in the WMS, the
    projection the data is being served in, metadata
    information, access constraints and contact
    information about the organization providing the
    data.

14
WCS GetCapabilities Request
  • As with the WMS a WCS MapFile is required to
    configure MapServer to execute WCS requests
  • A GetCapabilities request for WCS can be used to
    find out information about the service
  • http//camber.mc.man.ac.uk/cgi-bin/mapserv.exe?map
    c\Inetpub\wwwroot\MIMAS\wcs_mimas_mosaic.mapSER
    VICEWCSREQUESTGetCapabilities
  • This request refers to wcs_mimas_mosaic.map
    rather than the wms_mimas_mosaic.map. So how does
    the WCS MapFile differ from the WMS?

15
WCS MapFile
  • Mapfiles for WCS must contain -
  • LAYER NAME,
  • TYPE RASTER
  • LAYER DUMP TRUE
  • Metadata parameters prefixed with WCS or OWS in
    both the WEB element and LAYER element.

16
Get Coverage Request
  • When using the below URL a download dialogue box
    will appear and will prompt the user to save the
    file.
  • http//camber.mc.man.ac.uk/cgi-bin/mapserv.exe?ma
    pc\Inetpub\wwwroot\MIMAS\wcs_mimas_mosaic.mapSE
    RVICEWCSREQUESTGetCoverageCoverageLandsat7Pan
    BBOX0,0,700005,1050000CRSEPSG27700RESX75RE
    SY75FORMATecw
  • For MIMAS coverages save the file with a .ecw
    extension.
  • The coverage can then be viewed and used in an
    image processing package e.g. ERDAS Imagine and
    ER Mapper.

17
ER Mappers Image Web Server
  • Alternative for serving imagery is Image Web
    Server 7.0
  • Image Web Server provides ECW high speed
    streaming for all Landmap imagery and is also OGC
    WMS compliant
  • ECW streamed imagery can be accessed at
    http//camber.mc.man.ac.uk/rightwebmap/image_strea
    ming.htm
  • GetCapabilities request for IWS is
    http//camber.mc.man.ac.uk/ecwp/ecw_wms.dll?reques
    tGetCapabilitiesservicewms

18
MIMAS Image Streaming Viewer
19
MIMAS Web Clients RightWebMap
  • RightWebMap from ER Mapper integrates multiple
    image servers into single application.
  • Supports OGC WMS, ECWP, MapServer and ArcIMS
    protocols
  • Using this technology two new clients have been
    created as examples of interoperability
  • Planimetric user case for a research application.
  • Urban expansion user case for a teaching
    application.
  • WMS include ICEDS, EDINA, MIMAS and DEMIS

20
Features of MIMAS Web Client
  • Interface can be changed to display the viewer in
    frames or windows format.
  • Layers from two different WMS can be integrated
    together and transparency adjusted.
  • Links available in menu bar to download raster
    imagery from Landmap
  • The data can be queried and explored using the
    navigational tools.
  • The Order of the WMS services/layers can be
    changed.

21
MIMAS Planimetric Use Case - Frame
22
MIMAS Urban Use Case - Window
23
MIMAS ICEDS WMS
24
Interoperability Issues
  • No legend for WMS as yet, EDINA is working on
    producing a GetLegendGraphic request
  • Also issues with the same colour being used to
    symbolize two different map items which clash
    when the WMS are put together
  • Background halos behind feature data looking
    pixilated when combined with satellite imagery
  • WMS in different map projections. Solved by
    cascading the WMS from ICEDS and EDINA into a
    MIMAS mapfile and re-projecting on-the-fly the
    data into EPSG 4326 from EPSG 27700.
  • Reduced quality of imagery when downloading as
    WCS MIMAS data requested at 75m resolution.

25
Future Aims
  • WCS dynamic downloading of data
  • Incorporate the annotation service (from CCG) to
    the demonstrator projects
  • Explore other web client options e.g. DM
    Solutions Chameleon 2.0
  • Assist the interoperability team with the
    ability to produce legends for WMS
  • Trial run the web client and get feedback from
    the users on ways to improve the interface and
    WMS

WCS Download
FINISH
Please Fill Out the Questionnaire! ?
START
  • The team also needs to look at issues of
    security and data constraints, an authentication
    system such as Athens would be required if the
    clients were to be developed as services.

26
Contact Details
  • E-mail Gail.Millin_at_manchester.ac.uk
  • Telephone 0161 275 0581
  • MIMAS Interoperability Website -
  • http//camber.mc.man.ac.uk/iws/interoperability.h
    tm
  • Further Project Details - http//edina.ac.uk/proj
    ects/interoperability/
  • Thanks for Listening! ?
Write a Comment
User Comments (0)
About PowerShow.com