<div dir="ltr">I think the asteroid component in KStars needs to be updated to incorporate different sources instead of a single source like now, then it could parse the different sources and resolves any conflicts before making it available to the user.</div><div class="gmail_extra"><br clear="all"><div><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div>Best Regards,<br>Jasem Mutlaq<br></div><div><br></div></div></div></div>
<br><div class="gmail_quote">On Sat, Mar 17, 2018 at 5:25 AM, Steffen Möller <span dir="ltr"><<a href="mailto:steffen_moeller@gmx.de" target="_blank">steffen_moeller@gmx.de</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hello,<span class=""><br>
<br>
On 3/16/18 3:07 PM, Jasem Mutlaq wrote:<br>
<br>
</span><span class=""><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
If you have a method to automate this process, we can include it in KStars.<br>
</blockquote></span>
I now created a small to tool and tried<br>
<br>
wget -O - <a href="https://www.minorplanetcenter.net/Extended_Files/neocp.json" rel="noreferrer" target="_blank">https://www.minorplanetcenter.<wbr>net/Extended_Files/neocp.json</a> | ./neocp2kstars<br>
<br>
which gives me<br>
<br>
#catalog id longname RA Decl type magnitude<br>
neocp 0 A106yEM 9.8501 -37.3746 255 17.3<br>
neocp 1 ZFA1276 12.9752 19.5189 255 20.9<br>
neocp 2 ZFA142F 16.1963 17.7824 255 20.4<br>
neocp 3 ZFA13B2 15.2812 16.1363 255 20<br>
neocp 4 ZFA1343 14.0707 13.71 255 18.5<br>
<br>
.....<br>
<br>
Source code is at <a href="http://functional.domains/kstars/" rel="noreferrer" target="_blank">http://functional.domains/ksta<wbr>rs/</a> . There is apparently object type for asteroids since kstars knows the ephemerides, right? For this particular page, one does not really need to know much more than that the NEO is listed on it and thus help is needed, I tend to think. The magnitude is the most important parameter so the user can decide if the object is likely to be visible with the telescope and seing conditions. And then the user retrieves online the ephemerides for the objects of interest. For other lists, one may be tempted to want to know a bit morem i.e. more than the catalog is currently prepared for.<span class=""><br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
But we're getting our astroid data from JPL and not MPC, so that's the problem here.<br>
</blockquote>
<br></span>
To the best of my little understanding of the whole process, the neocp are not part of the catalogs, yet, so this should be fine wrt redundancy.<br>
<br>
I am too new with this all to make any judgement on how likely it is to expect differences/inconsistencies for numbered objects between the institutions' generated web sites and what kstars computes.<span class=""><br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Perhaps we can support more than one source of data.<br>
</blockquote>
<br></span>
This would be nice. Another list that I would like to see is<br>
<br>
<a href="https://www.minorplanetcenter.net/iau/NEO/LastObsNEO.html" rel="noreferrer" target="_blank">https://www.minorplanetcenter.<wbr>net/iau/NEO/LastObsNEO.html</a><br>
<br>
The MPC also offers a text file of that content which I happily also transform.<br>
<br>
Maybe it would help to introduce the concept of temporary validity of such star data. For any conflicting information the data in kstars should be superior I tend to think since it can determine the asteroidal positions for any time, right? Just for objects unknown to kstars one would like to see that data added. Extra information on the type of asteroid (hazardous or not, ...) and when it was last found would be nice to address, too.<br>
<br>
Many thanks and regards,<br>
<br>
Steffen<div class="HOEnZb"><div class="h5"><br>
<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
<br>
On Fri, Mar 16, 2018 at 5:04 PM, Steffen Möller <<a href="mailto:steffen_moeller@gmx.de" target="_blank">steffen_moeller@gmx.de</a> <mailto:<a href="mailto:steffen_moeller@gmx.de" target="_blank">steffen_moeller@gmx.de</a><wbr>>> wrote:<br>
<br>
Hello again,<br>
<br>
On 3/13/18 9:50 AM, Steffen Möller wrote:<br>
<br>
Dear KStars-Team,<br>
<br>
There are multiple web sites out there that support amateur<br>
astronomers with the prioritization of their asteroidal<br>
observations. I mean, there is no chance for kstars to know<br>
this offline since only the MPC knows when a newly reported<br>
asteroid needs a confirmation. These are somewhat tricky at<br>
times in that even when you are granted the opportunity to<br>
specify the geographic location of your telescope, these do<br>
not necessarily state the exact time at which it is available<br>
(which you need to ask for the ephemerides in a second step)<br>
or the object is so low above the horizon that one would shy<br>
away from it. So, I'd very much like to see these dynamically<br>
created web sites auto-feed my wish list and fall back to the<br>
comfort of kstars.<br>
<br>
Would that be desirable? If so, then I propose to contact the<br>
provider(s) of these web sites about the degree they want to<br>
support any such project e.g. by a XML/JSON version of their<br>
output if they don't have it already or the parsing could be a<br>
first code contribution of mine. These sites also differ in<br>
the extra information these offer about the asteroid. Once<br>
could such also consider to extend the data model that<br>
represents asteroids in kstars with such dynamic information.<br>
To mind comes the date at which the asteroid was last observed.<br>
<br>
Please kindly instruct me about what I should do towards any<br>
such development.<br>
<br>
<br>
I received a reply by Valentin who suggested to import such files<br>
manually. I was not ultimately happy about that suggestion, I must<br>
admit, since to me it was important to see the workflow as a whole<br>
somehow represented from within kstars. But he may have a point.<br>
The MPC offers both XML and json files here<br>
<a href="https://minorplanetcenter.net/data" rel="noreferrer" target="_blank">https://minorplanetcenter.net/<wbr>data</a><br>
<<a href="https://minorplanetcenter.net/data" rel="noreferrer" target="_blank">https://minorplanetcenter.net<wbr>/data</a>> and the<br>
<a href="http://www.minorplanetcenter.net/Extended_Files/neocp.json" rel="noreferrer" target="_blank">http://www.minorplanetcenter.n<wbr>et/Extended_Files/neocp.json</a><br>
<<a href="http://www.minorplanetcenter.net/Extended_Files/neocp.json" rel="noreferrer" target="_blank">http://www.minorplanetcenter.<wbr>net/Extended_Files/neocp.json</a>> in<br>
particular seems of interest to me.<br>
<br>
So, I'll then prepare a script to download that file, pimp it for<br>
an import to kstars and report about it here.<br>
<br>
Steffen<br>
<br>
<br>
</blockquote>
</div></div></blockquote></div><br></div>