Description: Populated Places of Syria Users should be aware: - Places represent the centroids of the admin4 (build up areas) layer and their attribution is identical
- Populated places do not use same p-code structure as the Admin layers
- 29 places fall outside of the Admin0 boundaries. Most fall right outside the border but "Mazraet Deir Elashayer" is the furthest, about 3,484 meters away from the closest boundary.
- 253 places do not have a 1 to 1 relationship between the English and Arabic names
- Populated Places only has parent attribution for their admin0-3 units, not for admin 5 (neighborhoods) - Places "Rasm Elbardaqana" and "Hosh Hammad" fall outside the borders of their attributed Admin1. - 6 places fall outside their attributed Admin2. - 12 places fall outside their attributed Admin3.
- The presence of parentheses and slashes in some names may indicate the need for secondary names to be separated and put in an alternate name field.
- The admin 3 unit of Masaada (SY140003) has no registered localities - Admin capital attribution is included for Admin0, 1 and 3 capitals. No Admin2 capital attribution is included.
Description: Admin 4 - Places/Built Up Areas Users should be aware: - 253 Admin4 names do not have a 1 to 1 relationship between the English and Arabic names 5 - The multipart feature of "Kharab Eljir" in Admin4 may be an error. It has been left as is
- Admin4 and 5 layers have p-code values which use a different format than the 0-3 p-code values
- Admin4 and 5 units do not nest with Admin0-3. Some units fall outside of the Admin0 borders. - Admin5 has 133 nesting errors with Admin4.
- 253 Admin4 names do not have a 1 to 1 relationship between the English and Arabic names.
- Admin4 "Rasm Elbardaqana" has Admin1 "Hama" attribution but is spatially in Admin1 "Homs". - Admin4 "Hosh Hammad" has Admin1 "As-Sweida" attribution but is spatially in Admin1 "Dar'a". - 6 Admin4 units fall outside their attributed Admin2 parent. - 12 Admin4 units fall outside their attributed Admin3 parent.
- The presence of parentheses and slashes in some names in the admin4 and admin5 layers may indicate the need for secondary names to be separated and put in an alternate name field.
Description: Admin 5 - Neighbourhoods Users should be aware:
- 5 Admin5 names do not have a 1 to 1 relationship between the English and Arabic names
- Admin4 and 5 layers have p-code values which use a different format than the 0-3 p-code values
- Admin4 and 5 units do not nest with Admin0-3. Some units fall outside of the Admin0 borders
- Admin5 has 133 nesting errors with Admin4.
- The presence of parentheses and slashes in some names in the admin4 and admin5 layers may indicate the need for secondary names to be separated and put in an alternate name field.