Sounds awesome! Let's talk about data. Do you know what kind of data you'll be getting from these planes and ships? How many individual tracks are you talking about?
We have two types of encoders currently for spatial data. The GeospatialCoordinateEncoder [1] is fed lat/lon coords and velocity, but it doesn't deal with altitude. It is a subclass of the CoordinateEncoder [2], which can be fed any array of coordinates and a radius. For more details on these encoders, see Chetan's video [3]. If altitude data is important, I suggest you try using the CoordinateEncoder, and manually calculate a radius for the encoder using velocity. [1] https://github.com/numenta/nupic/blob/master/nupic/encoders/geospatial_coordinate.py [2] https://github.com/numenta/nupic/blob/master/nupic/encoders/coordinate.py [3] http://www.youtube.com/watch?v=KxxHo-FtKRo --------- Matt Taylor OS Community Flag-Bearer Numenta On Thu, Oct 23, 2014 at 6:14 PM, Cameron Hunt <[email protected]> wrote: > I want to share a new project we're undertaking: integrating NuPIC into > our current environment where we do analysis on plane and ship traffic from > ADS-B and AIS messages. Integrating NuPIC is part of an overall rework of > our environment to shift to using Hadoop as our data persistence and > processing environment, and we're adding in Cesium/Geomesa for our > geospatial UI/UX, and Lab41's Dendrite/Titan distro for our graph data > UI/UX. > > Our goal would be to add anomaly scores generated by NuPIC into our user > review process. This means that for us it is as important to understand how > humans work with identified anomalies and feed their analysis back into the > algorithm. > > C4OE is a new non-profit that was created - in part - to better support > development of Open Source analytical software. So everything we develop > (or that we fund others to develop for us) will be released under an > appropriate Open Source license. > > -- > Cameron Hunt > Director, Center For Open Exploration > Cell: 843.654.4708 >
