Hello,
I've may have some time available in the next few months to devote to upgrading Drupal's GIS abilities. One area where I'd like to concentrate is exposing PostGIS data and functionality. In a nutshell, PostGIS allows storing arbitrary geometries (points, lines, polygons, multipolygons and combinations of those types) in database columns.
I'm in the process of writing a quick project proposal, and I wanted to see if anyone knew of existing work to pair Drupal with PostGIS. I would probably start by writing a CCK module to act as the Drupal <-> PostGIS bridge. Hopefully, since PostGIS is OGC based, I could keep it generic enough to later support MySQL spatial extensions or other OGC compliant database stores.
In addition to the db layer stuff, I'd like to work on views integration (for more powerful spatial queries) and a UI for entering data that is better than just plopping in WKT. Suggestions or prior work on this front would be most appreciated.
Please feel free to request features or specific behaviors. We'll see what I have time to complete.
Cheers,
-Mark
Comments
microformats
Could this work integrate the microformat geo? See here for info: http://microformats.org/wiki/geo. I will soon be turning to working on a mapping module for neighborhoods. Could your proposed module do this? If so, I'm willing to work on it with you. I'll take a look at the PostGIS link.
As for microformats in general, I think that most of them would be good candidates for CCK modules.
Related microformats to geo are adr (http://microformats.org/wiki/adr) which is for locations (by address?) if you don't know the name, or hcards (http://microformats.org/wiki/hcard) if you do know the name of the locations since adr is a child(?) of hcard.
seems very reasonable. I'll
seems very reasonable. I'll keep it in mind when writing formatters.
Thanks.
i'd like to help with this
i'd like to help with this if i could.
i think this should be built with geodan's geo-drupal distro idea in mind.
but i was hoping it could all run on LAPP (postgres v. mysql).
i've read several statements about mysql's lack of geo-spatial support and lower marks on scalability and speed.
Look at this
Look at this http://drupal.org/sandbox/geops/1212962 and its explication in http://www.geops.de/blog/64-spatial-data-and-drupal-7