Yes Andrea: it is both A&B, ideally. In context of a farm operation, the UseCase is: field worker records observations in field that then update layer(s) as appropriate in QGIS. For this to work well, the user needs to have the Geopackage from QGIS loaded, and then record the observation to the correct layer... But if that's not possible, then the user should at least be able to record observations as features in a layer that could then be exported as a .gpkg file, which could then be imported into QGIS and integrated from desktop after the fact. Dunno if this is consistent w/ design goals of SMASH, but we're looking for the most frictionless flow of geolocated & dateTimestamped observations -text and/or images (both ideally)- from field to QGIS.As to mechanism of data transfer between mobile app & desktop GIS: Dropbox would be an elegant solution, but anything (besides a GSS server, which i don't have and am not eager to acquire) would be better than status quo, from my perspective. Would be happy if i could just save to .gpkg and email the file to myself, for now... That or any other method you might suggest, i would be happy to try! /walt
To view this discussion on the web visit https://groups.google.com/d/msgid/geopaparazzi-users/fd1d0296-208a-4b17-9d34-e6945d23fccbn%40googlegroups.com.
But as to satisfying the aforementioned UseCase: do i understand correctly from this paragraph of SMASH docs that, if i put a .gpkg file there from QGIS, that i should be able to edit attribute tables in that file using SMASH? Without introducing anomalies that QGIS cannot handle? Meaning i can have RTE (Round Trip Editing) of .gpkg files between QGIS and SMASH (albeit via this somewhat frictional files trafficking process)? If i'm reading you and the docs right, that's what it sounds like...
But then the 1st msg in this thread seemed to indicate that there is some incompatibility, so i am wondering about the status of this issue.
Anyway: i will see if i can make the RTE work, soon as i find a way to write files TO the SMASH folder structure from outside the app (since import feature only works via GSS, and since the iOS "Files" app is a read-only browser). If you know of a way to do this, Silvia, i'd love to hear about how that is done!
To view this discussion on the web visit https://groups.google.com/d/msgid/geopaparazzi-users/8920c516-4cbf-4e6d-b7bd-9a1c335aaa98n%40googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/geopaparazzi-users/a7249429-72e0-4aaa-bd29-7433def71fc1n%40googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/geopaparazzi-users/CABCykqJbbZ6nSegUBeSn35w-CAUzsz-cP3z1-nYpTNasTzU4Dg%40mail.gmail.com.
Dear Ludwick,
happy to hear that you did some steps forward! :-)
> Progress! Some, at least. Could not make this procedure work with the "Files" app, but i found a new app- "FE File Explorer" -that did let me save a .gpkg file to the SMASH app (see image 1 attached).
> NB: I have saved that .gpkg file to both /Maps and /Projects, but it seems the Layers tool can only find it in /Projects.
Did you also try to browse the Smash folder using the button at the
bottom of the Layers View?
Regarding the visualization of the gpkg, did you follow the
instruction on our manual for the creation of the package?
There are some rules you have to follow to create a geopackage db
compatible with Smash.
We are now solving some issues regarding the geopackage visualization
and make the creation easier for the users. These new features will be
in the next release which will be released during this or the next
week.
If you can, could you please share with me the gpkg file so we can
test if the new version can load it?
Thanks
Silvia
...
Thanks for the good news, Silvia; i look forward to that next release with great interest... And meanwhile, i will read those instructions that i failed to notice, about how to create a Smash-compatible geopackage.Also i will send you under separate cover the .gpkg file from QGIS that i'm presently working with, so maybe you can tell me some of the cross-compatibility issues that this presents, that i might avoid them in future.As to using the button at bottom of Layers view to browse Smash folder: i have tried, it does let me browse the full Smash directory, but still: when i select the .gpkg in /Maps directory and press save, it does not show up in the comprehensive Layers view, as before.
/waltOn Mon, Sep 21, 2020 at 8:02 AM Silvia Franceschi <silvia.f...@gmail.com> wrote:Dear Ludwick,
happy to hear that you did some steps forward! :-)
> Progress! Some, at least. Could not make this procedure work with the "Files" app, but i found a new app- "FE File Explorer" -that did let me save a .gpkg file to the SMASH app (see image 1 attached).
> NB: I have saved that .gpkg file to both /Maps and /Projects, but it seems the Layers tool can only find it in /Projects.
Did you also try to browse the Smash folder using the button at the
bottom of the Layers View?
Regarding the visualization of the gpkg, did you follow the
instruction on our manual for the creation of the package?
There are some rules you have to follow to create a geopackage db
compatible with Smash.
We are now solving some issues regarding the geopackage visualization
and make the creation easier for the users. These new features will be
in the next release which will be released during this or the next
week.
If you can, could you please share with me the gpkg file so we can
test if the new version can load it?
Thanks
Silvia
...
--
You received this message because you are subscribed to the Google Groups "geopaparazzi-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to geopaparazzi-us...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/geopaparazzi-users/CAPR4Z2mHkKcdcsEo0D0w0cH%3D%2Bwd0Tk92D5jOtV9JNjicS9YNVQ%40mail.gmail.com.
Hi Walt,Thanks for the good news, Silvia; i look forward to that next release with great interest... And meanwhile, i will read those instructions that i failed to notice, about how to create a Smash-compatible geopackage.Also i will send you under separate cover the .gpkg file from QGIS that i'm presently working with, so maybe you can tell me some of the cross-compatibility issues that this presents, that i might avoid them in future.As to using the button at bottom of Layers view to browse Smash folder: i have tried, it does let me browse the full Smash directory, but still: when i select the .gpkg in /Maps directory and press save, it does not show up in the comprehensive Layers view, as before.just know that to make SMASH aware of your format (at least partially), today I have not been able to make the new release of SMASH :-)))))I should be able within this week.The problems with your geopackage is that the table names and column names contain special characters. While I had some protection for names starting with numbers, containing dashes and/or spaces, I had not thought that names might contain commas.And for sure I wasn't aware that column names were allowed to have the same issue.So we worked to make the system more flexible to be able to more easily fix issues that might come up in future.The solution is:a) wait for the upcoming release, I have been able to view your data in the upcoming version of SMASHb) change the names of tables and columns. In the current version in the store table names can't have commas and column names can't have any fuss (so no starting number, no spaces, no comma).Hope that helps for now. Thanks for this challenging exercise, I am sure it made the geopackage handling a bit better. :-)Cheers,Andrea
...
Thanks for the nuanced explanation, Andrea; this helps.
Of course it would be great if future version(s) can pre-empt any anomalies that users might introduce in their naming of tables & columns, but meanwhile we users do best to avoid bad practice. Including spaces in names of tables or columns is of course bad practice, as is the inclusion of commas in column names (which must be prepared for export in CSV form), so i don't do either of these things as a rule. But this particular case involves a GIS that i've inherited from a colleague, who didn't observe the same conventions as me, i now see; this is a BIG database (what i sent you is just one small part of it), so data conversion will take me some time.Meanwhile: i will certainly avoid those problematic names going forward, and will watch this space for news of the new release.
On Monday, September 21, 2020 at 3:24:44 PM UTC+1 moovida wrote:Hi Walt,Thanks for the good news, Silvia; i look forward to that next release with great interest... And meanwhile, i will read those instructions that i failed to notice, about how to create a Smash-compatible geopackage.Also i will send you under separate cover the .gpkg file from QGIS that i'm presently working with, so maybe you can tell me some of the cross-compatibility issues that this presents, that i might avoid them in future.As to using the button at bottom of Layers view to browse Smash folder: i have tried, it does let me browse the full Smash directory, but still: when i select the .gpkg in /Maps directory and press save, it does not show up in the comprehensive Layers view, as before.just know that to make SMASH aware of your format (at least partially), today I have not been able to make the new release of SMASH :-)))))I should be able within this week.The problems with your geopackage is that the table names and column names contain special characters. While I had some protection for names starting with numbers, containing dashes and/or spaces, I had not thought that names might contain commas.And for sure I wasn't aware that column names were allowed to have the same issue.So we worked to make the system more flexible to be able to more easily fix issues that might come up in future.The solution is:a) wait for the upcoming release, I have been able to view your data in the upcoming version of SMASHb) change the names of tables and columns. In the current version in the store table names can't have commas and column names can't have any fuss (so no starting number, no spaces, no comma).Hope that helps for now. Thanks for this challenging exercise, I am sure it made the geopackage handling a bit better. :-)Cheers,Andrea...
--
You received this message because you are subscribed to the Google Groups "geopaparazzi-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to geopaparazzi-us...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/geopaparazzi-users/9e98e0e4-836c-40c6-a0be-7884066cc84bn%40googlegroups.com.