Latest Contributions by GIS-Cambria

Getting familiar with the LGIM and addressing takes a little time and exploration. We've been working with this a bit and have some more to go, but for simplicity here's what I know so far: When creating a new address you click on a road centerline first to create the address point, then click on the location that the site address point will be. IF you don't double click then each location you click for a site address point will have the same address point number and related address point ID, then you can separately address each site address point with unit type and number. I've included a screen shot to help illustrate. To take this further, if you had building footprints and facility polygons you would also transfer information to these address sites such as if this site were called "Example Commons". ... View more

With the W3W service and API I think just being able to access W3W in an app can assist in locating an address and help with emergency services. If a caller says I'm at wrench.water.leaf then a dispatcher should be able to find that. At the least W3W will be part of our dispatching app. @Chris D and anyone else stating the vertical element: I contacted W3W and proposed they add a 4th ID to their spec. The 4th ID can be meter based and identify the height (use a - sign in front for below surface). A quad of info is just as easily parsed as a triplet, and the numeric part based on meter is easily 3D and converted to whatever local measurement. For example: wrench.water.leaf.4 is 4 meters above ground. Simple, easily parsed, and probably very quick to add/code into W3W. HOWEVER: when I spoke with someone from W3W about this they stated that so far the need for 3D was not significant?? Really W3W? ... View more

Yes. We would like to use AA to copy a feature ID from a layer to the Attachment table when an attachment is created. Glad you found a bug to squash. ... View more

Confirmed. AddIn was from one of the latest solution downloads, r/click on it and details properties say created 2/19/2016, just double checked; downloaded the UtilityNetworkEditing solution and checked the AddIn, same details. Opened Add-In-Manager and confirmed there too. Version 2.25.2016 ... View more

Awesome! Thanks. I had a fleeting thought that I was to remember to do this. So, here's the set up using the LGIM: FacilitiesStreets/Sign feature with the FACILITYID column (text 20) in the Sign_ATTACH table we added a column: FACILITYID (text 20) We wanted copy linked record to drive the FACILITYID from Sign to Sign_ATTACH using the PK/FK of Sign.GlobalID and Attach.REL_GLOBALID This doesn't work. But if we changed the method to fill in a different field and PK/FK on FACILITYID that we manually entered, it works. Makes me suspicious that it doesn't like to use the GlobalID. Also, with the attachments enabled there is the relationship class in the LGIM--don't know if that affects the AA method. DynamicValue example: Sign__ATTACH|FACILITYID|COPY_LINKED_RECORD|Sign|FACILITYID|GlobalID|REL_GLOBALID UPDATE: also tried Sign|FACILITYID|COPY_LINKED_RECORD|Sign__ATTACH|FACILITYID|REL_GLOBALID|GlobalID ... View more

Any of the downloads for Attribute Assistant (AA) would be useful. The trick is to create the correct rules in your DynamicValue table and, if using generate ID functions, also add the ID columns one would like to use into the GenerateID table. The combination of AA and the two tables mentioned can be modified to work within your own environment and doesn't require your data to be completely within the LGIM as the samples have. Below are a few quick examples of the rules for the DynamicValue table with the columns separated by |: BuildingFootprint|PARCELID|INTERSECTING_FEATURE|TaxParcels|PARCELNUM|C|True The |C| is a value to use centroids BuildingFootprint|BLDGID|GENERATE_ID|BuildingID|6|BFID-[seq] The |6| will pad the numeric generated ID to 6 characters from left. The GenerateID table is used to manage your numeric sequence. You would add a record to GenerateID with the field that your method will look for, in this example the attribute is |BuildingID|. The result would be BLDGID = BFID-000001 etc. ... View more

