Skip to main content

gugong

gugong is an accessible data library for The Fobidden City located in Beijing, China. The location of The Forbidden City is now called The Palace Museum.

While "The Fobidden City" might be more commonly known from the western world, the other name "GuGong", or literally translated as "The Past Palace", is more commonly used domestically in China. It's a shorter two-character-term "故宫" than the 3-character-term "紫禁城". The other possible reason might be today it's called "The Palace Museum", with the Chinese name as "故宫博物院". So it's just easy to call the first part of the name ommitting the word "musuem".

This library is built with historic facts and grounds collected from various open resources. It could be used as learning and educational purposes.

Background

2020 is the 600 anniversity of the establishment of The Fobidden City. Besides, it's a good timing to revisit the 600 years of history of the Ming and Qing dynasty together with The Fobidden City as part of the celebration.

Install

If you have PIP, install the package with the one liner.

$ pip install gugong
...

How to use the library

Import the library

In [1]: from gugong import GuGong

In [2]: gg = GuGong()

In [3]: gg.name
Out[3]: '故宫'

Check the data in the library

In [4]: for place in gg.places:
   ...:     print(place.name, place.arch_type)
午门 0
神武门 0
东华门 0
西华门 0
太和门 0
...

In [5]: for empire in gg.empires:
    ...:     print(empire.epoch_name, empire.temple_name)
    ...:
永乐 明成祖
洪熙 明仁宗
宣德 明宣宗
正统 明英宗
景泰 明景帝
成化 明宪宗
弘治 明孝宗
正德 明武宗
嘉靖 明世宗
隆庆 明穆宗
万历 明神宗
泰昌 明光宗
天启 明熹宗
崇祯 明思宗
福临 清世祖
康熙 清圣祖
雍正 清世宗
乾隆 清高宗
嘉庆 清仁宗
道光 清宣宗
咸丰 清文宗
同治 清穆宗
光绪 清德宗
宣统 清宣统皇帝

TODO

  • Simple Q&A
    • How to promounce some place or name in the Palace Museum
    • When is this built?
    • Who is this?
  • External Interfaces
    • To Baidu for more smartness about knowledge?
    • To Amap for more smartness about geography

Contact

If you find any mistake of inaccuracy in the data, please simply file an issue in GitHub.

If you have any concern on data infringement, please reach out to the author on the email saphires@163.com .

Metadata

Release files for gugong 0.5.5

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for gugong 0.5.5
File Size Uploaded
gugong-0.5.5.tar.gz 11.5 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for gugong 0.5.5
File Interpreter ABI Platform
gugong-0.5.5-py3-none-any.whl Python 3 none any Details

Total release size: 26.5 kB

Release files / gugong-0.5.5.tar.gz

Download URL gugong-0.5.5.tar.gz
Size 11.5 kB
Tags Source
SHA-256 checksum
How to use checksums
0cd93f47cd8e074f18620b9152fea69847132cceab02c973facf59585d3c450a
BLAKE2b-256 checksum
How to use checksums
95a6118b152d534414031c71bead3a9aeb15a09dd1bf32193d390a42ae9937d6
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/3.1.1 pkginfo/1.5.0.1 requests/2.23.0 setuptools/46.4.0 requests-toolbelt/0.9.1 tqdm/4.46.0 CPython/3.7.3

Release files / gugong-0.5.5-py3-none-any.whl

Download URL gugong-0.5.5-py3-none-any.whl
Size 15.0 kB
Tags Python 3
SHA-256 checksum
How to use checksums
7845eb6e6aadf1a27a6823d83252370fd588442f43dc3e886d0ebaaeb34c0943
BLAKE2b-256 checksum
How to use checksums
02272303b88e92ab8f9c57fa3f50d658b7bcb0e6bfe63892c6224d0731fed2c8
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/3.1.1 pkginfo/1.5.0.1 requests/2.23.0 setuptools/46.4.0 requests-toolbelt/0.9.1 tqdm/4.46.0 CPython/3.7.3

Release history Release notifications | RSS feed

This release

0.5.5 This release

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page