ApacheCon2022 was held last week in person in New Orleans, USA.   
Again this year there was a geospatial track. 

** Summary of Track as sent to ApacheCon planners

The Geospatial Track included five presentations and a capstone discussion.  
Attendance in the track varied from standing room only for the Geospatial 
Search with Apache Lucene presentation;  to a handful of people for the 
presentation on a new effort to define geospatial extensions to Parquet.  The 
capstone discussion session was a good mix of people representing projects 
using geo to the people addressing geo across projects.  A particular call to 
action came from Julian Hyde, Apache Calcite, to increase the amount of 
discussions on [email protected] <mailto:[email protected]> between 
ApacheCons.  This was the seventh Apache conference with a geospatial track; 
The first geo track was at Apache Big Data, 2016.  It is recommended to have a 
geospatial track in ApacheCon next year.

Geospatial Track chairs: George Percivall and Jim Hughes


** Agenda: Tuesday, October 4, 2022 

        • 11:20 Apache Science Data Analytics Platform (SDAP)  - Stepheny Perez
        • 12:10 Geospatial Search with Apache Lucene - Nick Knize
        • 02:20 Understanding and Streaming Geospatial Vector Data using Apache 
Kafka and GeoMesa - Jim Hughes and Austin Heyne
        • 03:10 Real-time analytics over Geospatial data at Uber scale with 
Apache Pinot -  Yupeng Fu
        • 04:10 Enabling scalable modern GIS with GeoParquet - Matthew Forrest
        • 05:00 Geospatial Track Capstone Discussion with Community Community 
Talk - George Percivall
                Capstone Discussion opening remarks 
<https://docs.google.com/presentation/d/1MqI-T6KyDHIMvcK-3AEZBrnO2HTa_Sf-/edit#slide=id.p1>

Presenters are encouraged to send a link to their slides in reply to this 
message.



George Percivall
GeoRoundtable <https://www.linkedin.com/company/geo-roundtable/>
IEEE Geoscience and Remote Sensing Standards Committee, Vice Chair
[email protected] <mailto:[email protected]> 

Reply via email to