Latest Contributions by DanielCota1

Carrie Carsell‌ I can only speak from a technical standpoint, but all of the functionality that comes with federating is outlined in the documentation below: https://enterprise.arcgis.com/en/portal/latest/administer/windows/about-using-your-server-with-portal-for-arcgis.htm#ESRI_SECTION1_139BD10752FF49D88005851DE59A0BDB As for publishing directly to Server from Pro, this is definitely possible, but not without federating. This is because Pro is designed to be integrated with the WebGIS platform, so layers can be shared with and seamlessly pulled from your online portal (ArcGIS Online or Portal for ArcGIS). As such, the only way for Pro to communicate with the ArcGIS Server for publishing would be if it were a federated server. As of now, the only way to publish to a standalone server is still through ArcGIS Desktop (ArcMap). I hope this helps.  ... View more

Gregory Christakos‌ RJ Sunderman‌ Do you guys have an idea as to why this could be? Does GE only populate the field options in the dropdown based on field type? Tags?  I just checked on my GE Server and see something similar. When I click on the dropdown, I see field options coming from the OOTB "incident" definition and not the definition I have set for the input. I have always manually typed out the field names for the X and Y parameters and it has never given me an issue, so I did not really put much thought into it. Maybe we are just missing something? ... View more

Hi Kyle Perri‌, If that truly is the JSON you are working with, then it would be expected that Geoevent is unable to construct geometry from it. There are no geometry fields to work with. Meaning, there are no X/Y or Lat/Lon fields that Geoevent would be able to read and create a geometry field from. I have worked with that API before, and I have found that using this endpoint works much better for testing: https://api.wheretheiss.at/v1/satellites/25544 As you see, it includes a latitude and longitude field that you can specify in the input connector configuration. Keep in mind, however, that this API is known to intermittently go down and requests to certain endpoints sometimes result in a "Too many requests" error. Aside from that, it should work better for your testing.  If you are interested, you can also try using http://api.open-notify.org/iss-now.json for your GE testing. I have not personally experienced any outage issues with this one. However, this JSON is nested, so be mindful of that when specifying the JSON Object. Hope this helps! -Daniel ... View more

Kyle Perri‌ Can you manually input the field names and see if it takes and allows the geometry to be constructed?  ... View more

Hi Kyle Perri‌ Is this nested JSON by any chance? Can you provide the configuration xml file or a screenshot of the input connector config? ... View more

Hi Leah Creiglow‌, The GeoEvent SDK comes bundled with GeoEvent Server as part of the installation files. You can find the documentation and samples for it at the following locations Windows: <ArcGIS Server installation directory>\GeoEvent\sdk (for example, C:\Program Files\ArcGIS\Server\GeoEvent\sdk). Linux: <ArcGIS Server installation directory>/GeoEvent/sdk (for example, ~/arcgis/server/GeoEvent/sdk). If you have seen it already, the documentation only shows examples using the Eclipse (Java EE edition) IDE.  However, in theory, as long as you have the proper components installed on the machine per the documentation (i.e. Java SE Development Kit, Maven, etc) then you should be free to use Visual Studio for your development needs. Since each IDE will differ in terms of what it will need to write, format, and compile the code (plug-ins, packages, and the like), we cannot really give definitive responses as to which to use, because there can be several routes you can take to accomplish what you need to to build custom connectors, transports, processors, etc. I hope this helps somewhat or can give you an idea of how to move forward. Perhaps fellow end-users who have tried Visual Studio in their development can give more specific examples.  ... View more

Hi Stefan P. Jung‌ I do not have a running GE environment in front of me right now to confirm, but GeoEvent has the option to set an HTTP and HTTPS Proxy in it's Global Settings. This is supposed to allow GeoEvent to connect to resources on the internet. If ArcGIS Server has a web context URL set, then this may need to be set to align with how you have the Server set. https://enterprise.arcgis.com/en/geoevent/latest/administer/managing-global-settings.htm ... View more

Hi MR Reddy‌ Just to clarify, are you looking to be able to have the input connector's Header Parameter Name:Value List property be automatically/programmatically updated while the input is running? ... View more

Hi Konrad Hughes‌ Try matching the letter case of how your username appears in your ArcGIS Online organization. GeoEvent is case sensitive when it comes to providing credentials for registered Servers/Portals/AGOL orgs.  For example, if your username in AGOL shows as ArcGIS2019, using arcgis2019 when registering the data store in GeoEvent will not work. Hope this helps! -Daniel ... View more

