[FIXED] Error when trying to spawn in Venezuelan Satellites VRSS-1/2

[EchoBravoPro]

Detailed the issue here with a screenshot:
https://github.com/PygmalionOfCyprus/cm ... ssues/3009

A save won't really do much good here, just try spawning them in on any scenario and you'll get the same error linked above.

Build is 1307.3 on Windows 10 Windows 10 Version 22H2 for x64-based Systems (KB5019275).

[michaelm75au]

Seems to be something wrong with the TLE data for those satellites. Possibly the date in the data...

[KnightHawk75]

Seems to be something wrong with the TLE data for those satellites. Possibly the date in the data...

Seems to be something wrong with the TLE data for those satellites. Possibly the date in the data...

If it's TLE related, then it's because all those entries have have malformed lines.
Line 1 and 2 in both cases are malformed TLE's in db 498a (and I didn't look but probably a dbs back to when they were added or last touched). Also on those specific sats the data itself doesn't seem to match up what's available online atm but that's a different issue.

I'm using code tags below to hopefully preserve formatting\spacing is critical if copy pasta'ing.

According to celestrak...should be:
http://celestrak.org/NORAD/elements/gp.php?CATNR=38782
DBID 153 compid 1

Code: Select all

VRSS-1
1 38782U 12052A   23047.81931402  .00000925  00000+0  14005-3 0  9990
2 38782  97.6351  78.3458 0016756 245.5355 114.4161 14.76301419559935

What the database 498a has with malformation.

Code: Select all

1 38782U 12052A 22156.83624162 .00000415 00000-0 66572-4 0 9996
2 38782 97.6602 195.8534 0017217 358.9870 1.1289 14.76320388522162

DBID 153 compid 2
http://celestrak.org/NORAD/elements/gp.php?CATNR=42954

Code: Select all

VRSS-2                  
1 42954U 17060A   23047.80489713  .00002333  00000+0  33788-3 0  9996
2 42954  97.8209 115.3597 0019961  97.5567 262.7901 14.76897722288645

What the database 498a has including the malformation.

Code: Select all

1 42954U 17060A 22156.72705301 .00000474 00000-0 75166-4 0 9993
2 42954 97.8496 226.7180 0018080 202.2090 157.8330 14.76452772250859

Another example: Vene-Sat1 is wrong\malformed as well but I'll explain where\why which applies to all of those mentioned below.
DBID 152 compid 1
http://celestrak.org/NORAD/elements/gp.php?CATNR=33414

Code: Select all

VENESAT-1               
1 33414U 08055A   23047.84958962 -.00000004  00000+0  00000+0 0  9993
2 33414   2.6178  87.2028 0060493 163.1423 227.1356  0.99271739 52381

What the database has.

Code: Select all

1 33414U 08055A 22155.63594253 .00000101 00000-0 00000-0 0 9997
2 33414 1.9636 89.8494 0056786 154.0182 109.7958 0.99268978 49827

Explanation of where things ^ are malformed
Line 1:
-missing 2 extra spaces after 08055A (3 chars represent the launch pieces"A__" then the separator space).
-first derv of the mean ".00000101" should have leading space before the decimal or a sign.
-second derv of mean is missing the leading space, + sign or 0 in first position.
-BDragterm should have leading space,sign or 0.
- missing leading 0 or spaces for 4 digit element set .
Making those adjustments assuming the space or 0 or + signs are used it would be valid with checksum 7
Line 2:
- missing leading 2 spaces or 00 prior in inclination of "1.9636"
- missing leading space or 0 prior to right ascension of "89.8494"
- missing space or leading 0 in mean motion "0.9926..."
Making those adjustments assuming the space or 0 or space or + signs are used it would be valid with checksum 7
One example of what it should have (assuming you don't want to use celestrak values):

Code: Select all

1 33414U 08055A   22155.63594253  .00000101  00000-0  00000-0 0  9997
2 33414 001.9636 089.8494 0056786 154.0182 109.7958 00.99268978 49827

My guess is, someone copied from HTML formatted\displayed document where non-breaking spaces were not used to display the exact values and it screwed with the correct formatting...without validating first. I've done the same thing myself.



The following DataSatelliteOrbits ID|ComponentNumbers|missionname _ALL_ have malformed TLE entries (yes I checked all those with existing entries..at least I think I did lol):
111|2|SkySat C2
111|5|SkySat C5
111|12| SkySat C12
145|3 |BRO-3
145|4 |BRO-4
145|5 |BRO-5
145|6 |BRO-6
145|7 |BRO-7
146|1 |LUCH (OLYMP)
152|1 |VeneSat-1
153|1 |VRSS-1
153|2 |VRSS-2
154|1 |Pleiades Neo 3
154|2 |Pleiades Neo 4
155|1| CERES 1
155|2 |CERES 2
155|3 |CERES 3
160|1 |USA 314
160|2 |USA 338

Helpful Validators for DB maintainers to use before pasting into database:
https://ducktools.net/tle-validator/
https://www.vcalc.com/wiki/MichaelBartmess/TLE+Checksum

[Dimitris]

This has been fixed by the time of the current public build.