Hi Maris, Le Sun, 29 Oct 2017 12:31:35 +0200, Maris Nartiss <maris....@gmail.com> a écrit :
> I added simple tests for v.profile. [1] > I also changed one of examples from documentation to use NC Basic > dataset. [2] > > If v.profile is moved to trunk, README file should be deleted. > > As there seem to be a lot of +1's and the requirement of tests is > fulfilled, this addon should be moved to trunk to gain some exposure > before release (or wait till 7.4.1). v.profile still uses the old buffering library methods which has quite a lot of issues. As an example, I attach the output map of the following example: v.profile input=geonames_NC@PERMANENT output=- separator=comma dp=3 buffer=500 profile_map=roadsmajor@PERMANENT profile_where=cat=193 map_output=test_profile I also attach the equivalent v.buffer output: v.buffer -c roadsmajor where=cat=193 dist=500 out=buff500 Would it be possible for you, Maris, to change to the GEOS method used in v.buffer in order to get the same buffering output ? This is not only formal as you can see when you use the following vector points as input: v.in.ascii in=- out=test_points << EOF 626382.68026139|228917.44816672|1 626643.91393428|228738.2879083|2 626907.14939778|228529.10079092|3 EOF v.profile then misses out on point 2, even though it is within 500m: v.profile input=test_points output=- separator=comma dp=3 buffer=500 profile_map=roadsmajor@PERMANENT profile_where=cat=193 Number,Distance,cat,dbl_1,dbl_2,int_1 1,2102.114,3,626907.14939778,228529.10079092,3 2,2960.822,1,626382.68026139,228917.44816672,1 Moritz
_______________________________________________ grass-dev mailing list grass-dev@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/grass-dev