Opened 20 years ago
Closed 20 years ago
#21 closed enhancement (fixed)
Introduce Point_set class
| Reported by: | ole | Owned by: | ole |
|---|---|---|---|
| Priority: | normal | Milestone: | AnuGA ready for release |
| Component: | Functionality and features | Version: | 1.0 |
| Severity: | normal | Keywords: | |
| Cc: |
Description (last modified by )
It may be desirable to have a class Point_set which contains collections of points with possible attribute values.
This would be very useful for set_quantity but also for allowing points to have methods for georeferencing and mappings between latitude/longitudes and UTM as in create_mesh.py in the Karratha study.
Point_set would point to geo_ref object and know whether values are relative to that or absolute. Points can also be geographic (lat/lon)
Change History (6)
comment:1 Changed 20 years ago by
| Description: | modified (diff) |
|---|
comment:2 Changed 20 years ago by
| Component: | documentation → pyvolution |
|---|
comment:3 Changed 20 years ago by
| Component: | Compilation and installation → Functionality and features |
|---|
comment:4 Changed 20 years ago by
| Status: | new → assigned |
|---|
comment:5 Changed 20 years ago by
comment:6 Changed 20 years ago by
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
This work has begun and we now have a Geo_spatial_data object we are building all point data around.
This is currently used by set_quantity
Note: See
TracTickets for help on using
tickets.

Geospatial object is partly implemented as of 31 Jan 2006
Perhaps equip domain with method get_geospatial_object returning vertices ?