sis-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris A. Mattmann (JIRA)" <>
Subject [jira] Commented: (SIS-28) Create a Layer Service for Google Earth Integration
Date Wed, 23 Feb 2011 21:58:38 GMT


Chris A. Mattmann commented on SIS-28:

Let's plug this into the OODT File Manager and its GeoRSS service...

> Create a Layer Service for Google Earth Integration
> ---------------------------------------------------
>                 Key: SIS-28
>                 URL:
>             Project: Spatial Information Systems
>          Issue Type: New Feature
>          Components: web services layer
>    Affects Versions: 0.2-incubating
>            Reporter: Paul Ramirez
>            Assignee: Paul Ramirez
>             Fix For: 0.2-incubating
> Create a layer service that feeds KML to Google Earth. The layer service will support
multiple layers that can be loaded with georss. Most of the interaction with Google Earth
will be accomplished via a NetworkLink as described here

> Layer List 
> GET /sis/layers
> Returns KML with NetworkLinks to all the layers available. This KML can have an expiration
date so that Google Earth will refresh it at a given interval of time. This will likely flow
into config for the service. Each layer will map to one quad tree store.
> Query Layer
> GET /sis/layers/{layerName}?BBOX=[bboxWest],[bboxSouth],[bboxEast],[bboxNorth]
> Support bbox query and return the KML that matches from a given quad tree (i.e. layerName)
> Create Layer
> POST /sis/layers
> Create a layer with the posted configuration. The configuration should include minimally
layer name and list of georss urls to be loaded
> Remove Layer
> DELETE /sis/layers/{layerName}
> Removes the layer and underlying quad tree storage from the service
> Load Layer
> POST /sis/layers/{layerName}
> Will reload the georss feeds associated with the given layer name
> With this set up I believe we would be able to have a simple first pass at Google Earth

This message is automatically generated by JIRA.
For more information on JIRA, see:


View raw message