We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
https://colab.research.google.com/drive/1FiKF3qPnHhNQyGfvBu3LPDuN4J9h0_-M?usp=sharing AIMS is great but it's much faster to go through the APIs http://data.niassembly.gov.uk/plenary.asmx Annoyingly, when you request JSON/JSONP payloads, the reference links don't cascade (i.e. the link to the next level object will be the XML endpoint, not the JSON endpoint, even if your first level object request was the JSON one)
Ideally focusing on the plenary apis to provide vote/history/context data http://data.niassembly.gov.uk/
The text was updated successfully, but these errors were encountered:
No branches or pull requests
https://colab.research.google.com/drive/1FiKF3qPnHhNQyGfvBu3LPDuN4J9h0_-M?usp=sharing
AIMS is great but it's much faster to go through the APIs http://data.niassembly.gov.uk/plenary.asmx
Annoyingly, when you request JSON/JSONP payloads, the reference links don't cascade (i.e. the link to the next level object will be the XML endpoint, not the JSON endpoint, even if your first level object request was the JSON one)
Ideally focusing on the plenary apis to provide vote/history/context data http://data.niassembly.gov.uk/
The text was updated successfully, but these errors were encountered: