<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content="text/html; charset=iso-8859-1" http-equiv=Content-Type>
<META name=GENERATOR content="MSHTML 10.00.9200.16618"></HEAD>
<BODY>
<DIV dir=ltr align=left><FONT color=#0000ff size=2 face=Arial><SPAN
class=524011214-16062013>Even if we go the extensions model with TWKB, would
like to see it managed in PostGIS proper just because I suspect it will need
direct dependency with liblwgeom (which is not a stable API) and which
pointcloud doesn't really have to contend with. So it would still be an
extra annoying compile to experiment with.</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT color=#0000ff size=2 face=Arial><SPAN
class=524011214-16062013></SPAN></FONT> </DIV>
<DIV dir=ltr align=left><FONT color=#0000ff size=2 face=Arial><SPAN
class=524011214-16062013>Nicklas correct me if I am wrong on
this.</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT color=#0000ff size=2 face=Arial><SPAN
class=524011214-16062013></SPAN></FONT> </DIV>
<DIV dir=ltr align=left><FONT color=#0000ff size=2 face=Arial><SPAN
class=524011214-16062013>Then I think it would follow the path of SFCGAL.
Except there isn't much reason to exclude it since it has no extra
dependencies aside from it isn't stable yet and not sure how well adopted it
would become.</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT color=#0000ff size=2 face=Arial><SPAN
class=524011214-16062013></SPAN></FONT> </DIV>
<DIV dir=ltr align=left><FONT color=#0000ff size=2 face=Arial><SPAN
class=524011214-16062013>Regina</SPAN></FONT></DIV><BR>
<DIV lang=en-us class=OutlookMessageHeader dir=ltr align=left>
<HR tabIndex=-1>
<FONT size=2 face=Tahoma><B>From:</B> postgis-devel-bounces@lists.osgeo.org
[mailto:postgis-devel-bounces@lists.osgeo.org] <B>On Behalf Of </B>Nicklas
Avén<BR><B>Sent:</B> Thursday, June 13, 2013 2:56 AM<BR><B>To:</B> Paul
Ramsey<BR><B>Cc:</B> PostGIS Development Discussion<BR><B>Subject:</B> Re:
[postgis-devel] TWKB in PostGIS, what do you think?<BR></FONT><BR></DIV>
<DIV></DIV>I think you are right Paul. That would make it possible to use also
on PostGIS 2.0 and 2.1 and also possible to release more frequent in the
beginning. I also realize that the interest from the client libraries is smaller
than I had hoped. So it would be stupid to put code in PostGIS that won't be
used. To get things fast I think some javascript guru need to look at the client
part and connect the parsing very close to the canvas drawing, to avoid all text
based javascript objects. /Nicklas 2013-06-13 Paul Ramsey wrote: There's no
great harm in including it, but it's more code to maintain that is pretty
prospective. Why not bundle up an extension against PostGIS? I was pleased with
how easy it was to do pointcloud_postgis as an extension that depended on both.
> >P > >-- >Paul Ramsey >http://cleverelephant.ca
>http://postgis.net > > >On Monday, June 10, 2013 at 1:40 PM,
Nicklas Avén wrote: > >> So, what i would like to ask is if PostGIS PSC
and dev community can >> decide that TWKB will be included when it is
ready? > > > > > </BODY></HTML>