Uploaded October 2026 | Updated November 2026, 14 hours ago
State of GeoDataFrames.jl by Maarten Pronk
PreTalx: pretalx.com/juliacon-2026/talk/TRBDEP
Reading and writing geospatial vector data is the bread and butter of any spatial ecosystem. In this short talk we present GeoDataFrames.jl, the default entrypoint for spatial vector data in the JuliaGeo organisation. We discuss recent and planned updates, such as support for native drivers and metadata passthrough, but also spatial indexing and lazy reading of datasets in the cloud.
Every spatial ecosystem needs packages to read and write vector data. In the JuliaGeo ecosystem, we've done so with GDAL, ArchGDAL and GeoDataFrames packages for a long time, slowly introducing more native file formats (ShapeFile, GeoJSON, GeoArrow). In the past (and current) year, GeoDataFrames.jl has seen an uptick in developments, as the community considers the package (should become) an entrypoint for the whole ecosystem.
Recent developments include:
- Native Julia driver support when loaded using extensions
- Metadata passthrough support, keeping metadata intact when possible
- GeometryOps integration, deprecating ArchGDAL operations
- GeometryVector (column) to make some handling of spatial data easier
Future planned developments include:
- Native GeoDataFrame ‹: AbstractDataFrame type so dispatch becomes easier
- Spatial index support (from GeometryOps) on GeometryVector
- Lazy reading mode
The above two developments (ideally with the new FilePaths design proposals) should enable lazily reading and subsetting of cloud native datasets.
State of GeoDataFrames.jl by Maarten Pronk
PreTalx: pretalx.com/juliacon-2026/talk/TRBDEP
Reading and writing geospatial vector data is the bread and butter of any spatial ecosystem. In this short talk we present GeoDataFrames.jl, the default entrypoint for spatial vector data in the JuliaGeo organisation. We discuss recent and planned updates, such as support for native drivers and metadata passthrough, but also spatial indexing and lazy reading of datasets in the cloud.
Every spatial ecosystem needs packages to read and write vector data. In the JuliaGeo ecosystem, we've done so with GDAL, ArchGDAL and GeoDataFrames packages for a long time, slowly introducing more native file formats (ShapeFile, GeoJSON, GeoArrow). In the past (and current) year, GeoDataFrames.jl has seen an uptick in developments, as the community considers the package (should become) an entrypoint for the whole ecosystem.
Recent developments include:
- Native Julia driver support when loaded using extensions
- Metadata passthrough support, keeping metadata intact when possible
- GeometryOps integration, deprecating ArchGDAL operations
- GeometryVector (column) to make some handling of spatial data easier
Future planned developments include:
- Native GeoDataFrame ‹: AbstractDataFrame type so dispatch becomes easier
- Spatial index support (from GeometryOps) on GeometryVector
- Lazy reading mode
The above two developments (ideally with the new FilePaths design proposals) should enable lazily reading and subsetting of cloud native datasets.




, built on byte-precise lowering and abstract interpretation. This year, we focus on the core design behind it: loading parts of user code to reuse Julias macro handling and compiler type inference. We compare this runtime-integrated approach with the overhauled LanguageServer.jl/JuliaWorkspaces.jl stack and demo its progress on real-world code.
At JuliaCon 2025, we introduced [JETLS.jl](https://github.com/aviatesk/JETLS.jl), then an early-alpha Julia language server built on [JET.jl](https://github.com/aviatesk/JET.jl)s abstract interpretation and [JuliaLowering.jl](https://github.com/JuliaLang/julia/tree/master/JuliaLowering)s byte-precise, provenance-tracking lowering. One year later, this talk goes beyond a progress report to examine the core design that makes this compiler-grounded analysis possible.
JETLS selectively loads parts of the target program into its analysis process. This runtime integration enables JuliaLowering to execute the program’s actual macros while preserving byte-precise source provenance, and JET to reuse Julia’s compiler inference to derive type information for source-level developer tooling.
We compare this design in depth with the [LanguageServer.jl](https://github.com/julia-vscode/LanguageServer.jl)/[JuliaWorkspaces.jl](https://github.com/julia-vscode/JuliaWorkspaces.jl) stack, which has undergone a major overhaul over the past year. Rather than presenting JETLS simply as a replacement, we place the two approaches on a spectrum of runtime integration: JETLS aims to provide precise information about macro expansion and lowering, together with compiler-inferred types, while the largely static approach prioritizes responsiveness and safety and benefits from greater production maturity.
These architectural differences become concrete in a live demo using real-world code from CSV.jl and JuliaFormatter.jl. We show how JETLSs runtime-integrated design translates into practical editor features, most of which were either early prototypes at last years talk or did not yet exist.
Finally, we summarize JETLSs current feature coverage, installation and environment isolation, and editor setup. We also briefly show how the same analysis is exposed through a CLI for CI and AI-agent workflows, showcasing agentic bugfixes drawn from a [Julia Base audit with JETLS](https://github.com/JuliaLang/julia/issues/62526).
Time permitting, we share performance measurements before outlining future work. JETLS: Bringing Julia’s runtime into language-server analysis | Kadowaki, Pfitzner](https://i.ytimg.com/vi/m-K5Wij8Q38/mqdefault.jpg)





