OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

emergency message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: [OASIS Issue Tracker] (EMERGENCY-15) Support GML for geospatial values

    [ https://tools.oasis-open.org/issues/browse/EMERGENCY-15?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=37813#comment-37813 ] 

Eliot Christian commented on EMERGENCY-15:

I offer here the same comment I offered on Issue 14 (apologies for for being redundant again).

It seems to me that GML is very complex and overkill for the needs of CAP. 

Perhaps in CAP 2.0 consideration should be given to adopting GeoRSS-Simple ( http://www.georss.org/simple ). This provides point, line, polygon, box, and circle. 

Looking at the GeoRSS-Simple example, though, we may need a provision that says beyond a small set of subelements  any other subelement tag or value that is not understood (e.g., "floor 2") can be safely ignored.

I also note that GeoRSS-Simple has elevation in meters. Perhaps this could help to address a long standing complaint that CAP uses feet for ceiling and altitude rather than meters?

> Support GML for geospatial values
> ---------------------------------
>                 Key: EMERGENCY-15
>                 URL: https://tools.oasis-open.org/issues/browse/EMERGENCY-15
>             Project: OASIS Emergency Management TC
>          Issue Type: Improvement
>          Components: CAP 
>            Reporter: Tony Mancuso
> Jacob Westfall; Geospatial values: I've heard a number of comments from others regarding CAP's geospatial values and I'm passing them on to the comments list. Better compatibility with GML is the most often heard comment.  The geo types of polygon and circle are suitable for the task of describing areas but their formatting, primarily circle, has caused questions and problems with transformations to/from GML.  Also the idea of a box in addition to a polygon has been raised.  The issue of CRSs has been raised but most of the comments were to keep it simple and stick to 4326. Perhaps the next version of CAP should address the issue of compatibility with GML, by including a simple GML profile to use and/or formatting the current geo types to allow for better transformation.

This message was sent by Atlassian JIRA

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]