FOSS4G North America Conference 2013 Preliminary Program

Recommendations

Info

GeoJSON is Spectacularly Wrong Sean Gillies, New York University GeoJSON is not just wrong, it is spectacularly, 45heliumweatherballoonsandalawnchair wrong. It invites coordinate order confusion. There is no language for defining schemata. It doesn't conform to ISO 191**. It is not even a real standard! And yet somehow people seem to find it good enough for everyday use, applying it to solve real problems without suffering major catastrophes. How can this be? How can something so wrong feel so right to developers? GeoJSON is a success because it has low technical and social barriers to entry and because it is incomplete and imperfect. I will discuss these properties and their happy consequences along with the overall strengths and weaknesses of the format, and offer some new patterns for using the format. Geospatial with MongoDB What is it good for? Cameron Goodale, NASA Jet Propulsion Laboratory With all of the hype surrounding the scalable document store called MongoDB I would like to present how my team used MongoDB for a simple single page webapp using Leaflet and HighCharts.js to help scientists visualize carbon dioxide from both remote sensing satellites and ground based stations. We are now looking to move into a more traditional open source GIS stack with PostGIS and GeoServer. My goal is to have the new GIS stack up and running in time for this talk. Project Overview Demonstrate the motivation for the web app, and also dig into why we decided to use Mongo instead of PostGIS to start. (we needed json for the app, and mongo is schemaless, plus we had no idea what our input data would be from one month to the next, and the web scale hype surrounding MongoDB). MongoDB is NoSQL People tend to forget that these NoSQL technologies are not direct replacements of RDBMSs. In this section I will reflect on some of the gotcha's people should be aware of when using Mongo (lazy inserts, eventually consistent data, fire and forget paradigm) and some of the steps Why are we now moving toward PostGIS and GeoServer Spoiler Alert: Users are asking for more features like WMS/WFS now. They like the webapp just fine, it is a quick look tool to show patterns in the data. Now users want to consume the data in their own desktop clients and perform much deeper analysis. Recap our Experience Mention what MongoDB is good for and maybe help others understand when MongoDB makes sense and when it's time to use a more traditional GIS stack.
LIDAR in PostgreSQL with PointCloud Paul Ramsey, OpenGeo How do you store massive point cloud data sets in a database for easy access, filtering and analysis? The new PointCloud extension for PostgreSQL allows LIDAR data to be loaded, filtered by spatial and attribute values, and analyzed via integration with PostGIS. We'll discuss the extension implementation, basics of loading data with PDAL, and how to use PointCloud with PostGIS to do onthefly LIDAR analysis inside the database. Dynamic Geospatial: Polygon Indexing and GeoJSON Support in MongoDB Greg Studer, 10gen the MongoDB Company This talk will go through new geospatial features added in MongoDB v2.4 and outline some of the work done "under the hood" to build out more sophisticated geospatial capabilities. MongoDB v2.4 adds two major features to its current geospatial querying capabilities support for GeoJSON documents and querying based on polygon and line geometries. Both of these features are based on the opensource Google S2 spherical geometry library. As the most visible JSON format for geospatial data, GeoJSON data is a natural fit to MongoDB's BSONbased document structure, and allows better interactivity with tools that understand GeoJSON. The move to GeoJSON is coupled with a number of indexing improvements longrequested by users (true wrapping spherical searches, geoindex reordering, and searches over multiple geospatial fields). A roadmap for future development is currently being defined based off this new work, where the goal is to further integrate the current 2d and 2dsphere indexing capabilities into a general solution for flatmap and sphericalworld applications.
Page 1 and 2: FOSS4G North America Conference 201
Page 3 and 4: Fast, Distributed Geoprocessing wit
Page 5 and 6: The emergence of HTML5 Canvas suppo
Page 7 and 8: outique desktop software, however.
Page 9 and 10: Justintime Spatial: Lightweight
Page 11 and 12: Javascript High Performance Data Vi
Page 13 and 14: applications. Rich data sources: ge
Page 15 and 16: An Open Source Framework for Volunt
Page 17: The open source Python geospatial s
Page 21 and 22: Andrew W Hill, CartoDB and Javier d
Page 23 and 24: An Overview Of OpenGeoportal Steve
Page 25 and 26: Case Studies Business of FOSS4G Bus
Page 27 and 28: Interactive Maps to Cryospheric Dat
Page 29 and 30: OpenLayers, and the Google Maps API
Page 31 and 32: DNR GPS (formerly DNR Garmin) is a
Page 33 and 34: carbon on snow can alter the energy
Page 35 and 36: and open way of making their commun
Page 37 and 38: support. Existing concept of operat
Page 39 and 40: Transportation and Utilities Open S

FOSS4G North America Conference 2013 Preliminary Program

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?