For us (recently ‘power users’ of LGIS) could be the following of big interest: is there a way NOT to name every database as ‘project.db’ (which is stored in a specifically named path) instead of giving it an own specific name (e.g. like in QGIS)? Handling tons of project.db’s is annoying and error prone sometimes…
I see. We already talked about renaming - so definitely planned idea.
Good to know!
Regarding the discussion: we have 15 tablets out in the field for citizen science. All of them with same LGIS project (beaver monitoring in Saxony). Projects are returning to our server by cloud but we have to take care to sort these into several paths… All are involved in QGIS. If we could name them as ‘project1.db’ … ‘project15.de’ thinks would get much easier!
I’m expectant… Sincerely, Jan
Dr. Jan Stegner
Büro für Landschaftsplanung und Naturschutz
Bitterfelder Straße 24
D-04849 Bad Düben
Tel.: 03 42 43-42 40 77
Mobil: 0177-49 77 584
USt-IdNr.: DE 282 365 935
I think that there are two solutions - to generate the name of db file based on name of project or enable to users to define custom name. I would vote for the first option but the question what will be possible
I’d like to inform that idea is implemented. From the next version will be project database named based on project. After rename of project, database file will be renamed as well.
The new version do not influence the name of already existed project DB.
Works great in ver 0.11.1! Even subsequent name change by 3rd party file admin is possible. Definitely helpful now when several guys are running same database (like we do in citizen science).