Opened 10 years ago

Last modified 11 months ago

#793 new enhancement

Provide breakline (fault line) support for surface interpolation modules

Reported by: marisn Owned by: grass-dev@…
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 Changed 10 years ago by hamish

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

comment:2 Changed 7 years ago by jdenisgiguere

Cc: jdenisgiguere added

comment:3 Changed 7 years ago by hamish

CPU: UnspecifiedAll
Keywords: breaklines added
Platform: UnspecifiedAll
Version: unspecifiedsvn-trunk

see also Alexander Muriy's v.triangle addon module,

http://grasswiki.osgeo.org/wiki/TIN_with_breaklines

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 Changed 4 years ago by martinl

Milestone: 7.0.07.0.5

comment:5 Changed 3 years ago by martinl

Milestone: 7.0.57.3.0

comment:6 Changed 3 years ago by martinl

Milestone: 7.3.07.4.0

Milestone renamed

comment:7 Changed 2 years ago by neteler

Milestone: 7.4.07.4.1

Ticket retargeted after milestone closed

comment:8 Changed 21 months ago by neteler

Milestone: 7.4.17.4.2

comment:9 Changed 17 months ago by martinl

Milestone: 7.4.27.6.0

All enhancement tickets should be assigned to 7.6 milestone.

comment:10 Changed 13 months ago by martinl

Milestone: 7.6.07.6.1

Ticket retargeted after milestone closed

comment:11 Changed 11 months ago by martinl

Milestone: 7.6.17.6.2

Ticket retargeted after milestone closed

Note: See TracTickets for help on using tickets.