# JuliaGeo talk at FOSS4G 2019

**URL:** https://discourse.julialang.org/t/juliageo-talk-at-foss4g-2019/28425
**Category:** Geo
**Tags:** conference
**Created:** [September 5, 2019, 12:01pm UTC](https://discourse.julialang.org/t/juliageo-talk-at-foss4g-2019/28425 "2019-09-05T12:01:39Z")
**Posts on this page:** 1
**Showing post:** 8

<div class="post-metadata">

### Author: ![visr](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/visr/32/17204_2.png) [@visr](https://discourse.julialang.org/u/visr)
#### Post date: [October 19, 2019, 7:51pm UTC](https://discourse.julialang.org/t/juliageo-talk-at-foss4g-2019/28425/8 "2019-10-19T19:51:40Z")

</div>

Ha thanks, we’re slowly edging closer. One of the steps was to make existing vector files a Tables.jl table, which is now done in [Shapefile.jl](https://github.com/JuliaGeo/Shapefile.jl) and [GeoJSONTables.jl](https://github.com/visr/GeoJSONTables.jl). From those I hid the geometry column to the Tables interface because I want to treat it specially later. We will need some work on an improved GeoInterface that @yeesian has done some thinking on lately. Then based on that interface perhaps we can set up a generic GeoTables interface for this kind of functionality.

Although besides the generic interfaces and types it might be good to also start working on a decent GeoDataFrame that just takes for instance a DataFrame and a vector of GEOS(?) geometries, and start defining some operations on them.

---

_[View the full topic](https://discourse.julialang.org/t/juliageo-talk-at-foss4g-2019/28425)._