City names, DST and Coordinates

[Guest guest]

Respected PVR Narasimhaji,

 

I'll address this post to you - but this post can be read as a eye-opener on a

few things I recently ran into with JHORA software.

 

Before I begin the content - I'll state that these are no way defects in JHORA

software - but kind of watch out scenarios for its users.

I'm using v7.33 of JHora.

 

JHora has sourced the City names and coordinates etc., from an external source

(probably USGS etc) and attached them to JHORA.

I noticed some problems with City names, Coordinates and Daylight Saving Times.

 

1) City names: For example Jaipur a prominent city in Rajasthan, India is

available in JHora on 7 different coordinates - varying between 75E49 to 95E24.

The correct one is Jaipur City.

There may be many such cities world wide that can be mistaken.

 

Not sure - if we can include the Region Name along with the City (like Jaipur

City, Rajasthan) - if the source carries it - something PVRji can respond to.

Will definitely help reduce such mistakes.

 

2) Coordinates: In a recent request to rectify a chart the lagna was on a border

of 2 min 11 secs. The place was Badulla Srilanka.

JHora carries two coordinates for Badulla, Srilanka

80E32 and 81E03. Google displays the coordinate for Badulla as 81E03, but

Badulla is actually a District as well - so could have a wider coordinate range.

The correct rectified lagna for the request was arrived using the 80E32

coordinates. I trusted more on jyotisha than on our coordinates.

 

Again recommend users to double check what they even get from other sources. If

you double checked coordinates for (Item 1) - then you would have issues using

the correct ones (Item 2)

 

3) Daylight Saving Time: I recently was looking at a chart where the native was

born in Jan 07,1964 in Sydney Australia.

between 1960-1969 Sydney did not use Daylight Savings but JHora displays

Daylight Saving.

After a short research I reduced the offset from 11 to 10 and rest fell in place

- Again research was needed.

 

The problem is again third-party software and also Australia

Australia has been going back and forth on the DST on and off many years - so

the software may bring in some inconsistency.

 

I faced all these issues in just the past few weeks - I thought it prudent to

bring this to the attention of all members.

 

Thanks,

Shrikanth Gopalan