Well, there *is* a definition. A geographic information system (GIS), or geographical information system, captures, stores, analyzes, manages, and presents data that is linked to location. In the context of web2py, it sure can make for a darn good interface to other GIS related tools, but has no GIS functionality on it's own. As an example of where the framework itself *is* part of a GIS, see Geodjango. In the first approach, you're pretty much limited by what your underlying apps can do. With the second, you can implement spatial oriented functionality yourself - and that's a significant difference.
On Apr 23, 9:12 pm, Tim Michelsen <timmichel...@gmx-topmail.de> wrote: > > The GIS topic is pretty complex - you have to decide early on whether > > you want a simple spatial interface which is basically a pretty > > picture viewer with some associated features OR do you want a real GIS > > level approach which encompasses a spatial operations and relations on > > data, projection, compilation of layers and maps based on on the input > > data, rendering/presenting them, etc, etc. Embedding google maps does > > not suffice to call something a GIS framework or module :) > > No, but would you call arcexplorer or uDig a GIS? > web2py can do frontend and presentation stuff as well as pass parameters > and inquires to backends. There are a number: > * openlayers & mapfish > * pythongis (shapely et. al.) > * GRASS for heavy progessing > > So I am at the moment interested in integration stuff. Make geo analysis > or information more accessible. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "web2py Web Framework" group. To post to this group, send email to web2py@googlegroups.com To unsubscribe from this group, send email to web2py+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/web2py?hl=en -~----------~----~----~----~------~----~------~--~---
