Re: Current state of Apache Commons Math and Geometry

That's one way to see it.
Of course if no one else is interested or do not have time to get 
involved then I'm better of continuing the work in Apache SIS.
Sure it's faster to do things on our own, without talking to anyone, 
that's how we end up with a lot of different libs doing more or less the 
same stuff.

Our philosophy in Apache SIS is to follow the standards and formats if 
they exist.
For Geometry that is ISO 19107, OGC Feature, the various Khronos specs 
and some others like SVG, CSS...
A good geometry API should be able to map the existing.

There is a good amount of overlapping, commons geometry is a rich library.

For now I will continue the work in Apache SIS.
I'll see how it goes and perhaps start coming back to you if it can be 
of mutual benefit.

Johann

Le 19/02/2026 à 14:27, Elliotte Rusty Harold a écrit :
> On Thu, Feb 19, 2026 at 8:32 AM Johann Sorel via dev
> <[email protected]> wrote:
>   part :
>> https://github.com/apache/sis/tree/geoapi-4.0/incubator/src/org.apache.sis.geometry/main/org/apache/sis/geometries
>>
>> Apache-commons-geometry contains a single kind of geometry :
>> Constructive Solid Geometry. which is really nice.
>> But what we are making is more like JavaTopologySuite, Esri-geometry,
>> SVG but with 3D (and more) support for PLY, GLTF, GPU...
> I'm not familiar with the math you're using, but it sounds like it's
> quite different from what's in commons geometry now and has limited
> overlap. If that's true, then I strongly recommend you make your own
> more targeted library and artifact rather than trying to shoehorn it
> into another library because the name sounds similar. Smaller, more
> focused libraries speed up development and enable you to build exactly
> what you need without trying to get consensus with another team.
> Frankenlibraries that include everything and the kitchen sink are
> already a problem for Apache Commons. I think you'll be much happier
> with your own library that you control and can tailor to your
> project's needs.
>