Log of /contributions/modules/geo/geo.info
Parent Directory
| 
Revision Log
| 
Revision Graph
Revision
1.5 -
(
view)
(
download)
(
annotate)
-
[select for diffs]
Wed Aug 6 07:05:46 2008 UTC
(15 months, 3 weeks ago)
by
vauxia
Branch:
MAIN
Changes since
1.4: +2 -2 lines
Diff to
previous 1.4
Cleanup and progress towards a working D6 field module:
- Renamed CCK fields with geo_ namespace ( e.g. geo_point, geo_linestring )
to avoid collisions
- Removed geo_backend_field functions. These were intended to outsource
CCK's hook_field implementations so that the backend modules could take
care of everything. Good idea, but it also created a lot of duplicate
code. Meanwhile, I'd argue that the geo module itself - and its backends
- should not be cognizant of CCK. That's what an API is, right?
- Renamed API functions to geo_db_add_field, geo_db_drop_field from
geo_add_geometry_column, geo_drop_geometry_column.
- Removed geo_insert_geometry_data, and added geo_db_field_from_wkt to
specify column insertions. We'll leave the rest of the inserting to the
calling function.
- Removing references to geo_field and its table tracking. This seemed
like a really good idea when we created it, but seems like needless
housekeeping now, as the field module is already keeping track of its geo
fields.
- Began updating and refactoring D5 to D6 code.
Revision
1.4 -
(
view)
(
download)
(
annotate)
-
[select for diffs]
Wed Aug 6 03:47:55 2008 UTC
(15 months, 3 weeks ago)
by
vauxia
Branch:
MAIN
Changes since
1.3: +3 -3 lines
Diff to
previous 1.3
Reorganizing prior to a D6 upgrade:
- remove unused geo_geocoding.inc (long live geocrippler!)
- remove geo_cck.inc from geo.module and create a separate field module
(geo_field)
- remove table introspection from geo.module and create a separate data
integration module (geo_data)
- move all sub-modules (the aformentioned geo_field and geo_data, plus
existing geo_gmap and geo_devel modules) into a separate modules directory.
Revision
1.2 -
(
view)
(
download)
(
annotate)
-
[select for diffs]
Tue May 15 02:49:31 2007 UTC
(2 years, 6 months ago)
by
mfredrickson
Branch:
MAIN
Changes since
1.1: +5 -5 lines
Diff to
previous 1.1
Initial saving and loading of GIS data in postgis working. I need to factor out some of the SQL I'm using so that I can work with other db backends. Future work: using gmap to select points/lines, etc. Views queries to gather spatial data from the db. Add indexes to geometry columns.
Revision
1.1 -
(
view)
(
download)
(
annotate)
-
[select for diffs]
Wed Feb 28 21:34:24 2007 UTC
(2 years, 9 months ago)
by
mfredrickson
Branch:
MAIN
The geo module is an incubator for other geo* related modules (* geography, geometry, geocoding, and others)
Some current plans include:
- hook_geocode: allow modules to expose geocoding functionality. Right now, other modules require hardcoded calls to specific geocoding functions.
- Geometry field and PostGIS integration: Location.module does a good job of handling discrete points; however it cannot express larger geometries. Good tools exist to help with this functionality (e.g. PostGIS extensions on Postgresql) and could be leveraged to meet use cases location does not support.
There will be inevitable overlap between geo and other modules with similar functionality. Geo will fill the niche of an arbitrator among them. It is our goal that geo will both take over some functionality currently spread across multiple modules, as well as farm off functionality to more appropriate modules when possible.
Initially, geo requires location and gmap. It's only functionality so far is to allow administrators to use specific location fields in a Google maps geocode process.
This form allows you to request diffs between any two revisions of this file.
For each of the two "sides" of the diff,
select a symbolic revision name using the selection box, or choose
'Use Text Field' and enter a numeric revision.
