POST
|
and making the join permanent isn't an option? The "." in the field name isn't a real name, but identifying the fact that the dot.notated fields belong to the joined table
... View more
05-07-2020
04:21 PM
|
0
|
1
|
79
|
POST
|
/blogs/dan_patterson/2016/08/14/script-formatting where is the part of the script that calls it? def is a method for the object 9. Classes — Python 3.8.3rc1 documentation and it looks like you are passing a list to it, so I would expect something.updateParameters(["a", "b", "csv", "d"]) # --- or something where the parameter list has at least 11 entries
... View more
05-07-2020
04:17 PM
|
0
|
0
|
60
|
POST
|
Did you complete the form here? Become a Member | Learn ArcGIS perhaps you have to provide further information .... can't hurt to check
... View more
05-06-2020
06:30 PM
|
0
|
0
|
77
|
POST
|
Count Overlapping Features—Help | Documentation is one interesting possibility.. But more generally, you should look at the Overlay tools An overview of the Overlay toolset—Help | Documentation Conversion to raster and there overlay equivalents are also the other option
... View more
05-06-2020
04:31 PM
|
0
|
1
|
39
|
POST
|
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
05-06-2020
03:17 PM
|
2
|
0
|
155
|
POST
|
Not really that easy. For instance, can you retrace a road segment? Do you have an origin? (which can affect the path). Perhaps you can elaborate on your end goal further.
... View more
05-06-2020
03:09 PM
|
0
|
1
|
39
|
POST
|
Your last sentence is the easiest for all featureclass geometries and the only way for poly* features. Just make sure you include the matching ID field (eg OBJECTID) to enable the join when saving the structured np array. an oldish missive /blogs/dan_patterson/2017/11/01/extendtable-permanent-joins-arcpy-and-numpy-play-nice
... View more
05-06-2020
10:35 AM
|
2
|
0
|
155
|
POST
|
maybe skip Arc* altogether and just use windows file explorer
... View more
05-06-2020
10:06 AM
|
0
|
0
|
62
|
POST
|
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
05-06-2020
04:05 AM
|
1
|
1
|
101
|
Online Status |
Offline
|
Date Last Visited |
11-11-2020
02:22 AM
|