<p>It appears that you are doing a simple parallax calculation, using a baseline obtained from the Earth's rotation over an hour. You appear to be neglecting the most significant change, the motion of the comet.</p>

<p>If you plot the position of C/2019 Y4 in SkySafari, you will see that around this date the comet's location against the star background shifts about 37 arc minutes per day, or a bit over 1.5 arc minutes per hour. The location is based on the orbital elements of the comet <a href="https://www.minorplanetcenter.net/mpec/K20/K20C76.html" rel="nofollow noreferrer">(MPEC 2020-C76)</a>, but also includes the effect of the Earth moving in its orbit, as mentioned in the comments.</p>

<p>There is no simple way of determining the distance of a solar system object from two position measurements alone. A rough estimate of the orbital elements requires at least three position and time measurements; the MPC orbital elements referenced above are based on many observations over several months.</p>

CC BY-SA 4.0
2020-04-07T18:08:52.557Z
I did mention that I know the comet is also moving, but I thought over the time of an hour it wouldn't have so much of an effect to put me too far off. If you look at my edit, I did take the comet into accoutn and re-calculate
MCG
CC BY-SA 4.0
2020-04-07T18:11:26.183Z
Saying that, +1 for the tips on how to get better measurements. I was just seeing if I could do it!
MCG
CC BY-SA 4.0
2020-04-07T19:18:44.290Z
I don't know how you tried to compensate for the comet's motion, but if you are still doing a parallax calculation, where is the apex of your triangle?
amateurAstro
CC BY-SA 4.0
2020-04-07T20:24:37.423Z
I didn't compensate for the comet's motion. I was hoping over the course of an hour at that distance it wouldn't make too much of a difference. The Apex I suppose would have been the location of the comet during the first observation
MCG
CC BY-SA 4.0
2020-04-07T21:21:57.987Z
Ok. I was responding to your comment that you "took the comet into account and re-calculate." Knowing the correct distance from SkySafari, you can check that the actual parallax is about 2 orders of magnitude smaller than the comet motion you neglected.
amateurAstro
CC BY-SA 4.0
2020-04-08T07:54:30.973Z
Ahhh, whoops, that was a mis-type! I meant the movement of Earth. That was more a response to a different comment lol. Apologies for that.
MCG
CC BY-SA 4.0
2020-04-07T18:03:46.220Z
2020-04-07T18:03:46.220Z
amateurAstro
<p>The issue that you have is that</p>

<ol>
<li>You are moving. The biggest component of your velocity is the orbit of the Earth around the sun (about 30km/s).  The Earth is also rotating, and this, of course makes all the stars move across the sky, but they all move together. Your motion due to the rotation of the earth is probably less than 0.3km/s</li>
<li>The comet is moving.  It is in an elliptical orbit around the sun and is moving at orbital speeds (10s of km/s)</li>
<li>You only have two observations and they are very close together in time. </li>
</ol>

<p>Because the comet is moving at a similar speed to the Earth, you would need to determine the orbit of the comet, you can't find only its distance.  Orbital determination requires a minimum of three observations, and for most mortals, you need a software package to do the calculations for you (unless you are Carl Fredrick Gauss, of course)</p>

<p>To accurately determine the orbit you should get a series of observations over a longer period of time and use something like <a href="https://www.projectpluto.com/find_orb.htm" rel="nofollow noreferrer">find_orb</a> to determine the orbit.</p>

CC BY-SA 4.0
2020-04-07T18:13:40.950Z
Thanks for the response. I was able to get within 10% once I decided to do pixel counting between the stat and finish position of the comet and take the angular separation from that. So I'm gonna take it as a win there! I understand I'll never get it accurate, but was hoping to get something approximate. I know there were a lot of things I didn't factor in, which I did try to make clear in the post, but I hoped they wouldn't make a huge difference
MCG
CC BY-SA 4.0
2020-04-07T18:14:19.690Z
Unfortunately, England doesn't have clear skies too often so these opportunities to do this are few and far between!
MCG
CC BY-SA 4.0
2020-04-07T21:25:08.880Z
Same here. I have only had two decent views of C/2019 Y4, and one observation where I might have barely seen it, in the past month. Last night was hazy with a near full Moon, so there was no chance.
amateurAstro
CC BY-SA 4.0
2020-04-07T18:10:02.977Z
2020-04-07T18:10:02.977Z
James K
<p>SO, I decided I would take some pictures of the comet C/2019 Y4 last night. Afterwards, I thought I would try and do a rough estimation of distance based on my observations. I don't have any fancy measuring tools, so a few approximations were made, but my result was way off. I've clearly done something wrong and was hoping someone could point out where I have gone wrong and correct me. </p>

<p>So, I basically layered my first picture over the second in photoshop and marked the start and end position over the course of 1 hour. </p>

<p><a href="https://i.sstatic.net/HXwDk.jpg" rel="nofollow noreferrer"><img src="https://i.sstatic.net/HXwDk.jpg" alt="enter image description here"></a></p>

<p>I apologise for the poor photo, the exposures were short and I haven't done any processing as I was only interested in the position. </p>

