Hey Peter,

On Mar 29, 2012, at 12:07 PM, Peter K wrote:

> Hi Chris,
> 
> thanks for your time & answers!

Anytime.

> 
>>> And how could I e.g. store just one integer at lat/lon or other information?
>> B/c Lat/Lons are normally stored in coordinate systems that aren't integer
>> in nature (e.g., WGS84). At least in the ones I work with.
> 
> Ah, no :)
> I meant, how could I associate an integer with a latlon value?

Gotcha, my bad. You were using Integer to represent e.g., Integer implements 
SpatialData, like
we have been talking, e.g., the data associated with a QTreeNode, or something 
like it.

> Or instead 'integer': how is GeoRSSData is used? I simply don't understand 
> this at the moment. 

The GeoRSSData is like assuming that each QuadTreeNode represents a point and 
an associated
datum, which in the case of our current implementation is a URL to an article 
or some "thing". This
should be more generalized.


> E.g. how would I get the rss data and where is it stored?

You would interrogate the QuadTree, where the data is stored. Imagine a load 
interface, which is
what we have now, to load up our generic Quad Tree, a generic spatial data 
structure.


> Or is 'filename' the only part of this rss data?

Bingo.

> 
>>> And capacity is (accidentially?) not used - what happens if the data
>>> node is full?
>> Great question -- that's probably a bug?
> 
> yes, it could be a bug. at least an exception should be thrown.

Great, could you file a JIRA issue, and if you have time, create a patch? I'd 
be happy
to apply it...

Cheers,
Chris

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Chris Mattmann, Ph.D.
Senior Computer Scientist
NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
Office: 171-266B, Mailstop: 171-246
Email: [email protected]
WWW:   http://sunset.usc.edu/~mattmann/
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Adjunct Assistant Professor, Computer Science Department
University of Southern California, Los Angeles, CA 90089 USA
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Reply via email to