CVS messages for Geo

June 26, 2009

• Commit #230034 by Allie Micka at 03:55
  Geo: /modules/geo/modules/geo_field/geo_field.module 1.23

    Ensure that field geometries are stored with an SRID

June 25, 2009

• Commit #229786 by Allie Micka at 19:07
  Geo: /modules/geo/geo.module 1.24

    Make input handling work properly for array formats (namely lat/lon, gmap)

June 18, 2009

• Commit #226912 by Allie Micka at 21:00
  Geo: /modules/geo/geo.module 1.23
  Geo: /modules/geo/includes/views/views_handler_filter_geo_distance.inc 1.5

    Upated views to work a little better.

• Commit #226516 by Allie Micka at 01:24
  Geo: /modules/geo/db/postgis.inc 1.12
  Geo: /modules/geo/geo.inc 1.15
  Geo: /modules/geo/geo.module 1.22
  Geo: /modules/geo/includes/geo.wkb.inc 1.10
  Geo: /modules/geo/includes/views/geo.views.inc 1.4
  Geo: /modules/geo/includes/views/views_handler_filter_geo.inc 1.6
  Geo: /modules/geo/includes/views/views_handler_filter_geo_distance.inc 1.4
  Geo: /modules/geo/modules/geo_field/geo_field.module 1.22

    - Some refactoring of the gis input / output mechanisms.  
    - Implement a crude on-the-fly conversion so that gis elements can expect one
      format, backends (e.g. field storage or views filters) can expect another 
      and the conversion is quietly performed.
     
    - Make elements for wkt, latlon work as both elements and views filters
    - Refactor widgets to account for the changes on geo_field
    - Get PostGIS distance handling working

June 11, 2009

• Commit #224072 by Allie Micka at 17:13
  Geo: /modules/geo/modules/geo_data/geo_data.module 1.12
  Geo: /modules/geo/modules/geo_data/includes/views/views_handler_field_geo_data.inc 1.4

    Adding geo_fields() changes to make this compatible with geo_field and geo.

June 10, 2009

• Commit #223826 by Allie Micka at 23:28
  Geo: /modules/geo/geo.module 1.21
  Geo: /modules/geo/modules/geo_field/geo_field.module 1.21

    Moving hook_nodeapi: rss item to its correct location in the geo module.

• Commit #223760 by Allie Micka at 20:52
  Geo: /modules/geo/geo.inc 1.14

    last-minute code snips sink ships.

• Commit #223660 by Allie Micka at 16:39
  Geo: /modules/geo/geo.inc 1.13

    Adding schema api call for previous commit

• Commit #223658 by Allie Micka at 16:39
  Geo: /modules/geo/modules/geo_field/geo_field.module 1.20

    Allow CCK to handle field storage "natively" using the Schema API
    
    This means removing over 100 lines of hacky code, and prevents the addition of 
    another pile of code to address the side-effects.
    
    This code:
      1) Provides a geo API call that returns a field definition that can be used
         by the Schema API for creating new columns.
      2) Removes all of the code in the Geo Field module that forces a field to
         "multiple" and then sneaks up behind CCK and molests its tables.  CCK
         is now free to create and move Geo data with impunity.
    
    STILL TO DO
    Because we're adding the columns manually and not with e.g. PostGIS'
    AddGeometryColumn() function, we'll need to account for the post-processing
    and indexes on the resulting tables.
    
    That's next.

• Commit #223398 by Allie Micka at 02:15
  Geo: /modules/geo/includes/views/views_handler_field_geo_distance.inc 1.3
  Geo: /modules/geo/includes/views/views_handler_filter_geo_distance.inc 1.3

    I believe that the hook_gis_input_info() - supplied inputs are now working
    properly for both default and exposed values.  Woo!
    
    There's a lot of cleanup and aesthetics to do, but you're now able to present
    users with a variety of meaningful inputs and have their supplied views filters
    "secretly" translated into meaningful GIS data.