@Anonymous wrote:
.... for the crosswalk i could use a dashed linetype but it won't show the line that runs up the sides of the dashes. .....
I was imagining the edge lines being separate -- a much simpler way than having them incorporated into a linetype. The only way I can imagine you could include those edge lines in a linetype definition would be with an embedded-Shape variety, like this:

But again, as a Shape, that could only be made of closely-spaced lines, not a true solid-filled area. And if they ever curve, the edges would be kinked. Also, if you do crosswalks at different overall widths, but the widths of the pieces are standard, you would need a separate Shape and linetype definition for every overall width you need!
Maybe you can find a .TTF text font that has a capital-I character with straight sides and squared serifs like that, and the right kind of proportions for your crosswalk width, to use in an embedded-Text variety of linetype, which would at least give you real solid fill. But a given character would give you only one overall width to suit a standard for cross-band and edge-strip widths.
Or, you could define a Block like that, and use it in either an associative ARRAY or MINSERT.
In all those possibilities, Wipeout-masking would be necessary at the ends to meet curved or angled curbsides.
Kent Cooper, AIA