<html>
<body>
At 10-08-2015 22:47 Monday, Alex Mandel wrote:<br>
<blockquote type=cite class=cite cite="">On 08/10/2015 12:49 PM,
Springfield Harrison wrote:<br>
> Hello Paolo,<br>
> <br>
> Good that you can report a different experience, hopefully a better
one than <br>
> mine. My operating system is W7 and I have many years of experience
in GIS, <br>
> mostly Manifold.<br>
> <br>
> I have received several suggestions for georeferencing vector files
-<br>
> <br>
> * Vector Bender, VectorGeoreference plug-ins. Both of these
failed due to<br>
> missing dependencies. Although the programs are
experimental, should not<br>
> the underlying essential files be in place?<br>
> * Grass V.rectify, v.transform. I believe these operate
through GRASS. I<br>
> have gone down so many rabbit holes lately that
some of these details are<br>
> beginning to blur. I believe the problem here
was using GRASS itself. <br>
> There seems to be a steep learning curve,
particularly with the definition<br>
> of a mapset. The whole thing fell apart when the
process for defining a<br>
> Group (why?) required a raster file for a purely
vector process. I have<br>
> stuck in a dummy raster file and will try again
eventually. This has been<br>
> hugely time-consuming with nothing to show for
it. <br>
> <br>
> My main complaints are twofold,<br>
> <br>
> * missing dependencies. From extensive traffic on this list
over the past few<br>
> weeks, the whole QGIS environment seems to be
rife with missing support<br>
> files. I understand that this is open source,
etc. but surely all the<br>
> essential pieces should be in place. When I
attempt to install Vector<br>
> Bender, it reports missing dependencies and packs
up. Why doesn't it just<br>
> install the missing dependencies, it seems to
know what and where they are?<br>
<font color="#FF00FF"><br>
Missing dependencies for Plugins are python libraries that do not
ship<br>
with QGIS as they are not QGIS specific and are set by plugin
authors<br>
outside the main QGIS build system. Sometime down the road we hope to
be<br>
able to pull such libraries as needed during plugin install...<br><br>
On Windows also note that QGIS/OSGeo4w ship with their own Python<br>
separate from the system to avoid conflicts. You have to install
extra<br>
python libs into this QGIS specific python.</font><br>
</blockquote><font color="#0000FF"><x-tab>
</x-tab>Right, a complex
process I suppose. I don't understand your second paragraph, and
don't really need to. However, it does indicate to me that one
needs a fair amount of very specific technical knowledge to do a full and
proper install. To me, this is a major failing, as I am not an IT
professional and only have rudimentary programming skills.
<br><br>
<x-tab> </x-tab>My
interest is in using the GIS tools that I need to their fullest, not in
unraveling the arcane foibles and quirks of a poorly implemented
installation process. As an end-user, my imperative is to do the
work, not endlessly fart around trying to get all of it's parts connected
and working. If I wanted to do that I would get a degree in
computer science and join the development team. Perhaps the
developers overestimate the technical computer skills of the
end-users. I suspect that most of us don't really care what goes on
under the hood, we just want to get work done.<br><br>
<x-tab> </x-tab>Sorry for
the rant, I have wasted many evenings on what should be a very simple
task. I was contemplating donating to the cause but will give that
thought a rest for now.<br><br>
<x-tab> </x-tab><x-tab>
</x-tab>Thanks again,
Cheers . . . . . . . . Spring Harrison<br><br>
<br><br>
<br>
</font><blockquote type=cite class=cite cite="">Nathan has a good blog
post about it, maybe someone can recall the link,<br>
I can't seem to find it.<br><br>
-Alex</blockquote></body>
</html>