Latest Contributions by PaulLeBlanc1

‎06-06-2024

@IvanDImitrovI am not aware of any issues in this area. This is valid arcade. FeatureSetByName($datastore, 'LineTypeLib', ['*'], false) If there isn't a table called LineTypeLib then the runtime error is expected.

‎05-14-2024

If you want to apply an asset package to a v6 UN, you must be using ArcGIS Pro 3.0 - 3.2 (ideally Pro 3.1).

‎05-13-2024

untools 3.1.1.1 is uploaded here and can be used like so. This is a RC build, so caveat emptor, not supported, etc. Please reach out to pleblanc at esri dot com (or direct message me here) with any issues/questions. import untools import arcpy # Override precision and scale for all float fields. untools.common.settings.SINGLE_PRECISION_SCALE = (6, 1) untools.common.settings.DOUBLE_PRECISION_SCALE = None # The default. arcpy.pt.AssetPackageToUtilityNetwork(...) To install, open a python command prompt and run conda install solutionsdev/label/pro3.1::untools

‎05-10-2024

It wouldn't be a default; you would have to opt in because we don't want to break backwards compatibility. It's been this way for 6 (!) years and you are the first I'm aware of that is raising this. 😄 Still ironing it out, but it would be something like this. If you left off that line, or set it = None, it would be the current behavior. import untools import arcpy # Override precision and scale for all float fields. untools.common.settings.SINGLE_PRECISION_SCALE = (6, 1) arcpy.pt.AssetPackageToUtilityNetwork(...) Yes, we would likely do this on Pro 3.1/3.3 only because those are Network Management Release versions.

‎05-10-2024

Few questions: Do you want all your floats in all tables to have the same scale/precision? Do you want all your doubles in all tables to have the same scale/precision? If yes, then supporting this would be quite straightforward and you could have a RC version of untools by Monday morning that would solve this. I've been toying around with this approach and it works nicely. If no, and you want certain fields to be numeric(x,y) and others to be numeric(a,b) then it would take longer (due to priorities and such) but would provide a nice level of granularity.

‎05-10-2024

The code above was to show that despite telling the system to create a FLOAT, it created a DOUBLE (implicit upcast). There is a very specific edge case where apply AP does explicitly upcast a FLOAT to a DOUBLE (i.e., it creates the field as a DOUBLE to begin with). You get a runtime warning informing you about this. If you create a FLOAT field and don't specific scale/precision, then you get a DOUBLE. Tested with the same software as above, so you'll see this behavior even after you upgrade your client. Edit: Apply AP has been creating FLOAT fields with the following payload since ~Pro 2.1. Scale/Precision are both 0 because that is how they are stored in FGDB. <AddField> <field_name>f_05_03</field_name> <field_type>FLOAT</field_type> <field_precision>0</field_precision> <field_scale>0</field_scale> <field_length>4</field_length> <field_alias>f_05_03</field_alias> <field_is_nullable>True</field_is_nullable> <field_is_required>False</field_is_required> </AddField>

‎05-10-2024

I'm testing with Pro 3.3 and SQL Server 16.0.4120.1 (what I have handy). import arcpy fields = [] for p in range(1, 10): for s in range(1, p): fields.append( dict( field_name=f"f_{p:02}_{s:02}", field_type="FLOAT", field_alias=f"Precision: {p}, Scale: {s}", field_precision=p, field_scale=s, ) ) for f in fields: arcpy.AddField_management( r'<my table>', **f ) print(arcpy.GetMessages()) The fields are created as numeric(p, s), but ArcGIS treats any precision >6 as a DOUBLE:

‎05-09-2024

File geodatabases don't support scale or precision (https://pro.arcgis.com/en/pro-app/latest/tool-reference/data-management/add-field.htm) so round-tripping is problematic unless we stored the desired scale/precision in a side table and read from that during field creation. What DBMS are you targeting? untools is not explicitly upcasting the field, so I'd need to dig further to understand where that is happening.

‎05-07-2024

