Importing JHora .jhd files: what carries over
What Trikona reads from a Jagannātha Horā .jhd file, what it
writes back, and what it leaves behind. The numbers below come from running Trikona's own import and
export code on sample charts. The sample charts are made up; no real person's birth data is used.
What carries over
| Field | JHora to Trikona | Trikona to JHora (.jhd export) |
|---|---|---|
| Birth date | Kept | Kept |
| Birth time | Kept, including fractions of a minute | Kept |
| UTC offset at birth | Kept as the fixed offset in the file, so a daylight-saving offset stays as JHora had it | Kept as a fixed offset |
| Longitude and latitude | Kept; JHora's west-positive longitude and UTC offset signs are converted | Kept, written back in JHora's sign convention |
| Place name | Kept (city, then the rest) | Kept, with spacing around commas tidied |
| Client name | Taken from the file name | Written as the file name, in plain letters (Indian scripts spelled in Latin letters) |
| Time-zone name and daylight-saving rules | Not in the file; only the offset is | Not written |
| Other values JHora stores in the file | Not read | Written as zero |
| Notes, consultations, predictions | Not in a .jhd file | Not written |
| Chart settings (ayanāṁśa, node, houses) | Not read; Trikona uses your Trikona defaults | Not written |
The results
Trikona to .jhd and back
27 sample birth records, covering both hemispheres, half-hour and 45-minute offsets, UTC offsets from −12 to +14 hours, daylight-saving dates, a leap day, the first and last supported years (1850 and 2149), Devanagari, Telugu, Arabic and accented names, and places with irregular commas.
- 26 of 27 were written to a .jhd file. 1 was refused on
purpose because its place name starts with a number, which the importer would read as data:
- 123, India
- All 26 written files came back with the same birth date, and with birth time within 0.001 ms, latitude within 0.001″, longitude within 0.001″ and UTC offset within 0.001 ms.
- The place name came back unchanged in 25 of 26. Changed:
- Mysuru , Karnataka,,India → Mysuru, Karnataka, India
- The client name came back unchanged in 18 of 26. The name travels as the file
name, in plain letters: accents and punctuation are dropped, a name in Devanagari, Bengali, Gurmukhi,
Gujarati, Odia, Tamil, Telugu, Kannada or Malayalam is spelled in Latin letters, and a name only in
another script, such as Arabic or Chinese, becomes "Chart":
- Phāṇi Kṛṣṇa → Phani Krsna
- राम → Ram
- कृष्ण शर्मा → Krishna Sharma
- రామ → Rama
- محمد → Chart
- St John's test → St John s test
- Dr. A. K. Sharma (test) → Dr A K Sharma test
- A very long synthetic client name that keeps going well past eighty characters in total → A very long synthetic client name that keeps going well past eighty characters i
Hand-written .jhd files with historical daylight saving
6 files, including New York's 1945 wartime and 1974 winter daylight saving, Sydney summer time and Santiago winter time. All 6 imported with the same birth date, and with birth time within 0.02 ms, latitude within 0.001″, longitude exactly the same and UTC offset exactly the same. The birth moment in UTC matched the official time-zone history for each place.
Files opened in JHora 8.0
20 .jhd files in this format were opened in the JHora 8.0 desktop program for an earlier calculation comparison. Trikona imports all 20 with the same birth date, and with birth time within 0.001 ms, latitude within 0.001″, longitude within 0.001″ and UTC offset within 0.001 ms.
What has not been checked yet
- Files saved by JHora itself from a real practice, with every option JHora can store. The files above were written in JHora's format, not exported from a JHora practice.
- Opening Trikona's exported .jhd files in JHora 8.0.
If a file does not import as you expect, tell us at support@trikona.app. Please do not send a client's birth details; describe the problem and we will reply.
Related pages
- Trikona and JHora: convention differences
- Trikona and Jagannātha Horā compared
- Sidereal calendar 2027
Bring your clients across
Trikona is free during early access.
Start free during early accessQuestions
Can I import my JHora .jhd files into Trikona?
Yes. In Trikona, open Tools, then Import, and choose .jhd files, a folder or a ZIP. Trikona reads the birth date, time, UTC offset, longitude, latitude and the place name, and shows a preview before it saves anything.
Is anything lost when I import?
The birth data is kept. The client's name comes from the file name, and anything else JHora keeps in its own files or settings is not read. The table on this page lists each field.
Can I send a chart from Trikona back to JHora?
Yes. Tools, then Export .jhd, saves a chart's birth data as a .jhd file. Opening those files in JHora 8.0 is not yet checked, so check the first one before relying on it.