Location misstake from config vs controller.js

[Wolfyann]

Hi, I've just configured my camera (with the last update) and some few days I don't undertand why the constellation overlay wasn't mine. I put the location on both (picture by camera AND constellation overlay), it's the difference.
So I reconfigure my camera (and I can't remove the first from the new map view), but the coordinates were always false. I changed manuelly in the controller.js (decimal format instead variable : data.longitude = DD.dddd Vs config.longitude ) and it correct now. It's a "bug" or I'm alone with this ?

[EricClaeys]

@Wolfyann, I'm not quite clear what the problem is, but it sounds like your constellation overlay doesn't match your stars? If so, look at the "Constellation Overlay" Wiki page for tips. It's a time consuming process to align the overlay to your stars, and you need to make sure your time, latitude, and longitude are correct.

You should never need to change any of the javascript files like controller.js. Only the configuration files config.js and possibly virtualsky.json. The latitude and longitude in config.js need to be numbers withOUT the N, S, E, or W. Don't forget that "S" latitude and "W" longitude are negative numbers.

Your map pin should go away as soon as you uncheck the Show On Map setting in the WebUI and click on the "Save Settings" button, assuming you are using the same Pi and same operating system as you did when you added the map pin. The map server simply looks at a unique machine ID to determine which pin to delete or update.

[Wolfyann]

@EricClaeys yes, in fact in the end the map does not correspond because some coordinates used are not those defined in the file settings-RPiHQ.json (for my conf). I've checked the config.js and the coordinates are properly defined without the compass points but in decimal format.

[EricClaeys]

@Wolfyann The map settings are stored in the settings-RPiHQ.json file. The settings for the Allsky Website (with the overlay) are stored in /var/www/html/allsky/config.js. The next release helps keep these in sync, but two configuration files are needed because a lot of people run their Allsky Website on a remote server.

For clarity, please let's keep this discussion limited to the overlay in the Allsky Website. The map problem is a different issue and you can create a separate Discussion for that. It help me understand what problem I'm looking at. Thanks.

For the overlay issue, you've double checked that the latitude and longitude in config.js are correct, with the correct signs? Since you are in France, both numbers should be positive. In the Allsky Website if you click on the camera icon on the left, does it show your latitude with an "N" and longitude with and "E"?

If so, did you look at the "Constellation Overlay" Wiki page for tips on how to align the overlay?

[Wolfyann]

Ok, well it's more clear for me after some tests :) and your explanations, many thanks ! Really !
Now it's ok for the contellation overlay on my camera, and I'd calibrated the position and picture siez, it's works fine ! I'm waiting for the next version. We can consider this discussion like "answered" :)
the overlay is important for me, because I want a kind of autocalibration to recognize the star field (like a startracker) and determinate the camera's position autonomously. The overlay may confirm my simulations.