Latest Contributions by BruceHarold

Hi Kobe This is quite a big topic, but the short story is coverages come in two flavours - having single or double precision coordinates - and use the concept of a fuzzy tolerance when geoprocessing against other coverages - coordinates within the tolerance of each other are considered identical.  Shapefiles are always double precision and have no concept of control over coordinate comparison tolerance - don't use them.  Geodatabases use a storage resolution for their features and an additional XY tolerance you use to model the accuracy of the data when making coordinate comparisons.  Because much geoprocessing functionality depends on coordinate comparison geodatabases are the recommended storage workspace for your data. Regards ... View more

Hi Mark When you create a locator using a 10 style you may set the relevant zone field to <None> and not specify it at run time - in your case ZIP.  There is an issue with 10.0 which requires that at least one zone field must be non-null, but this is fixed at SP1. Regards ... View more

Hi Sherrie It sounds like you should log a support call so an analyst can reproduce your issue.  Existing locators should work fine in ArcGIS 10.  One (remote) possibility is your existing locator did not have reference data stored in it and the connection required to wherever the data resides cannot be made for some reason. Regards ... View more

Dan Can you please log a support call and make your source data available to the analyst?  We'll try and repro your experience and see if SDE has anything to do with it. As an aside, we do not recommend SDE workspaces as places to store locators, file geodatabases or the filesystem are preferred. Regards ... View more

Hi Pat In your workbench, make sure to expose additional attributes for extended data. The parameters dialog for the KML reader has a control "Additional Attributes to Expose" which brings up the dialog in my first screengrab. Then in your workbech, expose and explode the list attribute - you'll get name and value attributes. You'll have to do more work to pivot the exploded features back into a single part per kml_id. Regards ... View more

Hi Nelson This is a known issue we're working on - if an ETL tool is the first background GP process in any session it will fail.  Run another GP tool first (Get Count if you can't think of anything else) and then the ETL processes.  They should then work. Regards ... View more

Hi The arcpy.Describe object also returns the subtypeFieldName. http://help.arcgis.com/en/arcgisdesktop/10.0/help/index.html#//000v0000002s000000.htm Regards ... View more

Hi Joe The best way for us to support address cases is to have sample data, which means attaching files to thread posts if using the forum.  If you are OK doing that then it works for us too, otherwise by support call works too. Regards ... View more

Hi Joe The address grammar is where new "patterns" can be defined for the new geocoding engine.  We're hoping that for major market locators that nobody will have to change the grammar, we would prefer users notify us about cases which cause issues (as you have done) and we re-publish the .lot.xml files on the geocoding resource centre.  I think your EXT issue will be resolved by Brad editing some other element values and not changing any grammar. Service Pack 1 for ArcGIS 10 will include many improvements to the geocoding experience with 10 locators. Regards ... View more

Hello Joe If you are customizing a 9.x locator you do so exactly as always with the collection of files you mention.  The Geocode directory under your ArcGIS 10 install is still there, but you may notice it is empty.  Simply copy your custom rule base files into the Geocode and Locators directories and you can create and use custom 9.x locators in ArcGIS 10. 10.x locators use the all-new geocoding engine in ArcGIS 10.   These are customizable via editing the .lot.xml file(s) in the Locators driectory.  Documentation for this is still under construction, but you should be able to see similarities with the CLS file elements. Regards ... View more

Hi Another approach might be a list comprehension: ptTupleList = [(p.shape.firstPoint.X,p.shape.firstPoint.Y) for p in arcpy.SearchCursor(myFC)] ...will give you a list of (X,Y) tuples. Also, please keep an eye on the GP gallery, there is a hull tool in the works for footprints of address points.  It may be out in September. Regards ... View more

Hi The 8.x tools are not shipped in ArcGIS 10, so the mif2shape.exe wrapper to do this conversion is not in 10.  The Data Interoperability extension is the correct ArcGIS product for conversion of 3rd party formats, although you may find other products capable of converting MIF data. Regards ... View more

Hi List comprehensions are an ideal way to get a list of field values: myList = [f.getValue(someField) for f in arcpy.SearchCursor(someFC)] SearchCursor arguments can include a SQL query, or can access a feature layer and therefore its selection set. Regards ... View more

Hi Don't forget that you can make your code workspace-portable by using the AddFieldDelimiters method to wrap field names, and Python's repr function to quote string literals in the SQL expression. Something like: uid =  row.getValue('uid') state = row.getValue('state') ws = gp.Describe(USA_State).path gp.Select_analysis(USA_State, USA_State_Select, gp.AddFieldDelimiters(ws,'UID') + " <> " + repr(uid) AND " + gp.AddFieldDelimiters(ws,'STATE')  + " = " + repr(state)) Regards ... View more

Nicholas The Data Interoperability extension solves this sort of problem.  You can get an evaluation license if you want to learn how. Regards ... View more