Re: [Qgis-user] Problem installing QGIS on Ubuntu 20.04 - key authentification

2020-08-11 Thread Andrea Giudiceandrea
evaroben wrote
> So it's the combination of two brand new versions that creates the
> problem?

Hi Eva,
after some other research about your issue and thanks to Richard
Duivenvoorde that checked and confirmed the issue on his system using other
tools, is now clear that the problem is not related to QGIS but:

- to a misconfigured security connection protocol used by the WMS server at
gibs.earthdata.nasa.gov (it uses an insecure SHA-1 hash function in some
circumstances)

- to a default higher security level connection (SHA-1 is not allowed)
requested by the version of the openssl library (1.1.1f) shipped with Ubuntu
20.04

You can workaround the issue following the advice provided at
https://askubuntu.com/a/1233456

Although it's not recommended to lower the security level of https
connections, I've personally tested that solution and it works on my Ubuntu
20.04, allowing QGIS to connect via SSL with the WMS server at
gibs.earthdata.nasa.gov.


Hi Richard,
you can also confirm the source of the issue checking that

curl -v
"https://gibs.earthdata.nasa.gov/wms/epsg4326/best/wms.cgi?SERVICE=WMS=GetCapabilities;
--cipher "DEFAULT@SECLEVEL=1"

works.

And also directly using openssl to connect to the server, checking that

openssl s_client -connect gibs.earthdata.nasa.gov:443

do not works, while

openssl s_client -connect gibs.earthdata.nasa.gov:443 -cipher
DEFAULT@SECLEVEL=1

works.

For further reference, see
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1864689


Regards.

Andrea



--
Sent from: http://osgeo-org.1560.x6.nabble.com/QGIS-User-f4125267.html
___
Qgis-user mailing list
Qgis-user@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-user
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user

Re: [Qgis-user] Label overlapping between layers

2020-08-11 Thread Christine
Good evening Pietro,
did you already consider to apply the functions of the label toolbar ?
With the tools of the label toolbar you may rearrange the automatic
positioning of the label (e.g. move, rotate). 

Regards, Christine



pieri70 wrote
> I would like that the label of the bottom one wil not overlap the top one
> geometry.
> Is there any way to achieve this?
> I played with label weight but I didn't get success





--
Sent from: http://osgeo-org.1560.x6.nabble.com/QGIS-User-f4125267.html
___
Qgis-user mailing list
Qgis-user@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-user
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user

Re: [Qgis-user] Migrating legacy QGIS instance

2020-08-11 Thread Charles Dixon-Paver
Sorry for the confusion Walt, but the "overhead" I was referring to here is
actually the fact that gpkg is implemented as a SQLite container with a
*minimum* filesize which adds a couple MB. I think the "overhead" will vary
depending on the type of data stored. Basically, if you make one for every
shapefile you could probably expect to end up with an additional ~5MB of
bloat to your existing data store for each shapefile converted...

Upper limits as you stated should be (in theory) ~140TB, or at least
somewhere upwards from whatever I would usually consider practical to store
in a database that's stored as a single flat file...

Regarding geomoose on Mac, you could try use docker to test it out
https://github.com/geomoose/docker-geomoose

In terms of the specifics on how to restructure your data infrastructure,
it seems like it's going to depend a lot on the specifics of your use case
and is probably outside the scope of this mailing list, or at least this
thread... Migrating projects is another beast altogether, so maybe someone
else can offer advice on that.

Regards

On Tue, 11 Aug 2020 at 20:20, Walt Ludwick  wrote:

