On Apr 19, 2009, at 4:05 PM, Roy Hyunjin Han wrote:
> >>> Do you know if anyone is working on a PostGIS extension for >>> SQLAlchemy? If not, I'd like to take a crack at it. >> >> My suggestions regarding this are of course building off of the >> postgis.py example, and also perhaps, if its feasable (not sure if it >> is), building the whole thing as a plugin to GeoDjango, which works >> with many different databases besides Postgres, and seems to have a >> lot of non-django-specific functionality. If the Django ORM >> bindings >> in GeoDjango could be replaced with SQLAlchemy bindings in an >> efficient way (where effiicient means, we're not taking Django ORM >> constructs and then translating to SQLA), we could leverage all the >> work they've done. >> > > Hmm. I was hoping I could add geospatial support to SQLAlchemy itself > rather than for a specific web framework. I didn't see anything in GeoDjango that is specific to Django except its bindings to the ORM, which is the part I'd want to replace, but I havent looked closely. If it is in fact tightly bound to only running in a Django web application then we'd have to scrap the idea. I of course am a Pylons user as well. geospatial support is definitely an external project in any case. SQLAlchemy is a core toolkit, but its not "batteries included". Utilities that build upon it like Migrate, FormAlchemy and such are separate projects. As soon as something goes in the core, its now linked to our release process, I'm getting the tickets and complaints personally, etc., theres no way a huge subject like geo support belongs there. I can't think of what advantage there would be to it being delivered in the core. > I think GeoDjango wraps the geospatial C++ libraries (GDAL, GEOS, > PROJ) with PostGIS but otherwise most of the core functionality seems > to be in the geospatial C++ libraries. it appears to support geometric schemas for several databases. > > Certainly, I can start with the > postgis.py example and use the GeoDjango API and MapFish API as > references. The MapFish community seems to have integrated PostGIS > with Pylons already and maybe I can ask them how they feel about a > geospatial extension for SQLAlchemy? I dont know much about MapFish but it appears to have a client/server, calls itself a web applciation framework, and seems completely complicated compared to just "we'd like to use PostGIS with SQLAlchemy". I'm just looking for smooth integration with PostGIS and other geospatial SQL extensions. If we decide my observation that GeoDjango has done a lot of work that needs to be re-done isn't really valid, and everything they've done is only useful for Django web applications, then that idea should be scrapped, and a simple library which builds upon SQLAlchemy expression constructs should be created. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To post to this group, send email to sqlalchemy@googlegroups.com To unsubscribe from this group, send email to sqlalchemy+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sqlalchemy?hl=en -~----------~----~----~----~------~----~------~--~---
