POST
|
Team, We have water assets in our existing feature classes that are marked as critical and we want to maintain this attribute in the UN ASSETGROUPs during the migration from GN to UN. Is is best add the field to the Asset Package and load the attribute into our user defined field or is there another method to model the criticality of an asset built into the UN? We have scoured the documentation and do not see anything relating to this concept. Thanks!
... View more
05-17-2024
12:05 PM
|
0
|
1
|
262
|
POST
|
Hi, We are trying to migrate some water utility data to the ArcGIS Utility Network schema, using data loading tools. We are now matching the target (Esri asset package) and source fields in the Data Loading Workspace excel file, but we have a question on how to migrate a source subtype to the designtype field in the target asset package. Can we create a Field Worksheet (Blue) that translates the source subtypes to the designtype field domain of Water_Valve_Type? Our current subtypes in the GN features would correspond to the Water_Valve_Types in the Asset Package Domains Thanks!
... View more
05-01-2024
02:34 PM
|
0
|
2
|
300
|
POST
|
I was hoping to get recommended best practices for service points within a panel as we prepare to migrate our data from the GN to the UN We currently have a mixture of service point modeling on our larger developments where some service points (meters) within a low voltage panel are daisy chained together with a single conductor running between each meter. Some meters are modeled as point-to-point, with the conductor beginning at the panel and terminating with the meter. Does the UN support both models or is there a specific model that is recommended? Thanks!
... View more
09-19-2023
08:53 AM
|
0
|
2
|
518
|
POST
|
Hi Derek, have there been any update to the ability of MDM's to apply data/content to the app or is it in the roadmap? I reviewed the whitepaper and technical paper but they seem a little old and there is no mention of future development. This would be super helpful to sideload MMPKs to the apps. TIA
... View more
08-02-2023
08:39 AM
|
1
|
0
|
371
|
POST
|
We too have a similar issue in that we need to 'anonymize' crime data to a street block number and not the actual address where the alleged crime occurred.
... View more
03-02-2022
09:28 AM
|
0
|
0
|
374
|
POST
|
Really dumb question but did you purchase the routing license? Routing is a separate charge and Esri will include the routing as part of the delivered FGDB when Streetmap Premium is purchased but if you are not licensed to use routing it will not work. That is the case for our agency: we purchased Streetmap Premium and the Routing_ND is included in the FGDB but we are not licensed to use it. If you did purchase the routing license then a call to support is advised. Hope this helps.
... View more
09-27-2019
03:21 PM
|
1
|
0
|
1205
|
POST
|
Also, you need to ensure that you follow the install steps or the patch will not work: "For pre-existing services, an update must be made to the service configuration in order for the fix to kick in. One way to do this is to disable and then re-enable editing and save via the Enable editing checkbox on the feature layer's item page in Enterprise." Good luck.
... View more
06-28-2019
09:04 AM
|
0
|
0
|
953
|
POST
|
We had the same issue; everything was working on Collector Classic for Android but iOS was throwing the exact same error. We were running Enterprise 10.6.1. There is a known issue which is "BUG-000116972 : Collector for ArcGIS (iOS) fails to submit photo attachments to hosted feature layers in ArcGIS Enterprise 10.6.1." We applied the patch which can be found here https://support.esri.com/en/download/7679 and the issue is resolved. Hope this helps.
... View more
06-27-2019
08:08 AM
|
1
|
2
|
953
|
IDEA
|
We should take this further and support this not only in Online but in ArcGIS Enterprise as well!
... View more
06-27-2019
07:57 AM
|
8
|
0
|
8976
|
IDEA
|
We should take this further and support this not only in Online but in ArcGIS Enterprise as well!
... View more
06-27-2019
07:57 AM
|
8
|
0
|
3583
|
IDEA
|
In ArcCatalog, users are able to right click a feature class contained within the Enterprise Database, select Manage > Locks to view who or what is locking the individual Feature. Now in Pro, users must right-click the database connection in the Catalog pane, click Properties, and expand the Connections section, then click Show connected users and locks. Then users must drill down to find the source of the feature lock via Object Name, Lock Type, or Lock Owner. This process is cumbersome to perform when searching for locks on an individual feature, especially if there are numerous editors and services running within the enterprise. ArcCatalog performs the action quickly and efficiently via the individual feature "Manage" menu. Often times feature parity is the key to adoption.
... View more
06-26-2019
01:10 PM
|
10
|
3
|
1469
|
IDEA
|
Just a thought for those still struggling with this, we too have hundreds of services running. When publishing services, you can disable schema locking of the service by changing "schemaLockingEnabled" to "false". It is under Parameters > Advanced. In ArcGIS Pro it is under Configuration > Configure Parameters > Advanced. This help keep the services from locking the data and allows schema changes while services are running.
... View more
06-26-2019
12:45 PM
|
0
|
0
|
719
|
POST
|
Im sure that this is a basic question so thanks in advance. I currently have an Arcade expression within a Javascript API WebApp that determines if a feature meets a DateDiff expression. The results from the Arcade expression are then sent to a UniqueValueRenderer within the app. var currentExpired = "IIf(DateDiff(Date(),$feature.DATERECEIVED,'days') > 365, 'Expired', 'Current')" I am trying to add a third condition and have written the following (though not truly in Arcade): var currentExpired = (DateDiff(Date(),$feature.DATERECEIVED,'days')) if (currentExpired > '365') { return 'Expired'; } else if (currentExpired < '7') { return 'Upcoming'; } else { return 'Current'; } I am trying to symbolize features that have a DATERECEIVED greater than 365 as 'Expired', those that are less than 7 days as upcoming, and everything else as current. Unfortunately, the logic seems to be flawed in that the upcoming features being symbolized are those that have been received within the last 7 days. Where have I gone wrong? Also, any ideas on how to write the expression in a truly Arcade format?
... View more
02-08-2019
11:04 AM
|
0
|
1
|
1483
|
Title | Kudos | Posted |
---|---|---|
1 | 08-02-2023 08:39 AM | |
1 | 09-11-2018 12:33 PM | |
1 | 09-18-2014 12:20 PM | |
1 | 09-27-2019 03:21 PM | |
8 | 06-27-2019 07:57 AM |
Online Status |
Offline
|
Date Last Visited |
06-21-2024
01:00 AM
|