> This makes good sense to me, Charles.  I've got enough experience with
> databases (tho not so much with geographic ones) that i'm comfortable w/
> SQL query tools. Unless a list or directory is small enough to eyeball with
> ease (certainly the case with this legacy QGIS instance i've inherited),
> i'd much rather search than dig for the data, so... In this sense at least,
> less fragmentation is more.
>
> That being said: i don't know if i can bundle all into a single .gpkg; if
> there is a size limit as low as 5MB on each one, then certainly not.
> Google search on string "Geopackage size limit" returns multiple
> credible-looking pages that cite a limit (subject to filesystem
> constraints) of 140TB.  Can you clarify about the "~5MB of storage overhead
> for each unique .gpkg" comment?
>
> In any case: if i go for selective consolidation -selection scheme still
> TBD[1]- then i must certainly bear in mind your caution about the data loss
> risk associated with careless use of certain processing tools/
> configurations.  If there be tools & configs oriented to one & only one
> .gpkg file, i don't yet know about them... But i'll certainly watch out for
> that and keep a good backup!
>
> [1] As to selection (or classification, i should say) and naming of .gpkg
> files that will consolidate any number of .shp files: i am thinking along
> lines of either data type (raster and vector being two high-level
> groupings, with subtypes that might have more to do with the schema of
> tabular data), or else data source (which often has much to do with data
> reliability, maintainability -and value, ultimately).  Need to think a bit
> more deeply on this, and would be happy for any guidance from more
> experienced GIS admins.
>
>
> On Tue, Aug 11, 2020 at 2:31 PM Charles Dixon-Paver 
> wrote:
>
>> Regarding the one-vs-many approach to gpkgs, I recommend consolidation
>> (within reason). I feel that the temptation to use gpkg as a drop-in
>> replacement for shp is familiarity with processes I personally consider to
>> be largely outmoded. I think it's worth getting over the initial
>> (relatively shallow) learning curve so that when you start working with db
>> oriented systems like PostGIS, everything makes sense right out of the gate.
>>
>> Basically it boils down to how you want to manage or distribute them as
>> you don't have traditional db roles. Personally, I try to package things
>> into "data.gpkg/something" and "data.gpkg/somethingelse" wherever possible,
>> rather than "a.gpkg/a" and "b.gpkg/b". It usually makes moving data around
>> easier for me. If you have a lot of inputs, maybe split it into unique
>> gpkgs based on some categorising criteria (like you might do with a schema)
>> rather than one monolithic gpkg. Performing maintenance (vacuum) on a large
>> number of unique gpkgs seems like an unnecessary chore.
>>
>> One limitation for gpkg is that certain processing tools/ configurations
>> will only support writing to an entire gpkg, so if you lack experience
>> you'll need to be careful not to overwrite all of your data and also have a
>> decent backup plan in place. Usually you can get away with utilising a
>> scratch.gpkg for that purpose with no risk to your primary datastore.
>>
>> Using the one-per-item feature offers little data management benefit from
>> shapefiles aside from removing the auxiliary files and being able to store
>> styles (as well as lae). There is little performance benefit over shp
>> directly from what I understand (both use WKB), but there is ~5MB of
>> storage overhead for each unique gpkg (if I remember correctly), but this
>> will depend on your use case.
>>
>> Hope that helps.
>>
>> On Tue, 11 Aug 2020 at 15:13, Basques, Bob (CI-StPaul) <
>> bob.basq...@ci.stpaul.mn.us> wrote:
>>
>>> *Depending on your end goal, you might be more suited to leaving 

Re: [Qgis-user] Problem installing QGIS on Ubuntu 20.04 - key authentification

2020-08-11 Thread Andrea Giudiceandrea
evaroben wrote
> gpg: key F7E06F06199EF2F2: 1 Beglaubigung wegen fehlendem Schlüssel nicht
> geprüft 
> gpg: Schlüssel F7E06F06199EF2F2: "QGIS Archive Automatic Signing Key 
> (2020) 

> qgis-developer@.osgeo

> " nicht geändert gpg: Anzahl 
> insgesamt bearbeiteter Schlüssel: 1 gpg:  unverändert: 1"

Dear Eva,
"1 Beglaubigung wegen fehlendem Schlüssel nicht geprüft " (="1 signature not
checked due to a missing key") just means the imported gpg key with id
F7E06F06199EF2F2 has 1 signature non verifiable. This is not a problem and
you can ignore it and it does not prevent to correctly import the key into
the apt keyring. Moreover, the key F7E06F06199EF2F2 is already in your apt
keyring ("Schlüssel ... nicht geändert", "unverändert: 1"). You can check
this running "sudo apt-key list F7E06F06199EF2F2".

Anyway AFAIK this gpg key is only needed for the QGIS installation and
update process and is not related with your SSL protocol connection error.

Which QGIS version are you using? I suppose 3.14.1, isn't it?

I can connect to the WMS sever at
https://gibs.earthdata.nasa.gov/wms/epsg4326/best/wms.cgi using:
QGIS 3.14.0 on Windows 10
QGIS 3.14.1 on Ubuntu 18.04
QGIS 3.12.3 (Flatpak) on Ubuntu 20.04

but I cannot connect to the WMS sever using QGIS 3.14.0 on Ubuntu 20.04 as
you reported:

WMS PROVIDER
Failed to download capabilities:
Download of capabilities failed: SSL handshake failed


Instead i can connect to other WMS servers using https (e.g.
https://wms.cartografia.agenziaentrate.gov.it/inspire/wms/ows01.php) with
QGIS 3.14.0 on Ubuntu 20.04.

Could you please check if you can connect to other WMS servers using https
(e.g. https://wms.cartografia.agenziaentrate.gov.it/inspire/wms/ows01.php)?

It's probably worth reporting the bug on the qgis-developer ml or on GitHub
if other user can check if they can or cannot use that WMS server at
https://gibs.earthdata.nasa.gov/wms/epsg4326/best/wms.cgi.

Regards.

Andrea Giudiceandrea



--
Sent from: http://osgeo-org.1560.x6.nabble.com/QGIS-User-f4125267.html
___
Qgis-user mailing list
Qgis-user@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-user
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user

Re: [Qgis-user] Migrating legacy QGIS instance

2020-08-11 Thread Walt Ludwick
This makes good sense to me, Charles.  I've got enough experience with
databases (tho not so much with geographic ones) that i'm comfortable w/
SQL query tools. Unless a list or directory is small enough to eyeball with
ease (certainly the case with this legacy QGIS instance i've inherited),
i'd much rather search than dig for the data, so... In this sense at least,
less fragmentation is more.

That being said: i don't know if i can bundle all into a single .gpkg; if
there is a size limit as low as 5MB on each one, then certainly not.
Google search on string "Geopackage size limit" returns multiple
credible-looking pages that cite a limit (subject to filesystem
constraints) of 140TB.  Can you clarify about the "~5MB of storage overhead
for each unique .gpkg" comment?

In any case: if i go for selective consolidation -selection scheme still
TBD[1]- then i must certainly bear in mind your caution about the data loss
risk associated with careless use of certain processing tools/
configurations.  If there be tools & configs oriented to one & only one
.gpkg file, i don't yet know about them... But i'll certainly watch out for
that and keep a good backup!

[1] As to selection (or classification, i should say) and naming of .gpkg
files that will consolidate any number of .shp files: i am thinking along
lines of either data type (raster and vector being two high-level
groupings, with subtypes that might have more to do with the schema of
tabular data), or else data source (which often has much to do with data
reliability, maintainability -and value, ultimately).  Need to think a bit
more deeply on this, and would be happy for any guidance from more
experienced GIS admins.


On Tue, Aug 11, 2020 at 2:31 PM Charles Dixon-Paver 
wrote:

> Regarding the one-vs-many approach to gpkgs, I recommend consolidation
> (within reason). I feel that the temptation to use gpkg as a drop-in
> replacement for shp is familiarity with processes I personally consider to
> be largely outmoded. I think it's worth getting over the initial
> (relatively shallow) learning curve so that when you start working with db
> oriented systems like PostGIS, everything makes sense right out of the gate.
>
> Basically it boils down to how you want to manage or distribute them as
> you don't have traditional db roles. Personally, I try to package things
> into "data.gpkg/something" and "data.gpkg/somethingelse" wherever possible,
> rather than "a.gpkg/a" and "b.gpkg/b". It usually makes moving data around
> easier for me. If you have a lot of inputs, maybe split it into unique
> gpkgs based on some categorising criteria (like you might do with a schema)
> rather than one monolithic gpkg. Performing maintenance (vacuum) on a large
> number of unique gpkgs seems like an unnecessary chore.
>
> One limitation for gpkg is that certain processing tools/ configurations
> will only support writing to an entire gpkg, so if you lack experience
> you'll need to be careful not to overwrite all of your data and also have a
> decent backup plan in place. Usually you can get away with utilising a
> scratch.gpkg for that purpose with no risk to your primary datastore.
>
> Using the one-per-item feature offers little data management benefit from
> shapefiles aside from removing the auxiliary files and being able to store
> styles (as well as lae). There is little performance benefit over shp
> directly from what I understand (both use WKB), but there is ~5MB of
> storage overhead for each unique gpkg (if I remember correctly), but this
> will depend on your use case.
>
> Hope that helps.
>
> On Tue, 11 Aug 2020 at 15:13, Basques, Bob (CI-StPaul) <
> bob.basq...@ci.stpaul.mn.us> wrote:
>
>> *Depending on your end goal, you might be more suited to leaving things
>> as they are and using  some sort of content explorer to organize the
>> existing data.  Then worry about migrating to different formats as needed.*
>>
>>
>>
>> *We’ve been using GeoMoose for this purpose.  It can connect to just
>> about any data source on the back end, such as SHP, Postgres, and
>> GeoPackage to name a few, but also can connect to proprietary services as
>> well.  Because it can use Mapserver as a display engine and data query
>> tool, it lends itself to online exploration of the data without the need
>> for a full blown GIS tool.  This allows for wide spread use by non-GIS
>> pros.  The datasets can still be managed by you with QGIS and/or in
>> Postgres/postgis, or whatever you prefer for that purpose.  The Mapserver
>> setup allow for connecting to just about any type of service behind the
>> scenes, and with the right configuration, you can also enable each dataset
>> in the GeoMoose catalog as a WMS/WFS data source, thee standard for open
>> data format access and publishing.*
>>
>>
>>
>> *Bobb*
>>
>>
>>
>>
>>
>>
>>
>> *From:* Qgis-user  * On Behalf Of *Walt
>> Ludwick
>> *Sent:* Tuesday, August 11, 2020 7:45 AM
>> *To:* qgis-user@lists.osgeo.org
>> *Subject:* Re: [Qgis-user] 

Re: [Qgis-user] Migrating legacy QGIS instance

2020-08-11 Thread Walt Ludwick
Thanks for the tip, Bobb; i had a look at https://www.geomoose.org/ and it
sounds good... But not for MacOS users, alas, unless i am missing
something.  If there be any such thing available for Mac tho (?), i would
love to give it a try!

On Tue, Aug 11, 2020 at 2:13 PM Basques, Bob (CI-StPaul) <
bob.basq...@ci.stpaul.mn.us> wrote:

> *Depending on your end goal, you might be more suited to leaving things as
> they are and using  some sort of content explorer to organize the existing
> data.  Then worry about migrating to different formats as needed.*
>
>
>
> *We’ve been using GeoMoose for this purpose.  It can connect to just about
> any data source on the back end, such as SHP, Postgres, and GeoPackage to
> name a few, but also can connect to proprietary services as well.  Because
> it can use Mapserver as a display engine and data query tool, it lends
> itself to online exploration of the data without the need for a full blown
> GIS tool.  This allows for wide spread use by non-GIS pros.  The datasets
> can still be managed by you with QGIS and/or in Postgres/postgis, or
> whatever you prefer for that purpose.  The Mapserver setup allow for
> connecting to just about any type of service behind the scenes, and with
> the right configuration, you can also enable each dataset in the GeoMoose
> catalog as a WMS/WFS data source, thee standard for open data format access
> and publishing.*
>
>
>
> *Bobb*
>
>
>
>
>
>
>
> *From:* Qgis-user  * On Behalf Of *Walt
> Ludwick
> *Sent:* Tuesday, August 11, 2020 7:45 AM
> *To:* qgis-user@lists.osgeo.org
> *Subject:* Re: [Qgis-user] Migrating legacy QGIS instance
>
>
>
> *Think Before You Click: *This email originated *outside *our
> organization.
>
>
>
> I'm on MacOS -and not so very comfortable with command line scripting- so
> it looks like i might have to go the drag way to import these .shp
> files. Will take some time, but at least that way i can be sure about what
> i've put where, and in what form.
>
>
>
> But i do wonder about the (a) "stick multiple shps into a single gpkg" OR
> (b) "create one per feature" decision, since i'm not experienced enough to
> have a clear preference about this.  Can you say anything about pros & cons
> of going one way vs the other?
>
>
>
>
>
> On Tue, Aug 11, 2020 at 11:45 AM Charles Dixon-Paver 
> wrote:
>
> Easiest way for me is to use the GDAL ogr2ogr
>  command using a bash script or
> cmd batch to traverse your directories (depending on how you installed QGIS
> this should be on your path). I don't know what environment you're running
> though.
>
>
>
> You can either stick multiple shps into a single gpkg or create one per
> feature as you prefer. ogr2ogr can also push shp files directly into
> PostGIS. When you want to consolidate or migrate data (between gpkgs or
> from gpkg to PostGIS) you can simply select the feature layers you want and
> use drag and drop from the QGIS 3 Browser panel to copy multiple features
> to a target location.
>
>
>
> Others might have different approaches though.
>
>
>
> Regards
>
>
>
> On Tue, 11 Aug 2020 at 12:24, Walt Ludwick  wrote:
>
> I've inherited a legacy GIS, built up over some years in versions 2.x,
> that i'm now responsible to maintain.  Being an almost complete n00b (did
> take a short course in QGIS a good few years ago, but still..), i could
> really use some advice about migration.
>
> i've created a new QGIS instance in version 3.14, into which i am trying
> to bring all useful content from our old system: oodles of shapefiles,
> essentially, plus all those other files (each .shp file appears to bring
> with it a set of.shx, .dbf, .prj, qpj  files, plus a .cpg file for each
> layer, it seems).  This is a significant dataset- 14gb, >1000 files -and
> that is just base data, not counting Projects built on this data or Layouts
> used for presenting these projects in various ways. Some of this is cruft
> that i can happily do without, but still:  i've got a lot of porting-over
> to do, without a clear idea of how best to do it.
>
> The one thing i'm clear about is: i want it all in a non-proprietary
> database (i.e. no more mess of .shp and related files) that is above all
> quick & easy to navigate & manage. It is a single-user system at this
> point, but i do aim to open it up to colleagues (off-LAN, i.e. via
> Internet) as soon as i've developed simple apps for them to use.  No idea
> how long it'll take me to get there, so...
>
> Big question at this point is: What should be the new storage format for
> all this data?  Having read a few related opinions on StackOverflow, i get
> the sense that GeoPackage will probably make for easiest migration (per this
> encouraging article
> ,
> it's a simple matter of drag -simple if you have just a few, i guess!
> [1]), and can easily support my needs in the short term, but then i wonder:
> How will i 

Re: [Qgis-user] Migrating legacy QGIS instance

2020-08-11 Thread Walt Ludwick
So the plot thickens!  In focusing so intently on the problem of .shp file
conversion, i've been a bit careless in my consideration of Projects and
their related files, but -though some of these projects are history that we
can afford to forget- some of them will need to be included in this system
migration, in fact.

SO: I'll need to do some triage on these projects... And then if there be
any "project packager plugin" that might facilitate the bundling and
migration of those selected projects, i'd love to give such a try.  Any
such plugin(s) that you could recommend?


On Tue, Aug 11, 2020 at 2:26 PM Nicolas Cadieux 
wrote:

> Hi,
>
> People are suggesting that ogr2ogr would work.  That will work with data
> but NOT with the QGIS projects.  QGIS projects calls various data files in
> various directories,  if you change the name of a file, the file type, the
> file directory structure, the project files will indicate that x number of
> files cannot be found...  The project file contains all the Published maps.
>
> While most vector data file will be easy to find because of known formats,
> it will be harder to travers the hard drive for the raster data as formats
> are similar (like tiff, jpg...) If vector data is stored in .csv or .txt...
> you will have the same trouble identifying just the spatial data from the
> rest.
>
> I hope your user had structure and method in his folders. (Method to the
> madness)
>
> One way could be to scan for the project file and see which ones are
> important and still open on the old machine.  Then, you could look for a
> project packager plugin that will save all the needed file in a single
> directory.  That will unfortunately take lots of manual work and lead to
> file duplications but at least, you will save the project files that
> contain a lot of work. I know of no other way to save the project file
> except to make an exact copy of the hard drive.  I usually, at the very
> least, make a copy of the hard drive as backup in case the user comes
> begging two years down the line for a very special project file he can’t
> find in the new system...
>
> If all you want is the data, I agree that geopackage and tiff seems like a
> good options.
>
> Good luck!
>
> Nicolas Cadieux
> Ça va bien aller!
>
> Le 11 août 2020 à 06:24, Walt Ludwick  a écrit :
>
> 
> I've inherited a legacy GIS, built up over some years in versions 2.x,
> that i'm now responsible to maintain.  Being an almost complete n00b (did
> take a short course in QGIS a good few years ago, but still..), i could
> really use some advice about migration.
>
> i've created a new QGIS instance in version 3.14, into which i am trying
> to bring all useful content from our old system: oodles of shapefiles,
> essentially, plus all those other files (each .shp file appears to bring
> with it a set of.shx, .dbf, .prj, qpj  files, plus a .cpg file for each
> layer, it seems).  This is a significant dataset- 14gb, >1000 files -and
> that is just base data, not counting Projects built on this data or Layouts
> used for presenting these projects in various ways. Some of this is cruft
> that i can happily do without, but still:  i've got a lot of porting-over
> to do, without a clear idea of how best to do it.
>
> The one thing i'm clear about is: i want it all in a non-proprietary
> database (i.e. no more mess of .shp and related files) that is above all
> quick & easy to navigate & manage. It is a single-user system at this
> point, but i do aim to open it up to colleagues (off-LAN, i.e. via
> Internet) as soon as i've developed simple apps for them to use.  No idea
> how long it'll take me to get there, so...
>
> Big question at this point is: What should be the new storage format for
> all this data?  Having read a few related opinions on StackOverflow, i get
> the sense that GeoPackage will probably make for easiest migration (per this
> encouraging article
> ,
> it's a simple matter of drag -simple if you have just a few, i guess!
> [1]), and can easily support my needs in the short term, but then i wonder:
> How will i manage migration to PostGIS when i eventually put  this system
> online with different users/ roles enabled?
>
> [1] Given that i need to pull in some hundreds of .shp files that are
> stored in a tree of many folders & subfolders, i also wonder: is there a
> simple way that i can ask QGIS to traverse a certain directory, pull in all
> the .shp files -each as its own .gpkg layer, i suppose?
>
> Any advice about managing this migration would be much appreciated!
> ___
> Qgis-user mailing list
> Qgis-user@lists.osgeo.org
> List info: https://lists.osgeo.org/mailman/listinfo/qgis-user
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user
>
>
___
Qgis-user mailing list
Qgis-user@lists.osgeo.org
List info: 

[Qgis-user] Label overlapping between layers

2020-08-11 Thread Rossin Pietro
Hello everybody
I'm facing a problem in Qgis 3.14
I have two polygon layers each one with its own labels.

A layer is on top of the other
I would like that the label of the bottom one wil not overlap the top one 
geometry.
Is there any way to achieve this?
I played with label weight but I didn't get success

Thanks
Pietro

AVVISO DI RISERVATEZZA Informazioni riservate possono essere contenute nel 
messaggio o nei suoi allegati. Se non siete i destinatari indicati nel 
messaggio, o responsabili per la sua consegna alla persona, o se avete ricevuto 
il messaggio per errore, siete pregati di non trascriverlo, copiarlo o inviarlo 
ad alcuno. In tal caso vi invitiamo a cancellare il messaggio ed i suoi 
allegati. Grazie.
CONFIDENTIALITY NOTICE Confidential information may be contained in this 
message or in its attachments. If you are not the addressee indicated in this 
message, or responsible for message delivering to that person, or if you have 
received this message in error, you may not transcribe, copy or deliver this 
message to anyone. In that case, you should delete this message and its 
attachments. Thank you.
___
Qgis-user mailing list
Qgis-user@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-user
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user

Re: [Qgis-user] Problem installing QGIS on Ubuntu 20.04 - key authentification

2020-08-11 Thread Richard Duivenvoorde
(not this is NOT related to earlier certificate issue around installing!!)

FYI, I get the same message (running master AND 3.14 on Debian Testing):

../src/core/qgsowsconnection.cpp:85 : (QgsOwsConnection) [0ms] encoded uri: 
'dpiMode=7=https://gibs.earthdata.nasa.gov/wms/epsg4326/best/wms.cgi'.
../src/providers/wms/qgswmscapabilities.cpp:40 : (parseUri) [0ms] uriString = 
dpiMode=7=https://gibs.earthdata.nasa.gov/wms/epsg4326/best/wms.cgi
../src/providers/wms/qgswmscapabilities.cpp:126 : (parseUri) [0ms] mBaseUrl = 
https://gibs.earthdata.nasa.gov/wms/epsg4326/best/wms.cgi?
../src/providers/wms/qgswmscapabilities.cpp:139 : (parseUri) [0ms] Entering: 
layers:, styles:
../src/providers/wms/qgswmscapabilities.cpp:142 : (parseUri) [0ms] Setting 
image encoding to .
../src/providers/wms/qgswmscapabilities.cpp:193 : (parseUri) [0ms] Contextual 
legend: 0
../src/providers/wms/qgswmscapabilities.cpp:2348 : (downloadCapabilities) 
[25ms] entering: forceRefresh=1
../src/providers/wms/qgswmscapabilities.cpp:2357 : (downloadCapabilities) [0ms] 
url = 
https://gibs.earthdata.nasa.gov/wms/epsg4326/best/wms.cgi?SERVICE=WMS=GetCapabilities
../src/core/qgsnetworkaccessmanager.cpp:231 : (createRequest) [0ms] Adding 
trusted CA certs to request
../src/core/qgsnetworkaccessmanager.cpp:112 : (queryProxy) [1ms] using fallback 
proxy for 
https://gibs.earthdata.nasa.gov/wms/epsg4326/best/wms.cgi?SERVICE=WMS=GetCapabilities
../src/core/qgsnetworkaccessmanager.cpp:288 : (createRequest) [0ms] Created 
[reply:55c59ecc2d10]
../src/providers/wms/qgswmscapabilities.cpp:2404 : (capabilitiesReplyProgress) 
[216ms] 0 of 0 bytes of capabilities downloaded.
../src/core/qgsmessagelog.cpp:29 : (logMessage) [0ms] 2020-08-11T16:27:44 
WMS[1] Download of capabilities failed: SSL handshake failed

You can make an issue for this, because it is strange that some versions of Qt 
accept this certificate, and others do not.

Note that if I try to retrieve the capabilities using curl, I also get an error:

$ curl -v 
https://gibs.earthdata.nasa.gov/wms/epsg4326/best/wms.cgi?SERVICE=WMS=GetCapabilities
[1] 443262
[richard@oost ~]$ *   Trying 2001:4d0:241a:442::5:443...
* TCP_NODELAY set
* Connected to gibs.earthdata.nasa.gov (2001:4d0:241a:442::5) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
*   CAfile: /etc/ssl/certs/ca-certificates.crt
  CApath: /etc/ssl/certs
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
* TLSv1.3 (IN), TLS handshake, Server hello (2):
* TLSv1.2 (IN), TLS handshake, Certificate (11):
* TLSv1.2 (IN), TLS handshake, Server key exchange (12):
* TLSv1.2 (OUT), TLS alert, handshake failure (552):
* error:1414D172:SSL routines:tls12_check_peer_sigalg:wrong signature type
* Closing connection 0
curl: (35) error:1414D172:SSL routines:tls12_check_peer_sigalg:wrong signature 
type

So my guess is that there is an certificate error on the WMS-site?

Some version info for those who maybe can figure out this:

$ curl --version
curl 7.68.0 (x86_64-pc-linux-gnu) libcurl/7.68.0 OpenSSL/1.1.1g zlib/1.2.11 
brotli/1.0.7 libidn2/2.3.0 libpsl/0.21.0 (+libidn2/2.3.0) libssh2/1.8.0 
nghttp2/1.41.0 librtmp/2.3
Release-Date: 2020-01-08
Protocols: dict file ftp ftps gopher http https imap imaps ldap ldaps pop3 
pop3s rtmp rtsp scp sftp smb smbs smtp smtps telnet tftp 
Features: AsynchDNS brotli GSS-API HTTP2 HTTPS-proxy IDN IPv6 Kerberos 
Largefile libz NTLM NTLM_WB PSL SPNEGO SSL TLS-SRP UnixSockets


QGIS version
3.15.0-Master
QGIS code revision
68e8e233f5
Compiled against Qt
5.14.2
Running against Qt
5.14.2
Compiled against GDAL/OGR
3.1.2
Running against GDAL/OGR
3.1.2
Compiled against GEOS
3.8.1-CAPI-1.13.3
Running against GEOS
3.8.1-CAPI-1.13.3
Compiled against SQLite
3.32.3
Running against SQLite
3.32.3
PostgreSQL Client Version
12.3 (Debian 12.3-1+b1)
SpatiaLite Version
4.3.0a
QWT Version
6.1.4
QScintilla2 Version
2.11.2
Compiled against PROJ
7.1.0
Running against PROJ
Rel. 7.1.0, August 1st, 2020


Regards,

Richard Duivenvoorde



On 8/11/20 4:21 PM, Andrea Giudiceandrea wrote:
> evaroben wrote
>> gpg: key F7E06F06199EF2F2: 1 Beglaubigung wegen fehlendem Schlüssel nicht
>> geprüft 
>> gpg: Schlüssel F7E06F06199EF2F2: "QGIS Archive Automatic Signing Key 
>> (2020) 
> 
>> qgis-developer@.osgeo
> 
>> " nicht geändert gpg: Anzahl 
>> insgesamt bearbeiteter Schlüssel: 1 gpg:  unverändert: 1"
> 
> Dear Eva,
> "1 Beglaubigung wegen fehlendem Schlüssel nicht geprüft " (="1 signature not
> checked due to a missing key") just means the imported gpg key with id
> F7E06F06199EF2F2 has 1 signature non verifiable. This is not a problem and
> you can ignore it and it does not prevent to correctly import the key into
> the apt keyring. Moreover, the key F7E06F06199EF2F2 is already in your apt
> keyring ("Schlüssel ... nicht geändert", "unverändert: 1"). You can check
> this running "sudo apt-key list F7E06F06199EF2F2".
> 
> Anyway AFAIK this gpg key is only needed for the QGIS 

Re: [Qgis-user] Problem installing QGIS on Ubuntu 20.04 - key authentification

2020-08-11 Thread evaroben

Dear Andrea,

yes, I verified with your Italian address, and it works. I somehow 
thought that the SSL failure had something to do with the keys not being 
deemed trustworthy.
And yes, I use QGIS version 3.14.1, and Ubuntu 20.04. So it's the 
combination of two brand new versions that creates the problem?


Being a complete newbie to QGIS, I found it quite disheartening not to 
be able to install and use the system properly...


Thanks a lot for your explanations!

Eva


Am 11.08.2020 16:21 schrieb Andrea Giudiceandrea:

evaroben wrote
gpg: key F7E06F06199EF2F2: 1 Beglaubigung wegen fehlendem Schlüssel 
nicht

geprüft
gpg: Schlüssel F7E06F06199EF2F2: "QGIS Archive Automatic Signing Key
(2020) 



qgis-developer@.osgeo



" nicht geändert gpg: Anzahl
insgesamt bearbeiteter Schlüssel: 1 gpg:  unverändert: 1"


Dear Eva,
"1 Beglaubigung wegen fehlendem Schlüssel nicht geprüft " (="1 
signature not

checked due to a missing key") just means the imported gpg key with id
F7E06F06199EF2F2 has 1 signature non verifiable. This is not a problem 
and
you can ignore it and it does not prevent to correctly import the key 
into
the apt keyring. Moreover, the key F7E06F06199EF2F2 is already in your 
apt
keyring ("Schlüssel ... nicht geändert", "unverändert: 1"). You can 
check

this running "sudo apt-key list F7E06F06199EF2F2".

Anyway AFAIK this gpg key is only needed for the QGIS installation and
update process and is not related with your SSL protocol connection 
error.


Which QGIS version are you using? I suppose 3.14.1, isn't it?

I can connect to the WMS sever at
https://gibs.earthdata.nasa.gov/wms/epsg4326/best/wms.cgi using:
QGIS 3.14.0 on Windows 10
QGIS 3.14.1 on Ubuntu 18.04
QGIS 3.12.3 (Flatpak) on Ubuntu 20.04

but I cannot connect to the WMS sever using QGIS 3.14.0 on Ubuntu 20.04 
as

you reported:

WMS PROVIDER
Failed to download capabilities:
Download of capabilities failed: SSL handshake failed


Instead i can connect to other WMS servers using https (e.g.
https://wms.cartografia.agenziaentrate.gov.it/inspire/wms/ows01.php) 
with

QGIS 3.14.0 on Ubuntu 20.04.

Could you please check if you can connect to other WMS servers using 
https
(e.g. 
https://wms.cartografia.agenziaentrate.gov.it/inspire/wms/ows01.php)?


It's probably worth reporting the bug on the qgis-developer ml or on 
GitHub

if other user can check if they can or cannot use that WMS server at
https://gibs.earthdata.nasa.gov/wms/epsg4326/best/wms.cgi.

Regards.

Andrea Giudiceandrea



--
Sent from: http://osgeo-org.1560.x6.nabble.com/QGIS-User-f4125267.html
___
Qgis-user mailing list
Qgis-user@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-user
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user

___
Qgis-user mailing list
Qgis-user@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-user
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user

Re: [Qgis-user] Migrating legacy QGIS instance

2020-08-11 Thread Charles Dixon-Paver
Regarding the one-vs-many approach to gpkgs, I recommend consolidation
(within reason). I feel that the temptation to use gpkg as a drop-in
replacement for shp is familiarity with processes I personally consider to
be largely outmoded. I think it's worth getting over the initial
(relatively shallow) learning curve so that when you start working with db
oriented systems like PostGIS, everything makes sense right out of the gate.

Basically it boils down to how you want to manage or distribute them as you
don't have traditional db roles. Personally, I try to package things into
"data.gpkg/something" and "data.gpkg/somethingelse" wherever possible,
rather than "a.gpkg/a" and "b.gpkg/b". It usually makes moving data around
easier for me. If you have a lot of inputs, maybe split it into unique
gpkgs based on some categorising criteria (like you might do with a schema)
rather than one monolithic gpkg. Performing maintenance (vacuum) on a large
number of unique gpkgs seems like an unnecessary chore.

One limitation for gpkg is that certain processing tools/ configurations
will only support writing to an entire gpkg, so if you lack experience
you'll need to be careful not to overwrite all of your data and also have a
decent backup plan in place. Usually you can get away with utilising a
scratch.gpkg for that purpose with no risk to your primary datastore.

Using the one-per-item feature offers little data management benefit from
shapefiles aside from removing the auxiliary files and being able to store
styles (as well as lae). There is little performance benefit over shp
directly from what I understand (both use WKB), but there is ~5MB of
storage overhead for each unique gpkg (if I remember correctly), but this
will depend on your use case.

Hope that helps.

On Tue, 11 Aug 2020 at 15:13, Basques, Bob (CI-StPaul) <
bob.basq...@ci.stpaul.mn.us> wrote:

> *Depending on your end goal, you might be more suited to leaving things as
> they are and using  some sort of content explorer to organize the existing
> data.  Then worry about migrating to different formats as needed.*
>
>
>
> *We’ve been using GeoMoose for this purpose.  It can connect to just about
> any data source on the back end, such as SHP, Postgres, and GeoPackage to
> name a few, but also can connect to proprietary services as well.  Because
> it can use Mapserver as a display engine and data query tool, it lends
> itself to online exploration of the data without the need for a full blown
> GIS tool.  This allows for wide spread use by non-GIS pros.  The datasets
> can still be managed by you with QGIS and/or in Postgres/postgis, or
> whatever you prefer for that purpose.  The Mapserver setup allow for
> connecting to just about any type of service behind the scenes, and with
> the right configuration, you can also enable each dataset in the GeoMoose
> catalog as a WMS/WFS data source, thee standard for open data format access
> and publishing.*
>
>
>
> *Bobb*
>
>
>
>
>
>
>
> *From:* Qgis-user  * On Behalf Of *Walt
> Ludwick
> *Sent:* Tuesday, August 11, 2020 7:45 AM
> *To:* qgis-user@lists.osgeo.org
> *Subject:* Re: [Qgis-user] Migrating legacy QGIS instance
>
>
>
> *Think Before You Click: *This email originated *outside *our
> organization.
>
>
>
> I'm on MacOS -and not so very comfortable with command line scripting- so
> it looks like i might have to go the drag way to import these .shp
> files. Will take some time, but at least that way i can be sure about what
> i've put where, and in what form.
>
>
>
> But i do wonder about the (a) "stick multiple shps into a single gpkg" OR
> (b) "create one per feature" decision, since i'm not experienced enough to
> have a clear preference about this.  Can you say anything about pros & cons
> of going one way vs the other?
>
>
>
>
>
> On Tue, Aug 11, 2020 at 11:45 AM Charles Dixon-Paver 
> wrote:
>
> Easiest way for me is to use the GDAL ogr2ogr
>  command using a bash script or
> cmd batch to traverse your directories (depending on how you installed QGIS
> this should be on your path). I don't know what environment you're running
> though.
>
>
>
> You can either stick multiple shps into a single gpkg or create one per
> feature as you prefer. ogr2ogr can also push shp files directly into
> PostGIS. When you want to consolidate or migrate data (between gpkgs or
> from gpkg to PostGIS) you can simply select the feature layers you want and
> use drag and drop from the QGIS 3 Browser panel to copy multiple features
> to a target location.
>
>
>
> Others might have different approaches though.
>
>
>
> Regards
>
>
>
> On Tue, 11 Aug 2020 at 12:24, Walt Ludwick  wrote:
>
> I've inherited a legacy GIS, built up over some years in versions 2.x,
> that i'm now responsible to maintain.  Being an almost complete n00b (did
> take a short course in QGIS a good few years ago, but still..), i could
> really use some advice about migration.
>
> i've created a new QGIS instance in 

Re: [Qgis-user] Migrating legacy QGIS instance

2020-08-11 Thread Nicolas Cadieux
Hi,

People are suggesting that ogr2ogr would work.  That will work with data but 
NOT with the QGIS projects.  QGIS projects calls various data files in various 
directories,  if you change the name of a file, the file type, the file 
directory structure, the project files will indicate that x number of files 
cannot be found...  The project file contains all the Published maps. 

While most vector data file will be easy to find because of known formats, it 
will be harder to travers the hard drive for the raster data as formats are 
similar (like tiff, jpg...) If vector data is stored in .csv or .txt... you 
will have the same trouble identifying just the spatial data from the rest.

I hope your user had structure and method in his folders. (Method to the 
madness)

One way could be to scan for the project file and see which ones are important 
and still open on the old machine.  Then, you could look for a project packager 
plugin that will save all the needed file in a single directory.  That will 
unfortunately take lots of manual work and lead to file duplications but at 
least, you will save the project files that contain a lot of work. I know of no 
other way to save the project file except to make an exact copy of the hard 
drive.  I usually, at the very least, make a copy of the hard drive as backup 
in case the user comes begging two years down the line for a very special 
project file he can’t find in the new system... 

If all you want is the data, I agree that geopackage and tiff seems like a good 
options.

Good luck! 

Nicolas Cadieux
Ça va bien aller!

> Le 11 août 2020 à 06:24, Walt Ludwick  a écrit :
> 
> 
> I've inherited a legacy GIS, built up over some years in versions 2.x, that 
> i'm now responsible to maintain.  Being an almost complete n00b (did take a 
> short course in QGIS a good few years ago, but still..), i could really use 
> some advice about migration.
> 
> i've created a new QGIS instance in version 3.14, into which i am trying to 
> bring all useful content from our old system: oodles of shapefiles, 
> essentially, plus all those other files (each .shp file appears to bring with 
> it a set of.shx, .dbf, .prj, qpj  files, plus a .cpg file for each layer, it 
> seems).  This is a significant dataset- 14gb, >1000 files -and that is just 
> base data, not counting Projects built on this data or Layouts used for 
> presenting these projects in various ways. Some of this is cruft that i can 
> happily do without, but still:  i've got a lot of porting-over to do, without 
> a clear idea of how best to do it. 
> 
> The one thing i'm clear about is: i want it all in a non-proprietary database 
> (i.e. no more mess of .shp and related files) that is above all quick & easy 
> to navigate & manage. It is a single-user system at this point, but i do aim 
> to open it up to colleagues (off-LAN, i.e. via Internet) as soon as i've 
> developed simple apps for them to use.  No idea how long it'll take me to get 
> there, so...
> 
> Big question at this point is: What should be the new storage format for all 
> this data?  Having read a few related opinions on StackOverflow, i get the 
> sense that GeoPackage will probably make for easiest migration (per this 
> encouraging article, it's a simple matter of drag -simple if you have 
> just a few, i guess! [1]), and can easily support my needs in the short term, 
> but then i wonder: How will i manage migration to PostGIS when i eventually 
> put  this system online with different users/ roles enabled?
> 
> [1] Given that i need to pull in some hundreds of .shp files that are stored 
> in a tree of many folders & subfolders, i also wonder: is there a simple way 
> that i can ask QGIS to traverse a certain directory, pull in all the .shp 
> files -each as its own .gpkg layer, i suppose?
> 
> Any advice about managing this migration would be much appreciated!
> ___
> Qgis-user mailing list
> Qgis-user@lists.osgeo.org
> List info: https://lists.osgeo.org/mailman/listinfo/qgis-user
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user
___
Qgis-user mailing list
Qgis-user@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-user
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user

Re: [Qgis-user] Migrating legacy QGIS instance

2020-08-11 Thread Basques, Bob (CI-StPaul)
Depending on your end goal, you might be more suited to leaving things as they 
are and using  some sort of content explorer to organize the existing data.  
Then worry about migrating to different formats as needed.

We’ve been using GeoMoose for this purpose.  It can connect to just about any 
data source on the back end, such as SHP, Postgres, and GeoPackage to name a 
few, but also can connect to proprietary services as well.  Because it can use 
Mapserver as a display engine and data query tool, it lends itself to online 
exploration of the data without the need for a full blown GIS tool.  This 
allows for wide spread use by non-GIS pros.  The datasets can still be managed 
by you with QGIS and/or in Postgres/postgis, or whatever you prefer for that 
purpose.  The Mapserver setup allow for connecting to just about any type of 
service behind the scenes, and with the right configuration, you can also 
enable each dataset in the GeoMoose catalog as a WMS/WFS data source, thee 
standard for open data format access and publishing.

Bobb



From: Qgis-user  On Behalf Of Walt Ludwick
Sent: Tuesday, August 11, 2020 7:45 AM
To: qgis-user@lists.osgeo.org
Subject: Re: [Qgis-user] Migrating legacy QGIS instance

Think Before You Click: This email originated outside our organization.

I'm on MacOS -and not so very comfortable with command line scripting- so it 
looks like i might have to go the drag way to import these .shp files. 
Will take some time, but at least that way i can be sure about what i've put 
where, and in what form.

But i do wonder about the (a) "stick multiple shps into a single gpkg" OR (b) 
"create one per feature" decision, since i'm not experienced enough to have a 
clear preference about this.  Can you say anything about pros & cons of going 
one way vs the other?


On Tue, Aug 11, 2020 at 11:45 AM Charles Dixon-Paver 
mailto:char...@kartoza.com>> wrote:
Easiest way for me is to use the GDAL 
ogr2ogr command using a bash script or 
cmd batch to traverse your directories (depending on how you installed QGIS 
this should be on your path). I don't know what environment you're running 
though.

You can either stick multiple shps into a single gpkg or create one per feature 
as you prefer. ogr2ogr can also push shp files directly into PostGIS. When you 
want to consolidate or migrate data (between gpkgs or from gpkg to PostGIS) you 
can simply select the feature layers you want and use drag and drop from the 
QGIS 3 Browser panel to copy multiple features to a target location.

Others might have different approaches though.

Regards

On Tue, 11 Aug 2020 at 12:24, Walt Ludwick 
mailto:w...@valedalama.net>> wrote:
I've inherited a legacy GIS, built up over some years in versions 2.x, that i'm 
now responsible to maintain.  Being an almost complete n00b (did take a short 
course in QGIS a good few years ago, but still..), i could really use some 
advice about migration.

i've created a new QGIS instance in version 3.14, into which i am trying to 
bring all useful content from our old system: oodles of shapefiles, 
essentially, plus all those other files (each .shp file appears to bring with 
it a set of.shx, .dbf, .prj, qpj  files, plus a .cpg file for each layer, it 
seems).  This is a significant dataset- 14gb, >1000 files -and that is just 
base data, not counting Projects built on this data or Layouts used for 
presenting these projects in various ways. Some of this is cruft that i can 
happily do without, but still:  i've got a lot of porting-over to do, without a 
clear idea of how best to do it.

The one thing i'm clear about is: i want it all in a non-proprietary database 
(i.e. no more mess of .shp and related files) that is above all quick & easy to 
navigate & manage. It is a single-user system at this point, but i do aim to 
open it up to colleagues (off-LAN, i.e. via Internet) as soon as i've developed 
simple apps for them to use.  No idea how long it'll take me to get there, so...

Big question at this point is: What should be the new storage format for all 
this data?  Having read a few related opinions on StackOverflow, i get the 
sense that GeoPackage will probably make for easiest migration (per this 
encouraging 
article,
 it's a simple matter of drag -simple if you have just a few, i guess! 
[1]), and can easily support my needs in the short term, but then i wonder: How 
will i manage migration to PostGIS when i eventually put  this system online 
with different users/ roles enabled?

[1] Given that i need to pull in some hundreds of .shp files that are stored in 
a tree of many folders & subfolders, i also wonder: is there a simple way that 
i can ask QGIS to traverse a certain directory, pull in all the .shp files 
-each as its own .gpkg layer, i suppose?

Any advice about managing this migration would be much appreciated!

Re: [Qgis-user] Problem installing QGIS on Ubuntu 20.04 - key authentification

2020-08-11 Thread evaroben

Dear Ben,

thank you so very much for your prompt answer. It made me very hopeful 
when seeing it, and I immediately tried, but unfortunatley to no avail.


That's the reaction of my terminal :

"neisolsayaparizabi@neisolsayaparizabi-N2x0WU:~$ wget -O - 
https://qgis.org/downloads/qgis-2020.gpg.key | gpg --import

--2020-08-11 14:27:17--  https://qgis.org/downloads/qgis-2020.gpg.key
Auflösen des Hostnamens qgis.org (qgis.org) … 104.27.139.220, 
172.67.167.146, 104.27.138.220, ...
Verbindungsaufbau zu qgis.org (qgis.org)|104.27.139.220|:443 … 
verbunden.

HTTP-Anforderung gesendet, auf Antwort wird gewartet … 200 OK
Länge: 1839 (1,8K) [application/pgp-keys]
Wird in »STDOUT« gespeichert.

-   100%[===>]   1,80K  --.-KB/sin 
0s


2020-08-11 14:27:17 (12,4 MB/s) - auf die Standardausgabe geschrieben 
[1839/1839]


gpg: key F7E06F06199EF2F2: 1 Beglaubigung wegen fehlendem Schlüssel 
nicht geprüft
gpg: Schlüssel F7E06F06199EF2F2: Öffentlicher Schlüssel "QGIS Archive 
Automatic Signing Key (2020) " 
importiert

gpg: Anzahl insgesamt bearbeiteter Schlüssel: 1
gpg:   importiert: 1
gpg: keine ultimativ vertrauenswürdigen Schlüssel gefunden"

The system imported one key, but indicated that it did not find any 
ultimately trustworthy keys.


THEN I ran the reminder:

"neisolsayaparizabi@neisolsayaparizabi-N2x0WU:~$ gpg --fingerprint 
F7E06F06199EF2F2

pub   rsa4096 2020-08-08 [SCEA] [verfällt: 2021-08-08]
  3987 7635 093F 2656 0197  11FA F7E0 6F06 199E F2F2
uid[ unbekannt] QGIS Archive Automatic Signing Key (2020) 



neisolsayaparizabi@neisolsayaparizabi-N2x0WU:~$ pub   rsa4096 2020-08-08 
[SCEA] [expires: 2021-08-08]


Der Befehl 'pub' wurde nicht gefunden, meinten Sie:

  Befehl 'dub' aus dem Snap dub (1.18.0)
  Befehl 'hub' aus dem Snap hub (v2.14.1)
  Befehl 'hub' aus dem deb hub (2.7.0~ds1-1)
  Befehl 'puf' aus dem deb puf (1.0.0-7build1)
  Befehl 'pcb' aus dem deb pcb-gtk (1:4.2.2-1)
  Befehl 'pcb' aus dem deb pcb-lesstif (1:4.2.2-1)
  Befehl 'publ' aus dem deb atfs (1.4pl6-14)
  Befehl 'dub' aus dem deb dub (1.19.0-1build2)

Informationen zu neuen Versionen sind mit 'snap info ' zu 
finden.


neisolsayaparizabi@neisolsayaparizabi-N2x0WU:~$   3987 7635 093F 
2656 0197  11FA F7E0 6F06 199E F2F2

3987: Befehl nicht gefunden.
neisolsayaparizabi@neisolsayaparizabi-N2x0WU:~$ uid   [unknown] 
QGIS Archive Automatic Signing Key (2020) 


bash: Syntaxfehler beim unerwarteten Wort »(«
neisolsayaparizabi@neisolsayaparizabi-N2x0WU:~$ ^C
neisolsayaparizabi@neisolsayaparizabi-N2x0WU:~$"

The system did not like the command "pub", and did  not accept the 
brackets.

I also deinstalled a previous key from 2019, doesn't help.

And I deinstalled the manually installed QGIS, and installed it via the 
Ubuntu Software centre, to no avail.


Your explanation that the 2020 key is very recent, so do you think that 
in some days some certificate will be added, and it works?


Best regards, and thank you very much again!

Eva






Am 11.08.2020 13:43 schrieb Ben Hur Pintor:

Hi Eva,

AFAIK, the 2019 keys have recently expired thus a new one was added
fairly recently for 2020 (a few days ago if I'm not mistaken).

The error you're mentioning also happens to me when I try to download
the key from a keyserver and add the key to apt in without manual
fingerprint verification.

When I use the longer method to add the key, that is to verify the key
first and add it afterwards, the error doesn't occur on my machine.

From the QGIS website:
_Get and verify the key_

wget -O - https://qgis.org/downloads/qgis-2020.gpg.key | gpg --import
gpg --fingerprint F7E06F06199EF2F2

pub rsa4096 2020-08-08 [SCEA] [expires: 2021-08-08]
 3987 7635 093F 2656 0197 11FA F7E0 6F06 199E F2F2
uid [unknown] QGIS Archive Automatic Signing Key (2020)


_Add key_

gpg --export --armor F7E06F06199EF2F2 | sudo gpg --no-default-keyring
--keyring gnupg-ring:/etc/apt/trusted.gpg.d/qgis-archive.gpg --import
sudo chmod a+r /etc/apt/trusted.gpg.d/qgis-archive.gpg

What I've noticed is that the TRUST of the new key is [UNKNOWN]
instead of [ULTIMATE] which could be the cause why adding it in one
command fails. I'm not sure as well if this has any repercussions as
to the validity of the keys. Probably they still need to be signed as
trusted since they are new. P.S. I'm not an expert with GPG or keys.

Try to use the longer method for adding the keys and see if it works
for you.

All the best,
Ben Hur

On Tue, Aug 11, 2020 at 6:28 PM  wrote:


Dear QGIS and Ubuntu users,

I installed QGIS on Ubuntu 20.04, and it doesn't really work. I
used the
advice on the QGIS website:
https://qgis.org/en/site/forusers/alldownloads.html#debian-ubuntu
[1]

On the terminal, I have a problem with the QGIS key and keystrings.
When
entering these commands
"wget -qO - https://qgis.org/downloads/qgis-2020.gpg.key [2] | sudo
gpg
--no-default-keyring --keyring
gnupg-ring:/etc/apt/trusted.gpg.d/qgis-archive.gpg --import sudo
chmod

Re: [Qgis-user] Migrating legacy QGIS instance

2020-08-11 Thread Walt Ludwick
I'm on MacOS -and not so very comfortable with command line scripting- so
it looks like i might have to go the drag way to import these .shp
files. Will take some time, but at least that way i can be sure about what
i've put where, and in what form.

But i do wonder about the (a) "stick multiple shps into a single gpkg" OR
(b) "create one per feature" decision, since i'm not experienced enough to
have a clear preference about this.  Can you say anything about pros & cons
of going one way vs the other?


On Tue, Aug 11, 2020 at 11:45 AM Charles Dixon-Paver 
wrote:

> Easiest way for me is to use the GDAL ogr2ogr
>  command using a bash script or
> cmd batch to traverse your directories (depending on how you installed QGIS
> this should be on your path). I don't know what environment you're running
> though.
>
> You can either stick multiple shps into a single gpkg or create one per
> feature as you prefer. ogr2ogr can also push shp files directly into
> PostGIS. When you want to consolidate or migrate data (between gpkgs or
> from gpkg to PostGIS) you can simply select the feature layers you want and
> use drag and drop from the QGIS 3 Browser panel to copy multiple features
> to a target location.
>
> Others might have different approaches though.
>
> Regards
>
> On Tue, 11 Aug 2020 at 12:24, Walt Ludwick  wrote:
>
>> I've inherited a legacy GIS, built up over some years in versions 2.x,
>> that i'm now responsible to maintain.  Being an almost complete n00b (did
>> take a short course in QGIS a good few years ago, but still..), i could
>> really use some advice about migration.
>>
>> i've created a new QGIS instance in version 3.14, into which i am trying
>> to bring all useful content from our old system: oodles of shapefiles,
>> essentially, plus all those other files (each .shp file appears to bring
>> with it a set of.shx, .dbf, .prj, qpj  files, plus a .cpg file for each
>> layer, it seems).  This is a significant dataset- 14gb, >1000 files -and
>> that is just base data, not counting Projects built on this data or Layouts
>> used for presenting these projects in various ways. Some of this is cruft
>> that i can happily do without, but still:  i've got a lot of porting-over
>> to do, without a clear idea of how best to do it.
>>
>> The one thing i'm clear about is: i want it all in a non-proprietary
>> database (i.e. no more mess of .shp and related files) that is above all
>> quick & easy to navigate & manage. It is a single-user system at this
>> point, but i do aim to open it up to colleagues (off-LAN, i.e. via
>> Internet) as soon as i've developed simple apps for them to use.  No idea
>> how long it'll take me to get there, so...
>>
>> Big question at this point is: What should be the new storage format for
>> all this data?  Having read a few related opinions on StackOverflow, i get
>> the sense that GeoPackage will probably make for easiest migration (per this
>> encouraging article
>> ,
>> it's a simple matter of drag -simple if you have just a few, i guess!
>> [1]), and can easily support my needs in the short term, but then i wonder:
>> How will i manage migration to PostGIS when i eventually put  this system
>> online with different users/ roles enabled?
>>
>> [1] Given that i need to pull in some hundreds of .shp files that are
>> stored in a tree of many folders & subfolders, i also wonder: is there a
>> simple way that i can ask QGIS to traverse a certain directory, pull in all
>> the .shp files -each as its own .gpkg layer, i suppose?
>>
>> Any advice about managing this migration would be much appreciated!
>> ___
>> Qgis-user mailing list
>> Qgis-user@lists.osgeo.org
>> List info: https://lists.osgeo.org/mailman/listinfo/qgis-user
>> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user
>
>
___
Qgis-user mailing list
Qgis-user@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-user
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user

Re: [Qgis-user] Migrating legacy QGIS instance

2020-08-11 Thread Walt Ludwick
This is great to hear, Phil & Charles; from what you both say, i gather
that migration to PostGIS will be easy enough, when the time comes for
that... And so i can standardize my new installation on GeoPackage without
concern that i may regret this later.  Thanks for instructing me about
these options!

On Tue, Aug 11, 2020 at 12:26 PM Philip Barlow <
phil...@pembrokeshirecoast.org.uk> wrote:

> OGR is a great option, if you wanted a GUI you could also do it with the
> “export to PostgreSQL” processing tool in batch processing mode (right
> click). Select all the layers and then you can auto fill the fields for
> primary key, geometry column etc.
>
>
>
> Phil
>
>
>
>
>
> *From:* Qgis-user  *On Behalf Of *Charles
> Dixon-Paver
> *Sent:* 11 August 2020 11:45
> *To:* Walt Ludwick 
> *Cc:* qgis-user@lists.osgeo.org
> *Subject:* Re: [Qgis-user] Migrating legacy QGIS instance
>
>
>
> Easiest way for me is to use the GDAL ogr2ogr
>  command using a bash script or
> cmd batch to traverse your directories (depending on how you installed QGIS
> this should be on your path). I don't know what environment you're running
> though.
>
>
>
> You can either stick multiple shps into a single gpkg or create one per
> feature as you prefer. ogr2ogr can also push shp files directly into
> PostGIS. When you want to consolidate or migrate data (between gpkgs or
> from gpkg to PostGIS) you can simply select the feature layers you want and
> use drag and drop from the QGIS 3 Browser panel to copy multiple features
> to a target location.
>
>
>
> Others might have different approaches though.
>
>
>
> Regards
>
>
>
> On Tue, 11 Aug 2020 at 12:24, Walt Ludwick  wrote:
>
> I've inherited a legacy GIS, built up over some years in versions 2.x,
> that i'm now responsible to maintain.  Being an almost complete n00b (did
> take a short course in QGIS a good few years ago, but still..), i could
> really use some advice about migration.
>
> i've created a new QGIS instance in version 3.14, into which i am trying
> to bring all useful content from our old system: oodles of shapefiles,
> essentially, plus all those other files (each .shp file appears to bring
> with it a set of.shx, .dbf, .prj, qpj  files, plus a .cpg file for each
> layer, it seems).  This is a significant dataset- 14gb, >1000 files -and
> that is just base data, not counting Projects built on this data or Layouts
> used for presenting these projects in various ways. Some of this is cruft
> that i can happily do without, but still:  i've got a lot of porting-over
> to do, without a clear idea of how best to do it.
>
> The one thing i'm clear about is: i want it all in a non-proprietary
> database (i.e. no more mess of .shp and related files) that is above all
> quick & easy to navigate & manage. It is a single-user system at this
> point, but i do aim to open it up to colleagues (off-LAN, i.e. via
> Internet) as soon as i've developed simple apps for them to use.  No idea
> how long it'll take me to get there, so...
>
> Big question at this point is: What should be the new storage format for
> all this data?  Having read a few related opinions on StackOverflow, i get
> the sense that GeoPackage will probably make for easiest migration (per this
> encouraging article
> ,
> it's a simple matter of drag -simple if you have just a few, i guess!
> [1]), and can easily support my needs in the short term, but then i wonder:
> How will i manage migration to PostGIS when i eventually put  this system
> online with different users/ roles enabled?
>
>
>
> [1] Given that i need to pull in some hundreds of .shp files that are
> stored in a tree of many folders & subfolders, i also wonder: is there a
> simple way that i can ask QGIS to traverse a certain directory, pull in all
> the .shp files -each as its own .gpkg layer, i suppose?
>
>
>
> Any advice about managing this migration would be much appreciated!
>
> ___
> Qgis-user mailing list
> Qgis-user@lists.osgeo.org
> List info: https://lists.osgeo.org/mailman/listinfo/qgis-user
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user
>
> Mae'r Awdurdod yn hapus i gyfathrebu yn Gymraeg neu yn Saesneg
>
> The Authority is happy to communicate in Welsh or English
> ***
> Website www.pembrokeshirecoast.wales
> Follow us on Twitter 
> Join us on Facebook
> 
> Watch us on Youtube
> 
> Look at us on Flickr 
>
>
> This email and any attached files should only be read by those persons to
> whom
> they are addressed and be used by them only for their intended purpose.
> If you are not the intended 

Re: [Qgis-user] Problem installing QGIS on Ubuntu 20.04 - key authentification

2020-08-11 Thread Ben Hur Pintor
Hi Eva,

AFAIK, the 2019 keys have recently expired thus a new one was added fairly
recently for 2020 (a few days ago if I'm not mistaken).

The error you're mentioning also happens to me when I try to download the
key from a keyserver and add the key to apt in without manual fingerprint
verification.

When I use the longer method to add the key, that is to verify the key
first and add it afterwards, the error doesn't occur on my machine.

>From the QGIS website:
*Get and verify the key*

wget -O - https://qgis.org/downloads/qgis-2020.gpg.key | gpg
--importgpg --fingerprint F7E06F06199EF2F2

pub   rsa4096 2020-08-08 [SCEA] [expires: 2021-08-08]
  3987 7635 093F 2656 0197  11FA F7E0 6F06 199E F2F2uid
[unknown] QGIS Archive Automatic Signing Key (2020)



*Add key*

gpg --export --armor F7E06F06199EF2F2 | sudo gpg --no-default-keyring
--keyring gnupg-ring:/etc/apt/trusted.gpg.d/qgis-archive.gpg
--importsudo chmod a+r /etc/apt/trusted.gpg.d/qgis-archive.gpg


What I've noticed is that the *trust* of the new key is *[unknown]* instead
of *[ultimate]* which could be the cause why adding it in one command
fails. I'm not sure as well if this has any repercussions as to the
validity of the keys. Probably they still need to be signed as trusted
since they are new. P.S. I'm not an expert with GPG or keys.

Try to use the longer method for adding the keys and see if it works for
you.


All the best,
Ben Hur

On Tue, Aug 11, 2020 at 6:28 PM  wrote:

> Dear QGIS and Ubuntu users,
>
> I installed QGIS on Ubuntu 20.04, and it doesn't really work. I used the
> advice on the QGIS website:
> https://qgis.org/en/site/forusers/alldownloads.html#debian-ubuntu
>
> On the terminal, I have a problem with the QGIS key and keystrings. When
> entering these commands
> "wget -qO - https://qgis.org/downloads/qgis-2020.gpg.key | sudo gpg
> --no-default-keyring --keyring
> gnupg-ring:/etc/apt/trusted.gpg.d/qgis-archive.gpg --import sudo chmod
> a+r /etc/apt/trusted.gpg.d/qgis-archive.gpg"
>   the system tells me:
>
> "neisolsayaparizabi@neisolsayaparizabi-N2x0WU:~$ wget -qO -
> https://qgis.org/downloads/qgis-2020.gpg.key | sudo gpg
> --no-default-keyring --keyring
> gnupg-ring:/etc/apt/trusted.gpg.d/qgis-archive.gpg --import gpg: key
> F7E06F06199EF2F2: 1 Beglaubigung wegen fehlendem Schlüssel nicht geprüft
> gpg: Schlüssel F7E06F06199EF2F2: "QGIS Archive Automatic Signing Key
> (2020) " nicht geändert gpg: Anzahl
> insgesamt bearbeiteter Schlüssel: 1 gpg:  unverändert: 1"
>
> You can see that my sytem is in German. It means something like: key
> F7E06F06199EF2F2: 1 authentification not verified because of missing
> key. When looking at the list of authentifications, the key in question
> is there:
>
> (screenshot attached)
>
> What can be the problem? QGIS is installed, but when wanting to connect
> to a map server, it indicates that this is not possible due to an error
> in the SSL protocol. I want to use the GIS data from this site:
>
> https://wiki.earthdata.nasa.gov/display/GIBS/Geographic+Information+System+%28GIS%29+Usage#expand-QGIS
>
> Thanks a lot for helping me!
>
> Eva___
> Qgis-user mailing list
> Qgis-user@lists.osgeo.org
> List info: https://lists.osgeo.org/mailman/listinfo/qgis-user
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user



-- 
---
*Ben Hur S. Pintor*
bnhr.xyz
h...@bnhr.xyz


open spatial & data solutions
___
Qgis-user mailing list
Qgis-user@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-user
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user

Re: [Qgis-user] Migrating legacy QGIS instance

2020-08-11 Thread Philip Barlow
OGR is a great option, if you wanted a GUI you could also do it with the 
“export to PostgreSQL” processing tool in batch processing mode (right click). 
Select all the layers and then you can auto fill the fields for primary key, 
geometry column etc.

Phil


From: Qgis-user  On Behalf Of Charles 
Dixon-Paver
Sent: 11 August 2020 11:45
To: Walt Ludwick 
Cc: qgis-user@lists.osgeo.org
Subject: Re: [Qgis-user] Migrating legacy QGIS instance

Easiest way for me is to use the GDAL 
ogr2ogr command using a bash script or 
cmd batch to traverse your directories (depending on how you installed QGIS 
this should be on your path). I don't know what environment you're running 
though.

You can either stick multiple shps into a single gpkg or create one per feature 
as you prefer. ogr2ogr can also push shp files directly into PostGIS. When you 
want to consolidate or migrate data (between gpkgs or from gpkg to PostGIS) you 
can simply select the feature layers you want and use drag and drop from the 
QGIS 3 Browser panel to copy multiple features to a target location.

Others might have different approaches though.

Regards

On Tue, 11 Aug 2020 at 12:24, Walt Ludwick 
mailto:w...@valedalama.net>> wrote:
I've inherited a legacy GIS, built up over some years in versions 2.x, that i'm 
now responsible to maintain.  Being an almost complete n00b (did take a short 
course in QGIS a good few years ago, but still..), i could really use some 
advice about migration.

i've created a new QGIS instance in version 3.14, into which i am trying to 
bring all useful content from our old system: oodles of shapefiles, 
essentially, plus all those other files (each .shp file appears to bring with 
it a set of.shx, .dbf, .prj, qpj  files, plus a .cpg file for each layer, it 
seems).  This is a significant dataset- 14gb, >1000 files -and that is just 
base data, not counting Projects built on this data or Layouts used for 
presenting these projects in various ways. Some of this is cruft that i can 
happily do without, but still:  i've got a lot of porting-over to do, without a 
clear idea of how best to do it.

The one thing i'm clear about is: i want it all in a non-proprietary database 
(i.e. no more mess of .shp and related files) that is above all quick & easy to 
navigate & manage. It is a single-user system at this point, but i do aim to 
open it up to colleagues (off-LAN, i.e. via Internet) as soon as i've developed 
simple apps for them to use.  No idea how long it'll take me to get there, so...

Big question at this point is: What should be the new storage format for all 
this data?  Having read a few related opinions on StackOverflow, i get the 
sense that GeoPackage will probably make for easiest migration (per this 
encouraging 
article,
 it's a simple matter of drag -simple if you have just a few, i guess! 
[1]), and can easily support my needs in the short term, but then i wonder: How 
will i manage migration to PostGIS when i eventually put  this system online 
with different users/ roles enabled?

[1] Given that i need to pull in some hundreds of .shp files that are stored in 
a tree of many folders & subfolders, i also wonder: is there a simple way that 
i can ask QGIS to traverse a certain directory, pull in all the .shp files 
-each as its own .gpkg layer, i suppose?

Any advice about managing this migration would be much appreciated!
___
Qgis-user mailing list
Qgis-user@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-user
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user

Mae'r Awdurdod yn hapus i gyfathrebu yn Gymraeg neu yn Saesneg

The Authority is happy to communicate in Welsh or English


*** 
Website www.pembrokeshirecoast.wales
Follow us on Twitter 
Join us on Facebook
Watch us on Youtube 
Look at us on Flickr


This email and any attached files should only be read by those persons to whom
they are addressed and be used by them only for their intended purpose.
If you are not the intended recipient please destroy all copies and inform the
sender by return email.

Please note that the contents of this email may be subject to public disclosure 
under the Freedom of Information Act 2000 and therefore the confidentiality of 
this message and any reply cannot be guaranteed.

Click here to view PCNPA Privacy Notice � Keeping your Information Safe

For further information on the PCNPA please visit our website at 
www.pembrokeshirecoast.wales

Please consider the environment before printing this email.

Dim ond y personau hynny yr anfonwyd yr e-bost hwn atynt ac unrhyw ffeiliau 
sydd 
ynghlwm ddylid eu darllen, a dim ond hwy ddylid eu defnyddio at y diben y 
bwriadwyd hwy. 
Os nad y chi yw'r person y 

Re: [Qgis-user] Migrating legacy QGIS instance

2020-08-11 Thread Charles Dixon-Paver
Easiest way for me is to use the GDAL ogr2ogr
 command using a bash script or cmd
batch to traverse your directories (depending on how you installed QGIS
this should be on your path). I don't know what environment you're running
though.

You can either stick multiple shps into a single gpkg or create one per
feature as you prefer. ogr2ogr can also push shp files directly into
PostGIS. When you want to consolidate or migrate data (between gpkgs or
from gpkg to PostGIS) you can simply select the feature layers you want and
use drag and drop from the QGIS 3 Browser panel to copy multiple features
to a target location.

Others might have different approaches though.

Regards

On Tue, 11 Aug 2020 at 12:24, Walt Ludwick  wrote:

> I've inherited a legacy GIS, built up over some years in versions 2.x,
> that i'm now responsible to maintain.  Being an almost complete n00b (did
> take a short course in QGIS a good few years ago, but still..), i could
> really use some advice about migration.
>
> i've created a new QGIS instance in version 3.14, into which i am trying
> to bring all useful content from our old system: oodles of shapefiles,
> essentially, plus all those other files (each .shp file appears to bring
> with it a set of.shx, .dbf, .prj, qpj  files, plus a .cpg file for each
> layer, it seems).  This is a significant dataset- 14gb, >1000 files -and
> that is just base data, not counting Projects built on this data or Layouts
> used for presenting these projects in various ways. Some of this is cruft
> that i can happily do without, but still:  i've got a lot of porting-over
> to do, without a clear idea of how best to do it.
>
> The one thing i'm clear about is: i want it all in a non-proprietary
> database (i.e. no more mess of .shp and related files) that is above all
> quick & easy to navigate & manage. It is a single-user system at this
> point, but i do aim to open it up to colleagues (off-LAN, i.e. via
> Internet) as soon as i've developed simple apps for them to use.  No idea
> how long it'll take me to get there, so...
>
> Big question at this point is: What should be the new storage format for
> all this data?  Having read a few related opinions on StackOverflow, i get
> the sense that GeoPackage will probably make for easiest migration (per this
> encouraging article
> ,
> it's a simple matter of drag -simple if you have just a few, i guess!
> [1]), and can easily support my needs in the short term, but then i wonder:
> How will i manage migration to PostGIS when i eventually put  this system
> online with different users/ roles enabled?
>
> [1] Given that i need to pull in some hundreds of .shp files that are
> stored in a tree of many folders & subfolders, i also wonder: is there a
> simple way that i can ask QGIS to traverse a certain directory, pull in all
> the .shp files -each as its own .gpkg layer, i suppose?
>
> Any advice about managing this migration would be much appreciated!
> ___
> Qgis-user mailing list
> Qgis-user@lists.osgeo.org
> List info: https://lists.osgeo.org/mailman/listinfo/qgis-user
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user
___
Qgis-user mailing list
Qgis-user@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-user
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user

[Qgis-user] Problem installing QGIS on Ubuntu 20.04 - key authentification

2020-08-11 Thread evaroben

Dear QGIS and Ubuntu users,

I installed QGIS on Ubuntu 20.04, and it doesn't really work. I used the 
advice on the QGIS website: 
https://qgis.org/en/site/forusers/alldownloads.html#debian-ubuntu


On the terminal, I have a problem with the QGIS key and keystrings. When 
entering these commands
"wget -qO - https://qgis.org/downloads/qgis-2020.gpg.key | sudo gpg 
--no-default-keyring --keyring 
gnupg-ring:/etc/apt/trusted.gpg.d/qgis-archive.gpg --import sudo chmod 
a+r /etc/apt/trusted.gpg.d/qgis-archive.gpg"

 the system tells me:

"neisolsayaparizabi@neisolsayaparizabi-N2x0WU:~$ wget -qO - 
https://qgis.org/downloads/qgis-2020.gpg.key | sudo gpg 
--no-default-keyring --keyring 
gnupg-ring:/etc/apt/trusted.gpg.d/qgis-archive.gpg --import gpg: key 
F7E06F06199EF2F2: 1 Beglaubigung wegen fehlendem Schlüssel nicht geprüft 
gpg: Schlüssel F7E06F06199EF2F2: "QGIS Archive Automatic Signing Key 
(2020) " nicht geändert gpg: Anzahl 
insgesamt bearbeiteter Schlüssel: 1 gpg:  unverändert: 1"


You can see that my sytem is in German. It means something like: key 
F7E06F06199EF2F2: 1 authentification not verified because of missing 
key. When looking at the list of authentifications, the key in question 
is there:


(screenshot attached)

What can be the problem? QGIS is installed, but when wanting to connect 
to a map server, it indicates that this is not possible due to an error 
in the SSL protocol. I want to use the GIS data from this site:

https://wiki.earthdata.nasa.gov/display/GIBS/Geographic+Information+System+%28GIS%29+Usage#expand-QGIS

Thanks a lot for helping me!

Eva___
Qgis-user mailing list
Qgis-user@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-user
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user

[Qgis-user] Migrating legacy QGIS instance

2020-08-11 Thread Walt Ludwick
I've inherited a legacy GIS, built up over some years in versions 2.x, that
i'm now responsible to maintain.  Being an almost complete n00b (did take a
short course in QGIS a good few years ago, but still..), i could really use
some advice about migration.

i've created a new QGIS instance in version 3.14, into which i am trying to
bring all useful content from our old system: oodles of shapefiles,
essentially, plus all those other files (each .shp file appears to bring
with it a set of.shx, .dbf, .prj, qpj  files, plus a .cpg file for each
layer, it seems).  This is a significant dataset- 14gb, >1000 files -and
that is just base data, not counting Projects built on this data or Layouts
used for presenting these projects in various ways. Some of this is cruft
that i can happily do without, but still:  i've got a lot of porting-over
to do, without a clear idea of how best to do it.

The one thing i'm clear about is: i want it all in a non-proprietary
database (i.e. no more mess of .shp and related files) that is above all
quick & easy to navigate & manage. It is a single-user system at this
point, but i do aim to open it up to colleagues (off-LAN, i.e. via
Internet) as soon as i've developed simple apps for them to use.  No idea
how long it'll take me to get there, so...

Big question at this point is: What should be the new storage format for
all this data?  Having read a few related opinions on StackOverflow, i get
the sense that GeoPackage will probably make for easiest migration (per this
encouraging article
,
it's a simple matter of drag -simple if you have just a few, i guess!
[1]), and can easily support my needs in the short term, but then i wonder:
How will i manage migration to PostGIS when i eventually put  this system
online with different users/ roles enabled?

[1] Given that i need to pull in some hundreds of .shp files that are
stored in a tree of many folders & subfolders, i also wonder: is there a
simple way that i can ask QGIS to traverse a certain directory, pull in all
the .shp files -each as its own .gpkg layer, i suppose?

Any advice about managing this migration would be much appreciated!
___
Qgis-user mailing list
Qgis-user@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-user
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user

[Qgis-user] Print composer: legend in multiple pages?

2020-08-11 Thread Luca Manganelli
Hello,

if I have a legend with many entries, it is possible to distribute it in
multiple pages in Print Composer?
___
Qgis-user mailing list
Qgis-user@lists.osgeo.org
List info: https://lists.osgeo.org/mailman/listinfo/qgis-user
Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user