<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<div class="moz-cite-prefix">Hi,</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">while I agree that there are lots of
bad examples of proprietary formats, I want to say a few words to
some of your examples:</div>
<div class="moz-cite-prefix">It is true that OpenStreetMap data is
difficult to handle - this is not because it is closed, but
because it is open. When the project was started the goal was to
make it as easy as possible for people to contribute to the
dataset. Thus there are few restrictions which makes it difficult
to render or process the data. But the alternative would probably
have been to discuss the data format for years instead of building
an amazing open dataset...</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">While Garmin makes it difficult to
upload custom maps to their units as Nicolas wrote, many of their
devices can be accessed as a USB drive and waypoint/track data can
simply be copied as .GPX-files. I have seen many devices needing
special software to transfer data, so this is actually easy.</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">When Google Earth first came to be, it
was amazing - access to satellite or aerial imagery had been
expensive and difficult before. So I don't have a problem with the
fact that Google didn't make the data available for everyone to
use (probably license restrictions prohibit this).</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">Text files aren't often that simple -
there are different encodings for example which aren't advertised
in the files, so you often have to guess to get special characters
right. They have no inbuilt validity checks, so errors can not be
easily recognised. In most use cases, structured (XML) formats are
preferable. And especially for large datasets, you get much better
performance and functionality using other formats like Geopackage.
The point in my opinion is that a format is open and well
documented.</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">Of course it is great if geodata is
available to the public. In the EU, there has been a lot of
movement in the last years with more and more data becoming
available under open licenses, let's hope this continues.<br>
</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">Regards,</div>
<div class="moz-cite-prefix">Jochen<br>
</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">Am 25.05.20 um 20:55 schrieb Falk
Huettmann:<br>
</div>
<blockquote type="cite"
cite="mid:CA+BKNPD+H7oUuDNy7VezP2c21cxK=TYvW-+u4caivnjonLhpbQ@mail.gmail.com">
<div dir="ltr">
<div>Dear Chris et al,</div>
<div><br>
</div>
...by using certain specific/clumsy formats -poorly documented
ones - you can virtually exclude
<div>people from data and from Remote Sensing data and GPS etc.</div>
<div>Google Earth as a classic example, and GARMIN as another,
or ESRI files, certainly NetCDF or many R packages even.</div>
<div><br>
</div>
<div>In reality, you will see that all what is shiny and new -
in demand- is to be sold, and usually not well publically
shared.</div>
<div>It takes many steps to get around it, if even that.</div>
<div><br>
</div>
<div>While I have used OpenStreet maps, it was very clumsy; more
bad examples exist, e.g. lack of metadata.</div>
<div>Whatever companies tell ya, they want to sell more stuff
(sell PR, or might face bankruptcy otherwise).</div>
<div><br>
</div>
<div>And it is my hope that with QGIS we get to open access and
open source,</div>
<div>of these data, and any other.</div>
<div><br>
</div>
<div>My format of choice is plain and simple ASCII text files
for those reasons, perhaps using the </div>
<div>Virtual Machine as a platform forever (well, as long as
that is reasonable, but not commercially driven).</div>
<div><br>
</div>
<div>Keep me posted please; very best & thanks</div>
<div> Falk Huettmann</div>
<div><br>
</div>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Mon, May 25, 2020 at 10:19
AM chris hermansen <<a href="mailto:clhermansen@gmail.com"
moz-do-not-send="true">clhermansen@gmail.com</a>> wrote:<br>
</div>
<blockquote class="gmail_quote">
<div dir="ltr">
<div dir="ltr">Falk and list;<br>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Mon, May 25, 2020 at
10:48 AM Falk Huettmann <<a
href="mailto:fhuettmann@alaska.edu" target="_blank"
moz-do-not-send="true">fhuettmann@alaska.edu</a>>
wrote:<br>
</div>
<blockquote class="gmail_quote">
<div dir="ltr">Dear List,
<div>I think these GPS high resolution suggestions are
great; </div>
<div>thanks.</div>
<div><br>
</div>
<div>But my real interest/question here is, how can we
bring it home to QGIS ?</div>
<div><br>
</div>
<div>I see GARMIN essentially trying to sell and
impose on us their GIS system,</div>
<div>same applies to OpenStreet Maps etc etc. So they
try to privatize geography and public space and
information, </div>
<div>which I am mostly opposed to.</div>
</div>
</blockquote>
<div><br>
</div>
<div>How is OpenStreetMap (I assume when you say
"OpenStreet Maps" you mean "OpenStreetMap") trying "to
privatize geography and public space and information"?
Not trying to start an argument here; this just seems
completely contrary to what I know of OpenStreetMap,
whose data is licensed under <a
href="https://opendatacommons.org/licenses/odbl/1.0/"
target="_blank" moz-do-not-send="true">https://opendatacommons.org/licenses/odbl/1.0/</a></div>
<div><br>
</div>
<blockquote class="gmail_quote">
<div dir="ltr">
<div><br>
</div>
<div>Instead, I wonder how we can use QGIS and release
the commercial</div>
<div>data into Open Source and public use ?</div>
<div>That's for HIGH RESOLUTION data discussed here.</div>
<div><br>
</div>
<div>Thanks for such questions and solutions.</div>
</div>
</blockquote>
<div><br>
</div>
<div>[stuff deleted] <br>
</div>
</div>
<br>
<br>
-- <br>
<div dir="ltr">
<div dir="ltr">Chris Hermansen · clhermansen "at" gmail
"dot" com<br>
<br>
C'est ma façon de parler.</div>
</div>
</div>
</blockquote>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
Qgis-user mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Qgis-user@lists.osgeo.org">Qgis-user@lists.osgeo.org</a>
List info: <a class="moz-txt-link-freetext" href="https://lists.osgeo.org/mailman/listinfo/qgis-user">https://lists.osgeo.org/mailman/listinfo/qgis-user</a>
Unsubscribe: <a class="moz-txt-link-freetext" href="https://lists.osgeo.org/mailman/listinfo/qgis-user">https://lists.osgeo.org/mailman/listinfo/qgis-user</a></pre>
</blockquote>
<p><br>
</p>
</body>
</html>