-
Notifications
You must be signed in to change notification settings - Fork 46
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
[BUG] Regression (?) in opq_osm_id()
#268
Comments
Thanks @agila5, I'll check it out next week. Looks indeed like some kinda 🐛, and there have been a few backend updates to opq functions lately, so you're likely right |
I just ran into this in an attempt to not map over queries and be kind to the overpass api ^^ The issue is this guard https://github.com/ropensci/osmdata/blob/main/R/opq.R#L426 Unless I missed something that check should be superfluous, happy to open a PR :) |
An easier workaround is:
|
Indeed if we ignore the guard clause and create the equivalent opq object it works fine:
I suspect the guard can be removed. @agila5 the failure with integers is expected, per the docs:
|
Thanks to @jmaspons for fixing this via PR linked above. |
Hi @mpadge! I want to report a possible regression in
opq_osm_id
. The following example (taken from?opq_osm_id
) fails with the current CRAN version:Created on 2022-03-10 by the reprex package (v2.0.1)
Session info
the github version:
Created on 2022-03-10 by the reprex package (v2.0.1)
Session info
but works with version 0.1.8:
Created on 2022-03-10 by the reprex package (v2.0.1)
Maybe it's intended, but I didn't find anything useful in the NEWS file.
Moreover, I notice that the following fails with a different error in the current CRAN version:
Created on 2022-03-10 by the reprex package (v2.0.1)
Session info
The text was updated successfully, but these errors were encountered: