Return-Path: Delivered-To: apmail-cassandra-user-archive@www.apache.org Received: (qmail 1258 invoked from network); 5 Feb 2011 18:05:26 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 5 Feb 2011 18:05:26 -0000 Received: (qmail 36819 invoked by uid 500); 5 Feb 2011 18:05:24 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 36685 invoked by uid 500); 5 Feb 2011 18:05:22 -0000 Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@cassandra.apache.org Delivered-To: mailing list user@cassandra.apache.org Received: (qmail 36677 invoked by uid 99); 5 Feb 2011 18:05:21 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 05 Feb 2011 18:05:21 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of sean.m.ochoa@gmail.com designates 209.85.214.44 as permitted sender) Received: from [209.85.214.44] (HELO mail-bw0-f44.google.com) (209.85.214.44) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 05 Feb 2011 18:05:13 +0000 Received: by bwz12 with SMTP id 12so4144675bwz.31 for ; Sat, 05 Feb 2011 10:04:53 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:from:date :message-id:subject:to:content-type; bh=rHMee3RpRlpQEqOpUf3M+svnqRCy762juL/0V/iZxSI=; b=HtJd9+iNLCTnPJE4RJ+OcUeZAOSFvZTvaicbppZoPVax3kOOYZL7Zp8lC7skFO3x4+ +IPLEjDyUizSqNiWTb0zfJ3NFje7NqmTJYD05Kaw6KGV5I3MbbW1GLYqdRUG1awDdFnx wndI0KxMK78tTe9vofHww+3rX//pUNwK2KgwE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; b=QAUIVqrSoK9sVwAiRwYi0YlyTKT4Vmqn3732Gp2ztkelxooxRoFv94T98emU3My/ez EWGr+hkGV3fB5SOGiF/gnawMK+hKDV7FUoenoTImPAKDqmJ+bdblDaqT5MYdDxPTiW+/ i6hzQw0xpQadfCeyduSSE1QXASrHSpJxHkQUQ= Received: by 10.204.69.73 with SMTP id y9mr12958576bki.76.1296929093314; Sat, 05 Feb 2011 10:04:53 -0800 (PST) MIME-Version: 1.0 Received: by 10.204.71.75 with HTTP; Sat, 5 Feb 2011 10:04:13 -0800 (PST) In-Reply-To: <4D4D8E1B.60706@gmail.com> References: <4D4D8E1B.60706@gmail.com> From: Sean Ochoa Date: Sat, 5 Feb 2011 10:04:13 -0800 Message-ID: Subject: Re: postgis > cassandra? To: user@cassandra.apache.org Content-Type: multipart/alternative; boundary=001636c5a8a8e7e94c049b8cd5c5 X-Virus-Checked: Checked by ClamAV on apache.org --001636c5a8a8e7e94c049b8cd5c5 Content-Type: text/plain; charset=UTF-8 That's a good question, Bill. The data that I'm trying to store begins as a simple point. But, moving fo= rward, it will become more like complex geometries. I assume that I can si= mply create a JSON-like object and insert it. Which, for now, that works. = I'm just wondering if theres a typical / publicly accepted standard of sto= ring somewhat complex spatial data in Cassandra. Additionally, I would like to figure out how one goes about slicing on large spatial data sets given situations where, for instance, I would like to get all the points in a column-family where the point is within a shape. I guess it boils down to using a spatial comparator of some sort, but I haven't seen one, yet. - Sean On Sat, Feb 5, 2011 at 9:51 AM, William R Speirs wrote: > I know nothing about postgis and little about spacial data, but if you're > simply talking about data that relates to some latitude & longitude pair, > you could have your row key simply be the concatenation of the two: > lat:long. > > Can you provide more details about the type of data you're looking to > store? > > Thanks... > > Bill- > > > On 02/05/2011 12:22 PM, Sean Ochoa wrote: > >> Can someone tell me how to represent spatial data (coming from postgis) in >> Cassandra? >> >> - Sean >> > -- Sean | M (206) 962-7954 | GV (760) 624-8718 --001636c5a8a8e7e94c049b8cd5c5 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable That's a good question, Bill= .

The data that I'm trying to store begins as a simple point. =C2=A0But, = moving fo=3D
rward, it will become more like complex geometries. =C2=A0I= assume that I can si=3D
mply create a JSON-like object and insert it. = =C2=A0Which, for now, that works. =3D
=C2=A0I'm just wondering if theres a typical / publicly accepted standa= rd of sto=3D
ring somewhat complex spatial data in Cassandra.
Additionally, = I would like to figure out how one goes about slicing on large spatial data= sets given situations where, for instance, I would like to get all the poi= nts in a column-family where the point is within a shape. =C2=A0I guess it = boils down to using a spatial comparator of some sort, but I haven't se= en one, yet.=C2=A0

=C2=A0- Sean

On Sat, Feb 5, 20= 11 at 9:51 AM, William R Speirs <bill.speirs@gmail.com> wrote:
I know nothing about postgis and little about spacial data, but if you'= re simply talking about data that relates to some latitude & longitude = pair, you could have your row key simply be the concatenation of the two: l= at:long.

Can you provide more details about the type of data you're looking to s= tore?

Thanks...

Bill-


On 02/05/2011 12:22 PM, Sean Ochoa wrote:
Can someone tell me how to represent spatial data (coming from postgis) in<= br> Cassandra?

=C2=A0- Sean



--
Sean=C2=A0|= M (206) 962-7954 | GV=C2=A0(760) 624-8718
--001636c5a8a8e7e94c049b8cd5c5--