"It sounds like you are trying to do at least 6 quite complicated things all at once, without really understanding any of them. This will not be easy."
Sigh. The story of my life in one sentence. On Tue, Oct 2, 2012 at 8:43 AM, Simon King <si...@simonking.org.uk> wrote: > On Mon, Oct 1, 2012 at 11:38 PM, Gery . <gameji...@hotmail.com> wrote: >> >> thanks but I want to use that live access to search at first through >> ExtJS/GeoExtJS/OpenLayers and through them there is only a url available >> (protocol HTTP), I also need to get the data as GeoJSON, so I think >> GeoAlchemy might not be the right solution, I think. If I'm wrong, please >> I'd love some points about it, thanks. >> > > It sounds like you are trying to do at least 6 quite complicated > things all at once, without really understanding any of them. This > will not be easy. > > 1. The client side of your application is presumably written in > Javascript and HTML, using javascript libraries such as ExtJS and > OpenLayers. You need to fully understand how these work. > > 2. The application will then make HTTP requests to a web server. You > need to understand at least the basics of HTTP. > > 3. The web server might be a single python script, or it could be > something running behind Apache. You need to understand your web > server. > > 4. The server side of your application might be using any of a number > of libraries to connect to the web server (such as > Django/Pyramid/Flask/cgi/mod_wsgi etc.). You need to understand > whatever mechanism your application is using to speak HTTP. > > 5. Your application can use SQLAlchemy and GeoAlchemy to retrieve data > from postgis into Python data structures. You will need to understand > postgis, SQLAlchemy, GeoAlchemy and Python. > > 6. Your application can then convert those Python data structures into > GeoJSON. You will need to understand GeoJSON. > > The SQLAlchemy mailing list can help you with exactly one part of this > (step 5). SQLAlchemy (and GeoAlchemy) is perfectly capable of querying > multiple tables and retrieving results. But how you accept the HTTP > request, and how you pass the results back, are completely outside the > scope of this list and I'm afraid you are unlikely to find much help > here with it. > > Sorry I can't be more help, > > Simon > > -- > 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. > -- 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.
