Details

    • Type: Improvement Improvement
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 0.1-incubating
    • Labels:
      None
    • Environment:

      indep. of env.

      Description

      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:

      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 parameters:

      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);

      I'm going to use this issue to track that focus of the initial refactoring.

      [1] http://www.lulu.com/items/volume_67/8010000/8010854/5/print/Hengl_2009_GEOSTATe2c1_f.pdf

        Activity

        Chris A. Mattmann made changes -
        Status In Progress [ 3 ] Resolved [ 5 ]
        Resolution Fixed [ 1 ]
        Hide
        Chris A. Mattmann added a comment -
        • resolved in r986558. Thanks to Nga Chung for doing an awesome project in CSCI572 to kick this off!
        Show
        Chris A. Mattmann added a comment - resolved in r986558. Thanks to Nga Chung for doing an awesome project in CSCI572 to kick this off!
        Chris A. Mattmann made changes -
        Field Original Value New Value
        Status Open [ 1 ] In Progress [ 3 ]
        Hide
        Chris A. Mattmann added a comment -

        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.

        WDYT?

        Cheers,
        Chris

        Show
        Chris A. Mattmann added a comment - 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. WDYT? Cheers, Chris
        Hide
        patrick o'leary added a comment -

        Talked before about a configuration factory for handling different radii
        wonder could we use the same factory concept for handling this too?

        Show
        patrick o'leary added a comment - Talked before about a configuration factory for handling different radii wonder could we use the same factory concept for handling this too?
        Chris A. Mattmann created issue -

          People

          • Assignee:
            Chris A. Mattmann
            Reporter:
            Chris A. Mattmann
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development