<html>
<head>
<style>
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Verdana
}
</style>
</head>
<body class='hmmessage'>
Thanks very much for the reply Glynn (sorry about the misspelled version of your name). Do you think I could use G_put_map_row_random to fill a new raster with the modified values of cells at various locations in the region and then use patch to change the original raster? What would the other cell locations contain in a raster map written in this way (nulls, zeros, nothing)? To help clarify, I'm writing a GRASS_ABM extension and the agents will need to modify the rasters they interact with, but the simulation could run for thousands of iterations and I want to maximize speed and minimize memory usage. Once I get a working skeleton of ABM functions together (move, read raster, change raster, spawn new agents, die) then I'll clean up the messy code, document, and let the ABM mailing list know about the progress.<br><br>Chris<br> <br>> From: glynn@gclements.plus.com<br>> Date: Sat, 6 Jun 2009 18:52:20 +0100<br>> To: w_chris_carleton@hotmail.com<br>> CC: grass-dev@lists.osgeo.org<br>> Subject: Re: [GRASS-dev] Python SWIG<br>> <br>> <br>> chris carleton wrote:<br>> <br>> > I've read somewhere (by Glenn, I think) that Python-SWIG might not<br>> > go much farther with GRASS due to some limitations of the SWIG<br>> > interface (I'm not expert enough to know either way). Despite that,<br>> > I can't see another way to program what I want to do with GRASS. So,<br>> > I was hoping that someone on the list has a full list of currently<br>> > wrapped GRASS functions so that I know what I have to work with so<br>> > far.<br>> <br>> Everything in the following headers has been wrapped:<br>> <br>> G3d.h<br>> P_datetime.h<br>> Vect.h<br>> arraystats.h<br>> cluster.h<br>> datetime.h<br>> dbmi.h<br>> display.h<br>> gis.h<br>> gisdefs.h<br>> gmath.h<br>> gprojects.h<br>> imagedefs.h<br>> imagery.h<br>> raster.h<br>> stats.h<br>> transform.h<br>> vect/dig_defines.h<br>> vect/dig_structs.h<br>> vedit.h<br>> <br>> However, some of those wrappers will be unusable because of an<br>> inability to pass an argument from Python or return the result to<br>> Python.<br>> <br>> > Fortunately, I can just use Python scripting in the module when<br>> > I don't have direct access to GRASS functions, although that's going<br>> > to slow it all down.<br>> <br>> > The other question I have is related to raster editing. I need to be<br>> > able to edit specific cells in a raster map based on coordinate<br>> > locations passed to the editing function (I can sort of see how to<br>> > do it using the buffers that hold the row of raster data), but I<br>> > don't want a whole new map generated every time an edit is made. Is<br>> > it possible to edit a cell and then just close the map without<br>> > re-writing the whole matrix?<br>> <br>> Rasters cannot be modified "in place".<br>> <br>> > Also, if I'm making say a thousand<br>> > calls to that function will there be a noticeable lag time because<br>> > of all the opening and closing of the raster map (i.e. how much time<br>> > does it take to open and close a raster for reading/editing?). <br>> <br>> Modifying rasters one cell at a time isn't practical.<br>> <br>> One practical option is the mechanism which d.rast.edit uses:<br>> individual changes are stored internally; the map is updated by<br>> exporting the changes to a raster map using r.in.ascii, then the<br>> changes are merged with the original map using r.patch.<br>> <br>> -- <br>> Glynn Clements <glynn@gclements.plus.com><br><br /><hr />Attention all humans. We are your photos. <a href='http://go.microsoft.com/?linkid=9666044' target='_new'>Free us.</a></body>
</html>