>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #494836. --> Reported by: [allie micka](https://www.drupal.org/user/15091) >>> <p>I'm working to deprecate the use of hook_widget, hook_widget_info, etc. as it pertains to geo data. Why?! Two reasons:</p> <p>1. Widgets are specific to CCK fields. This makes sense in most cases, but there are a lot of other places that can/should allow users to input data that is translated to GIS values. Most notably, views filters!</p> <p>2. We need some place to express the expected input/output formats so that the values that a user has entered are correctly translated to the values that the receiving code is expecting -- without a lot of mucking around on the part of the frontend code. You (the GMAP+Geo maintainer) should be able to assert that you want to express your input/output in "array" format, the field module may wish to use WKB, and a particular views filter may require WKT.</p> <p>These issues shouldn't be your problem, so Geo takes on the complexities of widgets and views inputs, while this module need only implement the following hook:</p> <div class="codeblock"> <pre><span style="color: #000000"><span style="color: #0000BB">&lt;?php<br></span><span style="color: #FF8000">/**<br>&nbsp;* Implementation of hook_gis_input_info().<br>&nbsp;*/<br></span><span style="color: #007700">function </span><span style="color: #0000BB">gmap_geo_gis_input_info</span><span style="color: #007700">(</span><span style="color: #0000BB">$gis_type </span><span style="color: #007700">= </span><span style="color: #0000BB">NULL</span><span style="color: #007700">) {<br>&nbsp; </span><span style="color: #0000BB">$inputs </span><span style="color: #007700">= array(<br>&nbsp;&nbsp;&nbsp; </span><span style="color: #DD0000">'gmap_geo_picker' </span><span style="color: #007700">=&gt; array(<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span><span style="color: #DD0000">'label' </span><span style="color: #007700">=&gt; </span><span style="color: #0000BB">t</span><span style="color: #007700">(</span><span style="color: #DD0000">'GMap picker'</span><span style="color: #007700">),<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span><span style="color: #DD0000">'gis input' </span><span style="color: #007700">=&gt; </span><span style="color: #DD0000">'array'</span><span style="color: #007700">,&nbsp; </span><span style="color: #FF8000">// the format you work with ( e.g. lat/lon array)<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span><span style="color: #DD0000">'safe reverse' </span><span style="color: #007700">=&gt; </span><span style="color: #0000BB">TRUE</span><span style="color: #007700">,&nbsp; </span><span style="color: #FF8000">// Whether or not a stored value will consistently translate to a value you expect<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span><span style="color: #DD0000">'gis types' </span><span style="color: #007700">=&gt; array(</span><span style="color: #DD0000">'point'</span><span style="color: #007700">), </span><span style="color: #FF8000">// The geo types you're willing to work with.<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span><span style="color: #DD0000">'element' </span><span style="color: #007700">=&gt; array(<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span><span style="color: #DD0000">'#type' </span><span style="color: #007700">=&gt; </span><span style="color: #DD0000">'gmap_geo_picker'</span><span style="color: #007700">,<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span><span style="color: #FF8000">// You can put whatever else you want in the element here<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span><span style="color: #007700">),<br>&nbsp;&nbsp;&nbsp; ),<br>&nbsp; );<br>&nbsp; return </span><span style="color: #0000BB">$inputs</span><span style="color: #007700">;<br>}<br></span><span style="color: #0000BB">?&gt;</span></span></pre></div> <p>There are other examples of this hook in geo.module and geocode.module.</p> >>> [!note] Pre-migration files - [gmap\_geo\_gis\_input.patch](https://www.drupal.org/files/issues/gmap_geo_gis_input.patch) >>>