Location hard-coded in virtualsky.js, overwrites everything else

[EorEquis]

Kept noticing that my overlay didn't match reality, seemed a few hours behind based on Sun position. Enabled "showposition" and saw that the virtusl sky overlay was forcing 34.43N, 119.86W, well west of my actual position.

Doublechecked everything elsewhere, all had the correct latlong.

Looked in /var/www/html/allsky/virtualsky/virtualsky.js and sure enough, the location for LCO is hard-coded :

// Set location on the Earth this.setLongitude(-119.86286); this.setLatitude(34.4326);

Changed it to match mine, but would expect this to pick the info up from the config files in future.

[EricClaeys]

@EorEquis It only uses the coordinates in virtualsky.js if it can't get the coordinates from config.js, usually because they are incorrectly formatted. The comment in that file: latitude_longitude_comment: "latitude and longitude must be decimal numbers with OUT the trailing N, S, E, and W.", needs to be followed. Typically when users see the problem you're seeing, they have N, S, E, and/or W in their coordinates.

[EorEquis]

Hrm, well I did have that issue before, but I thought I'd tested since fixing that.

I'll doublecheck, and see what happens. Thanks!

[EricClaeys]

@EorEquis Your config.js has well-formatted latitude and longitude, and the overlay has the Sun over what appears to be the Sun in the rainy picture. You may need to force your browser to re-read config.js by pressing Shift-F5.

[EorEquis]

It had the Sun correct because I'd hard coded the correct location into virtualsky.js. If I changed that by removing the - sign for longitude, it overrode what was in config.js.

Looks like our comments crossed though. It seems removing the " for the lat/long values resolved the issue.

[EorEquis]

Ah ha...so the config.js did not have N/W/S/E, but it DID have double quotes around the lat and long values. I removed those, seems to have done the trick.

I'm quite certain I didn't place those there, but then...I was pretty sure I hadn't put the N there earlier either, so....who knows.

[EricClaeys]

@EorEquis Interesting. I'll have to make sure the next version of the Website accepts quotes around numbers.
It will accept with or without N, S, E, W, and users won't have to do Shift-F5, so those issues should go away.
Thanks for letting me know.
Eric