Currently, only single geometry input is possible from OL2 EditingToolbarExt control, because new geometry drawing delete all previous input features.
But, tester app needs more input cases, so consider to support Multi Geometry input.

This changes may require layer separation.

• Current:
  • layerInput
    • featureA
    • featureB
  • layerOutput
    • featureResult
    • featureExpected
• After:
  • layerInputA
  • layerInputB
  • layerOutputResult
  • layerOutputExpected

Currently, there is almost no memory clean up code, so it needs to be fixed.
Also, consider to manage error better.

There is no visual output when tapping 1st point, and finishing polygon drawing is impossible when tapping 2nd point.
Probably, it's better to modify original implementation (limit rectangle and add menu, etc.)

Move sanak/geos-wasm#6 to this repo.

From the following issue's comment.
#3 (comment)

Well, upstream example uses MapLibre GL JS, so consider to switch MapLibre GL JS to match upstream. https://github.com/chrispahm/geos-wasm/blob/main/package.json#L54
Also, consider to use VitePress (Vue?) CSS styling. https://github.com/chrispahm/geos-wasm/blob/main/package.json#L58

Well, this may need a lot of changes, so I will create another issue for that, and revert issue's subject to original one.

Custom CRS

CRS (Coordinate Reference System) may require some hack or deep investigation, because current OL2 implementation is using custom canvas base one.

Links:

• leaflet - Projection XY with maplibre - Geographic Information Systems Stack Exchange
• Class: MercatorCoordinate - MapLibre GL JS

Draw/Modify interaction

The following patch seems to work.
maplibre/maplibre-gl-js#2601 (comment)

Currently, main.js is quite huge (> 1400 lines), and readability and maintainability is quite bad.
Consider to separate current main.js file to some parts (something like map, update args, compute, ui, etc.)

I created (or separated) this repo from the following PR,

• sanak/geos-wasm#5

• Upgrade testxml files from GEOS repository
• Support WKB HEX format
• Fix test error

but still needs the works.

The original issue is here.
sanak/geos-wasm#4

Related with #4

Latest (GEOS 3.12.0) testxml files are here.
https://github.com/libgeos/geos/tree/3.12.0/tests/xmltester/tests

The latest testxml format seems to support WKB HEX import, so supporting it will be necessary.
:
WKB HEX format seems to be supported in the latest OpenLayers.

• https://openlayers.org/en/latest/apidoc/module-ol_format_WKB-WKB.html
• https://openlayers.org/en/latest/examples/wkb.html

Otherwise, wkx library will be necessary like upstream.
https://github.com/syncpoint/wkx

Move from sanak/geos-wasm#3

Probably, this requires a lot of changes, so consider to support both (separate tester.js to ol2-tester.js and ol-tester.js) to check go and back.

In vite structure, tester.js is now main.js, but consider to separate map engine part.

Currently, operation select list has a lot of items, and it is quite difficult to find an item.
Consider to make operation select list to searchable like jQuery Select2 (https://select2.org/searching#matching-grouped-options) with Vanilla JS way.

Currently, if input geometry is empty (like POINT EMPTY), the following error occurred.

Uncaught Error: Cannot fit empty extent provided as `geometry`
    at assert (asserts.js:11:11)
    at View.fit (View.js:1353:7)
    at zoomToExtent (mapiopanel.js?t=1697297407333:349:21)
    at MapIoPanel.loadInput (mapiopanel.js?t=1697297407333:462:7)
    at HTMLSelectElement.loadTestCase (testcasepanel.js:198:24)

Also, if output (result) geometry is none by exception, the following error occurred.

Error: Invalid geometry type: EXCEPTION
    at Parser.parseGeometry_ (WKT.js:546:15)
    at Parser.parse (WKT.js:293:17)
    at WKT.parse_ (WKT.js:629:19)
    at WKT.readGeometryFromText (WKT.js:677:27)
    at WKT.readFeatureFromText (WKT.js:639:23)
    at WKT.readFeature (TextFeature.js:36:17)
    at featureFromWkt (mapiopanel.js?t=1697297407333:311:31)
    at MapIoPanel.loadOutput (mapiopanel.js?t=1697297407333:468:23)
    at updateOutput (geosop.js?t=1697297376663:160:26)
    at GeosOp.compute (geosop.js?t=1697297376663:455:13)

Above errors need to be handled correctly.

Currently, input arguments are all text type.
It would be nice to support enum select (drop-down list) and boolean checkbox in arguments.

• JTSTestBuilder
  • 
• GEOS WASM Buffer Example:
  •