Hi Hatice Korkulu‌ I took a look at your XML and ran a few internal tests. In each attempt, I was met with the inability to parse the XML past the point of the "records" element. Because it is nested AND makes the field names a property of the value tag, it becomes difficult for Geoevent to read the relevant values. Another staff member also took a look and they suggested that using a field mapper may work to flatten the nested XML structure, but even so, Geoevent does not recognize anything past the first "uid" field. Presumably, this is because the names of each field are all properties of the tag and not tags themselves.  In short, the structure of this XML does not seem to be compatible with GeoEvent. If it is at all in the realm of possibility to get the data reformatted, like the example below, then GeoEvent should not have an issues with it. Otherwise, we may be at an impasse here. <records>    <uid>###</uid>    <tstres>###</tstres>    <temperature>###</temperature>    <humidity>###</humidity>    <shumidity>###</shumidity>    <Lati>###</Lati>    <long>###</long> </records> ... View more

Hi Erik Blake‌ It's hard to say what exactly may have happened to cause your output to stop receiving events. The Geoevent logs can help point you in the right direction as to what what the cause could be, but if you can, go ahead and try recreating the output connector with the same configuration and see if it works. ... View more

Hello Zachary Hart‌, Thanks for reaching out to us with your concern. Glad to hear you are looking to better understand the full functionality of the ArcGIS Enterprise platform.  It is understood that you are concerned with the apparent increase in cost for the workflows that you are currently implementing in your organization. While I personally cannot speak to the specific price points, based off what you described, I believe you should still be able to have users edit the services published to your server without having to provide them a named user in your Portal orgazaniton. However, this would entail sharing the services publicly as opposed to only within the organization. For example, if you published a feature service with editing capability, it will be defaulted to be shared only to the publisher. Sharing it to a group or to the Portal org will require authentication from a named user in the Portal. However, if shared with Everyone (Public), then the service will be freely accessible to those who are not named users. This would allow for editing without a named user account. Of course this workflow comes with it's own concerns, but this would be a means of working around the cost. Federating unlocks more functionality with your Enterprise workflows (i.e. Hosted Feature Layers, premium web apps, etc.), but you are right. It does entail having to be bound by Portal's user store configuration. ... View more

Hi Leo Ladefian‌, One common method of flattening out the JSON using GeoEvent is to configure the input to specify the JSON Object that you want to pull the prospective fields from. In this case, I believe you want to pull from status_changes. If you specify this for the JSON Object in the input, then upon saving and starting the input, GeoEvent will pull data and create a definition from everything under status_changes. You can then use this definition for other connectors. You can also leverage the Field Mapper processor to map this definition to another that may include it's own "coordinates" field that you manually create. Now, extracting the coordinates is what may be a little tricky. Since it is a little more deeply nested in the JSON, we may have to create a separate input connector that polls the JSON, but this time, only specify the event_location.geometry object (JSON queries do work in this regard) in the input configuration. This way the definition that gets created will include the "type" and "coordinates" fields. From there, you can output this into a JSON file and then use the Field Enricher (File) processor to enrich the original GeoEvent service from the paragraph above with the two fields from this file. Finally, assuming all goes well, the output can receive the data from status_changes along with the data from the "coordinates" field and will be able to be viewed on a web map. I realize that this workflow is a little tedious and sounds a little unorthodox, but this is the only way I can think of to both flatten the JSON and extract the data from the nested field. I hope this helps out. -Daniel ... View more

Hi Sharon Huang‌ Thank you so much for posing this question on GeoNet. We appreciate your eagerness to dive into GeoEvent Server and work with/learn all of its capabilities. However, I am sorry to say that Esri does not provide any publicly accessible GeoEvent Servers for testing. This product is really meant to be managed internally as the services that you create from it oftentimes require that you provide access credentials to specified endpoints (JSON/XML feeds, feature services on AGS, etc.). GeoEvent will work to process incoming data and then output it to things like web services, local files, emails, and the like. Because of that, it would not exactly be feasible to allow the public to all access one GeoEvent Server. If you would like to discuss product licensing and pricing for your organization, I would encourage you to reach out to either your account manager or Esri Customer Service and they would be able to help you get started if that is something you think can eventually be implemented for you and your team. I hope this helps. -Daniel ... View more