Flexviewer 2.x: What functionality do you need?

[andrewj_ca]

I wanted to start a thread to see what functionality people are looking for or what enhancements to existing widgets people are looking for.  At the end of the day, what are your clients most interested in incorporating to the Flexviewer?

[RobertScheitlin__GISP]

Andrew,

   Nice fish for info. Looking for Flex-A-Widget ideas? 😉

[andrewj_ca]

More of wondering if I've already built something that would be good to share the source code for.  I'm not to sure I'd be able to build anything that would knock your socks off in time for the 'Flex-A-Widget' competition.  I'd also like to see if it is a new/good idea, would it be good for my organization?

[RobertScheitlin__GISP]

Andrew,

   Good idea, I remember some one else did a thread like this but it was a long time ago now. It will be good to get fresh ideas. I hope you get some good new ideas besides the same old "we want a high quality print widget" which seems so reasonable to non developers but is a development nightmare to make everything compatible with every ones needs. It would just be a continuous battle. I'll have to keep my eye on this thread.

[andrewj_ca]

I did an AVL widget last January that could be revamped and posted, my print widget is pretty good quality and was adapted from a post I got on here.  Has anybody else done an AVL widget?  Currently I'm tracking plows/sanders etc.

[ToddZimmerman]

I would be interested in see what functionality you have in the AVL widget. We are currently using the Query Widget with a 30 second refresh to track emergency vehicles.

[andrewj_ca]

Todd,

How are your AVL points stored? Ours are stored in a SQL table and I serve them through a webservice as xml.  I map the xml on a graphicslayer.  I use the 'mx.rpc.http.HTTPService' library to to call the service at user specified intervals.

[ToddZimmerman]

Ours are basically the same. Stored in a SQL Server table. I add the table to an ArcMap document through an OLE-DB connection and use the "Display XY Events" to convert the table to a featureclass in the document. Then just publish the document in ArcGIS Server and use the Query Widget to view it.

It would be nice to have an AVL widget based on the Query Widget that included the ability to follow a particular vehicle, i.e. keep the map centered on the vehicle while it moved. Also a button to zoom to the extent of all vehicles would be handy.

[SimonMorgan]

Not sure if this would be possible, but a universal GP widget would be nice. The widget could use any GP service as an input (maybe restricted to asynchronous or whatever was needed for programming purposes). In the config file, the user could configure the servcie URL and the inputs needed to run the GP service.

Email notification - a point is placed on a map and this triggers an email to a user. For example, if there is an issue with the map data, a flag could be placed on the map and the data administrator notified. Or, a member fo the public could be reporting a bench has been damaged and an email be sent to the maintenance supervisor.

[DavidAllen]

Ours are basically the same. Stored in a SQL Server table. I add the table to an ArcMap document through an OLE-DB connection and use the "Display XY Events" to convert the table to a featureclass in the document. Then just publish the document in ArcGIS Server and use the Query Widget to view it.

It would be nice to have an AVL widget based on the Query Widget that included the ability to follow a particular vehicle, i.e. keep the map centered on the vehicle while it moved. Also a button to zoom to the extent of all vehicles would be handy.

Or a cell phone tracking widget!!! Then we wouldn't need additional hardware in the trucks!

David Allen