<p>So,to me, it looks like it has moved approximately he same distance as the 2 stars to the right. These are TYC 4360-0254-1 and TYC 4360-1679-1 according to Sky Safari Pro.</p>

<p>I used the measurement tool in the app to measure the distance in arc-minutes, which gave me 1'55.1"</p>

<p>I converted this into degrees using Google, which gave me 0.0258333333 degrees. </p>

<p>I then decided to work out the approximate distance between my start and end points by using my latitude to work out the speed the earth was rotating (cos(latitude) x 1670) which I found <a href="https://image.gsfc.nasa.gov/poetry/ask/a10840.html" rel="nofollow noreferrer">HERE</a>. </p>

<p>My latitude is approx 50.82N, so I got my speed at 1055.04km. I used that as a distance. I now have a triangle with a base of 1055.04km and a top angle of 0.02583 degrees. </p>

<p>I turned this into a right-angle triangle by putting a line down the middle. I can now work out all 3 angles. I have 90, 0.010129 (half the original angle) and 89.987 (90-0.010129) I also have an opposite, adjacent and hypotenuse. I only know the adjacent which is half my original distance (527.52km), and I want to find the Opposite.</p>

<p>Using SOHCAHTOA, I can say tan(89) = opp/adj, thus opp = 527.52 x tan(89.987) which gives me 2,324,974.545km. </p>

<p>Sky safari gives a distance of 153.1 million km.</p>

<p>So where did I go wrong? Was it because of poor approximations? I know that the linear distance for the adjacent side isn't quite accurate because of earth curve, and I know the comet was also moving, and I know my measurement of the start and end position wasn't too accurate, but I was hoping to at least get within 10%, so I think I must have gone wrong somewhere in my method, rather than poor approximations.</p>

<p>I do hope I have put enough effort in for this to be considered a good question. I have tried re-measuring and double checking, but if there is any other info people need, then by all means, ask and I'll do what I can</p>

<p><strong>EDIT</strong></p>

<p>Because of the comment by barrycarter, I realised I had forgotten the movement of earth itself. As this is approximately 107207km/h, I included this in my calculations and ended up overshooting and getting 238,577,507km. </p>

<p>So, I made tiny adjustments to my parallax angle, and if I change this slightly, then I get very different answers. </p>

<p>Based on that, is it possible my crude measurement of the parallax angle is to blame?</p>

CC BY-SA 4.0
2020-04-07T14:34:34.283Z
I cant help with the question, but it's nice to see people having a go at things like this. Plus, I think it's a well written question, easy to understand and follow. I hope you get an answer as I'd be interested to try this myself!
Curious
CC BY-SA 4.0
2020-04-07T15:16:50.527Z
@barrycarter Ahhh! I forgot to include the movement of Earth too! but would it make much difference? I also just need distance travelled, rather than knowing my exact start positions
MCG
CC BY-SA 4.0
2020-04-07T15:30:42.933Z
@barrycarter I took your comment into account and have updated the question
MCG
CC BY-SA 4.0
2020-04-07T17:35:20.833Z
@barrycarter if you are quite confident in that, and believe I have the right method, then by all means write an answer and explain the reasoning behind the angle change, I'll happily upvote it and see if anyone else has any other answers
MCG
<distances><comets>
Calculating distance of comet C/2019 Y4 (ATLAS)
MCG
# Calculating distance of comet C/2019 Y4 (ATLAS)

(Asked by: username_0 on 2020-04-07)

SO, I decided I would take some pictures of the comet C/2019 Y4 last night. Afterwards, I thought I would try and do a rough estimation of distance based on my observations. I don't have any fancy measuring tools, so a few approximations were made, but my result was way off. I've clearly done something wrong and was hoping someone could point out where I have gone wrong and correct me.

So, I basically layered my first picture over the second in photoshop and marked the start and end position over the course of 1 hour.

