Latest Contributions by ScottOppmann

Russell - We simplify the data structure on the road centerline and site address layers by storing all the road name elements in the master street name table.  This helps us optimize the editing workflows and really simplified the configuration of the locators you'll use in the rest of your ArcGIS maps and apps. I do encourage users to load their existing data in to the road centerline and site address layers and then use the master street name table to clean up/standardize these values.  For example: if you have road centerlines that were gathered for a 911 project and they have their unique list of road names - load those in to the road centerline layer and push the road names in to the master street name table.  If you have site addresses that were derived from parcel centroids, load them in to the site address layer and push those road names in to the master street name table as well.  Then you can use the Attribute Assistant rules to push edits (to standardize names) you make to the master street name table to the site address and road centerline layers. Hope this helps and let me know if you have any further questions.  There is a video on the ArcGIS for Local Government Meetup site from a few years back that provides a detailed overview of the Addressing solutions.  A bit dated now, but the fundamentals of the address data management solution are still valid.   We will probably have another meetup this fall to review the addressing solutions again and talk about the enhancements we provided in the June 2016 release. Finally - if you are going to the UC this year, we have a TW that will dive deeply in to our Addressing Solutions. ... View more

Alex - We worked with Waze to integrate the RoadBlock and RoadBlockPoint schemas with their Connected Citizens program and I believe these domain values came from them.  But let me review them again post UC and see if we can standardize with the Direction domain values.  Thanks for pointing this out. Scott ... View more

Jacyln - The Address Data Management solution does support multi-unit dwellings.  Fundamentally, it assumes that each site address point is a unique address.  Then you can specify a unit type/unit designation as well as an alternate unit/type/unit designation.  Steve's example above is a great illustration.  Hope this helps and let me know if you have any questions. One more note on multi-units.  We are wrapping up some enhancements to the addressing tools for our June release.  Among others, these enhancements will allow you to auto-increment address numbers in situations like this. Finally - if you are going to the UC this year, we have a TW that will dive deeply in to our Addressing Solutions. ... View more

Justin's note is right on.  You can use the UNITTYPE, UNITID, ALTUNITTYPE, and ALTUNITID to track Apt and Suite numbers.  If you are using the Address Data Management solution and the Attribute Assistant Add-in, the unit designations will be concatenated in the full address field.  In Justin's example, you could add 5th North St in the FULLADDR and Highway 78 could be added in State Highway designation.  A few years ago, we highlighted these workflows during an ArcGIS for Local Government Meetup on our Address solutions.  Here is a link - http://help.arcgis.com/en/localgovernment/meetup/MayMeetup2013.zip ... View more

The Address Data Management solution currently allows you to store the following: Local Street Name & Alias (MasterStreetName) Federal Route & Alternate Federal Route (Road Centerline) State Route & Alternate State Route (Road Centerline) County Route (Road Centerline) If you have additional aliases, you could add them to the MasterStreetName table or RoadCenterline layer. If you need to author locators with the alias info, I'd put them on the RoadCenterline layer.  If you're tracking them for historical purposes, you could probably just add them to the MasterStreetName table. Christopher Ard​ - If you're willing to share the design you come up with for the street name alias, we'll see how to best incorporate in future releases of the Address Management solution. ... View more

Jeff Ward is correct, all the road name elements are contained in the MasterStreetName table.  The Address Data Management map creates a full street name when you add the individual elements to this table.    The Attribute Assistant and construction tools in the Address Data Management solution then uses the full name in the MasterStreetName table when you assign new road centerlines and site addresses  (no geodatabase relationship is required). I looked at the cldxf reference and only find two rare street name elements that are not included: Street Name Pre Type Street Name Pre Type Separator You can certainly extend the MasterStreetName table to include these elements in your full street name if you have these elements in your community.  You'll see these workflows illustrated in detail in the video on the solution site. ... View more

Jeff - We don't have a video specifically on the Schema Migration Wizard, but did cover it during our ArcGIS for Local Government: Deployment Tips and Tricks Meetup last spring.  Check out the video and fast-forward to the 22 minute mark.  If you have any specific trouble, let me know. Scott ... View more

Bryan - We have not developed or deployed any multi-model routing applications yet with the ArcGIS for Local Government solution.  So I can't say whether the information model will support such yet.  That being said, you can certainly extend the information model to support your specific needs.  Scott ... View more

Cassidy - If you have published feature services from the sample data, you must create a local copy of the feature service and then use the Attribute Assistant rules as described on the solution site.  If you are trying to do the edits in ArcGIS for Desktop against the Local Government Information Model, you'll need to modify the rules in the Dynamic Value Table and specifically the feature class names for signs and poles.  They currently are configured to work with Feature Services that are synchronized via a local copy. Hope this helps. Scott ... View more

Several years back, we removed the subtypes from the model to simplify its implementation and use.  We typically only use subtypes in the Information Model to control network connectivity or topology more specifically; or to define domains for specific feature types.  What we found was that while this was in the original utility models, it wasn't used in daily practice and as such added a level of complexity that wasn't needed by most utilities.  We removed the use of subtypes in the model and instead provided a complete solution for utility network editing that includes a simple information model, focused editing map, and a set of editing tools that optimize the workflow.  ... View more

I would bet that Diagrammer is failing because it does not support certain data types  introduced in later releases of ArcGIS (parcel fabrics, etc.).  You can produce a nice map dictionary with Xray for ArcMap that will show the layers, fields, etc. used in the Water Utility editing map.  Then use that map dictionary in concert with the the Data Dictionary we provide with the Information Model to determine what data is being sourced in the solution. If you really want a poster or something similar, Xray for ArcCatalog will produce that as well.  I would just suggest you do it on a subset of the Information Model - layers used in water utility editing.  Certainly do not attempt to create a poster of the entire Information Model (way too much content for a single poster).  ... View more

Sallie - I would use the data dictionary we provide for reference.  Here is a direct link to the TaxParcel layer for more information on the specific fields you mention.  Typically this information is maintained in your CAMA system and sourced from that system to derive the TaxParcel layer. ... View more