|
POST
|
That is the difference. Locators built in ArcGIS 10 handle the intersection connector differently than locators built in 9.3.1. I may give the blog post a shot. Thanks, Joe.
... View more
06-20-2013
06:45 AM
|
0
|
0
|
1300
|
|
POST
|
Joe - which version of ArcGIS are you using? What kind of geocoder? Mine fails every time... Interesting. Also, I had considered a point feature class (following this example of how to create one http://blogs.esri.com/esri/arcgis/2013/02/11/streetintersectionlist/). That blog post about creating the intersections makes it less tedious and time consuming...
... View more
06-19-2013
02:39 PM
|
0
|
0
|
1300
|
|
POST
|
Thank you so much for all of your input, gmohler. If anyone else knows how to customize the locator so that it will geocode without spaces around the intersection connector, I'd still appreciate the help.
... View more
06-13-2013
07:53 AM
|
0
|
0
|
1300
|
|
POST
|
You're correct, of course...but I'd rather not scrub the data beforehand. I want to customize a locator that can deal with this situation so I don't have a two-step process.
... View more
06-12-2013
06:25 AM
|
0
|
0
|
1300
|
|
POST
|
Does anyone know how to customize a locator so it will geocode an intersection in the format: W First St/N Main Ave or W First St&N Main Ave It works if I enter the intersection this way: W First St / N Main Ave or W First St & N Main Ave But if I'm missing the spaces, then I get 0 results. I have users who consistently enter intersections without the spaces. I'd rather solve this myself than force them to change their data entry. Thanks, Shawna
... View more
06-07-2013
10:50 AM
|
0
|
13
|
4141
|
|
POST
|
Any help would be most appreciated... I need to execute an MS SQL stored procedure which creates a temporary table with xy records, and then interact with that temporary table via arcpy to create a point feature class. I've got the stored procedure built, and I know how to make an XY event layer and then save the records to a feature class. Is there any way to execute the stored procedure and then use arcpy to interact with the results? So far, I cannot find a way to make this work.
... View more
07-06-2012
09:29 AM
|
0
|
0
|
2216
|
|
POST
|
I have the following line of code: arcpy.SelectLayerByAttribute_management(gridLyr, "NEW_SELECTION", "\"Page\" Like \'"+ Neighborhood +"%\'") This line works just fine running directly in Python, or when running as a script tool in toolbox. However, when I publish the toolbox to ArcGIS Server, I get the following error: ERROR 000358: Invalid expression Failed to execute (SelectLayerByAttribute). Any suggestions? I'm not sure what is wrong, since it works great from my script. Thanks, Shawna
... View more
12-16-2011
12:53 PM
|
0
|
0
|
1756
|
|
POST
|
Correction - you do not need to use definition queries to limit the number of atlas pages. After working with Jeff (thanks, Jeff) - we determined that I had a corrupt atlas grid. Once my grid was fixed, my performance issue was resolved with no need for extra steps in code.
... View more
11-23-2011
08:31 AM
|
0
|
0
|
1549
|
|
POST
|
I figured out a work-around for the performance issue. I don't load my entire atlas grid at once. Instead, I have a definition query on the grid to limit the number of pages. Then (since this script is going to take user input) I have my users enter in their area of interest. I take that input and updated my definition query. Finally, I have to refresh the data driven pages object to have the atlas update to the new area of interest. Adding these additional steps made it so an atlas book that had taken 7 minutes to run took just 30 seconds. So much better!!!
... View more
11-16-2011
09:11 AM
|
0
|
0
|
1549
|
|
POST
|
Okay- the culprit is my atlas grid. I tried creating a very small grid (just a few pages) and that runs almost instantly. So, I guess I need to have a smaller grid. That's unfortunate because I really need a comprehensive, County-wide atlas. Jake- thanks for your post, using a different time module wasn't the issue in this case.
... View more
11-08-2011
07:30 AM
|
0
|
0
|
1549
|
|
POST
|
Hi Jeff, There are sixteen layers in my mxd and no broken connections. I have tried saving it to a new file, but that doesn't make a difference in speed. I do have a join to a SQL database for labels, but I've tested removing the join and don't see any performance gain. It still takes 7 minutes. Do you have any other ideas for me to test? Thanks, Shawna
... View more
11-08-2011
06:35 AM
|
0
|
0
|
1549
|
|
POST
|
Update: I've found that it doesn't seem to matter what the second line of code is...even if I simply reference my data driven pages, it takes 6-7 minutes between the call to the mxd and the next call. mxd = arcpy.mapping.MapDocument(r"pathtomxd.mxd")
print datetime.datetime.now()
ddp = mxd.dataDrivenPages
print datetime.datetime.now() Why would that take so long?
... View more
11-07-2011
09:35 AM
|
0
|
0
|
1549
|
|
POST
|
I am using arcpy.mapping to create an atlas that will run via ArcGIS Server - the atlas uses two dataframes. One of the dataframes holds the data driven pages grid and the other dataframe has a locked extent (so it zooms to wherever the atlas dataframe is zoomed to). Everything works very well, except very slow performance for one step of my code. Here's some of the code I'm running- to find the mxd and then start updating some definition queries in my second dataframe (the one that has a locked extent): mxd = arcpy.mapping.MapDocument(r"pathtomxd.mxd")
print datetime.datetime.now()
for df in arcpy.mapping.ListDataFrames(mxd, "Street View"):
print datetime.datetime.now() When I compare the two datetime stamps- there is a 7 minute gap between the two. Why is that? The rest of the code runs in just about a minute (which is fine since it is exporting a whole map book). But I just can't figure out why this one step takes 7 minutes. Any ideas would be most appreciated! 😄 Shawna
... View more
11-07-2011
06:48 AM
|
0
|
8
|
1909
|