Latest Contributions by SarahAmbrose

Hi Dalinda, I have two recommendations, and they depend on the size of the data. Option 1 is good if you are using Pro, the portal Map Viewer, the ArcGIS REST API, or the ArcGIS API for Python.Option 2 is only available to you if you are using ArcGIS Pro to run analysis.  Share it as a feature service first - and in most cases I would recommend this! You can do this through Pro (creating a hosted or non-hosted layer) using the Sharing pane.  You can do this in Portal, by uploading a zipped file gdb + publishing a hosted layer through Portal. Once you have a feature service, you can analyze it! If the data in the file geodatabase is pretty small you could add it to the map in Pro, and just run analysis on it. Only do this if the dataset is small (< a few hundred features). A good example of this would be if you were joining a big dataset to a small dataset, or aggregating a lot of data into a small polygon dataset. For both of these examples, the file geodatabase is the "small" dataset! If this is a feature you’re interested in, I would recommend adding an enhancement request through Esri support services. I’ve made a note of it, but with an official enhancement request, we’re able to see when multiple users want the same functionality, and prioritize the most popular ones first. A note on this comment: By default, GeoAnalytics results are stored in the spatiotemporal big data store. At 10.5.1 or later in the portal Map Viewer, and in Pro 2.0 and later, you can optionally save your results in the relational data store as well.    Thanks for the question and let me know if I missed anything. Sarah Ambrose GeoAnalytics Product Engineer ... View more

Hi Dalinda,  Another great question! We aren’t able to tell how much of our users are mixing traditional desktop tools with GeoAnalytics tools. But, I can give you some general best practice guidelines and recommendations of when to use a mix of regular Pro GP tools and GeoAnalytics tools. When we run GeoAnalytics tools with regular desktop tools (talking about Pro specifically here) we mostly do it in the following scenarios: When we start using GeoAnalytics and use it to summarize, aggregate or analyze the data so that it becomes a more manageable size. Then we chain Pro tools on using the smaller, more manageable result. When we’re analyzing data that’s of a size we could analyze with Pro tools, but we’re hoping to take advantage of capabilities only available in GeoAnalytics (like time steps in Aggregate Points, tools unique to GeoAnalytics, accessing data in a big data file share). Let me know if you have any more questions on a specific use case or workflow. With more details on the type of data, data location and planned analysis, I can help figure out the best place to stage your data, and recommend how to take the most advantage of analysis on ArcGIS Enterprise.  Sarah Ambrose Product Engineer, GeoAnalytics Team ... View more

Hi Dalinda Damm,   Great question! GeoAnalytics definitely works for space only. We often emphasis time in presentations and documentation because it’s a new concept for analyzing GIS data. Most customers of GeoAnalytics have time enabled data, since big data is often observational data accumulated over time, but many don’t use time at all!   There are only 2 tools at 10.5/10.5.1 that require time, Create Space Time Cube and Reconstruct Tracks. At 10.6, the tool Detect Incidents requires time. Other than those listed tools, you can take advantage of lots of ‘run of the mill’ tools that have been implemented for distributed analysis. For example, some of our most popular tools that don’t require time are Aggregate Points, Join Features, Summarize Attributes, Find Hot Spots and Copy to Data Store.   Please let me know if you have any follow up questions.   Thanks, Sarah Ambrose Product Engineer, GeoAnalytics Team ... View more

Hi DalindaDamm‌,   It is expected that there will be new tools exposed in the GeoAnalytics Toolbox in ArcGIS Pro at each release (and we’re working on more now!). It’s important to point out that Pro is a client for GeoAnalytics Server. This means that tools are first implemented in GeoAnalytics Server, and Pro is just one way of running the tools you have on your GeoAnalytics Server (you can run them through the Portal Map Viewer, the ArcGIS API for Python and REST as well).   At 10.5 and 10.5.1 there are 12 GeoAnalytics Tools. At 10.6 we introduced three new tools, Calculate Field, Detect Incidents, and Geocode Locations from Tables. The Pro 2.1 release went out around the same time as 10.6, and exposed the Calculate Field and Detect Incidents tool.   We’re currently working on 10.6.1 which will include some new tools. It is planned that these new 10.6.1 tools will be exposed in Pro 2.2. We’ll be continuing this pattern in future releases. Please note, if you have GeoAnalytics Server version 10.5 and Pro 2.2, you can only use the tools from 10.5, not the tools that were created at 10.6 even though your Pro version is recent.   The focus of the new tools can be broadly categorized into a few groups: Classic GIS tasks (similar to join features, this could be something like appending data or applying overlays, as well as more track analysis to tie in with real-time data) More sophisticated analysis – we’re currently researching and working on machine learning and statistical techniques that are relevant to big data. Are there any tools or workflows you were hoping to use GeoAnalytics for?   Please let me know if that doesn’t answer your question. Let me know if you’ll be at the upcoming DevSummit, User Conference, of Federal User Conference and I can recommend some sessions to attend related to GeoAnalytics.     Sarah Ambrose Product Engineer, GeoAnalytics ... View more