Re: {Spam?} RE: {Spam?} RE: Q: IDS 11.5x - features..

Ian Michael Gumby wrote: > > > > Date: Wed, 8 Jul 2009 00:29:51 +0100 > > From: obnoxio@serendipita.com > > > This is cars we're talking about. How fast do you really think the data > > is going to be coming in from any given sensor? Really? Come on! > > > Hmmm. > > I guess you've never been in rush hour traffic on I-294 outside of > Chicago... ;-) > > Its not really the speed, but that you want to have fast access to the > data along with map data. So your map context is loaded in to memory and > the ancillary data is mapped above it also in memory, but not > necessarily as part of the underlying map context. The theory is that > you can then use the base map context for common data that would support > multiple apps. RTL? -- Cheers, Obnoxio The Clown http://obotheclown.blogspot.com -- This message has been scanned for viruses and dangerous content by OpenProtect(http://www.openprotect.com), and is believed to be clean.

On Jul 8, 1:34 am, Obnoxio The Clown <obno...@serendipita.com> wrote: > RTL? > > -- Sigh. Here's an example... in more but not complete detail... You have an underlying map context of a given metropolitan area. Rather than try and associate all of the ancillary data in the given map context, you create a hierarchy or 'layers' of specific data sets that reside in object sets associated to the underlying map, but not necessarily part of the map. An example, all of the fast food restaurants in the area. You'd actually place them in a separate layer than your underlying map context since they are POIs and not specific to the map entities. The same thing goes for traffic data. You need to track the flow of traffic however, it resides in a layer above the map context. So you have a system which will connect to the Tollway system to capture all of the RFID tags passing through their readers in real time. So your feed will contain numerous cars at a given tollway point, and there will be multiple tollway points providing data. In a city and its surrounding area of 4-6 million, plus cartage, during rush hour, that could be a lot of data. Hence the need for RTL. Is this really 25K 'ticks' in real time? Not for a given city, however... why do you only collect data for one city? Why not collect data for several major cities like Chicago, New York, Newark, Philli, 'Silicon Valley' (San Fran south to San Jose), etc ... Now how much data are you bringing in? (Even in different time zones, the 'rush hour' s overlap. Because we're talking about the map context being in memory, then the layers also have to be in memory. Unfortunately at this point things get a bit tricky as to what you want to capture and retain in memory or in the database.... But this is just one example. There are other areas where the RTL and TS are applicable. Thats in the financial area. I'll save that for a different post... ;-)