Bug: Incorrect latitude and longitude

[jcsmithhere]

I found an example where the latitude and longitude reported in the bolide data frame is not correct:

bdf.iloc[1463]:
datetime                                    2024-09-19 09:52:50.049000+00:00
longitude                                                         -95.642914
latitude                                                          -11.445276

and yet:

bdf.attachments[1463]:
[{'location': {'coordinates': [-113.73348999023438, -27.126758575439453],
...]

The values in the "attachments" is correct. This is the webpage for this bolide:
https://neo-bolide.ndc.nasa.gov/#/eventdetail/66edcf4c6e2a8c48a0c0adf9?ref=main

Looking at the website, it becomes immediately clear what is going on. This event has an extreme outlier datum at (-77.6, 4.2). The reported longitude and latitude is the mean, whereas the values reported in the attachments (which comes from the pipeline run) is the median.

I think we need to change the code that generates the latitude and longitude to use the median values.

I think the issue with the extreme outlier being added has been fixed as of pipeline release 1.0.0. But this detection is from a previous pipeline release.

[jcsmithhere]

The mean latitude and longitude is shown on the website page:

https://neo-bolide.ndc.nasa.gov/service/event/66edcf4c6e2a8c48a0c0adf9

So, this is not really a bug with the bolides package. The website page above displays both the mean and median latitude and longitude (in the black banner at top and then again right above the figure). So, the website is viewing both values but reporting the mean in the json file above.

This bolides package should take the correct value and ignore the mean values. It's a separate task to fix the website data.