Anshul Singhvi

Extents are somehow very slow

2

On Julia 1.12 Setup ```julia using Extents, GADM, Chairmarks import GeometryOps as GO switzerland = GI.geometry(GI.getfeature(GADM.get("CHE"), 1)) |> GO.tuples ``` Result ```julia-repl julia> @be GO.prepare_naturally($(switzerland.geom[1])) Benchmark: 17 samples with 1...

Deprecate geometry operations?

1

Having those methods here can cause confusion, maybe we should keep it in GeometryOps? e.g. geometric predicates, buffer, etc.

Should wrapper geoms take the CRS from their child geoms?

2

That would be nice for CRS passthrough on e.g. custom point types. Users can always do `crs = nothing` as well to restore "old" behaviour.

Wrapper show method improvements

1

- Show crs only on the top level geometry, not sub geometries - Show extent, if calculated, only on the top level geometry (?) - Compact CRS if possible, if...

Feature request: `GI.extent(::Extent)` returns that extent

3

Super convenient when sanitizing input to convert it all to extents.

So that we can have `GI.LineString[pointvecs...]`

This allows us to have a generic description of an axis aligned rectangle, that we can use for e.g polygon intersection.

flesh out GI for tables and rows

2

cc @tiemvanderdeure This still needs more fixes for GeometryOps compat which I will add as time permits. But in general at least it helps.

Implements GeoInterface.coordtype for Shapefile geometry types. Returns Float64. 🤖 Generated with [Claude Code](https://claude.ai/code)