In response to the following from William Unruh:
Hi William Unruh,
When I author a thread, I respond to all valid queries in that thread.
I don't leave anyone hanging (unless they've proven themselves unfit for a
response). Both you and Rudy are generally purposefully helpful, so I will
respond accordingly, with the same helpful tone and intent.
> And prolix response which never answers the questions, removed.
I am new to the word "prolix", so thanks for the new word!
https://www.merriam-webster.com/dictionary/prolix
1: unduly prolonged or drawn out : too long
2: marked by or using an excess of words
from pro- forward + liquºre to be fluid
> Below you talk about software that the user is supposed to buy.
I wonder where you got that idea from?
I assume I probably wasn't clear in that I've only bought mobile device
software a single time in my life, and that was just to write the apnote on
how to buy iOS & Android software using anonymous methods (for privacy
reasons). [I ended up wasting the rest of the money on that card because
the software cost less than the minimum amount I had to put on the card.]
Other than TurboTax, I haven't bought Windows software in, oh, maybe 5 to
10 years. And I have never needed to purchase Linux software ever.
All my tutorials exclusively use freeware, and all are cross platform on
purpose (if possible).
If you saw payware in any of my links, then one of us goofed because all my
tutorials utilize freeware for good reasons of leverage.
You have to remember, the "job" I'm trying to get done isn't what you think
it is. The job is to write the tutorial so that EVERYONE can get the job
done.
If the job was just for me to get the job done, I *already* did it.
The job isn't for me to get the job done, but to teach everyone else how
they can get the job done. Those people are on iOS, Android, Linux, and
Windows.
You have to realize I'm always trying to help people do what I can do.
> So why do you
> not make a wrapper which does all that "freaking complex" stuff?
Hehhehheh... I'm prolix; you're succinct.
You can write wrappers. I can't.
I write tutorials; you write wrappers.
Both benefit the tribal knowledge in different ways.
>> I just want to find someone who knows more than I do, to help guide me.
>
> But then they would be the ones who should be doing what you want to do, not
> you.
I must confess that sentence makes no sense.
I'm an advanced scuba diver. If I was going to dive in an area that I
wasn't familiar with, I have no qualms about asking for advice from people
who have dived there before.
If you don't understand that concept, then I can't teach it to you
(because it's as basic a concept as they get).
> Limit yourself to one software system.
What you don't know, or didn't get from the original post, is that the
entire tutorial is designed to be cross platform, like most of my tutorials
are designed to be.
So the software chosen on the mobile devices is free cross platform
software, as "should be" the software chosen for the desktop.
There are excellent reasons for that choice, where the *only* time you
break that rule is when one platform clearly excels over the other.
The minute you limit yourself to a single platform, you lose a huge
percentage of the people who would benefit from the tutorial.
Remember, the goal is the tutorial ... the goal isn't to get the job done
(I already did it ... but the way I did it is too complicated for the
tutorial for others to follow).
> Buy what? If they are interesting in doing the mapping, sure they will buy it
> instead of trying to follow directions from another novice who knows very
> little.
This is your philosophy. Mine is different.
Neither is right. Neither is wrong.
My philosophy is to write thousands of apnotes to help people "do things"
(I likely have ten thousand to my credit, but I don't want to hazard a
guess as the number is huge and not only in Usenet, so it doesn't matter
how many zeros there are).
The goal is so that users can benefit from following those apnotes.
And, another goal is that 1 out of 1,000 users *improves* the anpotes.
Everone wins because we all stand on someone's shoulders.
My philosophy is also that almost everything you need to do, is already
available in freeware (I've been a freeware junkie since the early days of
computers - where I almost never fail to find freeware to do the job).
My philosophy is that a cross platform solution has more leverage than a
single-platform solution, where I've already written the tutorial for the
cross-platform *use* of the geocalibrated maps on iOS and Android ... and
where I've written a single-platform horridly complex *geocalibration* of
the PDFs on Windows ...
Hence, the only thing this thread asks is:
What free tools on Windows & Linux, georeference PDF maps?
You seem to be displaying a dislike for the question, which is odd, since
it's a very simple question indeed.
>> And if it's cross platform, then one tutorial helps both Linux/Win users.
>
> So write two of them.
I don't know how to respond to that other than to say that if you don't see
the value of a cross-platform solution when leverage is your goal, then
you'll never see the value of anything (since the value is obvious).
> Good. Apparently it was not that complex.
Hehhehheh ... I like the sarcasm.
However, if you haven't done it, then there is 0 chance you can answer the
question.
I'm hoping there is 1 person out there who knows more than I do who can
help advise where the pitfalls are in my next choice of QGIS (since the
OziExplorer method is too complicated for most people).
> Because the expert should then be the guide not some novice who has no real
> idea how to do caving.
You are making a lot of mistakes which I can't disabuse you of since this
is the third obvious thing that you whoosehed on. I don't have the skills
to teach you the obvious, so, I'll just accept your point, which is that
you haven't done the task at hand.
Anyone who hasn't actualy done it, can't possibly answer the question
posed. All they can do is chitchat endlessly about their objections to
anyone trying to write a general solution for users.
If it was easy, everyone would have done it already since it's obviously an
extremely useful skill for people who route in the backcountry like I do
daily.
>>> Or, in a simple word K.I.S.S. Do not create a "white elephant" request
>>> when two smaller, normal elephants will suffice as well.
>>
>> I don't understand that statement.
>
> Keep it simple, stupid.
You have a wholly different philosophy than I do.
You apparently think two tutorials are better than one when both do the
same thing. I don't.
Remember, I already wrote the cross platform iOS/Android tutorial for
*using* the maps; I just need to write the cross-platform tutorial for
*creating* the maps.
> Instead of doing both windoes and Linux in one big white elephant, just do
> them separately. Use stuff on Linux and write up for Linux separately from
> Windows.
Philosophically, that's like taking two different cars when the family goes
on a trip to Disneyland. One for the wife and girls, and another for the
husband and boys.
If you think that's efficient, then I can't possibly disabuse you of your
notions. Suffice to say I think your approach is inefficient.
> You keep saying that.
Having said that, I know that it takes more intelligence and knowledge to
make cross-platform solutions, but I've been solving cross platform
problems my whole life.
It's as if you want to have one text file for Linux, and another text file
of the same thing for Windows, simply becuase they do the line feeds and
carriage returns differently.
If you really think having two files that do the same thing is more
efficient than having one that takes into account the variations, then I
can never disabuse you of your thoughts.
I think having a Word file on Linux and having that same file read on
Windows, is a good thing. You apparently think you should have two files,
one for Linux and one for Windows.
Sure, your method is brain dead and hence it's KISS.
But it's just stupid what you suggest.
It takes brains to create cross-platform solutions.
> No, you have not taken in his advice at all.
You've got to be kidding.
Both of you suggest the antithesis of what I'm trying to accomplish.
At the same time, neither of you have ever done the task even once.
When I decide to continue on the approach with the most leverage, you
lambaste me for not taking the "advice" to "just give up" from the both of
you?
Really?
C'mon. Did you purchase too many arguments this week or what?
I appreciate the helpful intent, really, I do - but - I'll say it again
that there is zero chance you can answer the question if you know less than
I do about the stated problem set.
> Apparently there is something he can teach you, but to teach one needs a
> receptive learner, which he does not have.
Don't worry. It's not your fault. You're trying to help.
Both of you think you're offering "advice", which I appreciate, but...
The question is a specific technical question of which way to go in a
complex cave system, where ...
If you've never scuba dived, and if you've never even been in a cave once
in your life, then you can't possibly give an expert scuba diver advice on
which way to go in a cave that he's only dived in once himself.
If you haven't done this task, you can't possibly answer the question.