You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Yeah we are trying to make the switch, see #127 and #128. It is quite a refactor as you can imagine JSON is a pretty important dependency for GeoJSON ;)
Important piece of information here, on 2026-09-26:
Using CSV 1 in Julia 1.13 results in an old version of GeoJSON being loaded. In other words, in packages that depend GeoJSON 0.8, there are incompatibilities between versions.
[336ed68f] CSV v1.1.0
⌃ [61d90e0f] GeoJSON v0.4.0
This is also the case on 1.12:
[336ed68f] CSV v1.1.0
⌃ [61d90e0f] GeoJSON v0.4.0
In both cases, installing GeoJSON first, and then CSV second results in the latest GeoJSON, but an old CSV:
(jl_QLPZRT) pkg> st
Status `/tmp/jl_QLPZRT/Project.toml`
⌃ [336ed68f] CSV v0.10.17
[61d90e0f] GeoJSON v0.8.4
Info Packages marked with ⌃ have new versions available and may be upgradable.
(jl_QLPZRT) pkg> status --outdated -m
Status `/tmp/jl_QLPZRT/Manifest.toml`
⌃ [336ed68f] CSV v0.10.17 (<v1.1.0)
⌅ [842dd82b] InlineStrings v1.4.6 (<v2.0.1): CSV, WeakRefStrings
⌅ [69de0a69] Parsers v2.8.8 (<v3.0.0): CSV, JSON3, WeakRefStrings [loaded: v2.8.7]
⌅ [ea10d353] WeakRefStrings v1.4.3 (<v2.0.0): CSV
I see there is work in progress in both #127 and #128 , I just wanted to flag this as workflows that rely on both CSV and GeoJSON are probably not that uncommon
Activity
visr commentedon May 12, 2025
For context see JuliaIO/JSON.jl#374. Indeed if JSON3 will be deprecated this would make sense.
tpoisot commentedon Sep 13, 2026
JSON3 is now deprecated (and has been for a few months)
quinnj/JSON3.jl@08b5f48
visr commentedon Sep 13, 2026
Yeah we are trying to make the switch, see #127 and #128. It is quite a refactor as you can imagine JSON is a pretty important dependency for GeoJSON ;)
tpoisot commentedon Sep 26, 2026
Important piece of information here, on 2026-09-26:
Using
CSV1 in Julia 1.13 results in an old version ofGeoJSONbeing loaded. In other words, in packages that dependGeoJSON0.8, there are incompatibilities between versions.This is also the case on 1.12:
In both cases, installing
GeoJSONfirst, and thenCSVsecond results in the latestGeoJSON, but an oldCSV:I see there is work in progress in both #127 and #128 , I just wanted to flag this as workflows that rely on both CSV and GeoJSON are probably not that uncommon
TimG1964 commentedon Oct 6, 2026
Just to add that continued dependence on JSON3 also blocks Parsers v3 which was released 2 months ago.