well, it's not an automatic import at all but if you want to give it a try it should work:
- reduce the number of points in your horizon mask to max 255 points (eg only even degrees ).
- 'Close' the polygon: add 0 values for the base of the polygon (see attached file after row 180)
- save the file as .csv
- close kstars
- use a sql lite editor (like 'DB Browser for SQL Lite') and open ./local/share/kstars/userdb.sqlite (do a backup first).
- Then in 'DB Browser for SQL lite' File->Import ->Table from csv file to import all the data in a table. Choose a table name like 'my_horizon'
- in the table 'horizons' add a record with these values: 1,my_horizon, My Horizon, 1
- reopen Kstars and select the horizon in Settings.
The area around the N Pole looks weird but I can be fixed.
yes it is parsing the input line by line.
Good to hear that it works.
weather watcher reads from data sources 5 parameters max: rain, temperature, wind (average), gust (wind gust) and forecasts. Other parameters are ignored.
The first 3 only (rain, temperature and wind) are defined as critical parameters; it means that they broadcast in Ekos the weather status. So for example if wind is >30 the observatory shuts down.
Coming to your question, the cloud parameter that you see in the documentation is taken as an output example from a commonly used weather station (AAG CloudWatcher SOLO).
As of today the driver ignores that parameter unless you use another parameter's slot. E.g. setting 'clouds' keyword in 'rain' slot.
Be aware that it's not a solution but just a way to fool Ekos:
- the 'rain' label will still be used for this parameter,
- the real rain value is now ignored!
- other drivers will still be think this as the real rain.
It should work when you set a web address as well.
Did you add the http:// at the beginning? Like
@Jasem: if I remember well it already happened. is there something I should change in the configuration of the driver?
@Jean-Louis: where is your Talon6 observatory based?
If you need assistance in configuring the driver don't hesitate to ask.
the parameters are coded in the WeatherWatcher driver so you cannot customize in the way you need.
But it should not be difficult to abstract the name of the parameters reading them from the driver configuration or an external file.
I've quickly checked in the source code, the parent classes of the driver doesn't make use of any of the parameter names in WW (e.g. 'wind' or 'temperature') so changing them dynamically should not harm the rest of the environment.
About the 'light'/ 'wind' hack: be aware that some of these parameters (marked as critical) are used to trigger actions like shutting down the observatory if the parameter is in a danger range. As far as i know these are: temp, wind, rain and weather forecast. I would not recommend but in case I would rather use 'wind gust' as fake parameter.
not exactly a Dome but a Roll Off Roof. Domes and Roofs share the same base class but Roofs have only Park / Unpark (i.e. open / close) features.
If this is enough for a test, happy to help.