Just an FYI, Roman Nurik and Shawn Shen just released this article on using GeoModel on App Engine:
http://code.google.com/apis/maps/articles/geospatial.html Mano Marks Geo Developer Advocate http://twitter.com/ManoMarks On Thu, Dec 10, 2009 at 9:41 AM, Roger Bedell <[email protected]> wrote: > Raj > Sounds like a red herring to me, so since SQL server is written in C++, it > lets me program directly to machine code? More likely they just don't have > any confidence in the security of the spatial extensions yet. Too bad. > Roger > > -------------------------------------------------- > From: "Raj Singh" <[email protected]> > Sent: Thursday, December 10, 2009 6:26 PM > To: <[email protected]> > Subject: Re: [Geowanking] do cloud databases do spatial? > >> Thanks for all the feedback. I'm going to put this stuff together on a >> web page when I get a chance, but wanted to share a little tidbit from >> a Microsoft rep here at the OGC meetings. SQL Server in the cloud >> (azure?) doesn't include the spatial functionality because it's built >> with .NET, and including it would allow people to program directly to >> the CRL (common language runtime?) in the cloud -- a HUGE security >> issue. >> --- >> Raj >> >> >> On Nov 23, at 8:33 AM, Josh Livni wrote: >> >>> Well, FeatureServer supports AppEngine as a backend for points using >>> GeoModel (I've used this in a few projects), and for points/lines/ >>> polys using a (slighty buggy, unfortunately) geohash >>> implementation. So there's your schemaless geojson/kml/etc API >>> covered? >>> >>> Not sure what you mean by store should be agnostic of language you >>> write your app in ... wouldn't that be inherent if you were only >>> accessing it by a geojson api? Or did you mean you wanted to be >>> able to also write the rest of the app on the same platform as the >>> store? I do this w/AppEngine, but it only supports python/java for >>> now. >>> >>> AppEngine's big limitation using GeoModel is it's somewhat cpu >>> intensive to query. Unless you can make use of quite a bit of >>> caching, you'll likely end up hitting their free limits pretty >>> fast. Deciding on your caching style would depend a bit on your >>> app's usage, and right now would require a little tweaking to the >>> store code. >>> >>> -Josh >>> >>> >>> On Mon, Nov 23, 2009 at 5:05 AM, Andrew Turner >>> <[email protected] >>> > wrote: >>> To open the question up - what are the example or best case interfaces >>> and mechanisms of a "spatially-enabled cloud database"? >>> >>> And by "cloud" I mean internet accessible, on-demand, fast >>> provisioned, near-limitless scaling without me having to do the >>> administration. So setting up PostGIS/JTS/CouchDB are not cloud >>> databases, just db's that people tend to run on horizontally scaling >>> systems. >>> >>> As a first step, I'd like to see a GeoJSON API for a schema-less >>> 'cloud' datastore that exposed an OpenSearch-Geo interface for >>> querying it. Start with Point, but definitely needs to gain support >>> more complex features as well. >>> >>> The store should be agnostic to the language I write my application >>> in. >>> >>> Andrew >>> >>> On Sat, Nov 21, 2009 at 12:52 PM, Josh Livni >>> <[email protected]> wrote: >>> > You didn't mention if you're using java or python style >>> appengine. If java, >>> > then go w/Sean's recommendation (JTS) -- if python, I'd recommend >>> GeoModel, >>> > which unlike a standard geohash implementation will let you both >>> query by >>> > bounding box and still have access to your single inequality >>> filter for >>> > other items... >>> > -Josh >>> > >>> > >>> > On Sat, Nov 21, 2009 at 2:14 AM, John McKerrell >>> <[email protected]> wrote: >>> >> >>> >> As we're on this subject... a friend asked me recently if I knew >>> a way to >>> >> get AppEngine to do bounding box requests, as far as he could >>> tell it wasn't >>> >> possible, I had a look and I couldn't see a way either. I think >>> perhaps the >>> >> issue was that he was using the GeoPt type but there's no way to >>> access the >>> >> lat/lon from within it in a search so if he just stored the lat/ >>> lon as >>> >> separate fields that might work better. It's not something I've >>> looked at >>> >> too much but if anyone can offer a suggestion that would be good. >>> >> >>> >> He was originally asking my about geohashing in case that would >>> help but >>> >> as far as I could tell it has the same problem as quadtiles in >>> that if >>> >> you're on the edge of a big tile you don't find stuff on the next >>> tile. As >>> >> it was a UK based app the meridian is likely to cause problems >>> there. >>> >> >>> >> John >>> >> >>> >> On 21 Nov 2009, at 02:00, Ivan Lucena wrote: >>> >> >>> >> > Oracle Spatial does work in the EC2 environment. Once you have >>> an EC2 >>> >> > account you can go to OTN , >>> >> > http://www.oracle.com/technology/tech/cloud/index.html, and get >>> an EC2 kit. >>> >> > That means Features, 3D Point Cloud, Raster, the whole package. >>> >> > >>> >> > ________________________________________ >>> >> > From: [email protected] >>> >> > [[email protected]] On Behalf Of Raj Singh >>> >> > [[email protected]] >>> >> > Sent: Friday, November 20, 2009 2:29 PM >>> >> > To: [email protected] >>> >> > Subject: [Geowanking] do cloud databases do spatial? >>> >> > >>> >> > So, does Amazon SimpleDB do spatial? >>> >> > http://aws.amazon.com/simpledb/ >>> >> > >>> >> > Or how about MS SQL Azure? >>> >> > http://www.microsoft.com/windowsazure/sqlazure/ >>> >> > >>> >> > Any others to know about? >>> >> > >>> >> > --- >>> >> > Raj >>> >> > >>> >> > >>> >> >>> >>> _______________________________________________ >>> Geowanking mailing list >>> [email protected] >>> http://geowanking.org/mailman/listinfo/geowanking_geowanking.org >> >> >> _______________________________________________ >> Geowanking mailing list >> [email protected] >> http://geowanking.org/mailman/listinfo/geowanking_geowanking.org >> > > _______________________________________________ > Geowanking mailing list > [email protected] > http://geowanking.org/mailman/listinfo/geowanking_geowanking.org > _______________________________________________ Geowanking mailing list [email protected] http://geowanking.org/mailman/listinfo/geowanking_geowanking.org
