[postgis-devel] Specifying end cap and join styles Buffer op

[Mark Cave-Ayland]

strk wrote:

>> Hm, loverly. Look how Oracle does it:
>>
>> http://download.oracle.com/docs/cd/B28359_01/appdev.111/b28400/sdo_objgeom.htm#i856140
>>
>> A "param string". I wonder how they decide what values deserve their
>> own slot and who has to live in the string.
> 
> There's an example, and it's all-inclusive:
> 
> 	'arc_tolerance=0.05 unit=km'
> 
> No end cap or join style. Not sure if arc_tolerance may be
> similar to GEOS's mitre limit. Martin ?
> 
> We could accept these in a single string:
> 
> 'endcap_style=round|flat|square join_style=round|mitre|bevel mitre_limit=5.0'
> 
> Note though that this wouldn't really make us Oracle-compatible
> as we use third numeric argument  for  quadrant segments whereas oracle uses
> that for precision (tolerance).

String parsing seems quite horrible in this day and age; any reason we 
can't use PostgreSQL arrays to pass in the information instead? I really 
don't care too much about Oracle compatibility since PostGIS as a 
project is heading more towards SQL-MM.


ATB,

Mark.

-- 
Mark Cave-Ayland - Senior Technical Architect
PostgreSQL - PostGIS
Sirius Corporation plc - control through freedom
http://www.siriusit.co.uk
t: +44 870 608 0063