Next highlight each column individually in Excel and check the properties.
Ask Excel to fix the problem and we're one step closer. Just highlight all the cells in the column (NOT by clicking the field / column heading) and the yellow exclamation mark with a drop down appears. The green triangles in the top left corner of the cells indicate that the cell has a number stored as text. That was the case in this specific example so let's take a look at what went wrong. Dates in Excel to Arc are a whole new post but other irregularities can also cause problems. If the formatting is wrong in Excel it's going to cause problems in Arc. More drastically you could just delete rows with empty cells if that data is redundant or not important. This can be solved by sorting your datasheet to make sure the top few rows (I think it's the top 8 that count) are all filled with data. faced with empty cells it defaults to the text (string) data type which can lead to subsequent values not being read properly. Arc reads the first few rows of a Excel sheet in order to assign data types. If the first few rows of the Excel sheet have empty cells in them this can confuse Arc. Underscores rule_the_roost here if you do need to separate words for readability. Don't use special characters (headings like are too special). Keep the number of characters low (I always aim for no more than 13). Let's have a look at a few possibilities and their solutions: 1 field headingsĪrc doesn't like fancy field (column) headings. They were there in Excel but had now vanished! The Null bells were tolling. I was approached recently as user had imported and Excel file into a geodatabase but then could not see the coordinates. Importing such a monster to a geodatabase can cause untold problems. It could be any version of Excel, it could be correctly formatted with notes, front page instructions and a glossary OR it could be have been put together by a digital Dr Frankenstein. Often for the GIS guru (you) it'll be from Excel.
0 kommentar(er)
