On Mon, Aug 3, 2009 at 8:19 PM, Glynn Clements wrote:
> Markus Neteler wrote:
>
>> > LOC_CHECK_LIBS checks for a specific symbol, so it should be
>> > straightforward to check for a symbol which is only present in 3.x.
>>
>> Something like this?
>> [nete...@localhost grass70]$ svn diff configure.in
Glynn Clements wrote:
Markus Metz wrote:
Yes, if you want to work with vectors not in the current mapset using
grass7, you have to rebuild topology for all vectors in the
corresponding mapset first.
So it's intentional that GRASS7 is no longer compatible with previous
vector maps?
Hamish:
[...] it would
be nice if v.info could work (even partially) for maps without topology
built. e.g. massive LIDAR datasets.
Try trunk r38644, new -l flag for v.info to open vector map on level 1.
Markus M
___
grass-dev mailing list
grass-de
Markus Neteler wrote:
> >> > LOC_CHECK_LIBS checks for a specific symbol, so it should be
> >> > straightforward to check for a symbol which is only present in 3.x.
> >>
> >> Something like this?
> >> [nete...@localhost grass70]$ svn diff configure.in
> >
> >> +
> >> LOC_CHECK_LIBS(geos,GEOSGeo
Markus Metz wrote:
> >> Yes, if you want to work with vectors not in the current mapset using
> >> grass7, you have to rebuild topology for all vectors in the
> >> corresponding mapset first.
> >>
> >
> > So it's intentional that GRASS7 is no longer compatible with previous
> > vector maps
Glynn Clements wrote:
> > Ah, ok, you use the grass57 dataset. I have now changed the version
> > number and compatibility info, you should now get reasonable
> > warnings/errors with the spearfish57 dataset.
>
> Okay, I'll check it.
Nope. As of r38644, the error message is unchanged.
--
Gl
On Sat, Aug 8, 2009 at 7:03 PM, Glynn Clements wrote:
>
> Markus Metz wrote:
>
>> >> Yes, if you want to work with vectors not in the current mapset using
>> >> grass7, you have to rebuild topology for all vectors in the
>> >> corresponding mapset first.
>> >>
>> >
>> > So it's intentional that GRA
Glynn Clements wrote:
Glynn Clements wrote:
Ah, ok, you use the grass57 dataset. I have now changed the version
number and compatibility info, you should now get reasonable
warnings/errors with the spearfish57 dataset.
Okay, I'll check it.
Nope. As of r38644, the error messa
I did not have time to respond to this line of discussion as I am
trying to get my class material ready,
but lib/rst also needs to be updated with offsets set to off_t and
fseek to G_fseek
in interp2d.c and write2d.c - see below. This should be done only in
grass7.
I think GRASS64 / 65 rs
Glynn:
Breaking backwards compatibility is allowed in 7.0. We'll probably be
breaking raster compatibility at some point (but in a far more
fundamental way; old rasters won't be recognised at all).
Something this fundamental should have been announced (maybe it was
and I missed it). Also, the e
you were right - thanks for the hint, fortunately it was just one
data set that was affected.
I am still wondering why tcltk browser shows files that start with . ?
I haven't had a chance to try this data set with wxgui.
Helena
On Aug 7, 2009, at 6:49 PM, Hamish wrote:
Helena wrote:
Also in
Markus Neteler wrote:
> >> I got carried away (replacing all fseek/ftell occurrences I could find
> >> with G_fseek/G_ftell, adjusting off_t as you showed above) and also made
> >> r3.in|out.v5d LFS-safe, but did not submit. Should I?
> >
> > Yes; ideally, we should use G_{fseek,ftell} everywhere
Markus Metz wrote:
> > d.vect, etc use the libraries and VECT_CFLAGS, so it isn't just v.*
> > modules which need to be checked. It might just be v.* modules which
> > need to be fixed; I don't know.
>
> OK. I will check all modules including or any of the
> headers in include/vect. All vector
Helena Mitasova wrote:
> I am still wondering why tcltk browser shows files that
> start with . ?
It is my understanding that that is a feature of the tcltk file
picker, and there is nothing we can do about it.
Hamish
___
grass-dev mailing l
Markus Metz wrote:
> >>> Ah, ok, you use the grass57 dataset. I have now changed the version
> >>> number and compatibility info, you should now get reasonable
> >>> warnings/errors with the spearfish57 dataset.
> >>>
> >> Okay, I'll check it.
> >>
> >
> > Nope. As of r38644, the er
[divide by zero in awk]
Markus Neteler wrote:
> ok... but how to add "protection"?
> The original input was 81 rows (pixels with certain
> temperature and their corresponding altitude from DEM).
>
> It prints out
> print tot, sumX, sumsqX, sumY, sumsqY, sumXY
> 7432 9.17582e+06 1.14575e+10 7432 7
Hamish wrote:
> how about adding something like this to the awk script:
(sorry about that being so rough+buggy, but you get the idea)
H
___
grass-dev mailing list
grass-dev@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-dev
#711: r.horizon crashes
---+
Reporter: eblizza | Owner: grass-dev@lists.osgeo.org
Type: defect| Status: new
Priority: normal| Milestone: 6.4.0
#580: WinGRASS: $GISBASE/etc/gui/scripts/ require something like $(EXE) to run
---+
Reporter: hamish| Owner: grass-dev@lists.osgeo.org
Type: defect| Status: new
Pri
#72: PNG driver: boundary rendering is off by one pixel
--+-
Reporter: hamish | Owner: grass-dev@lists.osgeo.org
Type: defect | Status: new
Priority: critical
20 matches
Mail list logo
