Latest Contributions by AmberBethell

I'm not sure if you have already figure out a way to do this but here is something you can try.  I assume that the page number in the inset map is comming from a label on a feature class being drawn in the data frame.  If that is the case I would add the feature class to my inset data frame two times.  For the first instance of the feature class, I would set a page definition query so that the value matches the data driven pages name.  I would add a label to this layer that uses a font that highlights the value.  For the second instance of the feature class, I would set a page definition query so that the value does NOT match the data driven pages name.  Then I would label this layer with a normal font.  ... View more

The functionality you are asking for is available using the Production Mapping custom steps - http://resources.arcgis.com/en/help/main/10.2/#/Product_library_custom_steps_and_tokens/010300000005000000/ To use the custom steps you must install both Workflow Manager and Production Mapping then run the ProductionCustomStepsPostInstall.exe - http://resources.arcgis.com/en/help/main/10.2/#/Running_the_postinstallation_for_the_Production_Mapping_custom_steps/010300000057000000/.  This executable only needs to be run once on the Workflow Manager database to add some tables. Once you have done these steps, in Workflow Manager Administrator you will see Production Mapping custom steps when you define a step type.  The Identify Product step allows you to choose which product in the product library will be used for the job.  This custom step includes the option to replace the job AOI with the extent of the product.  http://resources.arcgis.com/en/help/main/10.2/#/Workflow_configuration_for_the_Identify_Product_custom_step/0103000001zq000000/ Once you have linked a product to the job using the Identify Product step and checked it out of product library using the Check Out step, you can then have ArcMap automatically launch the mxd.  The trick to doing this is to use the Alternate MXD option in the Launch ArcMap step.  This help topic explains the parameters you need to use in order to set up the Launch ArcMap step.  http://resources.arcgis.com/en/help/main/10.2/#/Workflow_configuration_for_the_Launch_ArcMap_and_Edit_Product_custom_step/01030000030t000000/ ... View more

Have you tried the Polygon Overlap\Gap is Sliver check? This check will look for both overlaps and gaps with a single polygon layer or between two.   It has optional parameters to find only those overlaps and gaps that are long and thin or only those smaller than a specified size.  However if you leave the Thinness Ratio set to 1 and the Maximum Polygon Area set to 0 Meters, the check will find any overlaps and gaps regardless of size. ... View more

I don't currently have a 9.3.1 machine but I tested on 10.  I used the geometry on geometry check with the point as the first feature class and the line as the second.  I chose Intersects as the relation type and enabled the not option.  I did not specify a tolerance.  For my sample data I created a few lines and snapped points to the edge, vertex, and ends of some of the lines.  I create a point completely disconnected and another close to the end of the line but not snapped.  Only the points that were not snapped were returned.  The selected features in the attachment are the only ones returned for me.  If this option does not work for you, you can try the custom relation *T******* - this operation should find all points snapped to the end of the line (enable the not to find those not connected to the end of a line).  You can create a composite check that returns the results you mentioned - the orphans + those snapped to the ends.  Then you can add another Geo on Geo check to limit those results to those not snapped to the ends of points - use the *T******* with the not checked on.  If this doesn't make sense, let me know and I can included a sample bactch job. ... View more

I got a little confused as I tried to interpret your scenario.  On your graphic, the items circled in red say "Features that do not touch the interior (a non-endpoint) of a feature..."  If that is the case you can try the custom relation option with Geometry on Geometry and enter ***T*****.  This relation looks for when the boundary (end of line) touches the interior of the line it is being compared to.  To search for those that don't intersect the interior you can use the not checkbox with this relation. The text you posted made the scenario sound a little different.  Are you also wanting to know when one endpoint touches a feature and the other endpoint does not touch anything else? ... View more