Latest Contributions by EvanPerry

Thanks RJ Thanks for the clarification, all good without the headers indeed and seems to get through the processor noticeably faster too Cheers Evan ... View more

Hi Greg That's an interesting one, glad they have it sorted for you All the best Evan ... View more

??Hi Greg, No problem for the help, I know how frustrating it gets when things don't want to work when they should, sorry it didn't solve the issue From your email it looks like you've pretty much covered all the options. Only thing on the permissions is that it's the account that the GEP was installed under that needs full permissions on the input file. I did my test under my own user login which doesn't have admin rights on the server and that server is still at 10.2.1 It does sound a bit odd so will be interesting to see what ESRI support come back with Cheers Evan Evan Perry Manager Spatial Solutions d +64 4 590 6847 m +64 21 650 171 p +64 4 590 6800 f +64 4 590 6801 e evan.perry@ems.co.nz<mailto:evan.perry@ems.co.nz><mailto:evan.perry@ems.co.nz> e evan.perry@transpower.co.nz<mailto:evan.perry@ems.co.nz> energy market services a division of Transpower NZ Limited Ground Floor | Transpower House | 96 The Terrace | Wellington 6011 | New Zealand PO Box 5363 | Lambton Quay | Wellington 6145 | New Zealand Notice: This e-mail and any files transmitted with it are confidential and are for the sole use of the intended recipients. If you have received this e-mail and any attachment in error please immediately notify energy market services by "Reply" and delete it. Any review, dissemination, disclosure, alteration, printing, copying or transmission of it is prohibited and may be unlawful. Note also that its content could have been altered already without the author's consent. Any views expressed are those of the individual sender, except where specifically stated that they are the views of energy market services. ... View more

Hi Greg I've taken a quick look at your Original-Locations and have that successfully running, as is with the quotes, using the watch folder for CSV and just going out to another CSV file again. A couple of possible things spring to mind. As you have the coordinates coming in in 2 separate columns  you need to add in an extra column into the input Event Definition for the geometries to be assembled into and have the "Build Geometry From Fields" switch to yes and populate the x and y field in the Input Service You’ll also need to specify the Expected Date Format for your data as it’s not what the GEP expects as the default. Not that that’s stopping the in/out process but you get incorrect data the output field otherwise. You need to drop a uniquely named file into the watched for each time you. GEP won't process a file of the same name if it’s been processed before even if it has different content. Some good info in this thread regarding the CSV file inputs https://community.esri.com/thread/89695. Note in that thread about GEP expecting a two-line header in the file otherwise you'll be dropping one or two rows from each CSV I’ve (hopefully) attached screen shots of how I set the input Event Definition and the Input Service. I’ve assumed the first column in the file is the identifier for the flight so have tagged that as the TRACK_ID Once you get the CSV file out running and your happy with content in the output file then switch out the csv output in the GeoEvent Servicefor the feature service output, making sure the Event Definition data types from the feature service layer correspond to the equivalent data types from the GEP. You’ll need a Field Mapper Processor to point the GEP Geometry field to the Shape field in the feature service layer and the other fields also. Then you should be up and running. Hope this helps Cheers Evan ... View more