Posted by smkeesle on February 5, 2009 at 7:11pm
I have a project that needs to describe geographic "regions" (shape) and map them. I like the ability of the location module to do exactly that for a "point" (latitude/longitude). Is there a module that does the same thing for a region?
Could that be built on top of location?
Comments
try Geo
I've been wanting to do the same, and I think that the main project in this arena is http://drupal.org/project/geo although I last tried it when it was started as a 5.x module.
This is exactly the goal of the Geo module.
Download the module from http://drupal.org/project/geo , get CCK, Install the "Geo Field" module, and away you go! You may find limitations in presenting widgets for users to generate shape data (e.g. a draw-things-on-a-map widget). Time spent on creating such a formatter would greatly benefit the Geo project as a whole.
If you already have shape data, such as an ESRI shape file, you can also enable the Geo Data module and import your file into a table. You can add this as
Modules that work with Geo:
Add to trackfield?
I might be able to add this function to the trackfield.module:
http://drupal.org/project/trackfield
Perhaps a 'This data defines a closed shape' option is required (it's just storing lines at the moment).
Would you want that defining at the field level (ie. when one creates a CCK field in their content type) or field instance level (ie. when a user enters co-ordinate list to define the line or closed shape)? Or perhaps a combination of this (ie. the checkbox on the node entry page appears only if configured to for this field).
For my use (the definition
For my use (the definition of a big location), it would be useful as a CCK field in the content type.
But really, your content is supposed to be defining a path...not a region. I'm not sure it makes sense to build it in there. It seems like it should be an option in the "location" module (is this location a point or a region?)
Region == Path
Given that all a region is, is a path with the ends connected this seems logical to me. Perhaps I have warped logic? ;)
The way I see it, location.module is for point information. geo.module sounds like it is meant to be flexible enough to store paths, regions, etc. but as already stated that is not available.
Anyhow - it was just a suggestion, saves me some work if you don't think this is a good idea! :)