New answers tagged joins
The Make Query Table tool, based on GID will get what you want - every GID in the shape will get all matching GIDs in the xlsx (so, duplicate records). This will potentially generate a very large number of records. For example, if a GID appears in one table four times and six in the other, you will get 24 records. Note the result is temporary and must be ...
I do not think you can do that in ArcGIS OTB functionality. It requires perfect matches. It is sort of like the COMPGED function and as far as I know it is not built into Arc. Maybe if you do the join in another software that supports this function (SAS?)(http://www.lexjansen.com/nesug/nesug11/ps/ps07.pdf) then you will have more success. Check out this ...
I believe some of the comments already addressed the table join issue, so I'll just address the symbology/labeling. One of the most important things to consider when trying to symbolize/label is to make things easy to interpret at a glance. In order to do this, you want to avoid clutter, avoid anything too complicated, and to use intuitive symbology. In ...
The main difference is that in a classical join, inner (equi), left or right the joined fields or field must match exactly on both sides of the join, ie, in both tables you are joining. In a spatial join, there is no notion of exactness. Instead you are joining on an intersection, containment or even distance between a geometry field in one table and a ...
You are just adding location or proximity attribute data to your tabular query. If I have a sales order code number on in an order table, then in a "classical" join I might just look up the description of that sales order code number. If that same order table also has, say, an x_coord and y_coord column, I can use those values to find out sales districts ...
You may try to first import into Access (Personal File Geo database) then export them to your File Geo Database, excel is not very suitable to handle large records. For null values in your spreadsheet if numeric replace them with 0, it tend to solve the problem when joining, just make sure your join is on similar type fields (string to string, integer to ...
In the end I re exported the output to CSV and and imported using the table to table import and it worked fine.
I recommend taking a step back from the join, and first work out why not all rows are in the table that you created from your Excel file. Try using the Excel To Table (Conversion) tool which: Converts Microsoft Excel files into a table. to do this.
You cannot choose the join field because they are of different field types. Create a new field of the same type as the one you are trying to join too, then field calculate your values into your new field. The join should work.
Top 50 recent answers are included