Anshul Singhvi
Anshul Singhvi
It would be nice if this worked: ```julia resolution = size(earth_ras; order = (X, Y)) ``` instead, we currently have to do: ```julia resolution = length.(dims(earth_ras, (X, Y))) ``` and...
MWE: ```julia-repl julia> import DimensionalData as DD; using DimensionalData julia> intersect(DD.Dimensions.DimUnitRange(1:5, X()), DD.Dimensions.DimUnitRange(3:7, X())) 3:5 julia> typeof(ans) UnitRange{Int64} ``` Ideally this should return a DimUnitRange. Maybe it could also check...
MWE: ```julia using DimensionalData A = [1.0 2.0 3.0; 4.0 5.0 6.0] x, y, z = X([:a, :b]), Y(10.0:10.0:30.0; metadata=Dict()), Z() dimz = x, y da1 = DimArray(A, (x, y);...
Or something along those lines. Not sure exactly what the API should look like, but since we already have lookup vectors ready to go it could be very nice to...
This requires us to have good unary unions in GeometryOps. But it allows aggregating high-granularity datasets, going from counties to states for example. Maybe this just gets solved by DataFrames...
From https://discourse.julialang.org/t/screening-interest-in-a-unified-vector-raster-package-akin-to-r-terra/121613, it might make sense to make GeoDataFrames a single point of entry for vector datasets. Would there be interest in creating a "backend system" for GeoDataFrames, so that...
MWE: ```julia julia> using NaturalEarth, DataFrames, GeoParquet, GeoDataFrames julia> all_countries = naturalearth("admin_0_countries", 10) |> DataFrame |> x -> select!(x, [:geometry, :ADM0_A3]) 258×2 DataFrame Row │ geometry ADM0_A3 │ Union… String...
https://luxdl.github.io/DocumenterVitepress.jl/dev/getting_started#Preview-Documentation-Development-Instantly