|
POST
|
Clipping the SDE after loading data and enabling the topology is going to be quite difficult. You'd be better off extracting the data using an extent than loading that data into a new geodatabase. This will preserve the connectivity and subnetworks for that area. You can use the create offline work areas tool in enterprise, the download map button in ArcGIS Pro, or if you're very particular about how you extract the data you can create a runtime app do to the extract.
... View more
6 hours ago
|
0
|
0
|
10
|
|
POST
|
If you create a new feature template and create a feature, do you see the same behavior? If you haven't already, log a case with support.
... View more
6 hours ago
|
0
|
0
|
13
|
|
POST
|
Please log an issue with support. If your subnetworks are configured to populate the subnetworkname field on assemblies, then it should also set it to unknown when their content is no longer supported.
... View more
7 hours ago
|
0
|
0
|
10
|
|
POST
|
@VishApte_NGIS in the case of the utility network, all the UN_* tables will be pruned. In terms of what will happen if you run a trace from a moment earlier than the earliest historical moment, the trace may fail or return inconsistent results. This is because the information stored in the system tables to perform tracing will no longer be in sync with the information in your user tables.
... View more
yesterday
|
0
|
0
|
16
|
|
POST
|
Are you doing this in a named version or default? What are the edit mode configurations for the subnetwork definition for the subnetwork you're updating?
... View more
yesterday
|
0
|
1
|
55
|
|
POST
|
@samshrma998 @streamside . If you receive a warning when applying the edits, then it's a known issue (BUG-000181823). If the tool doesn't report any warnings or errors, but no resolutions are applied, then that is not something we are aware of, and you will want to log an issue, so support can investigate what is happening.
... View more
yesterday
|
0
|
0
|
11
|
|
POST
|
There is currently a known issue where the tool can fail to run and produce an error, but there aren't any issues I'm aware of where the tool silently fails. Please log an issue with support so we can understand what is happening.
... View more
Saturday
|
0
|
1
|
21
|
|
POST
|
What's happening is that you have paths between these different controllers. Use the shortest path trace to find the path between the two controllers, then fix it. Here are resources to help you: Inconsistent Stormwater Subnetworks: Stormwater Network Data Quality Assurance Tracing Article: Tips for tracing and quality assurance Tutorial: Perform quality assurance on subnetworks | Documentation
... View more
Saturday
|
0
|
0
|
12
|
|
POST
|
Does the tool output the list of FIDs (object ids) of the rows that failed? Another option is you can turn off all the mappings, except the one that is failing, then systematically remove mappings until you find the one that is failing (I typically remove/add half of the mappings at a time to speed up the process).
... View more
Wednesday
|
2
|
0
|
123
|
|
POST
|
There is an option to only prune system tables: Prune Branch History (Data Management)—ArcGIS Pro | Documentation. Make sure you read the documentation surrounding the tool to understand the preconditions for it to work effectively.
... View more
Wednesday
|
0
|
1
|
36
|
|
POST
|
If you're using something like the expanded model you would to create and use a D_Configuration table to withhold unused configuration, fields, etc from your final model without needing to physically remove them from your asset package. If you've already tidied up your model to remove this extra stuff, then you're fine. Why would you remove this extra stuff? Because it has an impact on performance. Using the D_Rename table allows you to alias things in the asset package without needing to alter any of the downstream configuration tables that would typically be affected by that change (Rules, Terminal Configurations, etc). Article on D_Configuration Article on D_Rename
... View more
Tuesday
|
0
|
0
|
106
|
|
POST
|
My preference is to stick with the original asset package and backport the configuration into the asset package. Why? The D_Rename and D_Configuration tables are consumed when you deploy the asset package. This means that once you export back to a new asset package you lose all the original configuraiton. Why is this important? Because no matter what model you're using you should be using the D_Configuration to streamline removing unused elements from the model. Using this approach, instead of physically removing them from the model, gives you the flexilibility to restore the unused elements from your model without needing to recreate things from scratch. This makes comparing schemas between releases much easier, because everything is based on the exact same geodatabase.
... View more
Tuesday
|
0
|
1
|
125
|
|
POST
|
@VenkataKondepati has the right idea. You can retrieve the differences directly from the default version for any two arbitrary moments in time. This ability was added in 10.9 when we introduced the fromMoment parameter (Differences | ArcGIS REST APIs | Esri Developer). However, I can see a few problems with the code he generated: It is using the wrong operation to calculate the differences. The operation should be differences (plural) not difference (singular). The second problem is that you must always reference the global id of the version. You cannot use the name of the version in the URL. This means you'll need to query the version management service to get the global id of the default version and use that in your URL. I'm not 100% sure about the way the moment is being calculated either. In terms of writing your own code, while you can write raw HTTPS requests to do this, there is an API available for this via the ArcGIS API for Python: https://developers.arcgis.com/python/latest/api-reference/arcgis.features.managers.html#version
... View more
Tuesday
|
1
|
1
|
86
|
|
BLOG
|
@PierreloupDucroix I have clarified that the class will need to be versioned. Because the editing approach for named versions will be the same for all three approaches, I don't feel compelled to get into specifics. The only difference is with the network features you have to run validate network topology and update subnetwork in a version when you add or modify the non-spatial content/non-spatial connectivity, but this is already called out.
... View more
a week ago
|
1
|
0
|
121
|
|
BLOG
|
One of the questions that comes up regularly from international customers is whether Esri offers versions of its Utility Network Foundations that have been translated into different languages. The short answer is that all the Utility Network Foundations available on solutions.arcgis.com are only provided in English (US). However, the tools are included with the foundations that make it easy for a customer or business partner to translate these models using the techniques described in the Renaming an item in an asset package article. The purpose of this article is to provide an overview of a process that allows you to quickly translate the contents of an asset package. There are several benefits to using this approach: The rename table doesn’t alter any of the underlying table names, field names, or database values. This means that solutions that expect specific values from this data model will not be affected by the aliases. The process is easier to iterate on because the aliases are changed as part of the deployment process. If you want to alter the underlying table names, field names, and values stored in the database, this approach will not achieve that. Create a rename table The first step of this process is to create and populate a rename table in your asset package. A comprehensive description of this process is described in the Renaming an item in an asset package article, but for this article we will keep things simple. 1. Run the Create Rename Table tool from the Utility Data Management Support toolbox Add one or more Rename Fields to represent the new alias(es) you wish to use. 2. Click Run When the tool completes, your asset package will then contain a D_Rename table that you can use to rename the description/alias of anything in your model. The next step is to get this information out of ArcGIS Pro and into a format that you can send off for translation and review. One convenient way to achieve this is to use the Export to Excel Geoprocessing tool, which you can find a shortcut for on the Attribute Table. 3. Use the burger button on the D_Rename table to display the context menu to export the contents to Excel. If you don’t want to use an Excel file you can also select all rows in the table and use the Copy Selection command to copy/paste the rows into a document of your choice. In this example, the content has been pasted into a basic text editor. 4. Translate all the values in the Current Name column to a new value You can perform this translation manually or use one of a variety of free and paid services for this purpose. Keep in mind the following: To re-import the values, you will need to remember the ObjectID of each value. This is discussed in the next section Certain properties have restrictions on length and special characters Once you’ve deployed the new database you may find you need to adjust some values All these considerations show that this will be an iterative process. You will need to manually review the values within the context of the application or data model and adjust. Importing renamed values Once you have a document containing the new values, you need to then update the rename configuration column in the D_Rename table of your asset package. The easiest way to do this is to use copy and paste, but this requires the order of the rows in the asset package and the table you are copying from to be identical. This is why it’s important that the document has the original object id from the asset package. The process is as follows: 1. Select the column that contains the new descriptions you want to use (Do not select the column header.) 2. Copy the selection to your clipboard 3. Place your cursor in the new column of the D_Rename table If you are only pasting a subset of the values from the translated document the cursor must be placed in the correct row of the document. The table view will ignore your current selection, even if you have the view filtered to the currently selected rows. 4. Paste the selection into the table You can use the keyboard shortcut or the paste command on the context menu to ensure you are pasting the values in the correct location. ArcGIS Pro will automatically parse the pasted rows into the new column. If you find that the data isn’t coming across properly, it may be that the order of items in your source document is different, or that the application the data was copied from isn’t properly formatting the data on the clipboard. 5. Save your edits. Now that you’ve populated the D_Rename table, it’s time to verify the results. Deploying a translated foundation Once the D_Rename table is populated, you need to deploy the asset package to see the translated description. The easiest way to do this is to use the Asset Package to Geodatabase tool to create a local geodatabase using the descriptions in the rename table. To perform the following steps, you first need to install the UN Package Tools for the ArcGIS Pro installation where you will be deploying the asset package. 1. Open the Asset Package to Geodatabase tool 2. Select the Asset Package that has the populated D_Rename table 3. Expand Asset Package Options Leave the box next to Load data checked if you want to review the coded value descriptions. Uncheck the box next to Post Process, this will make the process run faster without affecting your ability to review the results. Select your new descriptions for the Rename using parameter. 4. You may also want to adjust several other parameters, depending on your situation. • Folder Location • Geodatabase name • Feature Dataset Name • Utility Network Name 5. Click Run. 6. Review and resolve any errors reported with the D_Rename table. If this is your first time using these descriptions, you may see errors in the D_Rename table about values being too long or containing invalid characters. Review each of these errors and make the requested changes. Repeat this process until the asset package deploys without any errors. 7. Once the tool successfully runs, review the results in ArcGIS Pro. The easiest way to do this is to add the data in the newly staged geodatabase to a new map. If you open an existing map, you may still see the original field aliases on layers and the original coded value descriptions in your contents pane. Conclusion You’ve learned how to effectively use the D_Rename table to customize the aliases in your utility network foundation. You learned several techniques you can use to export and import the values in this table for translation purposes. You also learned about some of the considerations for the length of translated values and special characters you will need to consider when performing translation. Now that you’ve read this article you are well equipped to begin translating your own data models, whether they use a utility network foundation or another industry standard data model provided by an Esri business partner. Before you spend too much time creating your own model, you should always check with the Esri Distributor in your region to see if they, or another business partner, have already created a localized version of the data model you’re interested in. Localizing a data model is more than just translating values from one language to another, it also considers regional or local standards or regulations and norms. If there is already a localized version of the model that takes this into account this can save you a lot of time and effort.
... View more
a week ago
|
3
|
0
|
373
|
| Title | Kudos | Posted |
|---|---|---|
| 2 | Wednesday | |
| 1 | Tuesday | |
| 1 | a week ago | |
| 3 | a week ago | |
| 1 | 2 weeks ago |
| Online Status |
Online
|
| Date Last Visited |
30m ago
|