Kimhwa County

Kimhwa County is a kun, or county, in Kangwŏn province, North Korea.

Kimhwa County

김화군
Korean transcription(s)
  Chosŏn'gŭl
  Hancha
  McCune-ReischauerKimhwa-gun
  Revised RomanizationGimhwa-gun
Map of Kangwon showing the location of Kimhwa
CountryNorth Korea
ProvinceKangwŏn Province
Administrative divisions1 ŭp, 1 workers' districts, 13 ri

Geography

Kimhwa county is primarily mountainous, but the county's southeastern region is low-lying. The highest peak is Pae'gyŏnsan (백연산). The chief stream is the Pukhan River. Approximately 80% of the county's area is taken up by forestland.

Administrative divisions

Kimhwa county is divided into 1 ŭp (town), 1 rodongjagu (workers' district) and 13 ri (villages):

  • Kimhwa-ŭp (formerly Kŭmsŏngmyŏn)
  • Hakpang-rodongjagu
  • Ch'angdo-ri
  • Ch'osŏ-ri
  • Kubong-ri
  • Ŏho-ri
  • Pŏpsu-ri
  • Ryonghyŏl-li
  • Sangp'al-li
  • Sinch'ang-ri
  • Sinp'ung-ri
  • Tanghyŏl-li
  • Wŏnbung-ri
  • Wŏndong-ri
  • Wŏnnam-ri

Economy

The chief local industry is agriculture. Local crops include potatoes, maize, rice, wheat, and barley. In addition, livestock and silkworms are raised, and orchards are cultivated. There are several mines, exploiting local deposits of manganese, gold, copper, talc, fluorite, barite, and anthracite.

Transportation

Kimhwa is connected to the rest of North Korea by road.

gollark: There are some important considerations here: it should be able to deal with damaged/partial files, encryption would be nice to have (it would probably work to just run it through authenticated AES-whatever when writing), adding new files shouldn't require tons of seeking, and it might be necessary to store backups on FAT32 disks so maybe it needs to be able of using multiple files somehow.
gollark: Hmm, so, designoidal idea:- files have the following metadata: filename, last modified time, maybe permissions (I may not actually need this), size, checksum, flags (in case I need this later; probably just compression format?)- each version of a file in an archive has this metadata in front of it- when all the files in some set of data are archived, a header gets written to the end with all the file metadata plus positions- when backup is rerun, the system™ just checks the last modified time of everything and sees if its local copies are newer, and if so appends them to the end; when it is done a new header is added containing all the files- when a backup needs to be extracted, it just reads the end and decompresses stuff at the right offset
gollark: I don't know what you mean "dofs", data offsets?
gollark: Well, this will of course be rustaceous.
gollark: So that makes sense.

See also

This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.