<strong>
Locality</strong>
type in the locality of the territory.
ื <strong>
ืืืฉืื </strong>
ืืงืื ืืช ืืืฉืื ืืฉืื.
<strong>
Locality</strong>
type in the locality of the territory.
In another section of the Help file, TB user is directed to type locality into the description field, rather than locality field...??
We have had a locality discussion before I think, which led me to believe that locality is a general area within a city/town, that can have many territory maps. Now, however, I start to think that locality is unique to 1 territory map.
Who'll cut the knot for me?
The fields name and description relate to the fields that are available in a kml file by default. These fields are set in 3rd party tool, from which the kml file is exported.
Regarding the use of locality (I refer to the field on the Territory Map Card S-12), I 'm not aware of an official naming convention (which includes also the number field). Therefore this field may be unique in one congregation (as in ours) but not necessarily in other congregations.
The number field may also be used differently (unique integer number, combination of a letter and a number, e.g. city abbreviation and a unique number per city...). Therefore the import function can take the locality field into consideration, since the territory number is a unique integer number in TheocBase, and this may differ to what was used previously.
Ah, right. I'll go back to verify the exact terms Google uses, then. Very good!
<strong>
Locality</strong>
type in the locality of the territory.
ื <strong>
ืืืฉืื </ strong>
ืืงืื ืืช ืืืฉืื ืืฉืื.
ื <strong>
ืืืฉืื </strong>
ืืงืื ืืช ืืืฉืื ืืฉืื.
ื <strong>
ืืืฉืื </strong>
ืืงืื ืืช ืืืฉืื ืืฉืื.