Fill raised KML polygons up to 32,768 vertices

A raised polygon past 4,096 vertices lost its fill, which main drew.
Triangulating 32,768 vertices takes about 58 ms on a fast laptop, so the
fill limit moves there; 128 rings stay the hole limit, since holes make
earcut quadratic. The polygon loop yields to the event loop after 8 ms of
work, and the import cancels a draw whose globe went away while it
yielded, without reporting the file as unreadable.

KNOWN-ISSUES names the fill limit and two Navara limits: an expired
terrain token is not refreshed while the page is open, and a failing map
source does not fall back to another map.
This commit is contained in:
German Khokhlov committed 2026-11-10 14:03:35 +04:00
1 parent 2a761aa5eb
commit a913e5466e
4 files changed
+243 -14

No files matched your search

+6 -1
View File
@@ -26,7 +26,8 @@ function localizedValues(values) {
* @param {{load?: Function, drawFile?: Function, document?: Document,
* publish?: Function, connect?: Function}} deps
* `load(file, {color, signal})` defaults to `loadGeoFile` (the file's
* plain records) and `drawFile(engine, records, {visible})` to
* plain records) and `drawFile(engine, records, {visible, signal,
* isCurrent})` to
* `drawImportedFile` (their drawing: { report, setShow, refreshGround,
* footprint, destroy }); tests pass doubles. `publish({rows, hint})` hands the file
* list and hint to the view that renders them. `connect(actions)` answers
@@ -252,9 +253,13 @@ export function createGeoFileImport({
try {
item.drawing = await drawFile(attached.engine, loaded.records, {
visible: item.visible,
signal: attached.controller.signal,
isCurrent: () => !destroyed && scene === attached,
});
} catch (error) {
undraw(item);
// A draw cut short by a scene change is not a file error.
if (destroyed || scene !== attached) return false;
throw error;
}
if (destroyed || scene !== attached) {