Hey Tom -Sorry for the delay in getting back with you.
Where do the rangefans drop down values come from, and would you know why I am not seeing them? I don't have the Geoevent Server SDK installed. Is that required?
I believe the drop down values in the screenshot you provided are coming from the rangefans GeoEvent Definition.[ATTACH=CONFIG]34049[/ATTACH]When selecting 'Event' rather than 'Constant' for the 'Range Source' ... the 'Range Fan Field' should display a list of event fields for available GeoEvent Definitions. At least that is the behavior I see with my 10.2.2 instance of GeoEvent Processor. The list items you are referring to - rangefans:range, rangefans:bearing, rangefans:traversal, etc. - are different fields in the rangefans GeoEvent Definition. You should not need the GeoEvent Processor or ArcGIS for Server SDK installed to exercise the custom processors example.I initally thought that the screenshot in your message was one from your system, not a snip from the GitHub example page, so I prepared an instance of GeoEvent Processor 10.2.0, loaded the rangefan-processor-10.2.0.jar into the GEP framework and imported the GeoEventDefinitions-GeometryProcessors.xml configuration. I confirmed that the rangefans event definition was loaded, but when I tried to configure a 'Range Fan' processor in the Service Designer I did not see items in the event fields list for the rangefans event definition ... the only items in the list appeared to map to the incident event definition which gets installed with GEP.What release of GeoEvent Processor are you running?If you browse to the product's admin page for the installed processors ... what do you see for the RangeFanProcessor?1) Browse to: https: //<host>:6143/geoevent/manager/version.txt to verify your version of GEP.2) Browse to: https: //<host>:6143/geoevent/admin/processors3) Click the JSON link at the top of the page and search for "name": "RangeFanProcessor"I've highlighted code in the following block you should look for:
{
"name": "RangeFanProcessor",
"label": "Range Fan Processor",
"contact": "geoeventprocessor@esri.com",
"description": "Returns range fan derived from event center, range, bearing, and traversal angle",
"version": "10.2.0",
"domain": "com.esri.geoevent.solutions.processor.geometry",
"lastModified": "1393882661559",
"propertyDefinitions": [
{
"propertyName": "rangeSource",
"label": "Range Source",
"description": "Source of range Value",
"propertyType": "String",
"defaultValue": "",
"mandatory": true,
"readOnly": false,
"displayOption": "",
"dependsOn": "",
"allowedValues": [
"Constant",
"Event"
]
},
{
"propertyName": "range",
"label": "Range",
"description": "Maximum distance from event for analysis",
"propertyType": "Double",
"defaultValue": "1000.0",
"mandatory": true,
"readOnly": false,
"displayOption": "",
"dependsOn": "rangeSource=Constant"
},
{
"propertyName": "rangeEvent",
"label": "Range Event Field",
"description": "Geoevent field containing range data",
"propertyType": "String",
"defaultValue": "",
"mandatory": true,
"readOnly": false,
"displayOption": "",
"dependsOn": "rangeSource=Event",
"allowedValues": [
"rangefans:event_id",
"rangefans:x",
"rangefans:y",
"rangefans:z",
"rangefans:geo",
"rangefans:range",
"rangefans:bearing",
"rangefans:traversal",
"rangefans:date",
"rangefans:geodef",
"buffer:eventid",
"buffer:x",
"buffer:y",
"buffer:z",
"buffer:radius",
"buffer:date",
"buffer:geodef",
"TrackGap:trackId",
"TrackGap:gap",
"TrackGap:lastReceived",
"TrackGap:geometry",
"Flights-TcpText:FlightNumber",
"Flights-TcpText:StartTime",
"Flights-TcpText:OriginAirportCode",
"Flights-TcpText:DestinationAirportCode",
"Flights-TcpText:AircraftType",
"Flights-TcpText:Altitude",
"Flights-TcpText:Longitude",
"Flights-TcpText:Latitude",
"Flights-TcpText:geometry",
"Flights:FlightNumber",
"Flights:StartTime",
"Flights:OriginAirportCode",
"Flights:DestinationAirportCode",
"Flights:AircraftType",
"Flights:Altitude",
"Flights:geometry",
"ellipses:eventid",
"ellipses:x",
"ellipses:y",
"ellipses:z",
"ellipses:geo",
"ellipses:major_axis",
"ellipses:minor_axis",
"ellipses:rotation",
"ellipses:date",
"ellipses:geodef"
]
},
...
Notice beneath the rangeEvent property that a full set of the GeoEvent Defintions known to GeoEvent Processor are displayed along with all of their event fields. To confirm this I stopped my 10.2.2 instance and spun back up my 10.2.0 instance ... and there they were. When I re-launched Service Designer I was able to see them when configuring a Range Fan processor.[ATTACH=CONFIG]34048[/ATTACH]Long story short ... try stopping and restarting your GeoEvent Processor then rechecking the admin page to review the processor's JSON definition. If the JSON lists the rangefans event fields as allowed values, you should see them when configuring a Range Fan processor.- RJ