You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi @NathanW2 ,
Jamie MacKinney from Bayside here, hope you're well. I was looking to get your thoughts on the best path for use of Roam now that we have gone over to GDA2020 as our standard datum. We had been using Roam 2.7.1, which incorporated your custom code to correctly put dates of new/edited features into the database.
It seemed to me we had two options:
If there was a version 2.x of qgis that will support GDA2020, we could use roam 2.7.1 with the QGIS 2.x version installed on the server; or
install roam version 3, which I believe would allow use of a GDA2020/QGIS v3.x workspace, which would be saved on the server. (We are currently running QGIS 3.10 as our standard QGIS version corporately).
I was wondering if you would have suggestion as to best path to take? I wasn't quite sure whether Roam 3.x was at a stage to go into production, or if it was still in development phase?
Thanks
Jamie
The text was updated successfully, but these errors were encountered:
It supports GDA2020 and we have used it with a few of our customers in production environments. Bear in mind that Roam v3 has been tested with specific customer environments who have specific data collection workflows, so it would be a good idea to test it before you put it into production.
As you mentioned, you would need to use QGIS v3 to upgrade and deploy new projects to this later Roam release.
It supports GDA2020 and we have used it with a few of our customers in production environments. Bear in mind that Roam v3 has been tested with specific customer environments who have specific data collection workflows, so it would be a good idea to test it before you put it into production.
As you mentioned, you would need to use QGIS v3 to upgrade and deploy new projects to this later Roam release.
Matt
Chartis Technology
Thanks very much for that @robbochartis , that gives us a good way forward. We'll test and report back any problems. Thanks again
Hi @NathanW2 ,
Jamie MacKinney from Bayside here, hope you're well. I was looking to get your thoughts on the best path for use of Roam now that we have gone over to GDA2020 as our standard datum. We had been using Roam 2.7.1, which incorporated your custom code to correctly put dates of new/edited features into the database.
It seemed to me we had two options:
I was wondering if you would have suggestion as to best path to take? I wasn't quite sure whether Roam 3.x was at a stage to go into production, or if it was still in development phase?
Thanks
Jamie
The text was updated successfully, but these errors were encountered: