I have learned a great deal from the act of daily coding and treating code like a creative medium without any pressure on what I make or why. I found myself tackling hard challenges so I wouldn't get bored and learning a variety of new tricks to help make the sketching easier. I wrote about the process here:
I'll take a look - thanks! note that we do limit the line somewhat since the best matches are curves, lines, etc and self intersecting lines don't match very well.. The best kinds of lines are like the ones in this video (https://www.youtube.com/watch?v=w6-LK9BOVTA)
sorry! this is a bug based on how many events the mouse is firing and I've open an issue for it -- I will take a look at the app with a gaming mouse and work on a fix.
thanks -- do you know what graphics card that is? also you can try enabling "Override software rendering list" in chrome://flags/ -- I don't have a great handle on what gpus are blacklisted, but I know there are some that are.
putting this in the address bar can give you a lot of info as well "chrome://gpu"
which gives a value for how close to polylines are (it normalizes them and does some distance calculations)
the way the vp tree works is you provide a set of data and a metric for distance (in my case, the data was the polylines and the metric was from dollar) and it computes the structure. As long as the metric observes some basic principles (I think it's called triangle inequality) the spatial division will work and you can do a fast search for nearest neighbors.
no it's a really good question! I think this just has to do with the line detection algorithm and it tending to find more curves than sharp angle lines -- this is what the matches look like when you draw a Z:
they are not as good as when you draw a curve and I think it's just trimming based on general poor matches. I've found if I round the Z or make the angle less extreme I can get better results.
the matching is based on the input (lines from the line detection) and we do some tricks to try to get better matches if the results aren't great. One trick is for matches that aren't super great, we start to trim the line slight from the start so if the first pass is a bad match, we try 95% of the line (ie, the last 95%) then trim is some more, etc.
another thing to note is that the app progressively loads data in the background so you get better results after the first minute or so once all the data is loaded -- the app launches with only 20% of the overall data.
also another tip -- you can click on the city name in the left corner to load the same view in google earth (if you are curious about what you are looking at!)
https://www.instagram.com/zach.lieberman/
I have learned a great deal from the act of daily coding and treating code like a creative medium without any pressure on what I make or why. I found myself tackling hard challenges so I wouldn't get bored and learning a variety of new tricks to help make the sketching easier. I wrote about the process here:
https://medium.com/@zachlieberman/daily-sketches-2016-28586d...
I think daily activities are the best for growing -- short, concentrated, and limited in scope and can fit with the rest of your life.