Lan Saka District

Lan Saka (Thai: ลานสกา, pronounced [lāːn sā.kāː]) is a district (amphoe) of Nakhon Si Thammarat Province, southern Thailand.

Lan Saka

ลานสกา
District
District location in Nakhon Si Thammarat Province
Coordinates: 8°22′18″N 99°48′18″E
CountryThailand
ProvinceNakhon Si Thammarat
SeatKhao Kaeo
Area
 • Total342.90 km2 (132.39 sq mi)
Population
 (2012)
 • Total40,406
 • Density117.83/km2 (305.2/sq mi)
Time zoneUTC+7 (ICT)
Postal code80230
Geocode8003

History

The district was at first a minor district (king amphoe) named Khao Kaeo (เขาแก้ว), which was a subordinate of Mueang Nakhon Si Thammarat District. When the district office was moved to tambon Lan Saka, the district was renamed accordingly. In 1958 it was upgraded to a full district.[1]

Geography

Neighboring districts are (from the north clockwise): Phrom Khiri, Mueang Nakhon Si Thammarat, Phra Phrom, Ron Phibun, Thung Song, Chang Klang, Chawang and Phipun.

Khao Luang National Park is in Lan Saka District.

Administration

The district is divided into five sub-districts (tambons), which are further subdivided into 42 villages (mubans). Lan Saka is a township (thesaban tambon) which covers parts of tambon Khao Kaeo. There are a further five tambon administrative organizations.

No. Name Thai name Villages Pop.
1.Khao Kaeoเขาแก้ว67,293
2.Lan Sakaลานสกา75,775
3.Tha Diท่าดี78,031
4.Kamlonกำโลน118,804
5.Khun Thaleขุนทะเล1110,135
  
gollark: Maybe I should adapt the potatOS privacy policy as a code license.
gollark: MPL?
gollark: There is also the "secondary processor exemption" thing, which caused the Librem people to waste a lot of time on having a spare processor on their SoC load a blob into the SoC memory controller from some not-user-accessible flash rather than just using the main CPU cores. This does not improve security because you still have the blob running with, you know, full control of RAM, yet RYF certification requires solutions like this.
gollark: It would be freer™, in my opinion, to have all the firmware distributed sanely via a package manager, and for the firmware to be controllable by users, than to have it entirely hidden away.
gollark: So you can have proprietary firmware for an Ethernet controller or bee apifier or whatever, but it's only okay if you deliberately stop the user from being able to read/write it.

References
  1. lansaka.nakhoncdp.go.th Archived 2007-01-03 at the Wayback Machine
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.