Not sure if I should post this here. I have a problem compiling starspan
with support for GRASS.
# configuring reports no problems
./configure --with-grass=/usr/local/grass-6.5.svn
# attempt to compile...
make
[...]
src/stats/Stats.cc:232: error: ‘sort’ was not declared in this scope
make: *** [Stats.o] Error 1
The same problem appears also with a bare "./configure".
Does anybody else face problems currently with starspan?
Nikos
On Wed, 2009-01-28 at 18:05 +0100, Nikos Alexandris wrote:
Not sure if I should post this here. I have a problem compiling starspan
with support for GRASS.# configuring reports no problems
./configure --with-grass=/usr/local/grass-6.5.svn# attempt to compile...
make[...]
src/stats/Stats.cc:232: error: ‘sort’ was not declared in this scope
make: *** [Stats.o] Error 1The same problem appears also with a bare "./configure".
The same error appears with all of the three versions of starspan
1.2.01, 1.2.02, 1.2.03.
Perhaps it's not starspan-related.
Nikos
On Thu, Jan 29, 2009 at 4:22 AM, Nikos Alexandris
<nikos.alexandris@felis.uni-freiburg.de> wrote:
On Wed, 2009-01-28 at 18:05 +0100, Nikos Alexandris wrote:
Not sure if I should post this here. I have a problem compiling starspan
with support for GRASS.# configuring reports no problems
./configure --with-grass=/usr/local/grass-6.5.svn# attempt to compile...
make[...]
src/stats/Stats.cc:232: error: 'sort' was not declared in this scope
make: *** [Stats.o] Error 1The same problem appears also with a bare "./configure".
The same error appears with all of the three versions of starspan
1.2.01, 1.2.02, 1.2.03.Perhaps it's not starspan-related.
Hmm. Check the archives for Jonathan Greenberg -- he is one of the
lead developers. It would be nice to get starspan into OSGEO so that
questions / code patches ect. can be handled in an efficient manner.
Starspan is an emmensly important GIS tool, but suffers from a lack of
developers, documentation, and bug handling.
Perhaps I should take these comments to the OSGEO mailing list... What
do you think Jonathan?
Cheers,
Dylan
On Thu, 2009-01-29 at 09:07 -0800, Dylan Beaudette wrote:
On Thu, Jan 29, 2009 at 4:22 AM, Nikos Alexandris
<nikos.alexandris@felis.uni-freiburg.de> wrote:
> On Wed, 2009-01-28 at 18:05 +0100, Nikos Alexandris wrote:
>> Not sure if I should post this here. I have a problem compiling starspan
>> with support for GRASS.
>>
>> # configuring reports no problems
>> ./configure --with-grass=/usr/local/grass-6.5.svn
>>
>> # attempt to compile...
>> make
>>
>> [...]
>> src/stats/Stats.cc:232: error: 'sort' was not declared in this scope
>> make: *** [Stats.o] Error 1
>>
>> The same problem appears also with a bare "./configure".
>
> The same error appears with all of the three versions of starspan
> 1.2.01, 1.2.02, 1.2.03.
>
> Perhaps it's not starspan-related.
>Hmm. Check the archives for Jonathan Greenberg -- he is one of the
lead developers. It would be nice to get starspan into OSGEO so that
questions / code patches ect. can be handled in an efficient manner.
Starspan is an emmensly important GIS tool, but suffers from a lack of
developers, documentation, and bug handling.Perhaps I should take these comments to the OSGEO mailing list... What
do you think Jonathan?Cheers,
Dylan
Yes, it would be very nice to have starspan osgeo-integrated.
Please... 
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
Dylan Beaudette wrote:
On Thu, Jan 29, 2009 at 4:22 AM, Nikos Alexandris
<nikos.alexandris@felis.uni-freiburg.de> wrote:
On Wed, 2009-01-28 at 18:05 +0100, Nikos Alexandris wrote:
Not sure if I should post this here. I have a problem compiling starspan
with support for GRASS.# configuring reports no problems
./configure --with-grass=/usr/local/grass-6.5.svn# attempt to compile...
make[...]
src/stats/Stats.cc:232: error: 'sort' was not declared in this scope
make: *** [Stats.o] Error 1The same problem appears also with a bare "./configure".
The same error appears with all of the three versions of starspan
1.2.01, 1.2.02, 1.2.03.Perhaps it's not starspan-related.
Hmm. Check the archives for Jonathan Greenberg -- he is one of the
lead developers. It would be nice to get starspan into OSGEO so that
questions / code patches ect. can be handled in an efficient manner.
Starspan is an emmensly important GIS tool, but suffers from a lack of
developers, documentation, and bug handling.Perhaps I should take these comments to the OSGEO mailing list... What
do you think Jonathan?Cheers,
Dylan
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" ?
Kind regards, Nikos
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
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 <mlennert@club.worldonline.be>:
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
grass-user@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-user
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 <maris.gis@gmail.com> 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 <mlennert@club.worldonline.be>:
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
grass-user@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-user_______________________________________________
grass-user mailing list
grass-user@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-user
On Fri, Jan 30, 2009 at 11:30 AM, Daniel Victoria
<daniel.victoria@gmail.com> wrote:
...
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
...
Sidenote:
There is new activity ongoing to improve that situation:
http://trac.osgeo.org/grass/ticket/426
Markus