Latest Contributions by DanPatterson_Retired

David... to give you some ideas on how I handle nulls. For float/double np.nan is fine.  For string, None.  For time, np.NaT Sadly, no one can agree on nulls for integers (eg. there is no np.nint ) # Change FC <null> to a useful nodata value def make_nulls ( in_fc , include_oid = True , int_null = - 999 ) : "" "Return null values for a list of fields objects . This excludes objectid and geometry related fields . Throw in whatever else you want . Parameters - - - - - - - - - - in_fc : featureclass or featureclass table Uses arcpy . ListFields to get a list of featureclass / table fields . int_null : integer A default to use for integer nulls since there is no ``nan`` equivalent Other options include >> > np . iinfo ( np . int32 ) . min # -2147483648 >> > np . iinfo ( np . int16 ) . min # -32768 >> > np . iinfo ( np . int8 ) . min # -128 >> > [ i for i in cur . __iter__ ( ) ] >> > [ [ j if j else - 999 for j in i ] for i in cur . __iter__ ( ) ] "" " nulls = { 'Double' : np . nan , 'Single' : np . nan , 'Float' : np . nan , 'Short' : int_null , 'SmallInteger' : int_null , 'Long' : int_null , 'Integer' : int_null , 'String' : str ( None ) , 'Text' : str ( None ) , 'Date' : np . datetime64 ( 'NaT' ) , 'Geometry' : np . nan } # desc = Describe ( in_fc ) if desc [ 'dataType' ] not in ( 'FeatureClass' , 'Table' ) : print ( "Only Featureclasses and tables are supported" ) return None , None in_flds = desc [ 'fields' ] good = [ f for f in in_flds if f . editable and f . type != 'Geometry' ] fld_dict = { f . name : f . type for f in good } fld_names = list ( fld_dict . keys ( ) ) null_dict = { f : nulls [ fld_dict [ f ] ] for f in fld_names } # ---- insert the OBJECTID field if include_oid and desc [ 'hasOID' ] : oid_name = 'OID@' # desc['OIDFieldName'] oi = { oid_name : - 999 } null_dict = dict ( list ( oi . items ( ) ) + list ( null_dict . items ( ) ) ) fld_names . insert ( 0 , oid_name ) return null_dict , fld_names ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ‍ ... View more

Well nothing seems to be helping, so last stab... Feature Vertices To Points—Data Management toolbox | Documentation  to get the vertices of your split polylines, Then from there Near or spatial join to get the sequence of points. This type of problem may be better suited to a coding solution based on a query of the points of the resultant split polylines.  I have also not examined in any detail if splitting may result in segment orientation flipping. I have however, found some idiosyncracies associated with the generation of shapes from point sequences which raises that possibility. ... View more