[![enter image description here](https://i.sstatic.net/HXwDk.jpg)](https://i.sstatic.net/HXwDk.jpg)

I apologise for the poor photo, the exposures were short and I haven't done any processing as I was only interested in the position.

So,to me, it looks like it has moved approximately he same distance as the 2 stars to the right. These are TYC 4360-0254-1 and TYC 4360-1679-1 according to Sky Safari Pro.

I used the measurement tool in the app to measure the distance in arc-minutes, which gave me 1'55.1"

I converted this into degrees using Google, which gave me 0.0258333333 degrees.

I then decided to work out the approximate distance between my start and end points by using my latitude to work out the speed the earth was rotating (cos(latitude) x 1670) which I found [HERE](https://image.gsfc.nasa.gov/poetry/ask/a10840.html).

My latitude is approx 50.82N, so I got my speed at 1055.04km. I used that as a distance. I now have a triangle with a base of 1055.04km and a top angle of 0.02583 degrees.

I turned this into a right-angle triangle by putting a line down the middle. I can now work out all 3 angles. I have 90, 0.010129 (half the original angle) and 89.987 (90-0.010129) I also have an opposite, adjacent and hypotenuse. I only know the adjacent which is half my original distance (527.52km), and I want to find the Opposite.

Using SOHCAHTOA, I can say tan(89) = opp/adj, thus opp = 527.52 x tan(89.987) which gives me 2,324,974.545km.

Sky safari gives a distance of 153.1 million km.

So where did I go wrong? Was it because of poor approximations? I know that the linear distance for the adjacent side isn't quite accurate because of earth curve, and I know the comet was also moving, and I know my measurement of the start and end position wasn't too accurate, but I was hoping to at least get within 10%, so I think I must have gone wrong somewhere in my method, rather than poor approximations.

I do hope I have put enough effort in for this to be considered a good question. I have tried re-measuring and double checking, but if there is any other info people need, then by all means, ask and I'll do what I can

**EDIT**

Because of the comment by barrycarter, I realised I had forgotten the movement of earth itself. As this is approximately 107207km/h, I included this in my calculations and ended up overshooting and getting 238,577,507km.

So, I made tiny adjustments to my parallax angle, and if I change this slightly, then I get very different answers.

Based on that, is it possible my crude measurement of the parallax angle is to blame?

**Tags:** distances, comets

> **Comments:**
> **username_1**: I cant help with the question, but it's nice to see people having a go at things like this. Plus, I think it's a well written question, easy to understand and follow. I hope you get an answer as I'd be interested to try this myself!  
> **username_0**: @barrycarter Ahhh! I forgot to include the movement of Earth too! but would it make much difference? I also just need distance travelled, rather than knowing my exact start positions  
> **username_0**: @barrycarter I took your comment into account and have updated the question  
> **username_0**: @barrycarter if you are quite confident in that, and believe I have the right method, then by all means write an answer and explain the reasoning behind the angle change, I'll happily upvote it and see if anyone else has any other answers  

---

## 2 answers

### Answer by username_2 on 2020-04-07. Score: 4

It appears that you are doing a simple parallax calculation, using a baseline obtained from the Earth's rotation over an hour. You appear to be neglecting the most significant change, the motion of the comet.

If you plot the position of C/2019 Y4 in SkySafari, you will see that around this date the comet's location against the star background shifts about 37 arc minutes per day, or a bit over 1.5 arc minutes per hour. The location is based on the orbital elements of the comet [(MPEC 2020-C76)](https://www.minorplanetcenter.net/mpec/K20/K20C76.html), but also includes the effect of the Earth moving in its orbit, as mentioned in the comments.

There is no simple way of determining the distance of a solar system object from two position measurements alone. A rough estimate of the orbital elements requires at least three position and time measurements; the MPC orbital elements referenced above are based on many observations over several months.

> **Comments:**
> **username_0**: I did mention that I know the comet is also moving, but I thought over the time of an hour it wouldn't have so much of an effect to put me too far off. If you look at my edit, I did take the comet into accoutn and re-calculate  
> **username_0**: Saying that, +1 for the tips on how to get better measurements. I was just seeing if I could do it!  
> **username_2**: I don't know how you tried to compensate for the comet's motion, but if you are still doing a parallax calculation, where is the apex of your triangle?  
> **username_0**: I didn't compensate for the comet's motion. I was hoping over the course of an hour at that distance it wouldn't make too much of a difference. The Apex I suppose would have been the location of the comet during the first observation  
> **username_2**: Ok. I was responding to your comment that you "took the comet into account and re-calculate." Knowing the correct distance from SkySafari, you can check that the actual parallax is about 2 orders of magnitude smaller than the comet motion you neglected.  
> **username_0**: Ahhh, whoops, that was a mis-type! I meant the movement of Earth. That was more a response to a different comment lol. Apologies for that.  

---

### Answer by username_3 on 2020-04-07. Score: 3

The issue that you have is that

1. You are moving. The biggest component of your velocity is the orbit of the Earth around the sun (about 30km/s). The Earth is also rotating, and this, of course makes all the stars move across the sky, but they all move together. Your motion due to the rotation of the earth is probably less than 0.3km/s
2. The comet is moving. It is in an elliptical orbit around the sun and is moving at orbital speeds (10s of km/s)
3. You only have two observations and they are very close together in time.

Because the comet is moving at a similar speed to the Earth, you would need to determine the orbit of the comet, you can't find only its distance. Orbital determination requires a minimum of three observations, and for most mortals, you need a software package to do the calculations for you (unless you are Carl Fredrick Gauss, of course)

To accurately determine the orbit you should get a series of observations over a longer period of time and use something like [find\_orb](https://www.projectpluto.com/find_orb.htm) to determine the orbit.

> **Comments:**
> **username_0**: Thanks for the response. I was able to get within 10% once I decided to do pixel counting between the stat and finish position of the comet and take the angular separation from that. So I'm gonna take it as a win there! I understand I'll never get it accurate, but was hoping to get something approximate. I know there were a lot of things I didn't factor in, which I did try to make clear in the post, but I hoped they wouldn't make a huge difference  
> **username_0**: Unfortunately, England doesn't have clear skies too often so these opportunities to do this are few and far between!  
> **username_2**: Same here. I have only had two decent views of C/2019 Y4, and one observation where I might have barely seen it, in the past month. Last night was hazy with a near full Moon, so there was no chance.  

---

