POST
|
Yes, we require sub-foot accuracy for our locations.
... View more
03-18-2021
06:37 AM
|
0
|
0
|
620
|
POST
|
We are using Collector to inspect existing water meter point features and update their locations using a survey-grade GNSS receiver connected to an iPad. As outlined from the Collector App help docs (pictured below), when updating an existing point in the Edit screen, you have to tap the GPS button to center the point over your current location. If you don't click the GPS button, the location centers on the point that you select, which for us could be several hundred feet away from where it needs to be. Does anyone know of a way to set the GPS location to *always* be centered on your location? We edit such a large number of points and would like to save "clicks" wherever possible. Thanks in advance!
... View more
02-08-2021
10:53 AM
|
0
|
2
|
756
|
POST
|
We are also seeing this, although our feature service is hosted through Portal. We are not seeing the oddball required field on the Webmap Viewer in Portal, but it shows up when we try to make edits in the Collector app for iPad. Same thing, it is the layer that we are using for symbolizing. No luck so far in fixing it, but if we figure it out I will update here.
... View more
10-12-2020
05:55 AM
|
0
|
0
|
343
|
POST
|
I think I figured it out! I was trying to re-run my script after fixing a different error. I had env.overwriteOutput = True at the top of my script, but for some reason I think it wasn't actually overwriting the NA Layers in the file gdb. I have read that it's a common error with newer versions of Pro on some features for whatever reason. Once I removed the previously created NA Layer from my last script attempt, the new NA Layer was created without error and my stops were added with AddLocations just fine. Hopefully this helps for anyone else having similar issues! Thanks again for all your help, Melinda. My scripts are both working great now with .nax, .na, and .mp utilization!
... View more
08-07-2020
01:35 PM
|
0
|
0
|
314
|
POST
|
Ah, ok that makes sense. I didn't see an option to view syntax specifically for 2.5; is that documented somewhere or is it more of an understanding gained from working in Pro more and more? That worked for me, but I am now getting an error when I try to load my points into the stops sublayer. I am wondering if it is a similar issue, where one of the parameters I am using is only for 2.6? This is the block of code I am using: layer_object = arcpy.na.MakeRouteAnalysisLayer(network,route_name,"Driving Time","FIND_BEST_ORDER","","","ALONG_NETWORK","","DIRECTIONS").getOutput(0)
sublayer_names = arcpy.na.GetNAClassNames(layer_object)
stops_sublayer_name = sublayer_names["Stops"]
routes_sublayer_name = sublayer_names["Routes"]
arcpy.na.AddLocations(layer_object, stops_sublayer_name, input_points, "", "5000 Meters", "IDNO", "", "MATCH_TO_CLOSEST", "APPEND", "NO_SNAP", "5 Meters", "INCLUDE", "")
arcpy.na.Solve(layer_object, "SKIP") This is the error returned on line 7: ExecuteError: Failed to execute. Parameters are not valid.
ERROR 000840: The value is not a Network Analyst Layer.
Failed to execute (AddLocations). I am confused as to why it is not recognizing my "layer_object" as an NA Layer, especially because I can see the NA Layers being added to my map and table of contents while the script is running. Also, I apologize for asking so many questions! I am usually pretty good about being able to research my errors and figure out a solution, but I feel like with all the updates to Pro and new modules I need to utilize, I'm having difficulty finding common errors and solution documentation. Thank you in advance!
... View more
08-06-2020
12:39 PM
|
0
|
2
|
2692
|
POST
|
Hello Melinda, Thanks again for all the help lately! That method worked perfectly and I feel confident with the .nax module for routing now! Down the line we are possibly going to be using this script to host map services, so I am also trying to fix the .na module code to work in Pro and to better my understanding of its differences. Now I am having difficulty with the MakeRouteAnalysisLayer method. On this line: layer_object = arcpy.na.MakeRouteAnalysisLayer(network, route_name, "Driving Time", "FIND_BEST_ORDER", "", "", "ALONG_NETWORK", "", "DIRECTIONS", "") I am receiving this error: TypeError: MakeRouteAnalysisLayer() takes from 0 to 9 positional arguments but 10 were given I am working from this syntax: MakeRouteAnalysisLayer(network_data_source, {layer_name}, {travel_mode}, {sequence}, {time_of_day}, {time_zone}, {line_shape}, {accumulate_attributes}, {generate_directions_on_solve}, {time_zone_for_time_fields}) Previously, when I attempted to modify my code for use in Pro (before my initial post requesting help), it was not returning this error. Any insight into this? Thanks in advance, Jordan
... View more
08-03-2020
11:44 AM
|
0
|
4
|
2692
|
POST
|
Thank you Melinda! That's all I needed to make it work, and it looks great! The .nax module is definitely more straightforward and user-friendly; it looks like I saved myself about 20 lines of code with the switch. I do have one (hopefully) last question, regarding the returnDirections property. I have read that .nax stores everything in memory, and I would like to view the turn-by-turn directions for the generated route. I do not have much experience with in-memory storage. Is there a quick line of code I can insert to call to the route directions output, using that returnDirections property on the route solver? My purpose in viewing the directions is to see the sequence of the stops that are used on the route. Is there a better way to view the sequence using the .nax module than trying to view the directions output?
... View more
07-29-2020
06:31 AM
|
0
|
6
|
2692
|
POST
|
Hey Melinda, Thank you for your quick response. I read through the materials again with your explanations in mind and I attempted to edit my script accordingly. I was going to give it a whirl again using the .nax module and foregoing the arcpy.mp module (since the .nax module is more straightforward with exporting fields). However, I had a .nax module issue from the get-go. Even after checking out the network analyst extension, I am receiving this error on the following line: route.load(arcpy.nax.RouteInputDatatype.Stops, input_stops)AttributeError: module 'arcpy.nax' has no attribute 'RouteInputDatatype' Is this a sign that I should instead try to utilize the arcpy.mp module in conjunction with the legacy arcpy.na module?
... View more
07-28-2020
11:51 AM
|
0
|
8
|
2692
|
POST
|
Previously, I was working in ArcMap 10.6.1 and created a script utilizing the arcpy.na module. I had no Python background prior to this rather large undertaking, so my (still limited) Python knowledge is based in ArcGIS. The purpose of this script was to iterate through a set of polygons, select the intersecting points in each polygon, load these points into a new Network Analysis Route layer, solve that route, then move on to the next polygon and repeat. It was working pretty well! Then, I decided to migrate to Pro 2.5... I was successful in most of my gp tool migrations. However, there are 2 major "module-based" issues I am having: 1. I am having difficulty understanding how to migrate from the arcpy.mapping module to the arcpy.mp module in Pro. 2. I've been a little confused with the differences between the .nax module and the legacy .na module, even after reading the "choose your module" help page. The .nax module seems much simpler and more straightforward, but it appears to not have the ability to create network analysis layers. That is the main function of my script. I feel as though I am back at square one trying to navigate these migrations. Does anyone have any experience moving to these new modules? Is anyone else in the same boat as me?
... View more
07-22-2020
07:11 AM
|
0
|
10
|
3183
|
Online Status |
Offline
|
Date Last Visited |
09-01-2021
02:48 PM
|