Latest Contributions by RobertKrisher

@CodyPatterson As soon as something is traditionally versioned it will get an SDE_STATE_ID field (regardless of whether edits are moved to base) and this value is used along with several system-maintained tables to manage all the edits in default and versions. If you just use the versioned views, you don't need to worry too much about what's happening behind the scenes (because the views handle it all for you). There are several technical articles out there that explain this process (and the waters can get pretty deep on this stuff) Here's a good introduction to traditional versioning: Versioning 101 - ArcUser Technical Article - Esri Community Here's a description of the system tables: ArcGIS Help 10.1 - Versioned tables in a geodatabase in SQL Server ... View more

@joecastellana When editing directly in default no posting or starting/stopping editing is required. All edits are directly and irreversibly applied to default, so use with care. I've seen many organizations successfully use third-party messaging services or apps to coordinate work, but I think you should check out this presentation from IMGIS where Houston Water demonstrates their editing workflow and how they manage it using ArcGIS Workflow Manager. I'm always a sucker for a good dashboard but having real-time access to the status of every job in the GIS and knowing it's actually linked to the workflows we use for managing our versions is pretty sweet. The version management link provided by @MarceloMarques does a good job of explaining all the most popular workflows, but as @ClaudzPora noted they misspoke when they said you could create a 2-tiered version system. Everything needs to be 1 version off of default. If you do want to try and enforce a single editor, you'd need to protect default and have the workflow be that only one or two people are allowed to post to default (i.e. have the version administrator role). This way all edits are required to flow through your posters. I'd like to know a little more about your statement "Also we see instances of dirty areas being assigned to editors that were not working on those features which can cause some confusion", can you elaborate? ... View more

@OliviaGill3 Terminal devices cannot be drawn midspan on lines, they must split them. Once the line is split the junction-edge connectivity rules apply, but if you don't split the line you get a topology error. In most cases after splitting the line you will want to connect each line to a different terminal on the device, although in the case of drawing something like a fuse for a tap-line midspan (where it connects to three lines) you would connect the two lines on the upstream edge to one terminal, and the tap line to the other terminal. This configuration allows the fuse to be opened and only interrupt flow to the tap line, leaving flow on the mainline uninterrupted. ... View more

You don't need to explicitly map your default network junctions from your utility network into features of the utility network, they system will automatically create system junctions for these locations in a hidden system table. The only time you need to worry about migrating these features is when they represent real-world features or when they represent the connections between two lines that have a different asset type. In those cases, the type of junction you create will depend on the types of lines being connected (e.g. overhead to underground gets a riser or tap). The terminal error you are seeing is because you have said that the features on either end of the line have a 'CB:Bus Side' terminal, when actually the end of the line that has a connector on it should have the default value of None. The modify terminal tool will not let you manually populate an invalid value like this, so it may be that you have some script or workbench that is setting these values (or you are splitting lines after setting terminals)? ... View more

Those images look like elbows in a junction box. So, if that's what your engineer is interested in modeled you would map them to the appropriate asset type in the medium/low voltage elbow asset group. ... View more

@TóthRóbert  The visible option is used when calculating the association status of a feature or object. Specifically, is used to differentiate visible or hidden content. While this works great with features where we can use this status in display filters to hide content in your containers, as you noted it has much less meaning when applied to non-spatial objects. However, as you noted, you could use this value in network diagrams if you wanted to create some special diagrams that leveraged this value to hide non-spatial objects in your diagrams. ... View more