Latest Contributions by SteveGrise

I'm not sure what the issue is offhand. Are you able to open another simpler xml workspace document? Also I can't tell from the info which version of the software you are running, and if you have Excel installed. To me it looks like an issue with the Excel install, which might also be complicated by non-English version of Windows, I'm not sure. There's a new version at http://www.arcgis.com/home/item.html?id=9ea218ff575f4a5195e01a2cae03a0ae that includes enhanced validation. I don't think that would address your specific issue, but you might try that along with making sure that you can do a basic export/import from a Geodatabase. ... View more

Can you try uninstalling then re-installing the addin? Apparently there are some issues with addins when upgrading to 10.4.x from 10.3. You will need to manually uninstall then re-add it. ... View more

Here's a link to the latest: http://www.arcgis.com/home/item.html?id=9ea218ff575f4a5195e01a2cae03a0ae ... View more

Hi Chris, is Excel installed on the machine, if so which version? Was it working with a previous ArcGIS version install? ... View more

try steve @ vertex3.com ... View more

Hi Doug, if you send me the Xml workspace file I can take a look. I'm the author of X-Ray and I do a lot of repairs on these files - many things can go wrong and the Validator just checks for common errors. Either attach to a reply or you can send directly. ... View more

I made an update to the code. The result you needed from the validation is attached. Also I attached an updated xslt file that can be placed in your addin\xslt folder (i.e., a folder like C:\Users\Steve\AppData\Local\ESRI\Desktop10.2\AssemblyCache\{AB7D758E-ACB2-4583-8E74-CC9234ADA719}\xslt). The published download for the addin will take a bit longer to be updated. ... View more

Sure, if it was my data model I would write a script (xslt) that populates the default value for Strings to No Information and the default values for Integers to -999999 (or maybe just -9!). Then I would also have a small (Xml, csv, or json) file that has non-default values by feature class, subtype, and field. The script above would use those values where they exist. That way you could just worry about the exceptions. I will also take a look at adding a check for the issues you encountered to the X-Ray Validator. It would have made things easier! ... View more

StructureSrf had a similar issue to StructurePnt. The HD320* fields are integers but the default values are strings. Also I noticed the fields were Integer length 5 instead of 4 so changed that since it will likely be a problem. I attached an updated spreadsheet for those 3 feature classes that loaded for me using Import Using Geoprocessing and regular Xml Workspace Import. ... View more

I used the 'Import Using Geoprocessing' tool. I had the database set up with the domains already so it just had to add the feature classes. This will take longer to run but tells you exactly what the error is. On Settlement_Srf it failed: ZA340_LGF_GRP* are integer fields with default 'No Information' on cell e186. Needs to be changed in many places. F_CODE - AL022_PPLX default value is too long and I think should be AL022, had to fix this in the corresponding domain too. On StructurePnt the HD320* fields are integers but the default values are 'No Information' I ran out of time to check the last feature class tonight. ... View more

I typically delete half of the spreadsheets, save with a new name, then try to import. In this case I trimmed off the first dozen or so and isolated that one of the H feature classes was the issue. For me everything except the H's worked, so I'm surprised to see another error. The validation checks for many issues but not every possible error. ... View more

Ok, I gave you the wrong name. It is the HGGroupLocationSrf feature class. Look in cell E118. The basic issue is a type mismatch in the value for the Subtype default value that doesn't match the field definition. I noticed in some others that the FCSubtype default value in this area conflicts with the feature class default. I'm not sure if that might cause some issues in ArcMap. ... View more

Search lower down in the subtypes area. Steve ... View more

On the Feature Class HypsographyPnt, the FCSubtype DefaultValue for SubtypeCode 100355 (the first one) has a value of 'noInformation' rather than 100355. This string in the integer field appears to be the source of the issue. Once I replaced that I was able to import that and other parts of the model. ... View more

I will look at the Xml workspace document for the error if you send it to me. It is likely a different problem than the last few people have reported. This error is reported by the esri Xml Importer so there is little I can do to improve the messages, but there are many different things that can go wrong. steve (at) vertex3 (dot) com ... View more