satellite command

[0x5c]

• [ ] Sanitise that sat name

Satellites must match the satellite name from nasabare.txt e.g. AO-91 or ISS

• [ ] Filter for valid grids

Locations can be 4-12 character maidenhead grid squares

[classabbyamp]

Set the request type to application/json or set ?json=true to get json results instead of rendered pages or images.

We should be able to construct embeds for this

example: https://www.satmatch.com/satellite/FO-29/obs1/CN87UO/obs2/EN61ev40?duration_hrs=72&json=true

[classabbyamp]

is being bumped to a later version

Notes:

• how to download nasabase.txt?
• add argument for number of hours
• ask K5EM about adding peak angle of pass to JSON API
• possible embed layout (maybe remove end, only show start, duration, and peak):

[classabbyamp]

in progress work on this command is in the branch sat-cmd

[0x5c]

It would be somewhat easy to filter and match names from the provided nasabare.txt list. Worse part is parsing the file.

[classabbyamp]

at this point, I think it would be better to switch to using n2yo as our data source.

[0x5c]

So a full rewrite? Does ny2o support all the feature we used, and will it require gridtools?

[classabbyamp]

ya pretty much a full rewrite. not like there was much useful code there anyways, with how old it is. n2yo should be able to show things like max elevation and pass lengths. gridtools possibly required, but it's a super-simple integration, especially whe it's already used in the bot

[0x5c]

I don't really remember the original sat command, is there any info it had that ny2o does not? As for gridtools, would allow for accepting both squares and lat/long, and even do conversion if wrapped in a converter

[classabbyamp]

I think n2yo has a superset of info VS sat match. good idea on the gridtools

[0x5c]

Let's switch then New issue to start fresh?

[classabbyamp]

big issue with N2YO: only 1 observer for passes. we should bug the satmatch author again instead.