<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Hi Matthew<div><br></div><div>I tried for a while to motivate the georss group to accept at least a multi-polygon on the georss:simple (a huge requirement for the EO groups dealing with atmospheric data) but unfortunately with little reaction (also the list seems dead)</div><div><br></div><div>i wrote a proposal in the georss site back in september </div><div><a href="http://www.georss.org/multi_polygons">http://www.georss.org/multi_polygons</a></div><div><br></div><div>Probably we should join efforts and make our requirements there and see what happens </div><div><br></div><div>ciao </div><div><br></div><div>pedro</div><div><br></div><div><br></div><div><br></div><div><div><div>On Feb 11, 2011, at 7:22 PM, Cechini, Matthew F. (GSFC-423.0)[RAYTHEON COMPANY] wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-family: Calibri, sans-serif; "><div><div><div>Pedro,</div><div> Thank you for this response. I find it a little disappointing that the Draft #2 Geo OpenSearch spec handles complex geometries rather well, but the GeoRSS:Simple response does not, forcing us into using GML response elements. It would be nice if these response and request elements were more similar, but not tragically difficult to work around. I will be responding to the other messages regarding the time representation and rel links separately.</div><div><br></div><div>Thanks,</div><div>Matt</div><div><br></div><div><div><div style="margin-top: 0in; margin-right: 0in; margin-bottom: 0.0001pt; margin-left: 0in; font-size: 11pt; font-family: Cambria, serif; "><span style="font-size: 10pt; font-family: 'Courier New'; ">Matthew F Cechini<o:p></o:p></span></div><div style="margin-top: 0in; margin-right: 0in; margin-bottom: 0.0001pt; margin-left: 0in; font-size: 11pt; font-family: Cambria, serif; "><span style="font-size: 10pt; font-family: 'Courier New'; ">ECHO Operations Lead - Systems Engineer<o:p></o:p></span></div><div style="margin-top: 0in; margin-right: 0in; margin-bottom: 0.0001pt; margin-left: 0in; font-size: 11pt; font-family: Cambria, serif; "><span style="font-size: 10pt; font-family: 'Courier New'; ">Office: (301) 851-8049<o:p></o:p></span></div><div style="margin-top: 0in; margin-right: 0in; margin-bottom: 0.0001pt; margin-left: 0in; font-size: 11pt; font-family: Cambria, serif; "><span style="font-size: 10pt; font-family: 'Courier New'; ">Cell : (202) 251-8013<o:p></o:p></span></div><div style="margin-top: 0in; margin-right: 0in; margin-bottom: 0.0001pt; margin-left: 0in; font-size: 11pt; font-family: Cambria, serif; "><span style="font-size: 10pt; font-family: 'Courier New'; ">Fax : (301) 851-8283<o:p></o:p></span></div><div style="margin-top: 0in; margin-right: 0in; margin-bottom: 0.0001pt; margin-left: 0in; font-size: 11pt; font-family: Cambria, serif; "><span style="font-size: 10pt; font-family: 'Courier New'; ">E-Mail: <a href="mailto:Matthew.F.Cechini@nasa.gov" style="color: blue; text-decoration: underline; ">Matthew.F.Cechini@nasa.gov</a></span></div></div></div></div></div><div><br></div><span id="OLK_SRC_BODY_SECTION"><div style="font-family:Calibri; font-size:11pt; text-align:left; color:black; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt"><span style="font-weight:bold">From: </span> Pedro Gonçalves <<a href="mailto:pereira.goncalves@gmail.com">pereira.goncalves@gmail.com</a>><br><span style="font-weight:bold">Date: </span> Wed, 9 Feb 2011 07:29:45 -0600<br><span style="font-weight:bold">To: </span> Matt Cechini <<a href="mailto:Matthew.F.Cechini@nasa.gov">Matthew.F.Cechini@nasa.gov</a>><br><span style="font-weight:bold">Cc: </span> Douglas J Newman <<a href="mailto:Doug.Newman-NR@raytheon.com">Doug.Newman-NR@raytheon.com</a>>, "<a href="mailto:standards@lists.osgeo.org">standards@lists.osgeo.org</a>" <<a href="mailto:standards@lists.osgeo.org">standards@lists.osgeo.org</a>>, "Hua, Hook" <<a href="mailto:hook.hua@jpl.nasa.gov">hook.hua@jpl.nasa.gov</a>>, "Lynnes, Christopher S. (GSFC-6102)" <<a href="mailto:christopher.s.lynnes@nasa.gov">christopher.s.lynnes@nasa.gov</a>><br><span style="font-weight:bold">Subject: </span> Re: [OSGeo-Standards] Proposal for Open Search Geo extension support of point and line<br></div><div><br></div><div><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Hi Matthew <div><br></div><div>In fact the response can use the basic opensearch elements (os:Query, os:totalResults, os:itemsPerPage, os:startIndex and so on plus the atom:link for navigation) but the geospatial and temporal extension does not (at least currently) introduce any new response elements and it uses the already defined georss (from <a href="http://www.georss.org/Main_Page">http://www.georss.org/Main_Page</a>) to give geospatial information. </div><div>However I think we are missing a simple way to define the temporal dimension of the data. The elements already available in atom (like atom:updated and atom:published) are not adequate to most of the use cases in earth observation and geographic data because they refer when the resource was actually created and published and not when it was acquired [1]</div><div><br></div><div><div>I tried the nasa's echo and I noticed to it's using the query elements also as response elements for the temporal dimensions of the entries </div><div>For instance this request </div><div><br></div><div><a href="https://api.echo.nasa.gov/echo-esip/search/granule.atom?dataCenter=LAADS&shortName=MOD02QKM&versionId=5&numberOfResults=10&cursor=0&startTime=2000-02-01&endTime=2000-02-28">https://api.echo.nasa.gov/echo-esip/search/granule.atom?dataCenter=LAADS&shortName=MOD02QKM&versionId=5&numberOfResults=10&cursor=0&startTime=2000-02-01&endTime=2000-02-28</a></div><div><br></div><div>returns entries have the time:start and time:end elements: </div><div> ....<br><div><time:start>2009-05-01T00:30:00.000Z</time:start></div><div><time:end>2009-05-01T00:35:00.000Z</time:end></div>...</div></div><div><br></div><div>while this currently not defined in the specification I think that this a very good solution for this problem instead of adding a new namespace (e.g. ical) or using the more generic and ambiguous dc:date.</div><div><br></div><div>If you agree I will include this in the draft and also on the OGC specification that I'm editing now. </div><div>What do you all think ?</div><div><br></div><div>I'll updated the document and send it to the list for your comments </div><div><br></div><div>best regards</div><div><br></div><div>Pedro</div><div><br></div><div>[1] <a href="http://groups.google.com/group/opensearch/browse_thread/thread/cc5e437dbc97a883?hl=en#">http://groups.google.com/group/opensearch/browse_thread/thread/cc5e437dbc97a883?hl=en#</a></div><div><br></div><div><br></div><div><div><div>On Feb 8, 2011, at 9:45 AM, Cechini, Matthew F. (GSFC-423.0)[RAYTHEON COMPANY] wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div style="color: rgb(0, 0, 0); font-size: 14px; font-family: Calibri, sans-serif; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><div><div>All,</div><div> Please correct me if I am wrong. The Draft (#2) OpenSearch Spec contains modifications to the spatial <u>search</u> capabilities, but these modifications do not correspond to changes in the <u>response</u> format, correct? We should be looking to the GeoRSS (<a href="http://www.georss.org/Main_Page">http://www.georss.org/Main_Page</a>) 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.</div><div><br></div><div><blockquote style="margin:0 0 0 40px; border:none; padding:0px;" type="cite"><div>The OpenSearch-Geo response elements can be used by search engines to
augment existing XML formats with search-related metadata. See the <a href="http://www.opensearch.org/Specifications/OpenSearch/1.1#OpenSearch_response_elements" class="external text" title="http://www.opensearch.org/Specifications/OpenSearch/1.1#OpenSearch_response_elements" rel="nofollow">OpenSearch response</a> definition for a general overview of the response options.
</div><div>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. </div></blockquote></div><div><br></div><div>Thanks,</div><div>Matt</div><div><br></div><div><div><div style="margin-top: 0in; margin-right: 0in; margin-bottom: 0.0001pt; margin-left: 0in; font-size: 11pt; font-family: Cambria, serif; "><span style="font-size: 10pt; font-family: 'Courier New'; ">Matthew F Cechini<o:p></o:p></span></div><div style="margin-top: 0in; margin-right: 0in; margin-bottom: 0.0001pt; margin-left: 0in; font-size: 11pt; font-family: Cambria, serif; "><span style="font-size: 10pt; font-family: 'Courier New'; ">ECHO Operations Lead - Systems Engineer<o:p></o:p></span></div><div style="margin-top: 0in; margin-right: 0in; margin-bottom: 0.0001pt; margin-left: 0in; font-size: 11pt; font-family: Cambria, serif; "><span style="font-size: 10pt; font-family: 'Courier New'; ">Office: (301) 851-8049<o:p></o:p></span></div><div style="margin-top: 0in; margin-right: 0in; margin-bottom: 0.0001pt; margin-left: 0in; font-size: 11pt; font-family: Cambria, serif; "><span style="font-size: 10pt; font-family: 'Courier New'; ">Cell : (202) 251-8013<o:p></o:p></span></div><div style="margin-top: 0in; margin-right: 0in; margin-bottom: 0.0001pt; margin-left: 0in; font-size: 11pt; font-family: Cambria, serif; "><span style="font-size: 10pt; font-family: 'Courier New'; ">Fax : (301) 851-8283<o:p></o:p></span></div><div style="margin-top: 0in; margin-right: 0in; margin-bottom: 0.0001pt; margin-left: 0in; font-size: 11pt; font-family: Cambria, serif; "><span style="font-size: 10pt; font-family: 'Courier New'; ">E-Mail: <a href="mailto:Matthew.F.Cechini@nasa.gov" style="color: blue; text-decoration: underline; ">Matthew.F.Cechini@nasa.gov</a></span></div></div></div></div></div><div><br></div><span id="OLK_SRC_BODY_SECTION"><div style="font-family:Calibri; font-size:11pt; text-align:left; color:black; BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt"><span style="font-weight:bold">From: </span> Pedro Gonçalves <<a href="mailto:pereira.goncalves@gmail.com">pereira.goncalves@gmail.com</a>><br><span style="font-weight:bold">Date: </span> Fri, 28 Jan 2011 02:22:36 -0600<br><span style="font-weight:bold">To: </span> Douglas J Newman <<a href="mailto:Doug.Newman-NR@raytheon.com">Doug.Newman-NR@raytheon.com</a>><br><span style="font-weight:bold">Cc: </span> "<a href="mailto:standards@lists.osgeo.org">standards@lists.osgeo.org</a>" <<a href="mailto:standards@lists.osgeo.org">standards@lists.osgeo.org</a>>, "Hua, Hook" <<a href="mailto:hook.hua@jpl.nasa.gov">hook.hua@jpl.nasa.gov</a>>, "Lynnes, Christopher S. (GSFC-6102)" <<a href="mailto:christopher.s.lynnes@nasa.gov">christopher.s.lynnes@nasa.gov</a>>, Matt Cechini <<a href="mailto:Matthew.F.Cechini@nasa.gov">Matthew.F.Cechini@nasa.gov</a>><br><span style="font-weight:bold">Subject: </span> Re: [OSGeo-Standards] Proposal for Open Search Geo extension support of point and line<br></div><div><br></div><div><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Hi Douglas<div><br></div><div>Probably the Geo Extension already covers that request using the geometry parameter.</div><div>With this you can specify a WKT (POINT, LINESTRING, POLYGON, MULTIPOINT, MULTILINESTRING, MULTIPOLYGON) directly on this parameter </div><div>Something like </div><div><br></div><div><a href="http://example.com/?q=pizza&geometry=">http://example.com/?q=pizza&geometry=</a>LINESTRING(-111.032,42.943,-119.856,43.039)&format=rss</div><div><br><a href="http://example.com/?q=pizza&geometry=">http://example.com/?q=pizza&geometry=</a>POINT(-111.032,42.943)&format=rss</div><div><br></div><div>would this be in accordance with your needs ? </div><div><br></div><div>btw... the geo:rss elements are in fact used in the atom xml response not in the request http parameters</div><div><br></div><div>best regards</div><div><br></div><div>Pedro</div><div><br></div><div><div><div>On Jan 26, 2011, at 3:31 PM, Douglas J Newman wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><font size="2" face="sans-serif"><br></font><font size="3">The NASA ECHO project (</font><a href="http://www.echo.nasa.gov/"><font size="3" color="blue"><u>www.echo.nasa.gov</u></font></a><font size="3">)
is in the process of<br>
providing a search capability, via an ESIP interface (using the Open<br>
Search standard with Geo extension), by point and line.<br><br>
The current implementation can be seen at </font><a href="https://api.echo.nasa.gov/echo-esip/"><font size="3" color="blue"><u>https://api.echo.nasa.gov/echo-esip/</u></font></a><font size="3"><br><br>
The </font><a href="http://www.georss.org/simple"><font size="3" color="blue"><u>http://www.georss.org/simple</u></font></a><font size="3">
specification (which I believe the<br>
geo<br>
extension is based on) provides this support and we would like to<br>
propose<br>
it's addition to the open search geo spec.<br><br>
For example,<br><br>
Example URL templates:<br></font><font size="3" color="blue"><u><br></u></font><a href="http://example.com/?q=%7BsearchTerms%7D&pw=%7BstartPage?%7D&line=%7Bgeo:line?%7D&format=rss"><font size="3" color="blue"><u>http://example.com/?q={searchTerms}&pw={startPage?}&line={geo:line?}&format=rss</u></font></a><font size="3"><br></font><font size="3" color="blue"><u><br></u></font><a href="http://example.com/?q=%7BsearchTerms%7D&pw=%7BstartPage?%7D&point=%7Bgeo:point?%7D&format=rss"><font size="3" color="blue"><u>http://example.com/?q={searchTerms}&pw={startPage?}&point={geo:point?}&format=rss</u></font></a><font size="3"><br><br>
Example requests:<br></font><font size="3" color="blue"><u><br></u></font><a href="http://example.com/?q=pizza&line=-111.032,42.943,-119.856,43.039&format=rss"><font size="3" color="blue"><u>http://example.com/?q=pizza&line=-111.032,42.943,-119.856,43.039&format=rss</u></font></a><font size="3"><br></font><font size="3" color="blue"><u><br></u></font><a href="http://example.com/?q=pizza&point=-111.032,42.943,-&format=rss"><font size="3" color="blue"><u>http://example.com/?q=pizza&point=-111.032,42.943,-&format=rss</u></font></a><font size="3"><br><br>
I note that the section of the Geo extension on atom responses has the<br>
element,<br><br>
<georss:line>40.73763 -73.9972 40.73519 -73.99167 40.737015 -73.99035<br>
40.73643 -73.98914 40.734640 -73.990431 40.731617 -73.991504</<br>
georss:line><br><br>
we propose an additional element for point,<br><br>
<georss:point>40.73763 -73.9972</georss:point><br><br>
Please let us know if this is proposal is acceptable.</font>_______________________________________________<br>Standards mailing list<br><a href="mailto:Standards@lists.osgeo.org">Standards@lists.osgeo.org</a><br><a href="http://lists.osgeo.org/mailman/listinfo/standards">http://lists.osgeo.org/mailman/listinfo/standards</a><br></blockquote></div><br></div></div></div></span></div></blockquote></div><br></div></div></div></span></div>
</blockquote></div><br></div></body></html>