Latest Contributions by DanRose

I have a Python code that takes mains and laterals and summarizes the features using the Summary Statistics tool. I summarize the SHAPE.STLength() field, use the statistics type SUM, the 'Case field' of 'OWNEDBY' field (integer field type). When this runs (successfully), the tool reverts all values in the OWNEDBY field to its coded domain value, rather than keeping it with the description alias. Is there a way to keep this the alpha characters, rather than the numeric value? ... View more

Hello - looking for help with a Python script - I have a feature class consumed in a network dataset (street centerlines). Once a month, we get new data, and I need to replace the old with the new. What I want to this Python script to do:- Replace the old data with the new data, - Rebuild the network dataset and address locator. Issues: - In a non-versioned dataset, the fc cannot be worked with the truncate tool, as the 'Operation not supported on a feature class in a controller dataset', aka, it is still part of the network dataset. - In a versioned dataset, truncate is "not supported on a versioned table’. - In a versioned dataset, and in an edit session within ArcMap, truncate is also "not supported on a versioned table’. Acknowledgements: - There is no way to remove the fc from the network dataset using Python, because of the inability to work with the feature class wizard. There is also no way to remove the fc from the dataset without removing it from the network dataset. Also, deleting the entire dataset and rebuilding it and the network dataset is not an option, for the same reason with Python/the wizard; (re)building the network dataset IS available to Python.   Current, manual workflow: 1. Remove the network dataset components, 2. Remove the old fc, 3. Import the new fc, 4. Rebuild the network dataset based on the new fc, and 5. Rebuild the address locator. This workflow is not repeatable through Python. In another attempt to find a fix, was able to work through the entire process of 1. Registering the dataset as versioned, 2. Start an edit session in ArcMap, 3. Select and delete all assets in the fc, 4. Copy and paste (I know, not the proper method) the new data to the original fc (identical schema), 5. Rebuild the network dataset with the new data, and 6. Unregister the dataset. I'm not able, to put this into a Python script successfully using an existing map document, edit session, select, delete, add, etc. From start to finish, it's clunky and very time-consuming, dealing with 35k assets. I wanted to use truncate and append, but that solution isn't looking like it will work for me. I want this 100% automated, no fingers to touch anything. I've gone through 30 variations of scripts - good learning experience - however... any ideas? Working with SDE database connections and datasets. New data resides in a different db. ... View more

I have a similar issue, wondering if you can help: A new(er) GIS map doc, the data frame coordinate system and all data was captured (GPS) and drawn in NAD_1983_UTM_Zone_15N (matching the ESRI World Imagery). All datasets, aerials, parcels, street centerlines, etc. match, no issues there. UTM Zone 15N is in meters, I am displaying my units in feet. What I'm not understanding is that, for instance, I have a sewer main that measures (in reality and in my GIS) at ~533'; it displays (in the main's SHAPE_length field) as only 165. I can do the math, knowing that this is given to me in meters, approx. 1/3 of the actual distance. No matter what I do, I cannot get the map to display and measure everything in feet, representing the reality of field measurements. I've set all my datasets, aerials, parcels, and map document into my preferred coordinate system (NAD_1983 StatePlane Kansas South FIPS 1502) (which is in US Feet), then everything gets even more screwy - a mile section only measures about 1600 map units... Ideas? ... View more

Hello - Part of some farmed-out work we had done, every location where one of our water mains crosses another, a "jumper" symbol was placed, and connectivity established.  If you're familiar with connectivity, you know what happened - the mains and symbol were connected, and when a trace is done, it thinks that all the mains are connected, just like a tee fitting.  That's not what we want, and unfortunately we have 1800 of these that need to be fixed. The process I've found is tedious, and involves a ten-step process to disconnect, remove vertexes, reconnect the mains, and move the symbol back to the intersection without connecting it back to the mains. Does anybody know a more automated way of doing this?  I don't believe tools needed to perform this exist Toolbox to build a script that will let me do it automatically. Thx, D>R> ... View more