Opened 15 years ago
Last modified 6 years ago
#793 new enhancement
Provide breakline (fault line) support for surface interpolation modules
Reported by: | marisn | Owned by: | |
---|---|---|---|
Priority: | normal | Milestone: | 7.6.2 |
Component: | Vector | Version: | svn-trunk |
Keywords: | breaklines | Cc: | jdenisgiguere |
CPU: | All | Platform: | All |
Description
Current v.surf.* modules do not support breaklines (fault lines). It's common in geology and other fields to have line/surface that limits interpolated value expansion - interrupts spatial correlation (neighborhood influence).
IMHO breaklines should be taken into account at two times - first when choosing data input points for calculation (only points at one side of line) and second time - when assigning values for cells - only cells at one side of line should receive values.
I understand that this is longterm goal and it requires lot of discussions how it should be implemented. Still it's a wanted feature.
Change History (11)
comment:1 by , 15 years ago
comment:2 by , 12 years ago
Cc: | added |
---|
comment:3 by , 11 years ago
CPU: | Unspecified → All |
---|---|
Keywords: | breaklines added |
Platform: | Unspecified → All |
Version: | unspecified → svn-trunk |
see also Alexander Muriy's v.triangle addon module,
Hamish wrote:
try v.surf.icw from addons. [...] it is very computationally expensive so number of starting points should be kept low.
note the new version isn't quite as expensive as the old, and now supports multi-processing. Probably should still be limited to less than a few hundred input points though.
Hamish
comment:4 by , 9 years ago
Milestone: | 7.0.0 → 7.0.5 |
---|
comment:5 by , 8 years ago
Milestone: | 7.0.5 → 7.3.0 |
---|
comment:8 by , 7 years ago
Milestone: | 7.4.1 → 7.4.2 |
---|
comment:9 by , 6 years ago
Milestone: | 7.4.2 → 7.6.0 |
---|
All enhancement tickets should be assigned to 7.6 milestone.
try v.surf.icw from addons.
http://grass.osgeo.org/wiki/GRASS_AddOns#v.surf.icw http://grass.osgeo.org/wiki/Image:Inlets_03_SurfSal_icw_big.png
it is very computationally expensive so number of starting points should be kept low.
Hamish