I haven’t been using lately i.segment.hierarchical (addon), at the time I installed it the first time (2014) I remember I had to tweak the installation because it wouldn’t compile. Today I tried g.extension and it doesn’t compile, but I forgot the trick meanwhile …
I can dig into it, ok, but can’t this be fixed? and moreover, as it is such a convenient tool to be used in combination with i.segment, wouldn’t its place better be merged with i.segment, perhaps adding an option for performing hierarchical segmentation?
Dai Pietro…!
I haven't been using lately i.segment.hierarchical (addon), at the time
I installed it the first time (2014) I remember I had to tweak the
installation because it wouldn't compile. Today I tried g.extension and
it doesn't compile, but I forgot the trick meanwhile ..
I can dig into it, ok, but can't this be fixed?
I don't have time right now, but a few weeks ago I successfully installed and used i.segment.hierarchical. IIRC, there was an error message during the g.extension run, but the module ran fine nevertheless.
and moreover, as it is
such a convenient tool to be used in combination with i.segment,
wouldn't its place better be merged with i.segment, perhaps adding an
option for performing hierarchical segmentation?
I don't know if it has to be merged (I prefer many specialised modules instead of one that does it all), but I agree that it might have its place in trunk.
On Wed, Jan 20, 2016 at 11:13 AM, Margherita Di Leo <diregola@gmail.com> wrote:
Hi,
I haven't been using lately i.segment.hierarchical (addon), at the time I
installed it the first time (2014) I remember I had to tweak the
installation because it wouldn't compile. Today I tried g.extension and it
doesn't compile, but I forgot the trick meanwhile ..
I can confirm the problem (F23):
GRASS 7.1.svn (nc_spm_08_grass7):~ > g.extension i.segment.hierarchical
Fetching <i.segment.hierarchical> from GRASS GIS Addons repository (be
patient)...
Compiling...
Makefile:17: warning: overriding recipe for target
'/home/neteler/tmp/grass7-neteler-14002/tmp5NNeQD/i.segment.hierarchical/etc/i.segment.hierarchical'
/home/neteler/software/grass71/dist.x86_64-pc-linux-gnu/include/Make/ScriptRules.make:19:
warning: ignoring old recipe for target
'/home/neteler/tmp/grass7-neteler-14002/tmp5NNeQD/i.segment.hierarchical/etc/i.segment.hierarchical'
Traceback (most recent call last):
File "/home/neteler/tmp/grass7-neteler-14002/tmp5NNeQD/i.segment.hierarchical/scripts/i.segment.hierarchical",
line 155, in <module>
raise ImportError("Not able to find the path %s directory." % path)
ImportError: Not able to find the path None directory.
make: *** [i.segment.hierarchical.tmp.html] Error 1
ERROR: Compilation failed, sorry. Please check above error messages.
Markus
I can dig into it, ok, but can't this be fixed? and moreover, as it is such
a convenient tool to be used in combination with i.segment, wouldn't its
place better be merged with i.segment, perhaps adding an option for
performing hierarchical segmentation?
Dai Pietro..!
On Fri, Jan 22, 2016 at 9:23 AM, Moritz Lennert <
mlennert@club.worldonline.be> wrote:
On 20/01/16 11:13, Margherita Di Leo wrote:
Hi,
I haven't been using lately i.segment.hierarchical (addon), at the time
I installed it the first time (2014) I remember I had to tweak the
installation because it wouldn't compile. Today I tried g.extension and
it doesn't compile, but I forgot the trick meanwhile ..
I can dig into it, ok, but can't this be fixed?
I don't have time right now, but a few weeks ago I successfully installed
and used i.segment.hierarchical. IIRC, there was an error message during
the g.extension run, but the module ran fine nevertheless.
For the record, the trick that worked for me: I svn'ed in
/home/user/.grass7/addons/etc/ the whole i.segment.hierarchical folder, and
copied i.segment.hierarchical.py into /home/user/.grass7/addons/scripts,
but removed the .py extension.
and moreover, as it is
such a convenient tool to be used in combination with i.segment,
wouldn't its place better be merged with i.segment, perhaps adding an
option for performing hierarchical segmentation?
I don't know if it has to be merged (I prefer many specialised modules
instead of one that does it all), but I agree that it might have its place
in trunk.
On Fri, Jan 22, 2016 at 9:23 AM, Moritz Lennert
<mlennert@club.worldonline.be> wrote:
...
I don't know if it has to be merged (I prefer many specialised modules
instead of one that does it all), but I agree that it might have its place
in trunk.
... at least the manual still needs a boost before adding it to trunk.
Anyone willing to write it?
