Sign Management Solution

Question

I work for a State DOT. I am currently trying to symbolize our roadway sign inventory. We deployed the Sign Management Solution ( @ScottOppmann )  in AGO. The issue I am running into is that between the MUTCD manual and our specific state signs we have more than 1,000 sign symbols. Currently I am getting an error that not more than 200 unique symbols can be created. Does anyone know how to resolve so we can use more than 200 unique symbols? Is there any accounting for Sign Inventory in Roads and Highways?

style options.PNG

DanielWickens · Answer

@VeronicaS - I'm sorry I never got back to you, I am just now seeing this after responding to another one of your Community posts.

I wrote a blog article a few years back about Creating custom map symbols for the Sign Management Solution. It walks through the entire process including publishing the style as web style and using it in your Map Viewer symbol picker. However, there is still a limit of 200 unique symbols in the Map Viewer, so I would suggest symbolizing the most common signs in your inventory, and using the All Other Signs symbol provided with the solution for the less common signs.

VeronicaS · Answer

@DanielWickens I have a custom style that has all of the MUTCD signs and State specific roadway signs. Is there a way that I can use this style in the Sign Solution? Or is there a way that I can add the signs that are specific to my state with out running into the 200 feature limit? I know I can bypass the limit by publishing from Pro, I am just unsure how the Sign Solution will recognize the custom style or if it will cause issues. Do you have any words of advice?

DanielWickens · Answer

@VeronicaS - Both ArcGIS Online and ArcGIS Enterprise have the same limitation of 200 unique values. One workaround is to apply the symbology in ArcGIS Pro (where there is no limitation) and publish as a web feature layer, as described in this Esri Support KB article. I would advise you to publish the new service as a test first before swapping out any services in the solution. I'm not sure of the implications of swapping the service without testing it.

For Roads and Highways, signs are treated as event features. You can add fields to the Signs feature layer that comes with the solution that would be recognized by R+H (RouteID, Measure, Event ID, FromDate, ToDate, LocError, and Offset), and feed the data into R+H using the Append Events geoprocessing tool.

Alternatively, you can use GP tools or Arcade to calc the fields that are recognized by R+H.