Rocket model properties are not aligned across endpoints
See original GitHub issueThanks for an amazing API. I’m working on an iOS app that will consume more or less the whole thing 🚀
I’ve come across one peculiarity, however. On /rockets
the properties look like this:
{
"id": "falcon1",
"type": "Merlin A",
"name": "Falcon 1"
}
whereas on /launces
those properties are prepended with rocket_
like this:
{
"rocket": {
"rocket_id": "falcon1",
"rocket_type": "Merlin A",
"rocket_name": "Falcon 1"
}
}
This makes it a little more troublesome to make global model serialization.
Is there a reason for this misalignment? 🙂
Cheers 🙌
Issue Analytics
- State:
- Created 5 years ago
- Comments:22 (22 by maintainers)
Top Results From Across the Web
Monitoring ML models with Vertex AI | Google Cloud | Nov, 2022
This article, though is not about rockets. It is about machine learning models which you have already trained and launched or you are...
Read more >Responses section formatting - code and description not ...
In the Responses section, for each code, the text box containing the code description is vertically lower on the page than the code...
Read more >202439Orig1s000 Reviews - Accessdata.fda.gov
study arms and rivaroxaban vs. warfarin comparisons for these endpoints. The models estimated thrombotic and bleeding outcomes in ROCKET in ...
Read more >The best webpack configurations for React applications
If you've struggled to configure webpack for your React app, look no further. We cover both generic and specific config needs.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Also planning on making the endpoints a bit more REST friendly for v3. Currently these are the v2 endpoints:
https://api.spacexdata.com/v2/launches https://api.spacexdata.com/v2/launches/all https://api.spacexdata.com/v2/launches/latest https://api.spacexdata.com/v2/launches/next https://api.spacexdata.com/v2/capsules https://api.spacexdata.com/v2/rockets https://api.spacexdata.com/v2/launchpads https://api.spacexdata.com/v2/parts/cores https://api.spacexdata.com/v2/parts/caps https://api.spacexdata.com/v2/info https://api.spacexdata.com/v2/info/history https://api.spacexdata.com/v2/info/missions https://api.spacexdata.com/v2/info/roadster
Some are too nested, and some don’t accept any kind of query parameters. v3 will look like this:
https://api.spacexdata.com/v3/launches https://api.spacexdata.com/v3/launches/latest https://api.spacexdata.com/v3/launches/next https://api.spacexdata.com/v3/launches/upcoming https://api.spacexdata.com/v3/launches/past https://api.spacexdata.com/v3/dragons https://api.spacexdata.com/v3/rockets https://api.spacexdata.com/v3/launchpads https://api.spacexdata.com/v3/capsules https://api.spacexdata.com/v3/cores https://api.spacexdata.com/v3/info https://api.spacexdata.com/v3/history https://api.spacexdata.com/v3/missions https://api.spacexdata.com/v3/roadster https://api.spacexdata.com/v3/ships
Negligible performance difference, one example is live for rockets. https://api.spacexdata.com/v3/rockets