Object names with spaces are not exactly uncommon in the space-track catalog. In fact, just looking at the first few entries shows: 0 VANGUARD 1 1 00005U 58002B 21029.28808560 -.00000076 00000-0 -11346-3 0 9994 2 00005 34.2570 252.5344 1847877 288.6483 52.2921 10.84858932229781 0 VANGUARD 2 1 00011U 59001A 21029.82316623 .00000343 00000-0 18757-3 0 9993 2 00011 32.8666 285.4967 1467471 89.4624 287.3328 11.85740568643606 0 VANGUARD R/B 1 00012U 59001B 21029.61362424 .00000164 00000-0 81891-4 0 9992 2 00012 32.9013 279.6520 1666175 185.0152 173.1560 11.44390876305899
Even the example TLE at space-track ( https://www.space-track.org/documentation#tle ) has a space in it...
So... if the protocol you are using (or the code to handle it) does not handle object names with spaces correctly... maybe it's time for that protocol or code to be re-thought somewhat?
73 Mark VK5QI
On Thu, Feb 4, 2021 at 7:52 PM James Jipping jhjipping@gmail.com wrote:
Good Morning:
I recently wrote a Raspberry Pi application that uses the UDP transmission from SatPC32. Works like charm,. It selects the correct antenna (2M or 70cm) combos. It controls my crystal controlled WX receiver (auto selects the correct WX channel), selects the correct SDR / software setup for telemetry, etc.
Well, it worked like a charm until I encountered "OBJECT C" and "CAPE 3" in the elements. SatPC32's UDP uses a space as a data deliminator, so I get an error ( the satellite string has one too many pieces of data, 9 instead of 8) when SatPC323 starts to track one of these. That's OK. I just edit the keps file to read "OBJECT-C" and "CAPE-3" (which, by the way, is what it's called in all the literature). Well, it's NOT OK . It is pain in the neck. Every time I want to update my keps I have to remember to edit the file.
Do I have to live with this anomaly ? Or will the names become something without the space when they get their "official" designation?
Thank you, stay safe, Corvid free, and 73
Jim Jipping, W8MRR AMSAT #5512
Sent via AMSAT-BB(a)amsat.org. AMSAT-NA makes this open forum available to all interested persons worldwide without requiring membership. Opinions expressed are solely those of the author, and do not reflect the official views of AMSAT-NA. Not an AMSAT-NA member? Join now to support the amateur satellite program!
View archives of this mailing list at https://mailman.amsat.org/hyperkitty/list/amsat-bb@amsat.org To unsubscribe send an email to amsat-bb-leave(a)amsat.org Manage all of your AMSAT-NA mailing list preferences at https://mailman.amsat.org