Latest Contributions by MTCGIS

Hey Micah,  Thanks so much for your reply! I took a look at your example but ended up going another way. For the most part, the two input feature classes that I wanted to merge had the same field names. It occurred to me that by leveraging the fieldmappings and fieldmap object, I could avoid associating each field from each input feature class with the destination field since identical fields would just be merged without my intervention (at least that seems like how it works...) Here's what I did: 1) Created an empty FieldMappings object 2) Added tables from both input feature classes to the empty FieldMappings object 3) Created arrays of fields to be mapped from both input feature classes, careful to ensure that the index of the  input field name was the same index as the input field name which it would be mapped to 4) Created a fieldmap dictionary object 5) Iterated over the objects keys/values, found the field map in the field mappings object via field name added my input field updated field mappings object  removed field map of input field was mapped 6)  Created a temp table to store feature class reference 7) Merged feature classes w/ updated field mapping  Let me know what you think! Script below:  #This script should be run within the ArcGIS Pro Python window import arcpy outfc = r"TPA_Eligible_Transit_Stops_2017_test3" # Merge the following two feature classes together - map fields with the same content to single field # Each of the FC below were added to the project from MTC Organization ArcGIS Online railfc = r"TPA_Non_Bus_Eligible_Stops_2017" busfc = r"High_Frequency_Bus_Stops" # Create a new fieldmappings object and add the two input feature classes fieldmappings = arcpy.FieldMappings() fieldmappings.addTable(railfc) fieldmappings.addTable(busfc) #Get fieldmap for two fields in rail dataset which bus values will be merged into #    - Create array of bus fields which are to be mapped (input fields) #    - Create array of rail fields which bus fields will be mapped to (destination fields) #    - Create dict using zip methold - ensure order of fields matches map - to order within array    busfields = ["stop_id","lgcl_adjacent_hf_routes"] railfields = ["agency_stop_id","Distance_Eligible"] fieldmapdict = dict(zip(busfields,railfields)) #    - iterate over dictonary #    - find field map for each rail field (destination field) #    - add input field to fieldmap object (input field) #    - replace field map (destination field map) within fieldmappings object with updated field #    - remove bus field map from fieldmappings object (input field) for busfield, railfield in fieldmapdict.items():      fieldmap = fieldmappings.getFieldMap(fieldmappings.findFieldMapIndex(railfield))      fieldmap.addInputField(busfc, busfield)      fieldmappings.replaceFieldMap(fieldmappings.findFieldMapIndex(railfield), fieldmap)      fieldmappings.removeFieldMap(fieldmappings.findFieldMapIndex(busfield)) #create temp value table and store fc paths as rows vTab = arcpy.ValueTable() vTab.addRow(railfc) vTab.addRow(busfc) #merge arcpy.Merge_management(vTab, outfc, fieldmappings)‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍ ... View more

I encountered this issue as well in ArcGIS 10.3.1 While the Help documentation for Facilities Classes and Fields does not explicitly say only the point geometry type can be loaded, the Load Locations UI still allows selection of non-point geometry types. Furthermore, there is a check box underneath that restricts the drop down to only point layers, which implies that non-point geometries are valid locations. Both the documentation and UI should explicitly express application logic. The error message says "the input features must have the correct geometry type". The documentation should state the "correct geometry type". ... View more