Latest Contributions by ChrisDonohue__GISP

Sounds cool.  I'll give it a look, but unfortunately I'm on 10.2.1, so it may blow up due to version differences (the City has been holding off upgrading due to many other systems that connect to GIS that are not compatible with the newer versions of GIS, like ArcFM). Chris Donohue, GISP ... View more

A cartographic term I've seen for this sort of symbol is "herringbone".  However, I'm not sure if ESRI has a pre-made font already for it. Chris Donohue, GISP ... View more

In regards to the presence of a copyright mark and using an image, my Graphics Arts professor cautioned us in class against using others imagery without permission even if it did not include a copyright, as at least in United States copyright law just the creation of an image gives the creator implied copyright. The act of filing for an official copyright with the US government is an additional protection; but the absence of having filed does not negate their copyright, it just limits it. I'd cover your bases and get written permission to use their image/logo etc.  Given that you work for a government agency, you may also want to run it by your legal staff as to what the specific agreement needs to be.  Also, another complexity is that it may not be obvious who owns the copyright for an image/logo, as in some cases the organization using it had it created by another person/organization (for example, an independent Graphic Artist) and uses it under license from the creator. "Copyright is a legal right created by the law of a country that grants the creator of an original work exclusive rights for its use and distribution." Source:  Copyright - Wikipedia  Chris Donohue, GISP ... View more

I'd start by checking the Domain, Resolution,and Tolerance settings using ArcCatalog: If the data is in a Feature Dataset, check the Domain, Resolution, and Tolerance settings of the Feature Dataset in case any of them are wildly different than what they need to be. If instead the data is a stand-alone feature class, check the feature class itself for the Domain, Resolution, and Tolerance settings. Also, while you are checking the properties, do a quick check that the Projection/Coordinate system is appropriate for your data (just in case it was not assigned). Also, any chance your data is in a Parcel Fabric?  I ask as I hear there are other settings that affect editing of that type of data, so that may also be in play. Chris Donohue, GISP ... View more

There are a whole variety of things that can cause this.  To narrow things down, can you provide the following details: 1.  Which software package are you using and what version?  ArcGIS Desktop, ArcGISPro, etc.  10.5, 10.4, 10.3, etc? 2.  What type of database is the polygon feature class being stored in?  File or Personal Geodatabase, SDE, shapefile, coverage, etc? 3.  To digitize, are the standard Editing tools being used or another toolset? Chris Donohue, GISP ... View more

Besides what jskinner-esristaff suggested, are there maintenance scripts that are set up to automatically run at night?  For example, one to Reconcile all the versions?  Or a nightly process that automatically updates data by tearing it down and rebuilding it with revised data?  It may be that one of the scheduled processes has gone awry. Chris Donohue, GISP ... View more

I'm trying to remember if there were settings for coverages that affect Dissolve, but it's been too many years.  Let me instead tag someone who is very knowledgeable about working with coverages:  rastrauch  Chris Donohue, GISP ... View more

Just an idea - can you copy the data into a File Geodatabase and then run the Dissolve?  That may offer better results, as most of the limits for a File Geodatabase are higher than for a shapefile. Also, are you sure the topology for the lines is solid before the Dissolve is run?  It may be that the geometric distortions you are seeing are actually cases where the line topology was not properly connected in the first place. Chris Donohue, GISP ... View more

As suggested by Abdullah Anter , I'd look at Subtypes as a start.  One of the advantages of Subtypes is that one can code a default value that will be automatically populated. From the link Abdullah posted: Each subtype can have its own set of default values. In the above example, the local streets subtype could have the default value for a speed limit attribute set to 25 miles per hour, while the default value for the main streets subtype could be 35 miles per hour. Whenever a local street is added to the streets feature class, its speed limit attribute will automatically be set to 25 miles per hour. Whenever a main street is added, the speed limit will automatically be set to the default of 35 miles per hour. Note, however, that you will need to set up the defaults in the Subtypes ahead of time.  So if your project is a "figure out what we have as we go" type of project, you'll need to analyze all your combinations first so the Subtypes can be properly set.  Also, if this is a one-time project, it may be just as easy to instead Query the attributes and then Calculate the values for each selection to what they need to be instead of setting up Subtypes. Chris Donohue, GISP ... View more

An initial observation is that it appears that the Geodatabase has spaces in the name.  If that is the case, see if you can change the Geodatabase name using underscores instead of spaces.  There are quite a few processes in GIS that choke when a space is used in a filename or folder name, and unfortunately there is not a helpful error message that pops up to notify the user of this. Also, a question.  Does the same issue occur if one does the Calculate Field manually?  In other words, does it work when done manually, but does not work when employed through Modelbuilder? Chris Donohue, GISP ... View more

Tim: That's a pretty intense model you have there.  I can see why it is bogging down - Modelbuilder unfortunately is not known for speedy processes. When you do get it worked out, some of us might bribe you for copy of the model/code.  Like when the NENA standard finally becomes a mandatory requirement, me and this guy:  jborgion Hope the coding goes well, Chris Donohue, GISP ... View more

There's two common ways to do this - using either Python or Modelbuilder.  I'm not great at Python, so I will a discussion of how to do it with that to others.  As for Modelbuilder, here's what you could do: 1.  Place copies of all the feature classes in one folder, preferably with a short folder chain to the root. 2.  Design a Model using Modelbuilder with the following components: - Iterate ______ (Modelbuilder-only tool) - this will loop through all the feature classes to run the following processes.  Choose the appropriate Iterator to match your data. - Add Field geoprocessing tool - Calculate Field geoprocessing tool Note that the Calculate field would use the Value or Name output from the Iterate to populate the file name via the use of a Inline Variable Substitution. What is ModelBuilder?—Help | ArcGIS for Desktop  ArcGIS Help (10.2, 10.2.1, and 10.2.2) - Iterator Examples ArcGIS Help (10.2, 10.2.1, and 10.2.2) - Inline Variable Substitution After the model is run and all the feature classes now have the new field with the calculated value, you can run a Union geoprocessing tool to combine them. Chris Donohue, GISP ... View more

In theory, it can be rather large.  From ESRI documentation it appears that it could be as much as 256 Terabytes using the appropiate configuration keyword. But as for the reality, hard to say. The Top 9 Reasons to Use a File Geodatabase - ESRI (PDF) https://www.google.com/url?sa=t&rct=j&q=&esrc=s&source=web&cd=6&ved=0ahUKEwipxvalwO3SAhVLwGMKHeQnDI0QFgg4MAU&url=https%3…  Chris Donohue, GISP ... View more

I'd start by checking the Coordinate Reference System of the Grids and then also in the ArcMap Data Frames for all the parties.  What likely is going on is that the grids are not in a Coordinate Reference System, but either you or your colleagues are using a Coordinate Reference System in the MXD, so what you are seeing is the result. If it is a "small" shift, it might be as simple as a difference in Datum's.  For example, here in California a difference of about 200 feet in a NorthEast-Southwest direction is often a giveaway of a NAD1983 vs. NAD1927 Datum Shift.  In this case, one data layer may have been assigned to NAD1927 when it should have actually been assigned to NAD1983, or vice versa. Chris Donohue, GISP ... View more

Here's a previous GeoNet thread on a similar issue that was due to bugs.  In particular, look at the replies by curtvprice  Bug in Modelbuilder iterators when run as tool  You may also want to contact ESRI Support directly to see if they have a hotfix/patch. Chris Donohue, GISP ... View more