Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How to get the exact date and time from ecliptic longitude on gps coordinates #155

Open
ratobiajin opened this issue Oct 16, 2021 · 2 comments

Comments

@ratobiajin
Copy link

ratobiajin commented Oct 16, 2021

Hello! I am thankful for the effort you have done for this project. In Chinese and Japanese culture there are 24 Solar Terms, the dates of which are calculated taking into account the ecliptic longitude by two methods — píngqì (平気) based on the mean motion of the Sun dividing the tropical year evenly into 24 periods, and dìngqì (定気) based on the position of the Sun on the ecliptic. I'd like to have a script that calculates the exact local time (MM/DD hh;mm) for the given year at the location given by lat/lon GPS coordinates of main 8 Solar Terms, each of which take place at given ecliptic longitude, in both methods:

315° | 1 Lichun
0° | 2 Chunfen (Spring Equinox)
45° | 3 Lixia
90° | 4 Xiazhi (Summer Solstice)
135° | 5 Liqiu
180° | 6 Qiufen (Autumn Equinox)
225° | 7 Lidong
270° | 8 Dongzhi (Winter Solstice)

getSolarTerm(2022,4,"dingqi","35.6819,139.7534"), i.e. Xiazhi (Summer Solstice) of 2022, in case of Tokyo, Japan should return "06/21 18:14"
getSolarTerm(2022,4,"pingqi","35.6819,139.7534"), i.e. Xiazhi (Summer Solstice) of 2022, in case of Tokyo, Japan should return "06/22 04:55"

@camiteca
Copy link

Does #156 cover this case?

@ratobiajin
Copy link
Author

Does #156 cover this case?

No, unfortunately, it does not. I'd like to get date AND time from the provided GPS lat/lon coordinates AND ecliptic longitude.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants