<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
On 9/17/2016 8:09 AM, Sandro Santilli wrote:<br>
<blockquote cite="mid:20160917150927.GF8419@localhost" type="cite">
<pre wrap="">On Sat, Sep 17, 2016 at 04:25:06PM +0200, Björn Harrtell wrote:
</pre>
<blockquote type="cite" style="color: #000000;">
<pre wrap=""><span class="moz-txt-citetags">> </span>Found <a moz-do-not-send="true" class="moz-txt-link-freetext" href="https://github.com/mapbox/vector-tile-spec/issues/11">https://github.com/mapbox/vector-tile-spec/issues/11</a> supporting the
<span class="moz-txt-citetags">> </span>claim that a multi-layered vector tile is indeed a set of independent layer
<span class="moz-txt-citetags">> </span>messages. Still not sure about the possibility of aggregating the contents
<span class="moz-txt-citetags">> </span>of a layer as separate calls.
</pre>
</blockquote>
<pre wrap="">If I recall correctly, a good reason to have all the data at once
before starting to encode it was the indexing of values.
That is, attribute <span class="moz-txt-underscore"><span class="moz-txt-tag">_</span>values<span class="moz-txt-tag">_</span></span> can be put in a dictionary and only
referenced per-feature (think of a palette for graphics).
Such "dictionary" can help in case of large repeated values.
Using a row-by-row approach, makes it impossible to build such
dictionary, which is why my early attemps were just at producing
the geometric part, very much like the GML output works, delegating
composition of the whole final product to the caller (which could
eventually also be a ROW-taking wrapper).
</pre>
</blockquote>
<br>
You're right. Joining different layers is fine, but each layer has
some common information that is needed.<br>
<br>
Should it be an aggregate function then?<br>
<br>
<br>
</body>
</html>