sis-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris A. Mattmann (JIRA)" <>
Subject [jira] Commented: (SIS-3) Refactor SIS
Date Sat, 03 Apr 2010 17:49:27 GMT


Chris A. Mattmann commented on SIS-3:

Hey Patrick, yep +1. I'm thinking handling different radii boils down to handling part 4a
from above, which is "the size of the blocks of material associated with measurements". In
terms of a config factory, sounds good. I think the above is just a basic core data structure
that we could adopt in SIS, where all of our distance and geometry calculations could be based
on. Then, for example, we wouldn't have to worry about Point, NDPoint, blah-d-point or all
of that. We could still have those classes, but they would be hidden underneath.



> Refactor SIS
> ------------
>                 Key: SIS-3
>                 URL:
>             Project: Spatial Information Systems
>          Issue Type: Improvement
>          Components: distance functions, geometry objects
>         Environment: indep. of env.
>            Reporter: Chris A. Mattmann
>            Assignee: Chris A. Mattmann
>             Fix For: 0.1-incubating
> Now with SIS-1 out of the way, I'll begin work on refactoring what we've got for SIS
so far. 
> After reading [1], I think we should begin with the definition of a spatio-temporal reference
identified there:
> {quote}
> Any measurement we take in Earth and environmental sciences, although this is often ignored,
has a spatio-temporal reference. A spatio-temporal reference is determined by (at least) four
> 1. geographic location (longitude and latitude or projected X,Y coordinates); 
> 2. height above the ground surface (elevation); 
> 3. time of measurement (year, month, day, hour, minute etc.); 
> 4. spatio-temporal support (size of the blocks of material associated with measurements;
time interval of measurement);
> {quote}
> I'm going to use this issue to track that focus of the initial refactoring.
> [1]

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message