Log of /contributions/modules/geo/includes/geo.formatters.inc

---

Revision 1.7
Tue Nov 17 22:09:57 2009 UTC (11 days, 5 hours ago) by vauxia
Branch: MAIN
CVS Tags: HEAD
Changes since 1.6: +1 -1 lines
FILE REMOVED

Theme function reorganization, for consistency with my other development.
MAKE SURE TO REBUILD YOUR THEME REGISTRY!

---

Revision 1.6 - (view) (download) (as text) (annotate) - [select for diffs]
Tue Jun 9 04:22:43 2009 UTC (5 months, 2 weeks ago) by vauxia
Branch: MAIN
CVS Tags: DRUPAL-6--1-0-ALPHA1
Changes since 1.5: +7 -11 lines
Diff to previous 1.5

Allow CCK Formatter modules to define expected gis inputs ( point, linestring, etc) via hook_field_formatter_info()

1. A module declares CCK formatters using the usual syntax, but includes the
   "gis input" key:

   function geo_field_formatter_info(
     return array(
       'default' => array(
         'label' => t('Well Known Text'),
         'field types' => $field_types,
         'gis types' => array('point', 'linestring', 'polygon'),
         'gis input' => 'wkt',
       ),
       'lat' => array(
         'label' => t('Latitude'),
         'field types' => $field_types,
         'gis types' => array('point'),
         'gis input' => 'array',
       ),
     );
   }
2. Geo's CCK modules retrieve data in WKB format
3. On nodeapi:view, geo performs an on-the-fly conversion from WKB to the
   expected input format ( e.g. wkt, array, and so-on)

- Implemented this for all included formatters.

---

Revision 1.5 - (view) (download) (as text) (annotate) - [select for diffs]
Thu Jun 4 02:02:19 2009 UTC (5 months, 3 weeks ago) by vauxia
Branch: MAIN
Changes since 1.4: +2 -1 lines
Diff to previous 1.4

- Add extent handling (bounding box of an entire dataset)
- Add some 'aggregate => true''s to my function fields to keep Views in line.

- Beginnings of storage -> expected inputs for formatters.
- Beginnings of the "common language" thing I keep talking about.
- Beginnings of "selectable inputs" to switch out, say, a geocoded text field
  as an exposed view input.

THIS COMMIT WILL DO MORE HARM THAN GOOD!  STUFF IS PROBABLY BROKEN!
I just wanted to commit the proof-of-concept before tinkering with it on a
refactor.

---

Revision 1.4 - (view) (download) (as text) (annotate) - [select for diffs]
Tue May 19 18:29:12 2009 UTC (6 months, 1 week ago) by vauxia
Branch: MAIN
Changes since 1.3: +1 -2 lines
Diff to previous 1.3

Add geo_wkb_get_data as an API function to the geo.module file.  Eliminates the
module_load_include() dependency for formatters, etc.

---

Revision 1.3 - (view) (download) (as text) (annotate) - [select for diffs]
Tue Mar 3 02:16:28 2009 UTC (8 months, 3 weeks ago) by vauxia
Branch: MAIN
Changes since 1.2: +1 -53 lines
Diff to previous 1.2

- Adding a views field handler for geo_field, which makes way more sense than
trying to rely on a generic one.  This lets you configure geo  CCK fields in
views just like you're used to.
- Removing the borked SVG formatter for fields.  If it's useful, we'll re-add it
- Enhancing the SVG handler for views so that it more accurately portrays
  lines and points.

---

Revision 1.2 - (view) (download) (as text) (annotate) - [select for diffs]
Mon Mar 2 06:25:49 2009 UTC (8 months, 4 weeks ago) by vauxia
Branch: MAIN
Changes since 1.1: +2 -2 lines
Diff to previous 1.1

Views output formats for KML and SVG, based on polygon data.

---

Revision 1.1 - (view) (download) (as text) (annotate) - [select for diffs]
Sun Mar 1 03:46:06 2009 UTC (8 months, 4 weeks ago) by vauxia
Branch: MAIN

Moving field formatters from geo_field to geo, to accommodate formatters
for geo fields of any kind.