Latest Contributions by JohnDye

‎10-23-2014

Anyone know of a quick way to count the number of records returned by a da.SearchCursor with a where_clause applied? with arcpy.da.SearchCursor(MyLayer, "SHAPE@", SuperDuperAwesomeQuery) as rows: # how do I figured out how many records are in rows without iterating through rows???

‎10-13-2014

Thanks Jake, That makes a lot more sense. While I know its not a required entry for the PackageLayer tool to execute, it would be useful to be able to set that property through a parameter on the tool since that property can't be ported from a Layerfile or Feature Layer into the package when you're creating it since those input datatypes don't have that property. Was the idea behind not including that property in the GP tool to create a behavior where Access and Use Constraints is would always be null unless someone took the time to package and upload the LPKs 1-by-1 through the GUI?

‎10-13-2014

When you create a layer package manually through the ArcMap Table of Contents, there is a textbox labeled 'Access Use and Constraints'. I have a few questions on this little...property (I guess that's what it is) First, what is the actual intent of this property? Is it for me to enter things like classifications (ie. Public, Confidential, Proprietary, Secret, Top Secret, etc.)? If so, what's the point as there doesn't seem to be a way to interrogate it or even set it through arcpy? Additionally, that property also does not seem to become a property on the Layerfile or Featureclass packaged into the LPK when they are extracted, so I mean really...I don't know what to do with it. Secondly, why is it unique to LPKs or more correctly Packages? I mean, an LPK is just essentially a zipped Geodatabase replica (or shapefile...and shame on you if that's the case) and Layerfile. Admittedly, it's a little more than that because if you change the extension to .zip, you can't extract it so there's a little more going on under the hood there, but conceptually that's what we're dealing with. What's more, when you extract an LPK, you get the dataset and a layerfile referencing the dataset in your assembly cache and the layerfile is what gets added to your MXD but since Layerfiles nor Feature Classes have no Access Use and Constraints property there's no place for that property to be assigned. So...poof? It goes into the abyss? I'm just really confused over the whole thing. Summary is another property which Layerfiles and Feature Classes do not have, but I'm able to rationalize that property a bit more because Layer Packages can contain multiple datasets and layers. Therefore, a summary is useful in that it can provide information about the contents...so could the description as well...darn it, confused again...

‎09-12-2014

Perhaps an optional parameter for a XSL Stylesheet as well

‎09-10-2014

Thanks for the comment rfairhurt24, I am aware of the Attribute Assistant, I just think it's rather dumb that this is not a native GDB functionality. If they can do it with Length, Area and Perimeter, they can certainly do it with X & Y centroid. I mean, I could even write a Python Add-In to listen for the onEdit event and update the coordinates for the edited feature on my own, that doesn't mean I should have to. This is low-hanging fruit, IMHO. Just because something is already possible through a plug-in or extension doesn't mean it shouldn't eventually transition to a native functionality. ET GeoWizards has been able to rename and reorder fields for years (granted it does that by creating a new dataset) but the fact that ET Geowizards exists and can perform that functionality doesn't suddenly let ESRI off the hook for creating that much demanded functionality in the software. I mean, if that's the case then I should probably go ahead and download and install every single plug-in and extension there is for the software. Letting ESRI get by with a fragmented plugin this, extension that, addon here approach results in severe functionality fragmentation.

‎08-13-2014

Geodabases Feature Classes automatically create a Length and Area fields in the Attribute Table of a Feature Class as appropriate for the given geometry and the values displayed in these fields automatically recalculate and update without any action from the user whenever the feature is edited. Why doesn't the Geodatabase do this for the X, Y coordinate pair of the feature as well? I would love to see X, Y or LON, LAT fields in the table that update automatically whenever a feature is moved. For lines and polygons, and multi-type geometries, it could just use the centroid.

‎08-01-2014

fieldInfo objects are pretty neat but it seems to me they are missing a pretty important method. Currently, you can get field names, assign new names, set visibility, establish split policy, remove fields and return a list of the visible. I noticed you can't set a new field alias though. If you can set a new name using the setnewname() method, you should also be able to set a new alias using a setnewalias() method. I mean, names and alias' go hand-in-hand. Without this method, the only alternative to do this in python is to iterate through the fields after export and use the AlterFields tool.

‎08-01-2014

fieldInfo objects are pretty neat but it seems to me they are missing a pretty important method. Currently, you can get field names, assign new names, set visibility, establish split policy, remove fields and return a list of the visible. I noticed you can't set a new field alias though. If you can set a new name using the setnewname() method, you should also be able to set a new alias using a setnewalias() method. I mean, names and alias' go hand-in-hand. Without this method, the only alternative to do this in python is to iterate through the fields after export and use the AlterFields tool.

‎07-29-2014

" An IP address database is not something a user could even begin to create on their own" Nor is it something ESRI could create on its own. I think there are way, way, way too many moving parts to something like this. Even Google doesn't do this. They give you an approximation of where the IP should be coming from. Note the keyword, should. IPs can be spoofed pretty easily. In addition, I'm not sure how much value an approximate location would be with GIS. I just don't see how you could possibly get a reasonable Circular Margin of Error with IPs. They change constantly.

‎07-29-2014

" An IP address database is not something a user could even begin to create on their own" Nor is it something ESRI could create on its own. I think there are way, way, way too many moving parts to something like this. Even Google doesn't do this. They give you an approximation of where the IP should be coming from. Note the keyword, should. IPs can be spoofed pretty easily. In addition, I'm not sure how much value an approximate location would be with GIS. I just don't see how you could possibly get a reasonable Circular Margin of Error with IPs. They change constantly.

‎07-01-2014

Deleting a large amount of fields from a Feature Class using the Delete Fields tool takes an excessively long time. One of the tricks I use to speed this up is to simply turn the field visibility off in the Layer properties and then export the Feature Layer to a new feature class retaining only the visible fields. It's a lot faster (perhaps you guys should alter the Delete Fields tool to just make a feature layer and then export to a new Feature Class?). In any case, in the Feature Layer properties, you can also reorder fields. However, because Feature Layer's are in-memory, those changes aren't committed to the source dataset. Cool, I get that. - BUT - It would be fantastic if the Feature Layer's field order was honored on export, essentially creating a way to reorder fields in ArcMap by reordering the fields in the Feature Layer properties, then exporting the Feature Layer to a new FC or Shapefile.

‎06-13-2014

Can you post your addin file? I'll pull it down and see if I get the same thing on my end. Otherwise, I would think that you've likely got an old version sitting in your assembly cache and it's not being overwritten. When you install a Python Addin, it extracts the files to the Assembly Cache and that is where ArcGIS reads all of your business logic and configuration file from as well as where it stores any data you ship with it. Sometimes, when you close ArcMap, it doesn't completely close and the executable will remain in process, even though it would appear that it is closed. You can verify by looking at the Task Manager and ensuring there are no processes named ArcMap, AppRot, ArcGISConnection and ArcGISCacheMgr running. If you find any running, end them. Also, I would suggest you go into your Assembly Cache and just empty it out. On Windows7, the Assembly Cache is located at: C:\Users\<username>\AppData\Local\ESRI\Desktop10.0\AssemblyCache On XP, you'll find it at: C:\Documents and Settings\<username>\Local Settings\Application Data\ESRI\Desktop10.0\AssemblyCache Your addin will be contained in a folder in the above directories. The folder name for your addin is whatever your addin's AddinID was. Delete that Folder, then rebuild and reinstall the Addin and Start ArcMap.

‎06-12-2014

It looks like you may have an issue in the onFocus method. You create a list of the current layers in the dataframe called "Layers" but then try to iterate though them with for Layer in LayerList. Try changing LayerList to Layers. Doh! That's my fault. Sorry about that Dave! Great catch Sage!

‎06-12-2014

Hey David, Could you edit your post by putting the code inside of code brackets to make it easier to try and find and issues with your indentations? See this post to learn more: http://forums.arcgis.com/threads/48475-Please-read-How-to-post-Python-code In regards to why you're seeing item1 and item2, those are typically default listings provided by the ESRI Python Addin Template. There's nothing in your code that should be doing that, so I would suggest going into your Addin Manager in ArcMap and ensuring that you uninstall any Addin's related to this process so that the code is removed from your assembly cache. Then try reinstalling the addin you built from this code.

‎06-10-2014

Thanks Matt, That was a nice little improvement over df.zoomToSelectedFeatures() but I'm looking for a method to actually flash the selected feature as you can in ArcMap through the identify window. It generates a little crosshair on the screen and then flashes the feature in a kind of dark-green color.

Online Status	Offline
Date Last Visited	‎11-11-2020 02:23 AM

My Ideas

Latest Contributions by JohnDye

Fastest way to get number of rows in a da.SearchCursor

Re: PackageLayer_management() - Access Use and Constraints

PackageLayer_management() - Access Use and Constraints

Re: Programmatically access HTML Popup in Layer Properties

Re: Automatically Updating Coordinate Fields in Feature Class Attribute Tables

Automatically Updating Coordinate Fields in Feature Class Attribute Tables

'setnewalias' method for fieldInfo objects

'setnewalias' method for fieldInfo objects

Re: Add an IP Address Geocoder to ArcGIS

Re: Add an IP Address Geocoder to ArcGIS

Allow Fields to be Reordered when Exporting a Layer

Re: Addin Combo Box

Re: Addin Combo Box

Re: Addin Combo Box

Re: Flash Selected Feature?

Re: Authenticating to Portal

Getting 498: Invalid Token from AGS Server after p...

Re: ArcGIS Data Store Under the Hood

Re: ArcGIS Data Store Under the Hood

Re: ArcGIS Data Store Under the Hood