Tom Van Mele

yes indeed, this should be documented. the example is also not great i guess...

i think this is only the case for circles. afaik, all other objects can be indexed correctly. so perhaps we should just update the definition of a circle, because in...

about the first problem... the path `"https://github.com/compas-dev/compas/raw/main/samples/{}".format(filename)` is not correct. it should be `"https://raw.githubusercontent.com/compas-dev/compas/main/src/compas/data/samples/{}".format(filename)`

nice investigation :) will have a look...

maybe briefly, just FYI, the recommended way to import compas objects is to always to this from "the second level", which is where the public API is defined. these imports...

> > maybe briefly, just FYI, the recommended way to import compas objects is to always to this from "the second level", which is where the public API is defined....

about the centroid... the issue is related to how the centroid of the polygon object is calculated. ```python from compas.geometry import Polygon, Point from compas.geometry import centroid_points, centroid_polygon polygon1 =...

the polygon object uses `centroid_polygon` in the background to calculate the centroid, which considers the actual polygon surface rather than the corner points to avoid skewed results when there are...

will leave it open as a reminder that the current implementation can lead to unexpected results :)

@gonzalocasas needs to be discussed in the next dev meeting...