Hello everyone,
I had originally naively emailed Jody Garnett directly, to which he rightly replied that I should post my message here.
I was hoping someone could answer a question regarding Vector Tile caching in GeoServer.
After watching a presentation of Jody’s from FOSS4G25 on the subject, I was attempting to fine tune some of my own vector tiles. For the sake of making this brief, 2 of my 3 layers styled as such for testing using this geoCSS:
@mode "Flat";
desoto:desotoFloodZones_latest \[@z > 9\] {
fill:blue;
vt-attributes: 'fld_zone';
vt-labels: true;
}
desoto:desotoRooftops_latest \[@z > 15\]{
fill:red;
vt-attributes: 'coalesce';
vt-coalesce: true;
}
desoto:desotoParcelsDissolved_latest \[@z > 13\]{
fill:green;
vt-attributes: 'calc_label';
vt-coalesce: true;
vt-labels: true;
}
seem to work as expected. By that I mean, the Rooftops properly coalesce into essentially one multipolygon and the Flood Zones properly label via an accompanying point layer created by the “vt-labels: true” directive. However, the accompanying parcels label layer came out different than what I would expect, given what the Flood Zone labels result in. The Flood Zone labels were written to the tile cache as points, but the Parcel label layer was written to the cache as multipolygons. Specifically, a 1:1 match to the parcel layer itself. This essentially results in a doubling of the Parcel layer within the tile.
Do you know why that would be? I’m wanted to attach the output from ogrinfo of one of the cached tiles, but that is not allowed for new users.