The com.bbn.openmap.layer.event package was created from more complex layers from other projects, in order to provide a start on putting together a TimeFrameApp. BBN had some projects that displayed quite a bit of information that changed over time (after action review, situational awareness apps), and these components were generalized from application-specific components developed on those projects. The CSVEventImporter was a quick way to get time-based data into the EventLayer, but that's really the component that would be customized for your app - how your data would be injected into the display.
Likewise, the TemporalOMGraphics are also expected be extended to add customized state to map objects, allowing them to change their appearance based on their state at the app's current time. You've got a lot of options.
I used to work for BBN, now I work for PAE.
- Don
On Aug 19, 2013, at 12:12 PM, Gary Briggs wrote:
> Realistically, CSVEventLayer is unlikely to be my long-term solution,
> but it seems like a really great start.
>
> For want of a metaphor, I'm thinking of trying to implement a soccer
> game using it; the players run around a lot, but they also take actions
> such as passing the ball to one another [and there are lots of balls,
> and I want to overlay information about the players]. I'll have to think
> about what's a usefully generic way to declare it. I also specifically
> need to leave trails showing where players have been, ideally with the
> ability to color different segments of the trail differently. [eg, red
> might be when the player was carrying the ball and green when they
> weren't]
>
> I only heard about openmap because one model we're using at work uses
> it. The model works off a mysql database, but... the authors of the
> model's maptool implement a separate program in C++ that pushed to a
> network link layer in openmap, and implemented their own timeslider
> there [with rich control over what you get to see rendered]. It feels
> like it might be better implemented by drinking the openmap component
> kool-aid wholesale. Not sure.
>
> We have other models that I would also like to use openmap for rendering
> results from, but using link layer to model-specific tools seems less
> appealing to building a common format that all these tools can export to,
> and load using openmap components.
>
> Out of idle curiosity, do you actually work at BBN?
>
> Thanks,
> Gary
>
>
> On Mon, Aug 19, 2013 at 10:18:09AM -0400, Don Dietrick wrote:
>> Hi Gary,
>>
>> Thanks for the feedback, yours is the first I've received on these components. BBN uses them for projects, but you're the first to write in with comments and I appreciate it, since you're coming at it cold.
>>
>> I'll have to take a look at the visibility setting, there might be something else that needs to be set for it to be honored. It's been a little while since I've been in that code so I need to refresh my memory.
>>
>> - Don
>>
>>
>> On Aug 17, 2013, at 11:13 PM, Gary Briggs wrote:
>>
>>>> What's the protocol for sending in patches? I'd like to modify
>>>> CSVEventImporter to include a "description" property; the current one
>>>> has "{name} moving" as the event description of all events, which isn't
>>>> quite what I need.
>>>
>>> Well, either way, attached is a patch that implements:
>>> 1) Descriptions
>>> 2) Visibility [but ... ]
>>>
>>> But ... visibility doesn't seem to work.
>>>
>>> I call point.setVisible(visibility), but then it doesn't seem to be
>>> honored. Am I missing something obvious, that there's a better way to
>>> implement this?
>>>
>>> Thanks,
>>> Gary
>>> <csvevent_description.diff>
>
> --
--
[To unsubscribe to this list send an email to "majdart_at_bbn.com"
with the following text in the BODY of the message "unsubscribe openmap-users"]
Received on Mon Aug 19 2013 - 17:10:14 EDT