We've been using AA for a little while now. As a supervisor, nothing can make me happier than having a staff person successfully add new rules and tell me how much better AA has made things. For now we've focused on using AA to help with managing address points, road centerlines, site address points, fire boundaries, Master Street Names table, spatial relationships (attributes) between site address points, and parcels, Census Blocks/Tracts, USNG, zip codes, municipalities, ground elevation values from DEM, LAT/LONG values, GeneratIDs for multiple features/tables, etc... We've also recently dug into sign inventory management. Mike has built a fantastic tool that is very under advertised and has so much potential to really help with the local government stack. I really hope the powers that be at ESRI listen to that last comment because the LG solution is great for local govt. customers. The AA, with a few more example rules, can really help set up a turn key solution for the LG stack. I'd like to see more backing from ESRI with publicizing this AND I would like to see this port over to ArcGIS Pro. Mike, one AA rule we're working on for signs is copying linked record between the sign point and sign__attach table to fill in the sign ID (FacilityID) so we can recognize IDs that we're familiar with. We've tried the method with GLOBALID|REL_GLOBALID but that fails, however; substituting a different ID for the PK/FK relate works. Any chance you can check into this? ... View more

Yet another way to skin the cat is using Attribute Assistant (AA). You can add a rule to spatially dip (intersecting feature) just about anything and pass attributes between features. Something to be careful of though; feature envelopes. For example, we tried a bulk PIN transfer between address points and parcel polygons using AA and found that address points outside of a large parcel were still picking up that PIN. My only suspicion is the AA method used an envelope to select the point/parcel match. We did the spatial join to fill in all the existing address point/PIN info and then use AA for the maintenance. A spatial join will work more succinct in your case to get your foundation built, but then consider using AA for your ongoing maintenance. It's a fantastic tool! ... View more

Have you tried symbolizing using a quantity field? I'm not sure you can apply a range value on an extruded polygon without having something to first define the ranges. You might want to create multiple copies of the polygons in your layer, then add an elevation field and calculate each separate copied polygon into that specific elevation. Think of it like a layer cake. You'd have polygons stacked on polygons but each one in 3D has a specific place. ... View more

Not sure what version you're using but these tools work on SDE tables. Install the add in and use the tools menu. Under that you'll find reorder and replace field tools. *Caution* This will drop and recreate your table so any relationships will drop too. http://www.arcgis.com/home/item.html?id=9ea218ff575f4a5195e01a2cae03a0ae ... View more

Like the poster, printed 24x36 for my office. Any way to change "i am building" to "we are building"? (I hacked my copy to say "we are building" but doesn't look quite as clean as original). ... View more

All: If you check the July release notes on the LGIM it states several domains are deleted. However, if you import the latest LGIM.xml there are domains that still exist even though the release notes state they're deleted. Can someone else verify this to prove I'm not mistaking something? If this is verified, ESRI, please correct either the release notes or the latest LGIM.xml. DrinkingWaterAdvisoryDisinfect DrinkingWaterAdvisorySource DrinkingWaterAdvisoryType LitterSource LitterType piOpsTimePeriod piOpsUnits piWorkorderPriority piWorkorderType wLeakRepairMethod wLeakType wOpsConditionText WorkorderStatus ... View more

Ricardo, best of luck! I've been very slow to migrate but have finally started to test the LGIM and solutions while maintaining our current editing processes. One of the first steps for me was to prepare our data for address management. It's a different workflow and feature set than we used before but we are embracing the change and really see the light at the end of the tunnel. We had to get our road names into a master street name table forcing us to clean data and make sure it was distinct per municipality. We added a street name ID into the table to keep the relation between street segments and street names, and added street segment IDs to our existing address points to keep the address relate to the road all very useful in cleaning our data. Loading the data was simple once it was scrubbed. We still have to generate AddressPoints from our SiteAddressPoints--the plan is to geocode and generate the IDs to keep the integrity of the relationships. The Attribute Assistant add-in is a great asset and tool and has been very useful so far. The documentation on this tool and relative ease in modifying the functionality has enabled us to capture more data without requiring additional editing--for example assigning PIN (parcel ID) to SiteAddressPoints without extra effort.   We're tackling parcels at the same time but only started with that. We're really enthusiastic for what the LG stack will offer. ... View more