Version 8 (modified by rwilson, 14 years ago) (diff) |
---|
Internal Documentation/Classes
Class Geospatial_data
Defined in file geospatial_data/geospatial_data.py.
Discussion
Class Attributes
geo_reference | |
file_name | |
max_read_lines | |
data_points | |
attributes | Dictionary |
default_attribute_name | |
verbose | |
blocking_georef | |
blocking_keys | |
number_of_points | |
fid | |
start_row | |
last_row | |
show_verbose | |
verbose_block_size | |
block_number | |
number_of_blocks | |
header | |
file_pointer |
Class Methods
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. |
BearingTo(self, P) | Returns the bearing in degrees from self to point P. |
name | |
name | |
name | |
name | |
name | |
name | |
name |
Notes
This class is defined in the 'old' way. Will need to be changed for python 2.6/3.x.
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.
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. See above point, also.