TheocBase/TheocBase
-
4dbe40ee5cfbd7536a1dfdc806ce334e4cfa8995
4dbe40ee5cfbd7536a1dfdc806ce334e4cfa8995
Select the menu item<strong>
Layer>Add Layer>Add Vector Layer...</strong>
-
c7f1c66eee4d8cab1b1868e3ac3ab976e2bb9bb6
c7f1c66eee4d8cab1b1868e3ac3ab976e2bb9bb6
Click on the<strong>
Browse</strong>
button and select the "theocbase.sqlite" file. -
0d39e40c13023eb018928a26f0a74d0ffbc11860
0d39e40c13023eb018928a26f0a74d0ffbc11860
Click on the<strong>
Add</strong>
button. -
احتیاط:
احتیاط:
Caution: -
d6d94c5328e29111a28b62ff70caa9687a753c6a
d6d94c5328e29111a28b62ff70caa9687a753c6a
When editing the geometry in a third party tool like QGIS, TheocBase will not be aware of the changes during cloud syncing. In order to upload the changes you need to mark the territories as edited e.g. add a blank in the remark field. Alternatively you can also export the territories into a KML file and reimport this file in TheocBase. -
0d84a9a756e2271959f478f5a7856cfb40bd1aea
0d84a9a756e2271959f478f5a7856cfb40bd1aea
Add the layers by clicking on the<strong>
OK</strong>
button. -
817348a2e0e997c90ef87c78b83fabf0bc74a1f6
817348a2e0e997c90ef87c78b83fabf0bc74a1f6
Export into a KML File -
8eb988c435f58babc318124f1a1a1f9104f5abb1
8eb988c435f58babc318124f1a1a1f9104f5abb1
Right click the layer you want to export and select<strong>
Export>Save Features As...</strong>
-
bb0cd5f28ff1bfe24aa46da26dad7da92ff35616
bb0cd5f28ff1bfe24aa46da26dad7da92ff35616
In the<strong>
Format</strong>
field choose<strong>
Keyhole Markup Language [KML]</strong>
. -
cc8c2251cad9b909a69588df806712c8a93e0797
cc8c2251cad9b909a69588df806712c8a93e0797
Click on the<strong>
Browse</strong>
button and select a filename. -
f357a05cb0316664fd047be5dff8cadfd04b1dd2
f357a05cb0316664fd047be5dff8cadfd04b1dd2
Under<strong>
Select fields to export and their export options</strong>
check the following fields: -
fd96b0d46f733925e4c6ef5e64cd871030181a0d
fd96b0d46f733925e4c6ef5e64cd871030181a0d
Edit the<strong>
Datasource Options</strong>
-
86cee4a721d8bf900a420f1374ea0e35fe638cb3
86cee4a721d8bf900a420f1374ea0e35fe638cb3
Click<strong>
OK</strong>
to save the KML file. -
8eade98d325b2d2c8b91872aa03e8e73890f7ba8
8eade98d325b2d2c8b91872aa03e8e73890f7ba8
Choose<strong>
File</strong>
as<strong>
Vector Source Type</strong>
. -
6e5a7cdc750ac21dd5d04c54f1ee21555ed42c4a
6e5a7cdc750ac21dd5d04c54f1ee21555ed42c4a
Choose the<strong>
CRS</strong>
(Coordinate Reference System):<strong>
EPSG:4326</strong>
. -
aa7afb6cafe14e28350d7d0e331c0105854c2a14
aa7afb6cafe14e28350d7d0e331c0105854c2a14
Working with the Territory Data in a Geographic Information System (GIS) -
bc84ed667ea0688249dae6acf5458de669d0d587
bc84ed667ea0688249dae6acf5458de669d0d587
The TheocBase SQLite database can be opened in a GIS software that allows users to analyze or combine the data with other sources e.g. create high quality maps for the Kingdom Hall. In the following instructions QGIS is used, a multi-platform GIS available for free, but other programs may be used similarly. -
af1821a5b5b1b4f63b85fde3533a38e3e9b2f4d5
af1821a5b5b1b4f63b85fde3533a38e3e9b2f4d5
<span>
Select the layers you want to use in QGIS:</span>
<br><span><strong><!-- Table name: -->
territory<!-- Don't translate this. --></strong>
: for editing boundaries</span>
<br><span><strong><!-- Table name: -->
territories<!-- Don't translate this. --></strong>
: for viewing and analyzing the territories</span>
<br><span><strong><!-- Table name: -->
territory_address<!-- Don't translate this. --></strong>
: for editing addresses</span>
<br><span><strong><!-- Table name: -->
territoryaddresses<!-- Don't translate this. --></strong>
: for viewing and analyzing the addresses</span>
<br><span><strong><!-- Table name: -->
territory_street<!-- Don't translate this. --></strong>
: for editing streets</span>
<br><span><strong><!-- Table name: -->
territorystreets<!-- Don't translate this. --></strong>
: for viewing and analyzing the streets</span>
-
c6b137b609e576ef7637e00de548c26c94d3ad25
c6b137b609e576ef7637e00de548c26c94d3ad25
<span><!-- Field name: -->
territory_number<!-- Don't translate this. --></span><br><span><!-- Field name: -->
locality<!-- Don't translate this. --></span>
-
ad6958f2b433b631732a81e01a91446e4c02709a
ad6958f2b433b631732a81e01a91446e4c02709a
<span>
Enter "<!-- Field name: -->
locality<!-- Don't translate this. -->
" next to<strong>
DescriptionField</strong>
.</span><br><span>
Enter "<!-- Field name: -->
territory_number<!-- Don't translate this. -->
" next to<strong>
NameField</strong>
.</span>