Skip to content

Commit 6674868

Browse files
committed
more text
1 parent 6528c68 commit 6674868

File tree

1 file changed

+17
-0
lines changed

1 file changed

+17
-0
lines changed

chapters/01-spatial-data.qmd

+17
Original file line numberDiff line numberDiff line change
@@ -73,8 +73,25 @@ There is more to CRSs, as described in @sec-coordinate-reference-systems-intro a
7373
TODO: explain the JuliaGeo ecosystem like they explain geopandas
7474
E.g GeoInterface defines how to access any geometry, then LibGEOS (wrapping GEOS), GeometryOps, Proj, etc consume such geometries.
7575

76+
<!--
77+
78+
-->
79+
7680
### Vector data classes
7781

82+
Julia's geographic vector data model is based on the [Simple Features](https://en.wikipedia.org/wiki/Simple_Features) standard, which is an ISO standard for representing vector data. Simple Features defines types of geometries (points, lines, polygons, multipolygons, etc.), as well as "feature collections" that are basically tables of geometries associated with some data.
83+
84+
Starting with the highest level class, feature collections come in two flavours:
85+
- Loaded from file (`Shapefile.Table`, `GeoJSON.FeatureCollection`, ...)
86+
- Tables with geometry columns (e.g. `DataFrame`, but can be any [Julia table](https://github.com/JuliaData/Tables.jl))
87+
88+
One can easily convert from feature collections to
89+
90+
<!--
91+
92+
-->
93+
94+
7895
```{julia}
7996
using GeoDataFrames
8097
df = GeoDataFrames.read("data/world.gpkg")

0 commit comments

Comments
 (0)