Hi there!

I'm the maintainer of the Geo module, and it seems like there's a lot of overlap between these two projects. With Geo, you can:

- Create CCK fields that store geospatial data ( e.g. points, linestrings, polygons )
- Upload a zip file containing shape data and have it imported into a PostGIS or MySQL spatial table ( I wrote a shape file parser so that we don't have to rely on external function calls, and can use Drupal's schema API to create tables)
- Create CCK fields that reference a linked table that has been uploaded ( e.g. linking a country code to a table containing country geometries )
- Use the Views module to query for CCK and linked geospatial data ( or possibly just un-linked geospatial data ) in conjunction with other information. For example, you can find the political district for a user-submitted address, or you can find all of the items tagged with "foo" in a given zipcode.
- Provide a standard API with pluggable backends ( currently PostGIS and MySQL Spatial ) so that functionality beyond the scope of the Geo module can use its functionality.

However, what the Geo does NOT do is:
- Present aesthetically-pleasing input widgets or output formatters for geospatial information

At first I was elated to see this project, because I was hopeful that it meant that the geospatial data that people can already store and use through Geo could appear on beautiful maps. However, because of certain assumptions ( e.g. PostGIS, how the data is stored, the requirement for system calls and shp2pgsql, incompatible charactersets ), and the fact that there is no CCK or Views integration, the wonderful mapping capabilities

I am hopeful that you will consider working together on leveraging the storage and API capabilities of Geo, while focusing this module on mapping data from arbitrary sources, including Geo. Then, much of the functionality you are implementing here ( feeds, etc. ) could be handled by the Views module, and would be available to a wider audience. And work on additional backends can make more data available for mapping.

Comments

jpulles’s picture

jpulles commented

Hi Allie,

So far I haven't been able (lack of time) to install the development release of Geo and try e.g. the upload of a zipped shapefile, or other characteristics. The Geo module's concept is however very interesting to spent time on. I need to check it out (probably cvs?) together with the CCK and VIEWS modules. I'll probably have some time for that early October.

One of the things that is still missing from the mapping kit is using linked geospatial data for mapping. I would like to see how geo/cck/views would be useful in this.

What is missing from geo is probably an export of geospatial data as a shapefile. I always like it if things are symmetrical: if an import is possible, an export should be also (at least in the end); Drupal should not be input-only, especially not with geodata where file conversions are very common.

I would be happy to work together with you on getting the geo and mapping kit modules connect nicely together. It already seemed that at a not too distant future, this mapping kit would need to build on data from geo.

Kind regards,
John.

PS. Sorry if your elated feeling was spoiled ;-)

batje’s picture

batje commented

This is a real wonderfull cooperation that can only be cheered upon.

Can the mappingkit now be added to the header of http://groups.drupal.org/mapping in recognition of it being a great contribution to geo-capabilites of Drupal?

We can then also continue the integration conversation there as a group.

Good news, this is.

plopesc’s picture

plopesc
he/him
Primary language Spanish
commented

Hi!
I´m working in an University project which uses Geo and I´d like to contribute with the Geo development. I never have work in module developments, but I´m interested on this module. How can I help you?

jpulles’s picture

jpulles commented

In general when helping with module developments you can contribute patches for functionality you want to have added. Since you explicitly mention the Geo module, you probably want to do this for the Geo module instead of the Mapping kit so you may want to add an issue for http://drupal.org/project/geo. In case it wasn't a mistake, please propose which improvements you would like to see for the mapping kit project with preferable a patch ;-)

Regards,
John

forestmars’s picture

forestmars commented

This feature request has been open for 2 years with no updates? As much as has changed in the way Drupal can handle GIS, surely there is either some information about this, or at least mark as postponed with what info is needed.