Fwd: [OSGeo-Standards] Proposal for Open Search Geo extension support
of point and line
Pedro Gonçalves
pereira.goncalves at gmail.com
Fri Feb 11 12:50:29 EST 2011
Hi all
as my first post was rejected by the list moderator due to the file size here is a link to the new version of the document
http://www.terradue.com/news/10-032r2_OpenSearchGeoTemporal.pdf
best regards
Pedro
Begin forwarded message:
> From: Pedro Gonçalves <pereira.goncalves at gmail.com>
> Date: February 11, 2011 11:45:14 AM GMT+01:00
> To: "Cechini, Matthew F. (GSFC-423.0)[RAYTHEON COMPANY]" <matthew.f.cechini at nasa.gov>
> Cc: Douglas J Newman <Doug.Newman-NR at raytheon.com>, "standards at lists.osgeo.org" <standards at lists.osgeo.org>, "Hua, Hook" <hook.hua at jpl.nasa.gov>, "Lynnes, Christopher S. (GSFC-6102)" <christopher.s.lynnes at nasa.gov>
> Subject: Re: [OSGeo-Standards] Proposal for Open Search Geo extension support of point and line
>
> Hi all
>
> Here is a new version of the document.
> It includes tables with OGC returnables elements mapping and also it aligns it with OGC Modular Specification document (by defining requirements and the like in OGC parlance). I also added several more examples on how to use the atom:link elements
>
>
>
[10-032r2_OpenSearchGeoTemporal.pdf] removed
>
>
> Best regards
>
> Pedro
>
>
> On Feb 8, 2011, at 9:45 AM, Cechini, Matthew F. (GSFC-423.0)[RAYTHEON COMPANY] wrote:
>
>> All,
>> Please correct me if I am wrong. The Draft (#2) OpenSearch Spec contains modifications to the spatial search capabilities, but these modifications do not correspond to changes in the response format, correct? We should be looking to the GeoRSS (http://www.georss.org/Main_Page) specification for how to format our Atom feed results that include spatial information. The following text from the Draft spec have me perplexed and I want to make sure I'm on the right page.
>>
>>> The OpenSearch-Geo response elements can be used by search engines to augment existing XML formats with search-related metadata. See the OpenSearch response definition for a general overview of the response options.
>>> The following examples illustrate Geo-specific responses. For RSS and Atom responses, it is suggested to use the GeoRSS channel elements in addition to the OpenSearch-Geo elements.
>>
>>
>> Thanks,
>> Matt
>>
>> Matthew F Cechini
>> ECHO Operations Lead - Systems Engineer
>> Office: (301) 851-8049
>> Cell : (202) 251-8013
>> Fax : (301) 851-8283
>> E-Mail: Matthew.F.Cechini at nasa.gov
>>
>> From: Pedro Gonçalves <pereira.goncalves at gmail.com>
>> Date: Fri, 28 Jan 2011 02:22:36 -0600
>> To: Douglas J Newman <Doug.Newman-NR at raytheon.com>
>> Cc: "standards at lists.osgeo.org" <standards at lists.osgeo.org>, "Hua, Hook" <hook.hua at jpl.nasa.gov>, "Lynnes, Christopher S. (GSFC-6102)" <christopher.s.lynnes at nasa.gov>, Matt Cechini <Matthew.F.Cechini at nasa.gov>
>> Subject: Re: [OSGeo-Standards] Proposal for Open Search Geo extension support of point and line
>>
>> Hi Douglas
>>
>> Probably the Geo Extension already covers that request using the geometry parameter.
>> With this you can specify a WKT (POINT, LINESTRING, POLYGON, MULTIPOINT, MULTILINESTRING, MULTIPOLYGON) directly on this parameter
>> Something like
>>
>> http://example.com/?q=pizza&geometry=LINESTRING(-111.032,42.943,-119.856,43.039)&format=rss
>>
>> http://example.com/?q=pizza&geometry=POINT(-111.032,42.943)&format=rss
>>
>> would this be in accordance with your needs ?
>>
>> btw... the geo:rss elements are in fact used in the atom xml response not in the request http parameters
>>
>> best regards
>>
>> Pedro
>>
>> On Jan 26, 2011, at 3:31 PM, Douglas J Newman wrote:
>>
>>>
>>> The NASA ECHO project (www.echo.nasa.gov) is in the process of
>>> providing a search capability, via an ESIP interface (using the Open
>>> Search standard with Geo extension), by point and line.
>>>
>>> The current implementation can be seen at https://api.echo.nasa.gov/echo-esip/
>>>
>>> The http://www.georss.org/simple specification (which I believe the
>>> geo
>>> extension is based on) provides this support and we would like to
>>> propose
>>> it's addition to the open search geo spec.
>>>
>>> For example,
>>>
>>> Example URL templates:
>>>
>>> http://example.com/?q={searchTerms}&pw={startPage?}&line={geo:line?}&format=rss
>>>
>>> http://example.com/?q={searchTerms}&pw={startPage?}&point={geo:point?}&format=rss
>>>
>>> Example requests:
>>>
>>> http://example.com/?q=pizza&line=-111.032,42.943,-119.856,43.039&format=rss
>>>
>>> http://example.com/?q=pizza&point=-111.032,42.943,-&format=rss
>>>
>>> I note that the section of the Geo extension on atom responses has the
>>> element,
>>>
>>> <georss:line>40.73763 -73.9972 40.73519 -73.99167 40.737015 -73.99035
>>> 40.73643 -73.98914 40.734640 -73.990431 40.731617 -73.991504</
>>> georss:line>
>>>
>>> we propose an additional element for point,
>>>
>>> <georss:point>40.73763 -73.9972</georss:point>
>>>
>>> Please let us know if this is proposal is acceptable._______________________________________________
>>> Standards mailing list
>>> Standards at lists.osgeo.org
>>> http://lists.osgeo.org/mailman/listinfo/standards
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.osgeo.org/pipermail/standards/attachments/20110211/5340b423/attachment.html
More information about the Standards
mailing list