Hi Basav, Ultimately, this is a question of what is the best way to automatically import data into Arches. You'll need some extra programming, whatever route you take.
The most reliable way to import records into an existing Arches database is through use of the .arches/.relations file pair. You can find documentation on these files here: http://arches3.readthedocs.io/en/latest/arches-data/#from-arches. It is a CSV file, with one row per new attribute--in other words, if you are adding a new resource to the database with a name and a location, that would be two lines, one for the name, one for the location geometry. The relations file allows you to make resource-to-resource relationships between the resources you are uploading. With that in mind, and given that you'll need to do a little bit of intermediate work to prepare the data for import, I'd say that any app that allows you to export your records to an easy-to-access format will be as good as any other. You'll then have to write something to take that output table and convert it to .arches, and use the arches import function. Arches does have a built-in shapefile import, which would be the way to go if you were using QGIS, but it does not correctly group attributes. A while ago I did some work on a ArcGIS-based conversion toolbox <https://github.com/mradamcox/arc2arches>, which may be useful to you. Hopefully that helps you out a bit... Adam On Saturday, October 1, 2016 at 7:08:05 AM UTC-5, Basav Biradar wrote: > > Hi Dennis, > > Thank you for the quick response. I am very glad to learn about the plan > for an Android and iOS app for Arches. First half of next year might just > work for us. > > But as of today, which app would you recommend for us to use? We were > considering Qgis, ArcGis Collector since their output is GIS friendly - our > assumption is it would be not too difficult to integrate with Arches > databases. Can you please give feedback on this assumption? > > Thanks again, > Basav > > > > > > > On Friday, 30 September 2016 23:14:50 UTC+5:30, Dennis Wuthrich wrote: >> >> Hi Basav, >> >> Thanks for considering Arches for your heritage management system. >> >> The Arches team is already planning on developing an Android and IOS app >> for Arches that will allow users (with appropriate permissions) to >> create/edit data in the field. Our app will support both connected and >> disconnected (e.g.: without network connectivity) editing. As you suggest, >> the app will sync directly with your Arches server. You'll be able to >> apply rules to the sync, so that "crowd-sourced" data is reviewed and >> confirmed as part of the data loading process. >> >> We're expecting to have this app available for Arches v4 in the first >> half of next year. >> >> Hope this helps. >> >> Cheers, >> >> Dennis >> >> On Friday, September 30, 2016 at 8:00:53 AM UTC-7, Basav Biradar wrote: >>> >>> Dear good friends at Arches, >>> >>> We are proposing an institution to adopt Arches as the heritage >>> management and inventory system. We are looking through data collection >>> apps such as "Fulcrum" "ArcGis" "Kobo toolbox" "OpenData" as the possible >>> choices. >>> >>> The two main criteria we thought are necessary are - >>> >>> 1. Mobile version of the app should be available on Android PlayStore >>> and should be user friendly >>> >>> 2. Data collected from the app can be integrated with Arches app on the >>> server without much effort. Basically on using the "sync" option on the app >>> the data should be directly stored onto postgres SQL database which is >>> running the Arches as well. >>> >>> Has anyone done such integration? Please let me know your thoughts. It >>> will be very helpful. >>> >>> Much Thanks >>> Basav >>> >> -- -- To post, send email to [email protected]. To unsubscribe, send email to [email protected]. For more information, visit https://groups.google.com/d/forum/archesproject?hl=en --- You received this message because you are subscribed to the Google Groups "Arches Project" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
