GeoJSON.jl
GeoJSON.jl copied to clipboard
JuliaGeo
Utilities for working with GeoJSON data in Julia
I do not know if all GeoJSON features should share the same properties. But if not, the following is a bit of a nuisance. With GeoJSON 0.6.0 ``` a =...
Follow-up from #30: in that PR, we're made it clearer that > Note that GeoJSON.jl loads features into the GeoInterface.jl format and that this differs from GeoJSON in the following...
Use the JSONTables.jl methods of getting a list of column names and types. Unfortunately we cant just use their methods as we need to dig into the `properties` field of...
I've posted a question at Stackoverflow, but I guess I should post it here as well. In a nutshell, I'm reading a layer with census tracts, neighbourhoods, and districts in...
In the sense that an `GeoInterface.coordinates` will yield a JSON3 Array that no other package will parse as the coordinates they are. ``` julia> GeoInterface.coordinates(poly1) 1-element Vector{JSON3.Array}: JSON3.Array[[0.1, 0.0], [1.1,...
```julia julia> a = """{"type": "FeatureCollection", "features": [ {"type": "Feature", "geometry": {"type": "Polygon", "coordinates": [[[0.1, 0.0], [1, 0.2], [0.0, 1.0], [0.3, 0.0]]]}} ]}""" julia> poly1 = GeoJSON.read(a)[1].geometry julia> poly1[1] 4-element...
Similar to Shapefiles.jl it would be more user-friendly. Currently we have to read the file with Base.read and then read it again with GeoJSON.read.
Hello, The older version of the package had a geo2dict function to convert the continents json into a dictionary. What is the alternative way to doing that with the new...
It would be convenient if you could do something like `filter(f -> f.NAME == "France", collection)`, but currently filtering is not supported. Right now, I'm naivley pirating this like so:...
Right now we can convert FeatureCollection to DataFrames, but not back: ```julia julia> using GeoJSON, DataFrames julia> p = GeoJSON.Point(coordinates = [1.1, 2.2]) Point([1.1, 2.2]) julia> f = GeoJSON.Feature(p; properties...