The 3.3 release of untools contains the fixes from untools 3.2.0. For more information, see the 3.2 release notes. Tool reference Installing untools untools 3.3.4 - June 2025 Export Asset Package Resolve BUG-000174483 Assign Terminal Connections Flip logic when assigning terminals in sink based networks (see this post) Apply Asset Package Sync delimiters between CSV files and schema.ini untools 3.3.3.1 - December 2024 Create Utility Network Associations Restores behavior of GP tool broken with untools 3.3.3 (see this post) untools 3.3.3 - November 2024 Assign Terminal Connections Resolve issue with the "Honor Digitized Direction" using the incorrect upstream and downstream terminal Optimize and refactor code to scale on larger datasets Apply Asset Package Resolve issue when using a D_Configuration table and applying a subset of domain networks untools 3.3.2 - August 2024 Apply Asset Package Expose option (untools.common.settings) to run Compact. Previously this was always True, but now defaults to False. Improve Rename table validation Every row and column is now checked regardless if it is used. Duplicates and length restrictions are now more consistently validated. Miscellaneous Resolve issues with various geoprocessings and input/output parameters from python. untools 3.3.1 - July 2024 Apply Asset Package Support for Utility Network 6 & 7 Expose options (untools.common.settings) for custom precision/scale on single/double fields Resolved issue where standalone tables would not be created in the target workspace Stage Utility Network & Asset Package to Geodatabase Add new parameter to choose the Utility Network version to create (6 or 7) untools 3.3.0 - May 2024 Add support for Utility Network version 7 Big Integer network attributes Flow Direction network attribute Apply Asset Package Expose extent environment variable (in Asset Package to Geodatabase) Skip tiers whose valid controllers are completely removed by D_Configurations table Add support for terminal paths when there are 5 or more terminals Skip feature classes removed by D_Configurations table Support Data Reviewer attribute rules across tables Improve support for Date network attributes Validate contingent values on tables without subtypes Upgrade Asset Package Assign missing asset package domains to existing fields Miscellaneous Cleanup locks from arcpy cursors Remove extraneous console logger

‎05-07-2024

https://developers.arcgis.com/rest/services-reference/enterprise/querynetworkmoments-utility-network-server-.htm

‎05-02-2024

It is reading from this workspace domain: AP_Domain_Networks

‎04-17-2024

untools 2.9.5 was released 2023-01-19 (config states 3 & 4) untools 2.9.6 was released 2023-03-03 (config states 5 & 6) untools 3.0.0 was released 2022-06-23 Pro 3.0 is not a Network Management Release, which is why there is only untools 3.0.0

‎04-08-2024

Attribute rules in the asset package are stored in a side table (B_AttributeRules). See https://doc.arcgis.com/en/arcgis-solutions/latest/tool-reference/utility-network-package/pdf/Utility%20Network%20Package_Asset%20Package%20Reference.pdf Since it's much more convenient to use design view or geoprocessing to author attribute rules, it's a good idea to configure your attribute rules against the deployed utility network, not the asset package. The GlobalID field in the asset package is a GUID so that the values can be maintained.

‎02-21-2024

What version of Pro/untools are you using?

‎02-14-2024

This function differentiates between null and empty geometries. function empty_null_shape(geo) { return Decode(TypeOf(geo), "", "null", "Point", IIF(IsNan(geo.X), "empty point", "point"), "Polyline", IIF(Count(geo.paths) == 0, "empty polyline", "polyline"), "Polygon", IIF(Count(geo.rings) == 0, "empty polygon", "polygon"), "Multipoint", IIF(Count(geo.points) == 0, "empty multipoint", "multipoint"), "?" // Default ) }

Online Status	Offline
Date Last Visited	a week ago

My Ideas

Latest Contributions by PaulLeBlanc1

Re: Utility Network Package toolbox 3.3 release notes

Re: Apply Asset Package on UnTools/Pro 3.3 requires UN vesrion 7 - is there a way how to run on Version 6?

Re: Apply Asset Package: float changes to double in enterprise geodatabase

Re: Apply Asset Package: float changes to double in enterprise geodatabase

Re: Apply Asset Package: float changes to double in enterprise geodatabase

Re: Apply Asset Package: float changes to double in enterprise geodatabase

Re: Apply Asset Package: float changes to double in enterprise geodatabase

Re: Apply Asset Package: float changes to double in enterprise geodatabase

Utility Network Package toolbox 3.3 release notes

Re: Last Full and Partial ValidateTopology run

Re: Fetch Network Domains in an Asset Package

Re: UNTools 3.0 missing newer Configuration Categories domain values

Re: Exporting to Asset Packages: Global ID vs Guid data type confusion

Re: D_rename Tier error

Re: Count vertices to determine if shape is null

Re: Question on Upgrade Asset Package Tool - Utili...

Re: Asset Package To Geodatabase Fail

Re: Apply Asset Package Error

Re: Install untools breaks arcgis.gis connexion

Re: Asset Package to Geodatabase failed to find Li...