Opened 20 years ago
Last modified 16 years ago
#16 new defect
Make sure that georeferencing is used consistently (domain, pmesh, sww files, ...)
| Reported by: | ole | Owned by: | nariman |
|---|---|---|---|
| Priority: | low | Milestone: | AnuGA ready for release |
| Component: | Functionality and features | Version: | |
| Severity: | minor | Keywords: | |
| Cc: |
Description (last modified by )
The georeferencing object isn't used consistently yet. Some code in source:inundation/pyvolution/data_manager.py is working directly with xllcorner and yllcorner
Also make sure that georeferencing is tested everywhere (esp least squares)
Change History (9)
comment:1 Changed 20 years ago by
| Description: | modified (diff) |
|---|
comment:2 Changed 20 years ago by
| Severity: | normal → minor |
|---|
comment:3 Changed 20 years ago by
| Component: | Compilation and installation → Functionality and features |
|---|
comment:4 Changed 19 years ago by
| Status: | new → assigned |
|---|
comment:5 Changed 19 years ago by
comment:6 Changed 19 years ago by
Talked to Ole about the last issue (10/2/06) The Mesh interface was not being used correctly. The point lists were relative and the geo-reference wasn't passed in.
So this part of the issue can be crossed off.
Note though that using the ?geo-referenced points? class in this interface we could have the geo-ref info more tightly bound with the points, reducing the likelyhood of this sort of error.
comment:7 Changed 19 years ago by
| Priority: | normal → low |
|---|
Remove all xllcorner, yllcorner references.
comment:8 Changed 17 years ago by
| Owner: | changed from duncan to rwilson |
|---|---|
| Status: | assigned → new |
comment:9 Changed 16 years ago by
| Owner: | changed from rwilson to nariman |
|---|
Note: See
TracTickets for help on using
tickets.
Currently, it looks to me that meshes created are kept in absolute UTM coordinates through to domain. I think they should be made relative in the mesh constructor or pmesh2domain.