MVT point and line buffer clipping

Shared MVT circle/line display and rendered queries use point/line geometry clipped to its tile rectangle. Source queries retain original buffered fragments,properties and stable IDs. Display geometry does not replace the raw source. World copies retain existing longitude shifts.

const raw=await map.querySourceFeatures('vector',{sourceLayer:'roads'});
const drawn=await map.queryRenderedFeatures(pixel,{layers:['roads-layer']});

Source queries can include neighbour buffers and repeated IDs. Rendered queries deduplicate stable IDs per display layer/sourceLayer and return clipped geometry. Fully excluded points/lines do not enter the shared display view; disjoint line parts remain separate. Clipping preserves raw data and feature-state identity. Failed refresh retains existing atomicity rules.

Derived data shares the64MiB decoded tile budget. Unchanged JSON reuses the same Arc; additional derived content consumes budget. loaded/readyTiles still describe exact current-tile readiness,not visibility of every raw feature.

The complete HTML includes all four buttons,embedded MVT bytes,protocol/request transformation,raw/rendered queries,a single GeoJSON point opacity reference and cleanup. It runs without the acceptance server. The portable script uses local acceptance tiles. SqsMap generated the data.

Only point coordinates and line segments are clipped; rectangle edges are inclusive. Polygon/hole splitting,complete stroke-width/cap pixel clipping,boundary ownership and cross-tile geometry stitching/merging remain pending. Independent setStyle(URL) basemaps retain separate scope. Devices,hardware and formal distribution require separate acceptance.

Polygon/hole clipping is connected in07.14b and supersedes the earlier polygon limitation above.