Latest Contributions by KimberlyGarbade

Finally got it to work in a popup.  I tried 15 ways and it finally worked when I returned a single feature and used the feature's geometry. This is code in a popup         ... View more

For enterprise GDBs (at least in SQL Server in my case) this is common, but usually its not an issue, although I haven't tried Feature Class to Feature Class backup using a python script.  That being said.... In Python the output name is an input into the Feature Class to Feature Class function: arcpy.conversion.FeatureClassToFeatureClass(in_features, out_path, out_name, {where_clause}, {field_mapping}, {config_keyword}) So if you have a variable something like txtInFeatures (to use as the 'in_features' in the function reference above) and its value is in the form "DatabaseName.Owner.FeatureClassName", I would use something like this to generate the txtOutName (to use as the 'out_name' in the function reference above) txtOutName = txtInFeatures[txtInFeatures.rindex('.')+1:] below is a snip of a test I ran in a python emulator. Code on the left, result on the right. Hope this helps.   ... View more

Without knowing more all I can suggest is: 1) If you have different features selected during each run of a tool it can produce different results. Make sure you are filtering on the same records each time or clearing your selection before you run the tool. 2) Not sure I understand, but if you are running a Clip on an input feature class the Object IDs of the feature classes inputted into the Clip are not maintained, new Object IDs are generated.  If you then use that as input in a Near tool the Object IDs it will reference are those of the clipped data, which would make it hard to link back to the original.  Think about adding your own unique identifier to the original feature class.  This value will be maintained by the clip and will link to the same feature in the original feature class. 3) If adjacent polygons intersect each other the lines returned by the Feature to Line command will be split where the polygons intersect.  I hope I'm understanding correctly and that this is helpful at least in part.   ... View more

If the RFSTEST attribute in your table is defined as either a Float or a Double, and the precision and Scale of the Float or Double are set correctly to accommodate the pasted data then I might try changing something in Excel. If the column you are cutting out of in Excel is set to general or text you might try converting its contents to a numeric data type in Excel. Another thing I might try is converting your Excel sheet to a table in Excel. That being said I also don't copy and paste from Excel. I would would bring the Excel data into a map doc, create a join in the common key field, calc the field values over, then remove the join. That ensures the correct data goes to the correct record.  ... View more

I just ran a quick test this morning.  I created a very simple "Main" model and a sub-model whose only purpose is to Iterate through the database the results of the "Main" model are written to and collect their paths (if they exist).  I defined the output of the "Collect Values" tool (in the sub-model) as a parameter and saved the sub-model.  Then I just dragged the sub-model into the "Main" model just like any other tool.  Since the sub-model doesn't require any inputs (other than knowing that the feature classes to be used as inputs into the merge have been created) I just set the feature classes that were the results of my Select statements to Preconditions that have to be met before the sub-model will run.  Since I defined the output of the Collect Values tool in the sub-model to be a parameter it is shown as the output for the sub-model when it is dragged into the "Main" model.  Then I just used that value as input into the merge.  It worked for my very simple test, but your situation is a little more complex, but is should at least let your see how it works in one instance.  Hope this helps. P.S. you might have to clean up for it between runs.  For example if the first time your run it you have three inputs into the merge and it works as expected it might not work correctly the next time when you only expect 2 inputs into the merge, because the third input might still be existing in your database because you never cleared it out after the first run...Hope that makes sense.     ... View more