Latest Contributions by aymansalah

You may be able to add drag and drop to move layers around using a third party library.  This looks promising: GitHub - Shopify/draggable: The JavaScript Drag & Drop library your grandparents warned you about.  I played around with this for a little bit and here's what I ended up with: https://codepen.io/solowt/pen/yPeeeL?editors=1000#0  This isn't working completely.  There is some logical problem with how the layers are reordered.  I'm not sure where the issue is but if you really want this feature it should be doable with some work. One thing I noticed is that I needed to push each swap event onto an array and then apply the changes after the user stopped dragging the layer element.  The logical problem may be involved with how the new index is determined.  I'll take a further look if I get a chance. ... View more

Hello Ayman - To which Input are you referring?  At the 10.2.1 product release 'Poll an ArcGIS Server for Features' allows you to choose either the 'FeatureServer' or 'MapServer' endpoint of a published service to poll for feature data. Other product capabilities such as synchronizing GeoFences also support the selection of 'FeatureServer' or 'MapServer' endpoints. Are you trying to use a 'MapServer' endpoint and it is not working? - RJ ... View more

Hello Ayman "? If the event count for your Input polling ArcGIS Server for Features is not indicating that any features are being received, this is usually because an existing event definition does not match the data being received so the Input"?s adapter is not able to create a GeoEvent. I opened your map document from the map package you posted. None of the feature coordinates contain null values, but I did notice that several hundred of the UNIT_DBID attribute values were null. I used ArcMap"?s field calculator to assign those value to -1, just so that all of the features and attributes would have valid non-null values. I published the map document to my local ArcGIS for Server as a map service with feature access enabled (so I have a feature service as well). In GeoEvent Processor I created a new Input "?Poll an ArcGIS Server for Features"? with the following configuration. [ATTACH=CONFIG]30956[/ATTACH] The Input fs-poll-in immediately received 804 new events "� and every 60 seconds another 804 events were polled from the feature service. The GeoEvent Definition generated for the events looks like: [ATTACH=CONFIG]30957[/ATTACH] Note that you do not need to incorporate the Input in a GeoEvent Service or send event data to an Output to verify that an Input is able to poll ArcGIS Server for features. I would recommend using GeoEvent Processor Manager to delete the Input, GeoEvent Service, and Output you have created. Also delete any generated GeoEvent Definitions you have created for this data. Make sure that a newly created Input is able to create a new GeoEvent Definition. Be aware that the JSON adapter - the component used by the Input to interpret the data being received -  will generate a GeoEvent Definition based on the content of the first event received. The adapter will omit any fields from the GeoEvent Definition whose value is null. This is the behavior at 10.2.1 "� we are looking at changing it at 10.2.2 so that the fields will be created even if the attribute value in the first event received is null so that the generated GeoEvent Definition matches the schema defined by the feature service being polled. Hope this helps - RJ ... View more

Just want to clarify the problem.  The input connector which was receiving attributes and geometry is not reading geometry anymore.  You verified this by hooking this input up with a JSON file output and saw that the output does not contain the geometry that you expected. If this is the case, we should take a look at the input and the data that you sent to the input.  Specifically, here are the things I want to look at: 1. Input properties, you can either give me a screenshot or the configuration xml. 2. The GeoEvent Definition that is created by the input or is used by the input 3. The simulation data. I will have more information once I look at these.  According to your post, it seems that the input was working correctly but for some reason it started to not recognize the geometry.  I assume the source of the data didn't change.  I suspect the data might have changed that caused the input to not reading the input correctly.  Let's take a look at these three items. Thanks, Ming ... View more

Ayman, There are currently no built-in processors that project the geometry.  That leaves two options.  If you output the data to a Feature Service, your client application can specify the desired coordinate system when querying the feature service for features. If you need to project the geometry in the geoevent service, then you will need to create a custom processor using the SDK. -Ryan ... View more

where do I find those geoeventdefinitions in 10.5.1? ... View more

Hello Ayman - Thank you for clarifying what you were trying to accomplish. My apologies for misunderstanding... At the 10.2 / 10.2.1 release, the Output connector supporting logging event data to a CSV system file won't support what you are trying to do dynamically ... unless you know in advance the track IDs of the vehicles being reported by your AVL system. For example, if you knew that vehicles TRC2478, TRC290, and TRC2812 were expected to report, you could use filters to isolate events for each reporting vehicle and direct those vehicle reports to separate Output connectors. You would need to specifically configure each Output connector to write to either a file or sub-folder dedicated to a specific vehicle. If the track IDs of the vehicles being reported by your AVL system are not known, then pre-configuration of Output connectors and addressing the need with event filtering is obviously not an option. In that case you would have to develop a custom transport using the GeoEvent Processor SDK. Your custom transport could parse the outbound stream to discover the track ID, determine if a system file/sub-folder had been established for that vehicle, and take appropriate action. The ability for a transport to query an outbound stream for a track id was developed for the 10.2.1 product release. As a side note, Notifications (e-mail, SMS message, etc.) have been enhanced to enable service designers to retrieve address information from event attribute data in order to dynamically direct notifications to recipients. This capability will be available in the 10.2.2 product scheduled for release in March 2014. If similar capability is important to your successful adoption of GeoEvent Processor when working with system file output, please post the idea to the ArcGIS Ideas portal ( http://ideas.arcgis.com ). Community support for an idea helps us prioritize future product enhancements. Be sure when submitting ideas to tag the idea with "GeoEvent Processor" and check the "ArcGIS Server" category. Regards - RJ ... View more