-
-
Notifications
You must be signed in to change notification settings - Fork 89
New issue
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
Unexpected outcome when using QL query and build=False
#93
Comments
build=False
build=False
and leave responseformat
to be default
build=False
and leave responseformat
to be defaultbuild=False
That is confusing, you're right. Will address in next release unless you beat me to it with a PR ✊ |
Would you propose to detect the format from the raw query? In that case we'd need to assume that the query always starts with |
I prefer the former option, users are required to write a complete and valid overpass QL query if they set |
Makes sense. We would then ignore |
It's one option, or should we keep the content_type checking part and return appropriate Python object? if
|
I have pushed a branch, see if it is fine. :) |
It looks like the bug re-appear again.
Output:
|
It is expected the following codes should produce the same output, but it turns out they didn't.
Code 1
Output:
Code 2
Output:
The reason should be the default value of
responseformat
(geojson). Although my query said I want a json, the.get()
method still convert it to geojson (default responseformat). To obtain the desired output, I have to addresponseformat='json'
.This looks redundant. Not sure if it is what you desired.
The text was updated successfully, but these errors were encountered: