test with turf.lineString(<coords>,{},{id:0})
on v.5.1.6

if id is 0 the id field is missing

An extra null pointer check is not needed in functions like the following.

• LEdge
• [Range_tree_1](https://githu

@redblobgames I'm wondering whether we could drop the script { display: block; } hack — while it's definitely cool, it has some drawbacks:

• We can't add code highlighting to the code (e.g. with https://highlightjs.org/), which would help docs readability a lot.
• We have to split the code into two files entangled together, which makes refactoring inconvenient.
• It's impossible to lint it

When writing 3D objects in WKT, a "Z" is supposed to be added to the prefix, such that a 2D point and a 3D point are differentiated:

POINT (1,2)
POINT Z (1,2,3)

But as far as I tested, when writing 3D objects using the WKT writer of Boost Geometry, the "Z" prefix is never written, leading to this kind of output:

POINT (1,2)
POINT (1,2,3)

It seems to be similar for other

See section 12.4 of the User Guide (also, move that section to Developer's Guide, where its more appropriate).

Apparently NURBS Python converts NURBS geometry to triangle meshes on export to OBJ.
This implicit conversion is nowhere mentioned in the documentation. There should be a big warning box added.

Wavefront OBJ supports (trimmed) NURBS geometry. See e.g. a copy of the format description at Paul Bourke's website.

Software that can read (and write) such

Similar to your Processing example for Java, it would be helpful if you could include a basic p5.js example within the js folder.

In context of mapbox/mapbox-gl-native#15268: if the original polygons are correct, there is no need to provide result that reorders original and return true.
Client then constructs another container, copying and casting all returned to domain specific type... e.g
https://github.com/mapbox/mapbox-gl-native/blob/273ad436fb4d2a18c6749bd4e40fa56546e9285c/src/mbgl/tile/geome

There’s enough documentation in the form of documentation comments that we could use jazzy to generate HTML documentation based on it and publish it using GitHub pages.

/cc @captainbarbosa