- Nov 09, 2011
-
-
Allie Micka authored
-
- Feb 25, 2011
-
-
The Great Git Migration authored
-
The Great Git Migration authored
-
- Jun 10, 2010
-
-
The Great Git Migration authored
create branch 'DRUPAL-6--1'. Sprout from master 2010-06-10 16:09:06 UTC Allie Micka <allie_micka@15091.no-reply.drupal.org> 'Update function definition for point() to match the interface.' Cherrypick from master 2009-02-23 05:58:41 UTC Allie Micka <allie_micka@15091.no-reply.drupal.org> '#358255 by chiru - Error creating index using table prefix': db/mysql_spatial.inc db/postgis.inc geo.inc geo.module includes/shp2sql.inc includes/views/geo.views.inc includes/views/views_handler_field_geo.inc includes/views/views_handler_filter_geo.inc modules/geo_data/geo_data.admin.inc modules/geo_data/geo_data.module modules/geo_data/includes/views/geo_data.views.inc modules/geo_data/includes/views/views_handler_field_geo_data.inc modules/geo_field/geo_field.formatters.inc modules/geo_field/geo_field.install modules/geo_field/geo_field.module
-
Allie Micka authored
-
- Apr 27, 2010
-
-
Allie Micka authored
field value.
-
Allie Micka authored
functionality.
-
- Apr 26, 2010
-
-
Allie Micka authored
class. This mean that you can instantiate a geo object using WKB or WKT, run functions on it, and return it in any desired format. It also means that you can do basic data manipulations without any database interaction at all! You can now do stuff like: $geo = geo_load(); $g = $geo->geomFromWKB($wkb); $wkt = $g->asText(); - Completely deprecate the geo() function and the remaining sub-fuctions that were still in use: geo('rss_item') geo('wkt_validate') geo('wkt_from_point')
-
- Apr 23, 2010
-
-
Allie Micka authored
defined. This allows developers to use code such as: $geo = geo_load(); $point = $geo->point(1, 2); ...
-
- Apr 21, 2010
-
-
Allie Micka authored
geo_sql_load();
-
Allie Micka authored
-
Allie Micka authored
-
Allie Micka authored
Removing geo_supported_types() - this is now being handled through the interface.
-
Allie Micka authored
All of the functionality required for Geo should be accessed through the new class interface.
-
Allie Micka authored
-
Allie Micka authored
-
Allie Micka authored
- Using the above function name rather than the original geo() callback mechanism on the geo_field settings forms.
-
- Apr 04, 2010
-
-
Allie Micka authored
-
Allie Micka authored
is created, which means we can simply rely on the views data that already exists for the target geo_tables. This allows geo_data fields to function as one would expect, where you can relate a node to a dataset using a geo_data field, and then use that dataset for additional fields, filters, etc.
-
Allie Micka authored
-
Allie Micka authored
match location coords exactly
-
Allie Micka authored
-
- Jan 26, 2010
-
-
Allie Micka authored
separate where group called 'geo'. This will permit us to convert Geo's filters from AND to OR. For example, you can filter a view based on an event's location OR the location of a facility that an event is node-referenced to. Or, you could find your statewide representative whose state overlaps yours OR a representaive whose district overlaps yours... thus returning all representatives for a particular user. And so-forth.
-
- Jan 25, 2010
-
-
Allie Micka authored
-
- Jan 20, 2010
-
-
Allie Micka authored
-
Allie Micka authored
-
- Jan 19, 2010
-
-
Allie Micka authored
-
Allie Micka authored
-
- Jan 18, 2010
-
-
Allie Micka authored
- Add an api function to convert between 'gis type' and 'geo type'. - Add a sqlColumnDefinition() to the GeoSQL class, which can be overridden by subsequent classes. This moves more of the API functionality into the current API structure, and also allows it to be overridden by say, a lat/lon handler. - Also includes fix for #681756 by jerdavis - SQL error when adding a new Geospatial data field to new content type.
-
- Jan 13, 2010
-
-
Allie Micka authored
filter values. So, for example, a user can add an exposed value for a distance filter, and see the calculated distance as a field in the results.
-
Allie Micka authored
- Update geo_data field load operation to support the new Geo API.
-
- Jan 11, 2010
-
-
Allie Micka authored
sprint! http://groups.drupal.org/node/39240
-
- Jan 09, 2010
-
-
Jeremiah Davis authored
- Added drupal_load() for Content module prior to calling content_notify() in geo_field.install
-
- Jan 07, 2010
-
-
Allie Micka authored
-
Allie Micka authored
in views: Correctly setting up the 'select a target' form as a helper function for each of these. Basically, this means you can display your field as a numerical distance from a fixed point, sort by distance from that point, etc. The next step is to rely on existing views data, such as the already-selected filter values, so that we can fix the regression I created by removing the distance-specific views handlers. Then we roll alpha3!
-
- Dec 21, 2009
-
-
Jeremiah Davis authored
Correcting issue with allowed value select following previous commit. Added trim() call to option list
-
Jeremiah Davis authored
Correcting issue with use of parent::value_form() to properly pull the form elements into the correct tree within the $form
-
Jeremiah Davis authored
Value handling was not working correctly within the exposed filter. By always checking against the default, the form_state did not contain the value passed from the exposed form.
-
Allie Micka authored
-
Allie Micka authored
-