[postgis-devel] breaking changes in varInt code and twkb

Sandro Santilli strk at keybit.net
Fri Aug 22 22:24:09 PDT 2014


On Sat, Aug 23, 2014 at 12:03:11AM +0200, Nicklas Avén wrote:
> Sandro
> 
> in r12907 I did the switch to passing around **buf instead of *buf in
> twkb and varint. That affects all the varInt types. I don't think you
> have committed any code relying on varInt yet though. Right?

Not in trunk, but I have it in a fork:
https://github.com/strk/postgis/blob/mvt/liblwgeom/lwout_vt.c

> I couldn't see any performance difference, but it gets a little cleaner
> and is the first step to clean up more in all the values thrown around
> in the twkb code.
> 
> In the same commit I also added an option for including the twkb-size.
> That breaks any twkb clients out ther. But I suspect I rule all of them
> so far so it shuldn't be a big problem.
> 
> The sizes is an interesting option because it makes it possible to scan
> large files by jumping from geometry to geometry without actually
> decoding them.
> 
> In that way the deoding can be distributed to many threads.
> I have done some testing with ditributing the decoding to some
> webworkers and it seems to work great. 

Great!

--strk; 

 ()  ASCII ribbon campaign  --  Keep it simple !
 /\  http://strk.keybit.net/rants/ascii_mails.txt  



More information about the postgis-devel mailing list