Hi Florian, sorry for the late reply. I think this is a very useful component.
So did I understand it correctly. In the current version the trajectories have a fix length (m), defined by the user. Once m events are collected the trajectory is emitted to the next processor. Right? I think it could also be interesting to add two more modes as alternative static properties: * Based on time: The user defines a time threshold. When no event arrives within this threshold the trajectory is sent to the next component * Based on distance: If two consecutive events are at the same location (with respect to some epsilon defined by the user), the event with the trajectory is emitted. What do you think? Does this make sense to you? Philipp On 2020/04/13 18:04:28, Florian Micklich <[email protected]> wrote: > Hi all, > > I have started to create a new PE which creates a Trajectory for > spatial-temporal analysis. A Linestring and coordinate list with sub-points > is created from point (or lat / lng) events. > > The latest subpoint represents the latest geo-event. The other subpoints of > the LineString represents the stored history of events. There is also a limit > of supported amount of subpoints. If this limit is reached, the oldest point > is removed from the LineString [1] / CoordinateList [2]. > > It is also possible to store an extra number value for each subpoint. > > So beside of the lat /lng value, a special value like time, duration, speed > and so on can be stored and used for calculations. > > > Later it will be also possible to calculate the distance between each > subpoint. > > So with the ISS example: It is possible to store the positions and time of > the events (m value) as a trajector. With this values (and the distance) it > will be possible to calculate for example the speed of the ISS. > > > A good example of possible functionalities can be found int his paper. > > https://rdrr.io/cran/trajectories/f/inst/doc/article.pdf > > > Any idea or recommendations what other functionality should be implemented? > > A possible feature would be to handle LineSegments [3]. Another question > would be how to visualize this LineStrings in the dashboard map. > > > Kind regards > > Florian > > > [1] > https://locationtech.github.io/jts/javadoc/org/locationtech/jts/geom/LineString.html > > [2] > https://locationtech.github.io/jts/javadoc/org/locationtech/jts/geom/CoordinateList.html > > (3] > https://locationtech.github.io/jts/javadoc/org/locationtech/jts/geom/LineSegment.html > > Disy Informationssysteme GmbH > Florian Micklich > Lösungsentwickler > +49 721 16006 477, [email protected] > > Firmensitz: Ludwig-Erhard-Allee 6, 76131 Karlsruhe > Registergericht: Amtsgericht Mannheim, HRB 107964 > Geschäftsführer: Claus Hofmann > > Bitte beachten Sie folgende Informationen für Kunden, Lieferanten und Bewerber > - Datenschutz: www.disy.net/datenschutz > - Informationspflichten: www.disy.net/informationspflichten > >
