Ok, these are questions with a bit of meat :) > So I have no understanding of the usage of the database i.e. what goes > into the database (a new database for every project or only new > records for a project?) and how to close and reopen a project from the > database.
Database: The idea of the database is to have several projects in a folder structure. It's more or less the same as folders on your system with gpx or qms files. However the big advantage of the database is that items are linked to folders. Therefore you can have a group folder (blue) with all your hikes in project folders (green) each. Additionally you have a green folder "summary" that contains all tracks from the other green folders, too. As the tracks are just referenced by the folders you do not have to store each track twice as you would have with real files. Another advantage is that can can load just a few items of a project into the workspace. With a file you always have to load everything in the file. You can have several databases. I personally use only one. But other users have a database for planning data and one for recorded data. It's up to your taste. The items in one database are of course separated from another. Thus if you copy an item between two databases you will create a real copy. In the database view a project folder has a checkbox. By checking it the project folder is loaded into the workspace. Additionally you can use checkboxes at the items to load those on a per item base. > Will the tracks be stored or only references? Will the used map be > stored or only references etc. If only references are stored a > different/additional storeage is needed. All items (tracks, waypoints, routes, areas) are stored once on the database and are referenced by folders. QMapShack will ask you when creating a new reference to an item of you want to create a clone rather than just a new reference. The database will not reference gpx or qms files on your hard drive. > > For example, I have 2 recorded tracks, which should be kept as a > (named) project for archiving purpose. The structure of the database is totally up to you. Blue folders are used to group green or orange folders. Green folders are the project folders, just like gpx or qms files. The orange ones are the same. But the intended use is to store them in a green folder with additional data that is not of primary interest. I for example have a blue folder for every year. Let's say it's called "hiking 2016". Below that blue folder I have many green ones with the tour names and the recordings. Planning data used to plan the tour is in an orange folder below the green tour folder. But that is just an example. It's up to you how you want to structure your data. HTH Oliver ------------------------------------------------------------------------------ What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic patterns at an interface-level. Reveals which users, apps, and protocols are consuming the most bandwidth. Provides multi-vendor support for NetFlow, J-Flow, sFlow and other flows. Make informed decisions using capacity planning reports.http://sdm.link/zohodev2dev _______________________________________________ Qlandkartegt-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qlandkartegt-users
