Dear Adam,

Thank you very much for your reply. I found the two links that you sent me 
interesting reading. Your blog post sounded like a nice solution for the 
particular problem it tackled. 

I think our version of Arches is v3 because I can manage to get the points, 
polygons and lines into QGIS by going to the Add Vector layer button and 
then using a protocol. The problem then is that I only get the spatial 
attributes with their ID numbers and no further useful information. I would 
like to connect to the Arches database via the DB Manager and then write 
queries using the DB manager (for example, to give me all my heritage 
resources with an area of more than 10ha which have been damaged by 
construction work, with their names).

Would it be easy to do that?

Best wishes,

Matt

On Monday, August 7, 2017 at 4:05:32 PM UTC+1, Adam Cox wrote:
>
> Hi Matt,
>
> This will depend greatly on what version of Arches you are using. v3 held 
> all geometries for the entire database in a single postgis table, I've 
> connected to that table in QGIS before to make edits just to test, but I 
> think you would want to make some db views that would bring in some extra 
> resource attributes (like name, etc.) and make that single table a little 
> more user-friendly (instead of just a lot of shapes). I wrote this blog 
> post a while ago related to this idea. 
> http://legiongis.com/using-qgis-geoserver-and-postgis-to-make-and-maintain-arches-overlays.html
>
> In Arches v4, geometries are actually stored along with all other business 
> data in a table of "Tiles". You can see this in the Data Model 
> https://github.com/archesproject/arches/wiki/Data-Model, and the 
> geometries themselves are stored as json objects. So the process of 
> connecting with QGIS would be trickier because there isn't any single 
> postgis table that holds all the feature geometries. Hopefully others from 
> the development team can chime in on this. As far as I can tell, you would 
> have to write some SQL to pull geometries out of the TileInstance table and 
> populate proper geometry tables with them, which you could then connect to 
> with QGIS.
>
> Adam
>
> On Mon, Aug 7, 2017 at 5:25 AM, M Hobson <matthew...@gmail.com 
> <javascript:>> wrote:
>
>> Hello everyone,
>>
>> I have just joined a project that uses Arches for its main database. I am 
>> interested in connecting to the database through QGIS's DB Manager. The 
>> previous project I worked for used this functionality in QGIS very 
>> successfully with a relational SQL database. The project team were able to 
>> write SQL queries and import the results as layers directly into QGIS. 
>> These layers updated automatically when data in the database altered.
>>
>> Does anybody have any experience of doing this with an Arches database? 
>> Is it easy to set up? Are there any reading materials about how to write 
>> queries for the Arches database?
>>
>> Many thanks in advance for any advice or information offered.
>>
>> Matt H
>>
>> -- 
>> -- To post, send email to arches...@googlegroups.com <javascript:>. To 
>> unsubscribe, send email to archesprojec...@googlegroups.com <javascript:>. 
>> 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 archesprojec...@googlegroups.com <javascript:>.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 
-- To post, send email to archesproject@googlegroups.com. To unsubscribe, send 
email to archesproject+unsubscr...@googlegroups.com. 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 archesproject+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to