POST
|
That's great info, thanks for sharing. Not having to select a travel mode is even better than creating a new Network Dataset that doesn't have any!
... View more
02-22-2018
03:06 PM
|
0
|
0
|
938
|
POST
|
Yea, the Hierarchy suggestion is just a good practice for fiber routing in general and I thought it may help since it tends to be higher tier highways and such that have one-way roads with large medians. What sort of Network Dataset are you using? If you have the source data available, then you should be able to just build a new Network Dataset off of that data that has no Travel Modes attached to it. Not having a Travel Mode should mean that it does not recognize any field that would otherwise indicate a direction restriction, and *should* allow you to traverse any street segment in any direction without issue. Does it make sense what I'm suggesting? Let me know if you need me to elaborate.
... View more
02-21-2018
02:40 PM
|
0
|
0
|
938
|
POST
|
Hi Rich, Are you using Streetmap Premium for the input Network Dataset, or something else? The easiest way to avoid this is probably to adjust a couple of the Analysis settings in your Closest Facility Layer. The first few that I would try: 1) If you haven't already, uncheck the box for "Use Hierarchy". We likely don't need to for fiber routing. 2) There's a setting that asks how you want to treat U-turns at junctions. Try selecting the option for "Don't Allow" and see how that changes the results. I've had success with it, but you'll just have to see if it works with your dataset or if it just creates 3 left turns instead of a single U-turn. If that doesn't fix the issue then we will probably have to do some edge consolidation, which can get more complicated. Let me know what happens. Thanks, Hunter
... View more
01-24-2018
12:28 PM
|
2
|
2
|
938
|
POST
|
Robert is correct - Junshan and Derek should know, but I highly suspect that this will not be included anytime soon. With how new Web App Builder still is, our development teams are getting a very high volume of requests. I would encourage you to go to ideas.arcgis.com and submit an enhancement request for this if you are not able to develop it yourself.
... View more
07-01-2015
01:26 PM
|
0
|
0
|
1085
|
POST
|
You're correct - the current Query widget does support multiple layers and fields, but the configuration does not allow the end user to actually type their own SQL query. You would have to go through and manually define queries for each layer and field, which is obviously undesirable to say the least. As far as I know a widget like you're describing is not on the Web App Builder roadmap, however, Robert Scheitlin has developed an "Enhanced Search Widget" that may meet some of your criteria, or at least give you a place to start.
... View more
07-01-2015
12:26 PM
|
2
|
3
|
1085
|
POST
|
Hi Kevin, Honestly, I'm not certain if this is on the Web App Builder roadmap or not at this time. However, as I'm sure you're aware, Web App Builder does have a "Query" widget that can be used as a "Select by Attributes" tool depending on what you're trying to do. If you're trying to see only the query results in the attribute table, then check the option to create an operational layer, navigate to your attribute table via the arrow at the bottom of your map, and the new layer with only the selected records should be one of the tab options in there. Alternatively, if for some reason it is not there, open your layer list, hit the drop down arrow next to the operational layer, and click "Show in Attribute Table". If you're interested in editing a selection then our "Batch Editor" widget can be used. This should allow you to edit using "Select by Location" or a "Select by Feature" functionality. This widget can be found here in our open github repository. As far as *directly* addressing your question - widgets in Web app Builder will have the ability to communicate with each other in the near future. This would presumably mean that the query widget would be able to directly communicate with the attribute table widget to reflect your selection directly. Hope that helps. Thanks, Hunter
... View more
07-01-2015
09:15 AM
|
2
|
5
|
1321
|
POST
|
We have had a lot of requests for this and it has been formally added to the WebAppBuilder enhancement request list. Usually this means that it will be included in core within a few releases.
... View more
06-29-2015
07:30 AM
|
3
|
14
|
1321
|
IDEA
|
One of the critical value components to the Operations Dashboard for ArcGIS is the ability to track events in real time. In order to continue to be relevant with regards to real-time data tracking and management, Operations Dashboard must support Stream Services and Stream Layers. Even if supporting widgets and data feeds from a stream layer is difficult, Ops Dashboard should at least allow a user to pull in a Stream Service/Layer as a visual reference, just like you can do in a web map.
... View more
04-03-2015
09:39 AM
|
35
|
9
|
3977
|
BLOG
|
Thanks for this, Richard - very helpful. Would you mind breaking down the logic in this line for me? I would like to know what each of the components is doing: valueDict1 = {r[0]:(r[1:]) for r in arcpy.da.SearchCursor(sourceFC, sourceFieldsList)}
... View more
02-26-2015
08:37 AM
|
1
|
0
|
18947
|
POST
|
Thank you for the clarification! You mentioned that you have a data source that contains the bus routes - do you also have data for each of the bus stops? In order to creates isochrone polygons and determine the accessibility of each bus stop (which it sounds like you are trying to do), you will need a point layer that contains each bus stop as a feature. Am I understanding your goals correctly? Thanks, Hunter
... View more
02-26-2015
08:01 AM
|
0
|
0
|
602
|
POST
|
Good question - one way to do it would just be to clip your input features to only use the area that you're interested in, but if your network dataset spans a large area then this won't be optimal. The other (and more direct) way to do it would be to use the "Calculate Locations" geoprocessing tool, which will generate a field telling the network dataset where those features are in relation to it, and then running the "Add Locations" geoprocessing tool using that new field instead of the line features geometry. That should make the features a reference rather than a sort of copied memory object. Does that make sense? Let me know if you have any additional questions and how that works out for you -Hunter
... View more
02-26-2015
07:53 AM
|
1
|
0
|
956
|
POST
|
Yes, that's it! I can't remember if "1" is the largest or "6" is the largest, but if you run a selection on the two or three largest and just export a new layer from that it should give you all major highways and freeways. You'll just have to play with it and see what fits your needs that best.
... View more
02-24-2015
01:08 PM
|
2
|
2
|
956
|
POST
|
Deogratias, Xander is right - we need more information about your question to properly assist. If you are talking about site accessibility, then Jayanta has provided the correct documentation above. If you are talking about road accessibility or accessibility of some other network then we should have a different discussion. Please provide us with some additional details so that we can help you out. Thanks, Hunter
... View more
02-24-2015
08:51 AM
|
1
|
0
|
602
|
Title | Kudos | Posted |
---|---|---|
1 | 02-24-2015 08:23 AM | |
1 | 02-24-2015 08:51 AM | |
1 | 02-26-2015 01:09 PM | |
1 | 02-26-2015 08:37 AM | |
2 | 01-24-2018 12:28 PM |
Online Status |
Offline
|
Date Last Visited |
11-11-2020
02:24 AM
|