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
in order to simplify the processing and reduce i/o for clients of the API
The text was updated successfully, but these errors were encountered:
/point already has this? :) http://mapit.mysociety.org/point/27700/400000,300000.html?type=MTD
/point
Sorry, something went wrong.
Can add for /postcode to reduce i/o a bit as you say, but I don't think it will simplify any processing that I can think of.
/postcode
[…] I don't think it will simplify any processing that I can think of.
Usually downstream applications that use the API are only interested in some of the area types. So usually they would:
… before doing any further work on them.
Adding a type parameter would make 2. unnecessary. I’d vote for it to allow for a list of types though (ie. ?type=CCG,SHB,…).
?type=CCG,SHB,…
No branches or pull requests
in order to simplify the processing and reduce i/o for clients of the API
The text was updated successfully, but these errors were encountered: