Presentation from Mr. Tim Loomis, a Senior Systems Engineer at National Oceanic and Atmospheric Administration (NOAA).
He will address the implications for managing imagery data that has geographical components per pixel and bring up a broader discussion on what the move toward geospatial rectification of web transactions means for security and data management at our Meetup in February 10th here - http://www.meetup.com/Tech-Roots/events/219644408/
Geospatial Rectification of Web Transactions and Data Security
1. GIS On The Web: Location, location, location
NOAA Environmental Visualization Lab
Tim.loomis@noaa.gov
Security, Data Management, Tech
2. An Idiot Foretells the Future
• Energy-neutral computing
• Place-as-Node: every construct passing
data
• Graphene economy
• GIS – Follow the Trail
Prognostication!
4. A day in my life….
• Coffee
• Check on data flow: http://www.nnvl.noaa.gov/Dashboard/Panel.html
• Tomcat, apache, Geoserver administration
• Check for events, monitor satellites
• Ongoing edits to databases, PHP, javascript, REST, IDL, McIDAS scripting
• Answer questions to Vizlab webmaster
• Answer questions, provide products to media, NOAA comms, DOC comms
• Plan upgrades to systems; code migration
• Projection systems consults: museums, Science on a Sphere, 4K
• Documentation, Adobe Ae Ps Ai, Maya
5. the Assumptions
I need information about the place I’m in, fast and comprehensive
GIS location data is permanent, information only has a certain lifespan
I don’t want to wait!
2 way street: You will come up with more interesting uses for GIS data
6. Technology stack for NOAA View
• Linux
• Apache Tomcat
• PostgreSQL – PostGIS
• Oracle JRE, JAI, ICE policy
• Geoserver
• OpenLayers, JQueryUI, Jcrop, css, etc.
7. Internet of Things
• ID each thing to geospatial
• What’s the limit to data gathering?
• Informed consent
• Aggregate data collection useless if people opt out of IoT participation
• What does ownership mean? Computing products blurring the line
• Does the thing we own report on us or itself?
• Evolution to rental model for stuff; separate the human from the data collection?
• Gov’t vs. commerce vs. law enforcement vs. media vs. finance vs. P2P
8. Security
• Source origination – super-important to follow the citation ( what does
that mean in context of geospatial data?)
• Efficiency of Identity
• Opt out, opt in… - user takes control; no way opt out will be default
• Securing the router
– Security by proximity
– Broad distribution
– Each router constantly checking fidelity. Hash-passing nightmare or opportunity for
geospatial root servers?
• Web Mapping Service – tiled images
– Copy compressed binary file to the end of an image
– 10K image tiles; 10K variations of hacker tools?
9. Geospatial routers
• Commercial: Solace
• Open source: OGC OpenLS, pgRouting
• Layering over IP network, process coordinates instead of IP addresses
• Build your own! Make some money!
• Oh yeah…Filtering…
10. Big Data
• Geospatial is the biggest of the big
• Sensed data – do we build a model of the earth?
– Darth Vader’s Death Star just a big hard drive
• Personal location data – every day, volume larger than social-generated data
• We need to analyze shape relationships on a massive scale
• The best big data platform for analyzing geospatial, sensor and location data IS:
– Doesn’t exist; Hadoop? Spark? PostgreSQL? Don’t incorporate spatiotemporal analytics (large scale)
– Built for the virtual world; assign unique numbers to web transactions, words, etc., and analyze for
relationships.
11. Big Data
• Database engine – needs to continuously index and store high-velocity sensor data
at speed while being queried in real time
• Geometry engine – (to compute mathematical relationships between shapes)
– Correctness, precision, performance suitable for large-scale analytics, not just making maps
– Time becomes a huge factor
– SpaceCurve rolled their own. No open source platform; database, disk, math not trivial
12. Attend the Meetup on Geospatial
Rectification of Web Transactions and
Data Security | February 10
OR