-
Notifications
You must be signed in to change notification settings - Fork 4
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
robustness to relational assumptions #89
Comments
A superficial fix for the start of some of the issues here is in this remote commit. That at least introduces an initial degree of robustness that I think should be present, although of course this has effects that will still need to be processed downstream because the resultant table will have empty There are also of course larger issues at play. I do concur with your general assumptions / visions up until now that the It does not, however, solve a coupla larger issues.
? I need that vision to really be able to work towards a solution here. |
They are randomly generate UIDs, no two will ever be the same (though SC0 ought to be, with some caveats around coordinate precision/identity). identical(SC(minimal_mesh), SC(minimal_mesh))
# [1] FALSE
set.seed(10)
x <- SC(minimal_mesh)
set.seed(10)
identical(x, SC(minimal_mesh))
[1] TRUE |
Oh yeah, stupid me, of course. Ta! Oh no, but hey, this is going to affect the |
There is a missing |
silicate is currently very naive in what it tries to do, and if there's a disconnected between the set of
object$object_
andobject$object_link_edge
then conversions toSC0
and so on will fail (trySC0(x)
).Assuming:
we can get around both of these, by filtering out parents that don't get reference, and ignoring links that go nowhere - but there'll need to be some kind of formalism around this.
Reprex for a given example from osmdata_sc:
Created on 2018-11-27 by the reprex package (v0.2.1)
The text was updated successfully, but these errors were encountered: