[postgis-tickets] r15794 - Use ansi standard names for arg types for ST_AsMVT and ST_AsMVTGeom to be consistent with rest of docs. Note that ST_AsMVT should not be used with geometry collection directly, but a geometry collection can be converted to suitable form with ST_AsMVTGeom.
Regina Obe
lr at pcorp.us
Fri Sep 22 07:03:30 PDT 2017
Author: robe
Date: 2017-09-22 07:03:29 -0700 (Fri, 22 Sep 2017)
New Revision: 15794
Modified:
trunk/doc/reference_output.xml
Log:
Use ansi standard names for arg types for ST_AsMVT and ST_AsMVTGeom to be consistent with rest of docs. Note that ST_AsMVT should not be used with geometry collection directly, but a geometry collection can be converted to suitable form with ST_AsMVTGeom.
More adjustments to support garden testing ST_AsMVT and ST_AsMVTGeom
Closes #3858
Modified: trunk/doc/reference_output.xml
===================================================================
--- trunk/doc/reference_output.xml 2017-09-22 12:45:40 UTC (rev 15793)
+++ trunk/doc/reference_output.xml 2017-09-22 14:03:29 UTC (rev 15794)
@@ -1360,9 +1360,9 @@
<funcdef>geometry <function>ST_AsMVTGeom</function></funcdef>
<paramdef><type>geometry </type> <parameter>geom</parameter></paramdef>
<paramdef><type>box2d </type> <parameter>bounds</parameter></paramdef>
- <paramdef choice="opt"><type>int4 </type> <parameter>extent=4096</parameter></paramdef>
- <paramdef choice="opt"><type>int4 </type> <parameter>buffer=256</parameter></paramdef>
- <paramdef choice="opt"><type>bool </type> <parameter>clip_geom=true</parameter></paramdef>
+ <paramdef choice="opt"><type>integer </type> <parameter>extent=4096</parameter></paramdef>
+ <paramdef choice="opt"><type>integer </type> <parameter>buffer=256</parameter></paramdef>
+ <paramdef choice="opt"><type>boolean </type> <parameter>clip_geom=true</parameter></paramdef>
</funcprototype>
</funcsynopsis>
</refsynopsisdiv>
@@ -1419,13 +1419,13 @@
<funcdef>bytea <function>ST_AsMVT</function></funcdef>
<paramdef><type>anyelement </type> <parameter>row</parameter></paramdef>
<paramdef><type>text </type> <parameter>name</parameter></paramdef>
- <paramdef><type>int4 </type> <parameter>extent</parameter></paramdef>
+ <paramdef><type>integer </type> <parameter>extent</parameter></paramdef>
</funcprototype>
<funcprototype>
<funcdef>bytea <function>ST_AsMVT</function></funcdef>
<paramdef><type>anyelement </type> <parameter>row</parameter></paramdef>
<paramdef><type>text </type> <parameter>name</parameter></paramdef>
- <paramdef><type>int4 </type> <parameter>extent</parameter></paramdef>
+ <paramdef><type>integer </type> <parameter>extent</parameter></paramdef>
<paramdef><type>text </type> <parameter>geom_name</parameter></paramdef>
</funcprototype>
</funcsynopsis>
@@ -1446,6 +1446,10 @@
deep. The keys and values in the object will be parsed into feature attributes.
</para>
+ <important>
+ <para>Do not call with a <varname>GEOMETRYCOLLECTION</varname> as an element in the row. However you can use <xref linkend="ST_AsMVTGeom" /> to prep a geometry collection for inclusion.</para>
+ </important>
+
<para><varname>row</varname> row data with at least a geometry column.</para>
<para><varname>name</varname> is the name of the Layer. If NULL it will use the string "default".</para>
<para><varname>extent</varname> is the tile extent in screen space as defined by the specification. If NULL it will default to 4096.</para>
More information about the postgis-tickets
mailing list