Anshul Singhvi

Can't `convert(Float64, unitful_float64)`?

2

MWE: ```julia-repl julia> using Unitful julia> convert(Float64, 1.0u"m") ERROR: DimensionError: and m are not dimensionally compatible. Stacktrace: [1] #s103#141 @ ~/.julia/packages/Unitful/GYzMo/src/conversion.jl:7 [inlined] [2] var"#s103#141"(::Any, s::Any, t::Any) @ Unitful ./none:0 [3]...

Enforce that all axis types are <: AbstractAxis

2

As brought up in Slack just now. Still needs tests but works locally with GeoAxis. One question that remains is what to do about polar axes. With the naive implementation...

CSV.jl fails to parse a file that DuckDB is fine with

2

MWE: ```julia import CSV, QuackIO using DataFrames file = download("https://raw.githubusercontent.com/newzealandpaul/Maritime-Pirate-Attacks/refs/heads/main/data/csv/pirate_attacks.csv") # try QuackIO first dataset = QuackIO.read_csv(DataFrame, file) # works # now try CSV CSV.read(file, DataFrame) # errors ``` The...

Remove ambiguity and implement `getgeom`, `ngeom` for `Wrappers.Point`

6

This was mentioned on Slack, the output is probably a bit better than a method ambiguity error now.

Implement crs and geometrycolumn fallbacks via DataAPI

1

- [ ] Needs tests - [ ] needs docs

Proposal: allow `Polygon` to be constructed from a vector of `PointTrait` geometries

5

That would allow a much cleaner syntax than the current `Polygon([LinearRing(...)])`...

Proposal: `geometrycolumn(x) = first(geometrycolumns(x))`

5

It's difficult to teach users why they should have to use `first(geometrycolumns(x))`, and it's not easy to remember when starting out. Would it make sense to have a convenience function...

[WIP] Add a Tables.jl extension for FeatureCollection and Feature

2

This PR treats FeatureCollections as row tables, and Features as rows. ```julia julia> @time DataFrame(fc2) 6.790032 seconds (10.19 M allocations: 3.447 GiB, 1.13% gc time) 177×169 DataFrame Row │ geometry...