coordinates of a Polygon about geometrybasics.jl

[visr]

That only gives back the first two points, that make up the first line. I could loop over the lines and pick out the right ends, but there is probably a more direct / faster way.

[Sov-trotter]

Yeah I am slowly realizing that the inherent geometrybasics methods like that I have used above don't quite support our use case(Makie).

I could loop over the lines and pick out the right ends, but there is probably a more direct / faster way.

I am trying to do a similar thing in the above referenced PR.
Here's something I tried as per the above PR.

using BenchmarkTools
pts = collect(Point{2, Float64}(x/2, (x+1)/3) for x in 1:10000)

ls = LineString(pts)

@btime ls.points.parent.data
128.521 ns (6 allocations: 192 bytes)
10000-element Array{Point{2,Float64},1}:

[knuesel]

This can be closed now that #73 is merged?

[Sov-trotter]

I think this is more like a nested structure. Where we can't get to the point directly, but something like this works :

pts = Point{2, Int}[(3, 1), (4, 4), (2, 4), (1, 2), (3, 1)]
pol = Polygon(pts)
ngon = decompose(GB.Ngon, pol.exterior)
coordinates(ngon[1])

Also some nested decomposition works,

ngon = decompose(GB.Ngon, pol.exterior)
point = decompose(Point, ngon[1])

The stacktrace kinda hinted it,

Stacktrace:
[1] (::GeometryBasics.var"#152#153"{Int64,GeometryBasics.Ngon{2,Int64,2,Point{2,Int64}},Int64})(::Int64) at C:\Users\visser_mn.julia\dev\GeometryBasics\src\geometry_primitives.jl:57
Also like you said here,
Because this seems a bit inconsistent at times, as we saw above coordinates(::Polygon) returns lines, but if we put in an Ngon, a fixed size polygon, then we get the points: