Changes between Version 7 and Version 8 of ClassGeospatial_data


Ignore:
Timestamp:
Mar 2, 2009, 8:02:08 AM (16 years ago)
Author:
rwilson
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • ClassGeospatial_data

    v7 v8  
    3434== Class Methods ==
    3535
     36|| '''__init__(data_points=None, attributes=None, geo_reference=None, default_attribute=None, file_name=None, latitudes=None, longitudes=None, points_are_lats_longs=False, max_read_lines=None, load_file_now=True, verbose=False)''' || Constructor.     ||
    3637|| '''!BearingTo(self, P)''' || Returns the bearing in degrees from `self` to point `P`. ||
     38|| '''name''' ||  ||
     39|| '''name''' ||  ||
     40|| '''name''' ||  ||
     41|| '''name''' ||  ||
     42|| '''name''' ||  ||
     43|| '''name''' ||  ||
     44|| '''name''' ||  ||
    3745
    3846== Notes ==
    … …  
    4048This class is defined in the 'old' way.  Will need to be changed for python 2.6/3.x.
    4149
    42 Not sure that building in blocking to this class is the correct approach.  Perhaps better to override file semantics to provide blocking and then get this class to contain a reference to a file-like object to get data from.
     50'''Way too overloaded''' in the constructor.  For instance, data_points are `either` a 2-dimensional array of points `or` a filename of input data.  Yet there is also a file_name parameter for a filename!?  Maybe better not to fill with data in the constructor but call one of a selection of 'file_with_data' routines later.
     51
     52Not sure that building in blocking to this class is the correct approach.  Perhaps better to override file semantics to provide blocking and then get this class to contain a reference to a file-like object to get data from.  See above point, also.
    4353
    4454-----