Latest Contributions by SarahAmbrose

I agree with @BobBooth1. 1. It sounds like you have correctly filtered your polygon layer, great! Remaining decisions are mostly about excluding features in your lines layer to lower the number of credits consumed.  2. For the environment settings you have a few viable options: Processing extent: You have a few options: Layer - This will use the extent defined on the layer (even if you have a filter, it's pulling it from the original layer), and isn't filtering down the features. This will produce the same result as below, but will cost more credits than if you exclude some features for analysis (via other env settings). Display extent - this will help help cut down on credit consumption. Note that it won't "clip" the input features, it will use anything that intersects with your display extent. I would recommend using this option, and make sure when you run the analysis you are "viewing" the area of interest. If you don't want think about what's covered in the extent when you run the data, you can choose "Coordinates" and then "Set coordinated from display" - this will set the extent when you click the button, and won't change even if you zoom or pan around before clicking run.    Output coordinate system - I would keep it as the default unless you know your result should be in a different coordinate system than the inputs.  Another option, if you have a way to filter the roads based on region, you could also do that. Then when you run the analysis, it would only use your roads within Burford. Currently, you have  > 260,000 features of roads, and it looks like you probably only care about a very small subset of them. So if you can filter them on an attribute, I would recommend that over the environment settings. A future note - if this is data you continuously use in the future, and you only care about Burford you could make a view of the data. Then, you could use the view in the future (which lets you apply spatial and attribute filters on a layer) and they look like they are a layer in your org. Doing that would mean you wouldn't need to filter the next time you open it in the map, nor would you mistakenly run analysis on all the features. https://doc.arcgis.com/en/arcgis-online/manage-data/create-hosted-views.htm I don't think you need to make a view for this analysis, it's more to make long term maintenance + analysis easier once you've figured out your future needs + complete this analysis.    ... View more

Hi @Jay_Gregory, Great question - the requirements for ModelBuilder in Online are outlined here:  https://doc.arcgis.com/en/arcgis-online/analyze/licensing-modelbuilder-mv.htm   I think it's most likely that you don't have the correct user type. Can you please verify that you are a professional or professional plus?  Please let me know if that doesn't enable ModelBuilder for you. It should be available even if you're not in the early adaptor program.   Thanks, Sarah Ambrose, Product Engineering Lead, Web Analysis ... View more

Hi @MobiusSnake I'm on the web analysis teams and can answer these questions. You are right, in Map Viewer we now keep a history of analysis in the map so you can easily rerun tools, review failures and messages, and iterate on your analysis. There is documentation on history here. So for your specific questions: 1. The only things stored in history are what you see in the history panel. This includes: The parameters (including input layer URL and filters) Any errors or warnings about the job The time it completed, the status, and any credits consumed The output layer   2. The history is stored within your web map. If you don't save the web map, your history is gone.  3. You can delete the history items by clicking on the X. You also don't need to save the web map, if you just want your results, and have no need for the history. Please let us know if you have any follow up questions, Sarah Ambrose Product Engineer, Web Analysis ... View more

Hi @Jay_Gregory, great question. To create a layer that only has unique points, you can use a few tools in succession to create a polygon for each point, dissolve the overlapping polygons to find unique locations, and then find the centroid of each unique polygon to create the unique points. Below is a workflow to complete this:  Run Create Buffers on the geocoded points. Use a small distance, like 1 foot. For other parameters, use the tool defaults.   Run Dissolve Boundaries on the Create Buffer output. There is now a single polygon at each unique geocoded location.  Run Find Centroids on the Dissolve Boundaries output. This will create a unique point for each unique location.   [Optional]If you want to keep the attributes from your original data, you can use Join Features to add the attribute data to the new point layer. The target layer will be the Find Centroids output and the join layer will be the original data.  Perform Drive Time Analysis like you planned to.  Thank you again for the great question - we’ll be sure to look at how we can create this functionality into a single tool in the future. Please let us know if this works or you have any questions. If you are using ArcGIS Online, try out the tools in the new Map Viewer so you can take advantage of new features like an updated UI and history.  Sarah Ambrose Map Viewer Analysis and GeoAnalytics Product Engineer ... View more

Yes - the same problem in Edge. This issue should now be fixed with the latest release of Online, and working as of yesterday.  To learn about what's new in analysis, check out this blog. ... View more