nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Traverse Tool should populate COGO for multiple layers when using Group Templates

jcarlson

Situation: I'm drawing up a plat. I could just draw the lot lines, then copy them into the right-of-way layer. But why not just draw them both at the same time?

This is sort of possible using a group template. But when I do a Traverse this way, the second layer's lines don't get any of their COGO attributes updated.

The technical backend of what's happening in a Traverse may prevent this from working properly, but I'd *love* if I could do this.

Trouver plus de publications taguées avec

Editing

Under Consideration

Status: Under Consideration

Réponses

AlfredBaldenweck

AmirBar-Maor

@jcarlson

Very interesting idea and use of group templates for parcels!

It will have to be specific to Lines in a group template that are both COGO Enabled.

Q: What would happen to attributes that are your lot lines and are also on the ROW lines? Should these be copied if the fields match the name and type?

Any fields that do not match will not get copied over.

Q. Any attribute rules that conflict with copying the COGO values will take precedence - is that OK?

jcarlson

1. I think having the attributes match would be fine. I'm thinking about this in the context of creating a new traverse, and it's mostly the COGO I'm concerned.

Though now that I think about it, I would love it if I could specify per-layer attributes. In a standard template, I can have the tool display a prompt for attributes.

What if a group template could prompt attributes for each layer in the template? I say that because I would love to draw, say, a lot line with the label position to the right, and simultaneously draw a right-of-way line with the label position to the left.

But that may be too much to ask for. I could always flip the attribute after the fact, too.

2. Attribute rules taking precedence is okay, I think that's what I'd expect.

Rejoindre la conversation

Connectez-vous pour publier, suivre du contenu, et plus encore. Nouveau ici ? Inscrivez-vous gratuitement.