Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Some Data Issues #1114

Open
aepryus opened this issue Jun 10, 2022 · 0 comments
Open

Some Data Issues #1114

aepryus opened this issue Jun 10, 2022 · 0 comments

Comments

@aepryus
Copy link

aepryus commented Jun 10, 2022

  • The video for Nilesat-301 is pointing to an audio version; here is the real video: https://youtu.be/UpCZu89zb5Y
  • The Nilesat-301 mission is missing its badge. I'm not sure where these are usually sourced, but: https://spacexnow.com/patches/spacex/Nilesat-301_thumb.png
  • Starlink v0.9 (mission CRS-14 reused capsule #79) is using a different Starlink badge as all the other Starlink missions. This one is notably bigger.
  • The block number of B1019 and B1020 are listed as '1' which is associated with 'v1.1', however wikipedia lists them as 'FT' which generally seems to be associated with block '2' in this data set.
  • More of a question than an issue, but wikipedia also says: "Since no data is provided, F9s listed as simply "FT" (Full Thrust) denote Blocks 1 to 3, while Block 4 is listed as "FT Block 4"". In this data set however, there is a distinction between block 2 and 3. How is this data determined?

Also, I'm currently using the following code to determine the booster version; is there perhaps a better way to accomplish this:

	var version: String {
		if booster == .falcon1 { return "" }
		else if booster == .falcon9 {
			if serial[1] == "0" { return "v1.0" }
			else if ["B1019", "B1020"].contains(serial) { return "FT" }
			else {
				switch block {
					case 1: return "v1.1"
					case 2: return "FT"
					case 3: return "FT"
					case 4: return "block 4"
					case 5: return "block 5"
					default: return  ""
				}
			}
		}
		return ""
	}
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant