[OSGeo-Discuss] C++ library for "gridding"

[Gary Lang]

Yes.

One of the things that excited me when I met with Prof. Chen was how many OSGeo (and close friends) they were working on there and how much work they were ready to submit back to the projects.

--- Original Message ---
From: "Paul Ramsey" <pramsey at refractions.net>
Sent: Thu 10/19/06 4:50 pm
To: "discuss at mail.osgeo.org" <discuss at mail.osgeo.org>
Cc: "Chen Rongguo" <chenrg at lreis.ac.cn>, "song" <song7537338 at 163.com>, "xianfeng song" <song.osgeo at gmail.com>
Subject: Re: [OSGeo-Discuss] C++ library for "gridding"

That's great news! Is this work being done in the GRASS CVS? On a  
branch?

P

On 19-Oct-06, at 4:28 PM, Venkatesh Raghavan wrote:

> Hi All,
>
> Our colleagues in China have informed that they are
> working on modifying GRASS commands for data
> processing and analysis to C-API functions.
>
> Perhaps, Helana and others would work together
> or support Prof. Chen in speeding up development
> of the GRASS C-API.
>
> Regards
>
> Venka
>
> Paul Ramsey wrote:
>> I'll admit to interest, but can't really help. I would like to  
>> eventually add raster analytics to PostGIS, and hopefully do so  
>> through library linking rather than actually implementing the  
>> features in the core PostGIS code.  It would be nice to have a  
>> common library to work on this stuff in.
>> P
>> On 19-Oct-06, at 10:09 AM, Helena Mitasova wrote:
>>> If anybody is interested in developing general library for gridding
>>> that would include some of the standard methods and at the same time
>>> allow easy implementation of new functions, I will be happy to help.
>>> Our original intention with the RST modules in GRASS was to  
>>> create such
>>> library(including 2D, 3D and 4D) but I had to move on to erosion  
>>> modeling
>>> before it could be finished - so whatever we have done is now  
>>> scattered in
>>> the GRASS modules.
>>>
>>> Helena
>>>
>>> Markus Neteler wrote:
>>>> Hi,
>>>>
>>>> we are working on the SWIG interface to solve that to some
>>>> extend. A major rewrite is the alternative :-)
>>>>
>>>> Markus
>>>>
>>>> PS: See
>>>> http://grass.gdf-hannover.de/wiki/GRASS_and_Python
>>>> http://grass.gdf-hannover.de/wiki/GRASS_and_PHP
>>>> http://grass.gdf-hannover.de/wiki/GRASS_and_Shell
>>>>
>>>> On 10/18/06, Paul Ramsey <pramsey at refractions.net> wrote:
>>>>> Yes, unfortunately the algorithmic goodness of GRASS is scattered
>>>>> throughout the program executables rather than consolidated in a
>>>>> library.
>>>>>
>>>>> On 18-Oct-06, at 2:37 AM, Rob Agar wrote:
>>>>>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/discuss/attachments/20061019/decb183a/attachment-0001.html>