Latest Contributions by GregHollard

‎11-07-2024

[Reposted. Original post 07-26-2024 06:16pm] I've had issues trying to automate adding attributes to Mosaic Datasets at the Add Rasters stage as well. I could not find a way to do it in the same operation, but using arcpy.management.AddFields() and arcpy.management.CalculateFields() processes after the rasters have been added I can populate the attributes. The recommendation is to use an UpdateCursor instead of the CalculateFields, but I could not get that to consistently work, I think it is the old Catalog Refresh issue rearing it's head again. That help link is from 10.1, and while the process is pretty similar in Pro, I would not rely too heavily on old documentation.

‎03-22-2017

Hi Melita, The data is projected in the New Zealand Transverse Mercator Projection. The legal ramifications have to do with the calculation of fees for permits. A lot of work was done to select a process that would give a consistent value for areas within the 5.7 million square kilometres of our Exclusive Economic Zone and extended continental shelf. Greg

‎03-21-2017

Definition queries are (still!) not supported with WFS services. To quote the documentation from http://server.arcgis.com/en/server/latest/publish-services/windows/wfs-services.htm "The map document is just a specification of the layers that will be available in your WFS service. Symbology, query definitions, and field aliases defined at the layer level do not transfer to the WFS service, because the purpose of the service is to expose the features in the data." The two solutions I've used for this is either a product over the top of the WFS services (shout out to con Terra), or implementing the definition queries in views in the enterprise GDB.

‎01-25-2017

I can see your point, but I'm not in a position to argue with either the legal process that requires these functions to be used or with the research done to produce the functions in the first place. I'm just looking for the best way to include these functions in the ArcGIS Platform so we can streamline our processes.

‎01-24-2017

We use extensions by Jeff Jenness to help create accurate and consistent area values for some pretty large features, but it would solve some integration issues if the Vincenty distance and area formulas could be added to the list of options to the python methods for area and distance. The differences for an example polygon are shown below. The differences is small, but significant enough to make a difference. Currently the options for the getArea method are : PLANAR GEODESIC GREAT_ELLIPTIC LOXODROME PRESERVE_SHAPE It would be great if we could do this: !Shape!.getArea("VINCENTY","HECTARES")! Thanks also to Dan Mahr‌ for a great article about Calculating Geodesic Areas

Online Status	Offline
Date Last Visited	a week ago

My Ideas

Latest Contributions by GregHollard

Re: Mosaic Dataset Attributes

Re: Add "Vincenty" formulas to the Python getArea method

Re: WFS Service isn't respecting the definition query of the ArcGIS Map Service?

Re: Add "Vincenty" formulas to the Python getArea method

Add "Vincenty" formulas to the Python getArea method

Re: WFS Service isn't respecting the definition qu...

Add "Vincenty" formulas to the Python getArea meth...