Latest Contributions by DanielCota1

Shakil Choudhury‌ Thank you so much for providing the app. I took a look and I do see the same behavior as you described. For testing purposes, I did also copy the code into my own app and was able to see the same issue as well. However, what I found was that after modifying the Expand widget to have the "Expanded" property set to false instead of true, it will open and close without any cutoff. See below: var legendExpand = new Expand({       expandIconClass: "esri-icon-layer-list",       expandTooltip: "Expand Legend",       collapseTooltip: "Collapse",       expanded: true,       mode:"drawer",       view: view,       content: legend,       group: "top-right" Is this something you can try and/or work with? In any case, I have went ahead and logged a bug against this because it should still work regardless to keep the button in place whether this property is set to true or false. If you have any questions in regards to the bug, feel free to contact Esri Support and they can assist with that. ... View more

Hi Shakil Choudhury‌, Any chance you can provide a sample of the code you are working with? I tested the widget functionality on iOS Safari and it seems to work fine with the sample from Expand widget - 4.9. As such, there is not much ground to log any bugs against the API. Also, what version of iOS is the device running? -Daniel ... View more

Hi Fraser Hand‌, I do not have any working experience with using BitLocker or any other encryption methods in an Enterprise deployment, but I do know that it is known to cause major performance issues with the software, if not totally breaking it. The reason being is that there is constant web communication and intercommunication that takes place with the software (all running in the background) and the encryption process that is being done ends up slowing everything down significantly. -Daniel ... View more

Hello Mark McCart‌, I believe this would be expected for GeoEvent. The throughput will be determined by many different factors (the size of the event/data, the machine resources, etc). 500 sounds about right, but I would also be curious to know the nature of the data being written along with the performance of the Spatiotemporal Data Store machine. The BDS is designed to handle large amounts of data, but not necessarily when they come in at a frequency it cannot handle if resources are maxing out. Either way, while we constantly strive to improve GeoEvent's performance, I think it will be a long time before we can reach the point of writing millions of records in the same time it takes to currently work with a couple hundred or thousand. Again, there are a ton of moving parts here, but overall, I would look into ensuring that the data is clean and the machine resources are sound. -Daniel ... View more

Hi Jean-Marie DULISCOUET‌, Any chance you can provide the URL that you are trying to access within Geoevent? Depending on how the JSON is accessed, it can require a certain MIME type. Thanks, Daniel ... View more

Hi Jason Sphar‌, There a couple of things I would like to address... The definition looks like what would be expected from the sample JSON you provided. It creates a couple of grouped fields where the nested JSON is detected. That is how Geoevent parses it based off the JSON structure. However, depending on your desired output, you may want to configure the input connector to only pull from a certain subset of the JSON. For example, if you only want the data under "data' to be parsed and processed through Geoevent, you will want to set "data" as the JSON Object Name in the input connector configuration. If you want ALL of the data in the JSON to go through, you will want to manually create a flattened definition that will then be used for the feature service output. From there, you can use a field mapper in the Geoevent Service to map the hierarchical definition from the input to the flattened definition on the output. When creating the flattened definition, you will want to pay close attention to the schema and the field types that the definition is using. It should match the original as much as possible. One last point to consider, and this may not hold true for your final workflows, but the sample JSON you provided does not seem to include any spatial data that can be used to construct geometry for a feature service, at least not from what I can tell. If you want to add this data to a feature service that can be displayed on a web map or other mapping client, it needs that spatial component. Now, you may plan on using different data or using a processor to append spatial data within the Geoevent service, but as it stands now, there is none. Just wanted to make sure you were aware. I hope this helps. -Daniel ... View more

Ellen Lester‌ Do you mind if I ask you to show us what the schema looks like for both the Stream Service and the Feature Service? You can check this by going to the REST endpoint for each service and clicking on the layer ID.  i.e. layerName(0) Also, this can very well be a small fluke. Have you already tried republishing the stream service and re-implementing the new service into the Geoevent service? Thanks, Daniel ... View more

Hi Matt Fancher‌, On the surface, GeoEvent is capable of passing credentials to authenticate against a certain endpoint. This can either be done through a GET request where the parameters for credentials/token are passed within the URL itself or through a POST where the headers for authentication are specified in one of the input connector's properties. I am unsure if there is a means to send one request, receive the response, and then send another through the connector.  Do you have a means of accessing the endpoint you need in one fell swoop, to where you can bypass the authentication or somehow include it in a single request? ... View more

Hi Andrew Bednara‌ Try going to Server Admin > system > platformservices > Synchronization_Service > status to first check if it is started. You can then try starting it if it was stopped or restarting it using the start operation. After the status is shown as STARTED again, check to see if logging in works. -Daniel ... View more

Hi Braulio Galvez‌ There does look to be an issue with the sample services on that server. It could be related to the Geoevent services that output to the stream layers or it could be a misconfiguration on the servers themselves. RJ Sunderman‌ might have some insight on this. -Daniel ... View more

Hi Xiaoyi Zhang‌ Have you taken a look at the following documentation? Upgrades to Portal 10.6.x will require that you upgrade Living Atlas content as well from Organization > Edit Settings > ArcGIS Online. From here, click Upgrade Content (FAQ) - Upgrade your ArcGIS Enterprise portal—Portal for ArcGIS (10.6) | ArcGIS Enterprise  (How-To) - Upgrade your ArcGIS Enterprise portal—Portal for ArcGIS (10.6) | ArcGIS Enterprise  I hope this helps. -Daniel ... View more

Understood. I agree that it would be a stretch for Geoevent to play nicely with the {} special characters. However, it may not matter if the URL in a browser does not work. Put simply, Geoevent will read any data that is accessible at a certain endpoint. Whether that is just all of the JSON for a certain resource, or queried JSON, it's all the same to Geoevent. JSON is JSON. If it does not work in a browser, then it likely will not work in Geoevent. -Daniel ... View more

Hello J molk‌ May I ask what is the result if you were to manually construct the query URL by appending the parameters yourself and then see if it is resolvable on a web browser on the GeoEvent Server? i.e. http://flightxml.flightaware.com/json/FlightXML2/SearchBirdseyeInFlight?parameter1=test&parameter2=test I see that the base URL needs authentication to access, so I am assuming you include that information in the Header Parameter Name:Value List field? Either way, it could be that the query string that is being added is either in a format that Geoevent cannot recognize or that it is in some way invalid. Please see if you can test manually constructing the URL and then navigating to it in a browser. If that works to return the expected JSON, try seeing if you can use that URL as the value for the URL field in the input connector. It would also be working double-checking that the MIME types included in the input connector are: text/json, application/json You can also check the Geoevent logs to see if any messages were logged for inaccessibility to the URL you provided. ... View more

Javier Rodolfo Pintos Ettlin‌ Hello Javier, There are two things to address here. You are correct. Any connection to the admin API is going to require a token. Otherwise, trying to access that endpoint will result in a "Forbidden" error. However, the message that you mentioned says "Unsupported media type." This is likely due to the fact the MIME type in the input connector configuration is not set correctly. The monitoring endpoint is formatted as JSON. Since it is not a JSON file that is being accessed and rather a JSON API, you will want to make sure the MIME type specified is application/JSON. Once this is set, you should no longer run into the Request failed (HTTP/1.1 415 Unsupported Media Type) error. Now, going back to the access concern...the way to work around this would be to somehow include the token in your request to the endpoint. The simplest way would be to generate a token from the Portal admin directory. From there, you can append the token to the URL and use that URL for the input connector's URL parameter. You should then see the counts go up for that input and a definition be created. I hope this helps! -Daniel ... View more

Shawn Bowers‌ Hi Shawn, Either resetting or uninstalling/reinstalling Geoevent (after a backup) is usually recommended for these kinds of issues because you can be more sure that the old configuration was removed. However, if you are intent on avoiding this workflow, what you can look into is leveraging the Geoevent API to update these settings programmatically. The following operations would probably be your best bet. The first would be to get the JSON structure for the default data store configuration and the second would be to update that JSON to use the URL that you want to change it to. https://<SERVER>:6143/geoevent/admin/api/index.html#!/datastores/getDefaultDataStore  https://<SERVER>:6143/geoevent/admin/api/index.html#!/datastores/addOrUpdateNewArcGISServerConnection_1  If you have any experience working with JSON web API's, then you can explore this workflow to get your connection updated. I hope this helps. -Daniel ... View more