Latest Contributions by KeithD1

‎04-13-2017

Seeking advice on labeling (or annotating) roadway route concurrencies, WITHOUT using Roads and Highways (I have access to an Advanced license for ArcMap10.1, soon 10.4). Here is what I want to achieve. Note how the labels for (93/1/3) and (93/1) are placed close together rather than being spread out along the line. I have two pre-existing choices for accessing the geometry. this structure: FID Route 1 IH-93 2 USH-1 3 CTH-3 or this: FID Route1 Route2 Route3 1 IH-93 USH-1 2 IH-93 USH-1 CTH-3 3 IH-93 USH-1 The former uses as a single feature per route; features overlap wherever routes become concurrent. In the later, the concurrencies have already been identified and merged into a single feature with each route being identified in the attribute table. Any advice on producing labels or annotation in this situation?

‎11-21-2016

Thanks for the detailed and thorough response, Xander!

‎11-16-2016

Thanks Joshua. This looks powerful enough to justify waiting for the 10.4 deployment at my workplace. If anyone else is reading this, I would still be interested in a 10.1 based solution.

‎11-16-2016

Looking for suggestions on trimming polyline features to a specified length starting at a specified distance from the start of the tine. Both values are provided as feature attributes. The resulting features should be perfectly coincident with the original ones, just one end will be removed. Seems like there should be a pre-installed tool for this...am I missing something? I'll be automating the resulting process (ArcPy?) running on ArcMap 10.1 (soon 10.4) with an Advanced license, in case that opens up any additional possibilities. Thanks!

‎10-22-2016

I'm working with the Make Query Table tool to join two Personal Geodatabase feature classes and one table, in support of a "snap to closest feature with matching attributes" process. The table, produced by the Generate Near Table tool, indicates the distance between any pair of features from the two feature classes. Currently I'm able to handle the "with matching attributes" portion in the SQL, but I'm having to handle the "closest" part in subsequent steps. The two features classes are very large so there are likely to be millions of matches, which is why I'm interested in only outputting the closest one, in order to have reasonable processing time. Is it possible, in SQL, to combine everything in one step? So first it would be subsetting to "matching attributes" and then it would be subsetting to the one with the lowest distance. I can post an example if that would help. Thanks!

‎09-23-2016

Thanks Dan, I appreciate the response. A little over my head at this point, but maybe for my next Python project I'll be able to incorporate what you described! For now, I'll just redundantly copy-paste the codeblock where I need it to go.

‎09-23-2016

I'm not sure what you mean by "save it as a text file even inside a python script". If I enclose everything in triple double quotes, then it won't execute, but it will still become a variable?

‎09-23-2016

I'm using arcpy.CalculateField_management() with a large-ish codeblock. Is there a way to store the codeblock so it can be easily reused multiple times, and more importantly, easily edited? This is part of a larger script. For instance (psuedo-code): codeblock = " line 1 statements line 2 statements some indented statements # a comment line 3 statements " arcpy.CalculateField_management("1st_dataset_name","field_to_calculate","codeblock") arcpy.CalculateField_management("2nd_dataset_name","field_to_calculate","codeblock") What would be the proper way of doing this? Thanks!

‎09-22-2016

Thanks for the quick reply - the code now works as expected.

‎09-22-2016

Can anyone explain what I've done wrong here. Have a feeling this is really simple...(new to Python). This code si being pasted into the Immediate window in ArcMap 10.1, in order to calculate a field with an "incrementing" value. I would like to specify the starting value externally. Thanks! This works: arcpy.CalculateField_management("xx4_ncard","as_drv_srt","autoIncrement()","PYTHON_9.3","rec=0\ndef autoIncrement():\n global rec\n pStart = 1 #adjust start value, if req'd \n pInterval = 1 #adjust interval value, if req'd\n if (rec == 0): \n rec = pStart \n else: \n rec = rec + pInterval \n return rec") ‍ This doesn't: start = 1 arcpy.CalculateField_management("xx4_ncard","as_drv_srt","autoIncrement()","PYTHON_9.3","rec=0\ndef autoIncrement():\n global rec\n pStart = " + start + " #adjust start value, if req'd \n pInterval = 1 #adjust interval value, if req'd\n if (rec == 0): \n rec = pStart \n else: \n rec = rec + pInterval \n return rec") ‍‍‍

