Talk:List of asteroid close approaches to Earth in 2017
Latest comment: 4 years ago by AlanM1 in topic Table improvement
 | This article is rated List-class on Wikipedia's content assessment scale. It is of interest to the following WikiProjects: | |||||||||||||||||||||||
| ||||||||||||||||||||||||
.jpg){kind=small}
Table improvement
editI'd like to improve display space usage and reduce repetition in tables. E.g., List of asteroid close approaches to Earth in 2017#Timeline of known close approaches less than one lunar distance from Earth in 2017 has this:
| Date of closest approach |
Date discovered |
Object | Nominal geocentric distance (AU)[a] |
Nominal geocentric dist. (LD) |
Size (m) (approx.) |
(H) (mag) |
Closer to Moon? |
|---|---|---|---|---|---|---|---|
| 2017-01-09 | 2017-01-07[1] | 2017 AG13 | 0.00139 AU (208,000 km; 129,000 mi) | 0.54 | 13–41 | 26.1[2] | |
| 2017-01-25 | 2017-01-20[3] | 2017 BX | 0.00178 AU (266,000 km; 165,000 mi) | 0.69 | 5–18 | 28.0[4] | |
| 2017-01-30 | 2017-01-29[5] | 2017 BH30 | 0.000347 AU (51,900 km; 32,300 mi) | 0.13[b] | 4–12 | 28.8[6] | |
| 2017-02-02 | 2017-01-30[7] | 2017 BS32 | 0.00109 AU (163,000 km; 101,000 mi) | 0.42 | 7–24 | 27.3[8] | |
| 2017-02-23 | 2017-02-21[9] | 2017 DG16 | 0.000920 AU (137,600 km; 85,500 mi) | 0.36 | 3–9 | 29.3[10] | Yes |
| ... | |||||||
which I'd like to improve to:
| Date of closest approach |
Date discovered |
Object | Nominal geocentric distance[c] | Size (m) |
H | Closer to Moon? | |||
|---|---|---|---|---|---|---|---|---|---|
| AU | 000s km |
000s mi |
LD | ||||||
| 2017-01-09 | 2017-01-07[11] | 2017 AG13 | 0.00139 | 208 | 129 | 0.54 | 13–41 | 26.1[2] | |
| 2017-01-25 | 2017-01-20 | 2017 BX | 0.00178 | 266 | 165 | 0.69 | 5–18 | 28.0 | |
| 2017-01-30 | 2017-01-29 | 2017 BH30 | 0.000347 | 51.9 | 32.3 | 0.13 | 4–12 | 28.8 | |
| 2017-02-02 | 2017-01-30 | 2017 BS32 | 0.00109 | 163 | 101 | 0.42 | 7–24 | 27.3 | |
| 2017-02-23 | 2017-02-21 | 2017 DG16 | 0.000920 | 137.6 | 85.5 | 0.36 | 3–9 | 29.3 | Yes |
| ... | |||||||||
If there were such a thing as a μAU in common usage, that column could come down to 4 digits, and be easier for humans to parse as integers ~100–2000. Or maybe label it "10-6 AU"? Note, BTW, that the sorting of that column doesn't currently work, probably because of the converted values. A nice template could be created for the rows to eliminate alot of the wiki markup currently required. —[AlanM1 (talk)]— 09:55, 31 March 2020 (UTC)
- I think it is better when the AU conversion is done by an automated formula as people are often wrong. -- Kheider (talk) 14:52, 31 March 2020 (UTC)
- @Kheider: Yes, that's my intent. With the source data from the SBDB in AU, a row might look like:
{{CA row |app_date=2017-01-09 |close_date=2017-01-07 |name_year=2017 |name_2=AG |name_3=13 |link=y |sbdb_id=3766433 |au=0.001395 |size=13–41 |mag=26.1 |bgcolor= |closer= }}- It would calculate the MPC and SBDB source refs and the distances in km, mi, and LD. —[AlanM1 (talk)]— 16:47, 31 March 2020 (UTC)