CVS messages

CVS (Concurrent Versions System) is a code management system used by developers to collaborate and track modifications of code.

December 9, 2009

Commit #299992 by Allie Micka at 17:34

  #654608 Big changes to Views handling for all Geo data.  
  
  THIS WILL BREAK YOUR CURRENT GEO VIEWS!
  
  This change unifies all geo views support into one spot rather than 
  expecting individual field modules to implement their own field handling
  
  * You are now allowed to establish relationships between different geometry
    datasets based on corresponding geometries.  For example:
  
    - A geocoded address, stored as geo_field point, can match itself to an 
      entry in an uploaded neighborhood dataset.  Based on this relationship,
      you can show data from that dataset in that view (e.g. neighborhood 
      name or the population of the matching city.
  
  * Some handlers, in particular the distance handlers, have been deprecated.
    Instead, we're using the full power of *all* available GIS functions for
    filters, sorting and fields.  Leveraging views' number handlers, you can:
  
    - Find routes (linestrings) that are longer than 1km but shorter than 10km
  
    - Find neighborhoods (polygons) that are larger than 5 square miles.
  
    - Find businesses (points) that are within 10 miles of me (another point)
  
  * Many of the functions in the 'old' Geo API (geo.inc, db/*.inc) have been 
    deprecated and removed.  Wherever they've been used, they've been 
    replaced by corresponding Geo API functionality.

December 2, 2009

Commit #296932 by Allie Micka at 19:51

  - Add indexing capabilities - setting "indexed" on a geometry should trigger the
    creation of a geospatial index on its table.
  - Fix bug in that prevented setSRID(), setGeometryType() from working 
    consistently
  - Update shp2sql to create a new geo dataset and support the schema api rather
    than creating tables that aren't recognized or tracked by Drupal
  - Adding geo_create_dataset() API function to facilitate the above.
  - #648712 set default geo_type column GEO_UNKNOWN rather than GEO_SRID_DEFAULT. 
    We don't know, obviously, so why not acknowledge that rather than making 
    assumptions ;)

Commit #296606 by Allie Micka at 02:21

Geo: /modules/geo/geo.module 1.35
Geo: /modules/geo/includes/geo.api.inc 1.1
Geo: /modules/geo/includes/geo.input.inc 1.1
```
  Reorganization:  move Geo's API functions into geo.api.inc
                   move input elements to geo.input.inc
```

Commit #296598 by Allie Micka at 01:42

  Geo API
  - Add a geo_delete() API function to, well, delete geometry datasets.
  - Permit geo_load() to accept array('name' => 'name_of_geometry')
  - Add a geo_type() API function that converts e.g. 'point' to GEO_TYPE_POINT
  
  - Remove the geo_dimension column from the geo table.  We'll handle
    coordinate dimensions differently later.
  - Remove corresponding dimension-setting code to GeoInterface and all of 
    its classes, reverting the dimension() function to the spec default.
  - Add accessors setName() and name() to GeoInterface, GeoSimple, GeoSQL.
  - Using hook_content_fieldapi(), keep track of any CCK fields that directly
    manage geo data.
  - Add an update hook to find all already-existing CCK fields and add them.

December 1, 2009

Commit #296390 by Allie Micka at 21:25

  SOME VERY LARGE AND IMPORTANT CHANGES!
  
  1. One of my big TODO items has been to document the OGC specifications for 
  geospatial data and consistently implement it as an API.  This commit 
  adds an Interface class for the specification, plus implementations for
  MySQL, PostGIS and some strictly PHP-based calculations.
  
  These will eventually supercede some of geo.inc's functions and the files
  in the db directory.  As of now, they do not.
  
  This allows us to account for all of the specification's functionality, and
  to consistently identify what's supported by the available backends.
  
  2. Another big TODO item has been to track each geospatial dataset and 
  its metadata in a central table.  My first attempt was in the geo_data
  module, but is better managed by the Geo API itself.
  
  This commit adds a tracking table "{geo}" to catalog all geo datasets, and 
  copies whatever we can find into that table.
  
  3. Adding a handful of API functions to geo.module to access the above
  functionality - list handlers, load a handler, list datasets, etc.

November 23, 2009

Commit #293186 by Allie Micka at 20:49

Geo: /modules/geo/geo.module 1.32

  - Make geo_field_types() return an array, and use geo_field_type_names() to 
    return a flat array.
  - Update calls to geo_field_types() to reflect this.
  - Add a geo_field_names() API call, which also returns a flat array.

Commit #293176 by Allie Micka at 20:35

Geo: /modules/geo/geo.module 1.31
Geo: /modules/geo/modules/geo_field/geo_field.module 1.28

  - New API function: geo_fields(), which returns all CCK fields that contain
    any type of Geo data.
  - Clean up the hook_field:sanitize hackery that was appending a pre_render
    hook to $node->content for nodes with geo fields.  Instead, use the above
    API function and declare it accordingly.
  - Similarly, use geo_fields() and not field-module-maintained $node->geo_fields
    array in hook_nodeapi:rss item.

November 17, 2009

Commit #290374 by Allie Micka at 22:09

Geo: /modules/geo/geo.module 1.30
Geo: /modules/geo/includes/geo.formatters.inc NONE
Geo: /modules/geo/theme/geo.theme.inc 1.1
```
  Theme function reorganization, for consistency with my other development.
  MAKE SURE TO REBUILD YOUR THEME REGISTRY!
```
Commit #290284 by Allie Micka at 19:07

Geo: /modules/geo/geo.module 1.29
Geo: /modules/geo/modules/geo_field/geo_field.module 1.27
```
  #537342 - Input gets lost on preview
```

November 9, 2009

Commit #286338 by Allie Micka at 17:44

Geo: /modules/geo/geo.inc 1.16
Geo: /modules/geo/geo.module 1.28
Geo: /modules/geo/modules/geo_data/geo_data.module 1.14
Geo: /modules/geo/modules/geo_field/geo_field.module 1.26
```
  - In geo_field, don't return anything the field's value is NULL
  #568098 by greggles - reduce notices
```

CVS messages

December 9, 2009

December 2, 2009

December 1, 2009

November 23, 2009

November 17, 2009

November 9, 2009

CVS

Most active projects

Most active developers

User login

Contributor links