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

---

Revision 1.2 - (view) (download) (as text) (annotate) - [select for diffs]
Thu Sep 25 21:51:33 2008 UTC (13 months, 4 weeks ago) by vauxia
Branch: MAIN
CVS Tags: DRUPAL-6--1-0-ALPHA1, HEAD
Branch point for: DRUPAL-6--1
Changes since 1.1: +10 -4 lines
Diff to previous 1.1

Restore PostGIS functinality:
  - Return PostgreSQL-supported column definitions for db_create_table in
    shp2sql code
	- Account for SRID's now that we have a database that notices
  - Remove no-longer-supported db_* functions from postgis.inc
  - Abstract field_query code in views handlers, and implement an indexed
    ( postgis ) and non-indexed ( mysql ) version in the backend code.

---

Revision 1.1 - (view) (download) (as text) (annotate) - [select for diffs]
Wed Aug 20 15:06:39 2008 UTC (15 months ago) by vauxia
Branch: MAIN

Another big commit:
 - CAN NOW PARSE AND BULK IMPORT SHAPE DATA.  I rule!
 - continuing to refactor code into geo.inc
 - Add another field module for geo_data.  In contrast with geo_field, which
   stores geospatial information, geo_data *references* geospatial information.
   Workflow being:
     1. Download shape data from any source ( census, usgs, etc. ).  For
        example, a list of states with id, name, and polygon shapes.
     2. Import said shape data at admin/build/geo
     3. Add a geo_data field that links to the new geo_data_state table via
        key.  Thus, the field provides a nice select list of states and
        stores an id value like 'MN' or '27'.
     4. In views, add a filter and/or an exposed filter, which limit queries
        using geo functions.  For example, using "Within" and this input:
          POINT(-94.312499886749 46.712163633385)
        the query will return all nodes tagged with "MN"

     See also: legislative lookups and district or precinct maps.