‎09-21-2016

Hmmm, I was afraid of this response. So the original field names are 16 character, but ArcMap thinks it's going to protect me by truncating to 10? What I think I'll do is simply warn the user of possible truncation and build some lines of AML code for them to paste into workstation to rename those fields to their original (up to 16 character) names. If they (read: me) fail to perform this extra step, it'll become obvious downstream when those fields are unavailable. Thanks for the responses both of you!

‎09-21-2016

I've encountered a problem with the Table to Table tool. While attempting to copy a table from a Personal Geodatabase (.mdb) into an INFO workspace (directory), field names are truncated to 10 characters. I'm executing the tool via the python code below. convInfoWrkspace = "E:/info_workspace_directory/" #directory representing an INFO workspace convTempPGDBTblOut = "pgdb_tbl" #table in the personal geodatabase. table is in the ArcMap TOC convInfoNameOut = "info_tble" #table to be created in INFO workspace arcpy.env.workspace = convInfoWrkspace arcpy.env.overwriteOutput = True arcpy.TableToTable_conversion(convTempPGDBTblOut,convInfoWrkspace,convInfoNameOut)‍‍‍‍‍‍‍ Interestingly, and I think tellingly, when using the same tool via the GUI (ArcToolbox), it won't even allow me to export to an INFO workspace. Instead, it adds a .dbf extension and creates a .dbf table. And, being a .dbf, the field names are truncated to 10 characters. The instructions for the tool state that by removing the .dbf extension on the output table name, an INFO table is created...but I'm unable to remove the ".dbf" - it's instantly re-added. One more thing...I noticed that in Arc\INFO, the fields with truncated names actually do list the un-truncated name as the "alternate_name". I realize INFO is going the way of the dodo, but does anyone have any suggestions on how to preserve the original field name? This is occurring with version 10.1 SP1 (Build 3143).

‎09-13-2016

Thanks Dan, this strategy is perfect...nice and simple. Sent from my iPhone

‎09-13-2016

Hopefully this is an easy answer... I have a process to script which is interrupted by some manual steps...therefore I've split the process into two separate Python scripts. 1) Run Script A in which the user specifies various parameters. The script creates an empty table based on those parameters. 2) The user is asked to perform some manual steps in ArcMap in order to populate the empty table created in Script A (these steps cannot be scripted, unfortunately, as they rely on a custom ArcMap extension that can only be accessed via its GUI). How long this will take is indeterminate...could be <1 minute or could be <1 hour. 3) Finally, run Script B, which continues where Script A left off. How do I get the parameters from Script A into Script B? That is, assuming there isn't some way to do this all as one script with a "Pause" function in the middle. Thanks!

‎06-03-2016

Is it just me, or does ArcMap 10.1 have a habit of unnecessarily redrawing the display? With complex maps, this really slows down a workflow! A few examples: Changes are made outside of the data frame, such as a page title (layout view) A legend is slightly repositioned A map element within the data frame is slightly reposition without changing how it overlaps with features. Zooming in/out Turning on or off the only label layer Minor symbology changes to a layer towards the top of the 'stack' Sure, I understand the necessity of re-rendering before the final production output...but sometimes it's just overkill!!!

Online Status	Offline
Date Last Visited	‎02-12-2022 04:10 PM

My Ideas

Latest Contributions by KeithD1

labeling roadway route concurrencies?

Re: trim line to specified length

Re: trim line to specified length

trim line to specified length

SQL question

Re: reusing a codeblock?

Re: reusing a codeblock?

reusing a codeblock?

Re: including Python variable in codeblock

including Python variable in codeblock

Re: problem with Table to Table

problem with Table to Table

Re: Python scripting question

Python scripting question

Excessive re-drawing in ArcMap

Re: problem with Table to Table

Re: Enable ArcGIS Pro to access ESRI Personal Geod...