[Qgis-user] Migrating legacy QGIS instance

Wed Aug 12 09:59:45 PDT 2020

Hi,

QPackage would help. "Qpackage is a tool to save both your QGIS project 
and data contained in the project to a new directory."

Nicolas

On 2020-08-11 1:34 p.m., Walt Ludwick wrote:
> 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 
> <njacadieux.gitlab at gmail.com <mailto:njacadieux.gitlab at gmail.com>> 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 <walt at valedalama.net
>>     <mailto:walt at valedalama.net>> 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
>>     <https://medium.com/@GispoFinland/learn-spatial-sql-and-master-geopackage-with-qgis-3-16b1e17f0291>,
>>     it's a simple matter of drag&drop -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 at lists.osgeo.org <mailto:Qgis-user at 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 at lists.osgeo.org
> List info: https://lists.osgeo.org/mailman/listinfo/qgis-user
> Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-user
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/qgis-user/attachments/20200812/04de8baf/attachment.html>