Latest Contributions by JohnAlsup

The order of the alias was done to allow us to better automate the map creation process.  Outside of our process, it makes no difference. ... View more

Hi Jurgen Was this asset package modified in any way after being downloaded? ... View more

Hi mpatilesriaustralia-com-au-esridist , thanks for pointing this out.  There some significant changes to the utility network in 2.6 and we have not yet updated our foundation to include those changes.  However, for now you can just remove the Utility Network Layer from the map and add it back, only it, not all UN layers, and everything should work correctly. ... View more

Objectid is only unique to that database.  If you use any type of disconnected capabilities, your objectid's are not maintained and will be different between databases.  I would not use ObjectID as a unique ID.   ... View more

Thanks Manuele, that information helped a lot.  So I suspect that the two controllers have different subnetwork controller names (which they should) but also two different subnetwork names.  Since they participate in the same Mesh, they must share the same subnetwork name.   ... View more

Hi Manuele.   Is this a model you created from scratch or did you start with the esri Utility Solutions Electric Model? If this is from scratch, did you configure Controller A and Controller B to be in different tiers? ... View more

One great advantage to the method Mike has shown you is that if you are using the UN in a Service, then this operation always executes.  It is not dependent on the client.  So if you added a pole from a web app, the connection point would be automatically created, even though no template was used.   ... View more

Sounds like you have identified a software defect.  I would encourage you to log an issue with esri support.  Sounds like you have a good workflow for them to recreate the issue. ... View more

Hi Robert. You may want to check out this site.  https://maps.nccs.nasa.gov/arcgis/home/item.html?id=2e0471ae7a114277a8a1b16568c6cd20  It appears the data you are referring to is actually published by Home Land Security as part of HIFLD. ... View more

Hi Billy.  The purpose of the Assembly feature is to allow for a single point representation of multiple items.  In cases where you have a three phase fuse and you want to be able to operate the fuses by phase, you must have one device (fuse) per phase.  That gives you three fuses (devices) and two line end (junctions) where you really only want to see a single fuse symbol.  All of the device and junction features are then put in to the fuse assembly feature.  Now can you represent the three phase fuse as a single device, sure, but you will not be able to open a fuse on a single phase.  This may not matter to you, but to others it will.  When I worked a power company, we had many cases of switches and fuses where not all phases were operated the same way at the same time (mixed open and closed).  Also, again, if you need to have the case I have described, then you would want to use the assembly.  In that case, do you want your users to have to know when to work with an assembly vs a device?   ... View more

Hi Billy. One reason is consistency.  Let's take the service point example.  Let's say I have an apartment complex with 100 units and I will have 100 Device/LV Service Points.  I would prefer to place all those in a Device/Service Points in to a single Assembly/LV Service Point.  Now, I would only see these 100 features when i either enable view content or zoom in very close.  But, for the user/editor, they want to be able to turn the service point Visibilty On and Off or change scale suppression.  If you don't put all Device/Service Points in the Assembly/Service Point, then the user now has two places to change these settings.   Of course this is personal preference.  I like consistency.  Others may not. ... View more

Check your connection type for your database connect.  I suspect it's using traditional versioning ... View more

Hi Mike, it sounds like the Deploy tool may have encountered an issue but did not report an error on changing the datasource. So, did you verify that all the source layers in the map used for publishing were pointing to the correct data source?  Next, did you use the "Electric Network Foundation" map to publish with?  If so, were there any modifications to it? ... View more

Hi Eddy the attributes Pull Through, J-Bars and Unibar can be either added to the structurejunction class or set the alias for an existing field that is not used for junction boxes and assign a domain to it with the appropriate values.  I will be looking at adding these to our base model next week and can email you with how we will do this in the next release of the model. Load Break is a bit more complicated.  So, we have designed our electric data model to allow for traces that can identify load breaking equipment quickly.  For example, return the first load break devices upstream of my point/position.  We do this by assigning the "E:Load Break" network category to the specific asset types in the ElectricDevice or ElectricJunction feature classes.  Given this is a structure, that won't work.  But, if you don't care about these cabinet's being used in traces to find the closest upstream load breaking device, then you can just use an attribute.  But, if you want to find the first upstream load breaking device, we need a feature in the elecricdevice or electricjunction class.  In the Electric Model, notice that we have features that go inside the cabinet that are in the electric device class the Medium Voltage Elbow/Load Break Feed Thru,which would be like a G&W "Multiple Point Junction"  https://www.gwelectric.com/webfoo/wp-content/uploads/JBAR.pdf  ... View more