I found a bug while doing some large geocoding projects regarding the "flipped" status. On some edges this caused a geocode to be placed a far-cry from where it should have been.
The bug is how the gem was handling the return of the "flipped" value from SQLite. Since SQLite is typeless it was returning the string but not evaluating correctly in ruby. I forced a ruby type-cast to integer using "to_i" and then looked for the value to be 1 to be truly flipped.
The other change is removing the notice about the Excensus branch. I'm trying to keep things a bit cleaner and culled the branch. That makes the notice in the README pretty irrelevant.
Hi Folks,
I found a bug while doing some large geocoding projects regarding the "flipped" status. On some edges this caused a geocode to be placed a far-cry from where it should have been.
The bug is how the gem was handling the return of the "flipped" value from SQLite. Since SQLite is typeless it was returning the string but not evaluating correctly in ruby. I forced a ruby type-cast to integer using "to_i" and then looked for the value to be 1 to be truly flipped.
The other change is removing the notice about the Excensus branch. I'm trying to keep things a bit cleaner and culled the branch. That makes the notice in the README pretty irrelevant.