Speaking as a user... I used starspan a couple of times and it's great. But what I most liked about it is that _it works outside of GRASS_! It's independent of GRASS, so an user with just a shapefile and some GeoTiffs can use it happily.
At the same time that I believe it's a great tool and it should receive more attention, the ability to work with other formats and outside of grass is very important. Maybe have something like the gdal tools, where the user can transform and query any image outside grass but also, it works inside the GIS. I say this because I had several grass rasters that I needed to do a zonal stats with a very big shapefile. I was having a hard time importing the shapefile into grass so, starspan to the rescue! Fast and simple. Just my 2c Daniel On Fri, Jan 30, 2009 at 7:48 AM, Maris Nartiss <[email protected]> wrote: > Hello Nikos, > probably create a trac wish report "Investigate Starspan integration > possibilities into GRASS". It can be used also later as meta bug to > track integration blocking code bugs. > > I haven't used Starspan and currently have no requirements to do so, > still integrating various small projects into larger ones is a good > thing - lessens work fragmentation and improves code handling - any > GRASS dev can poke around that code. > Maris. > > 2009/1/30, Moritz Lennert <[email protected]>: >> On 29/01/09 20:06, Nikos Alexandris wrote: >>> On Thu, 2009-01-29 at 10:15 -0800, Jonathan Greenberg wrote: >>>> Folks: >>>> >>>> I would LOVE to see someone take over development on starspan -- I >>>> did submit a OSGEO application but it came back denied, more or less, >>>> because of lack of community support. There are a lot of bugs and user >>>> interface issues still remaining that would be nice to get cleaned up, >>>> but I'm not a C programmer and, while I developed the algorithm itself, >>>> I was not the coder. >>>> >>>> If anyone is interested in working on the development, please email >>>> me! If you all are not sure what STARSPAN does, it is a flexible way to >>>> get raster data (raw or summarized) associated with vector coverages >>>> (similar to Arc's zonalstats, although with more output types). E.g., >>>> if you want to get the average pixel values from a SET of raster images >>>> underlying a single vector coverage, starspan will spit out a CSV >>>> containing the vector's original database, along with a column for the >>>> average pixel value for that polygon. The algorithm tends to be very >>>> fast, especially in cases where the polygon coverage is a fraction of >>>> the raster coverage (which tends to be the case in many problems). >>>> >>>> --j >>> >>> Jonathan + all, >>> >>> please excuse my ignorance if I ask something that I shouldn't: could >>> you imagine starspan as part of GRASS? Something like "v.starspan" ? >>> >> >> >> http://lists.osgeo.org/pipermail/grass-user/2008-July/045882.html >> http://lists.osgeo.org/pipermail/grass-user/2008-August/045886.html >> >> +1 >> >> Moritz >> _______________________________________________ >> grass-user mailing list >> [email protected] >> http://lists.osgeo.org/mailman/listinfo/grass-user >> > _______________________________________________ > grass-user mailing list > [email protected] > http://lists.osgeo.org/mailman/listinfo/grass-user > _______________________________________________ grass-user mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/grass-user
