http://localhost/ticket/1272 <p> Consolidate the extra <tt>spatial</tt> as the field for providing information about the geographic extent of the package. This will integrate automatically with the spatial search and give developers a single point to develop geospatial features. </p> en-us http://assets.okfn.org/p/ckan/img/ckan_logo_shortname.png http://localhost/ticket/1272 Trac 0.12.3 rgrp Fri, 19 Aug 2011 09:24:27 GMT http://localhost/ticket/1272#comment:1 http://localhost/ticket/1272#comment:1 <p> Assume these are the 3 spatial fields listed on <a class="ext-link" href="http://wiki.ckan.net/Geospatial_Capabilities"><span class="icon">​</span>http://wiki.ckan.net/Geospatial_Capabilities</a>. I'm a big +1 here. Starting point would be a bit more documentation on that wiki page. Questions: </p> <ul><li>Is this work going in ckanext-spatial? </li><li>What is being proposed here, I assume, is to automatically index those fields in our geospatial search. </li><li>Should we develop a simple display widget using google maps or similar (this is orthogonal to the WMS preview i think) which *just* uses the core fields. This is probably a separate ticket and possibly separate from ckanext-spatial extension. </li></ul> Ticket shevski Thu, 29 Sep 2011 15:16:31 GMT http://localhost/ticket/1272#comment:2 http://localhost/ticket/1272#comment:2 <ul> <li><strong>milestone</strong> changed from <em>ckan-backlog</em> to <em>ckan-current-sprint</em> </li> </ul> Ticket amercader Fri, 30 Sep 2011 11:26:36 GMT http://localhost/ticket/1272#comment:3 http://localhost/ticket/1272#comment:3 <ul> <li><strong>status</strong> changed from <em>new</em> to <em>closed</em> </li> <li><strong>resolution</strong> set to <em>fixed</em> </li> <li><strong>milestone</strong> changed from <em>ckan-current-sprint</em> to <em>ckan-sprint-2011-10-10</em> </li> </ul> Ticket