Latest Contributions by LanceShipman

There have been a lot of changes in the geopackage support since BUG-000090526. The raster2gpkg tool for 10.4 and 10.4.1 was updated in October 2016 base on the changes included in the 10.5 release.  Are you talking about the image located at: https://portal.opengeospatial.org/files/63156  ... View more

I took a look at your Excel file. Open the properties, on the General tab select "Unblock". It opens with MS Excel without any problems. ... View more

The max integer display was a solid clue. The MS Excel driver is interpreting the field as a Long. Since all of your values are greater than max integer, the field overflows, hence the  2147483647. At Pro 1.4 the column is seen as a double and displays correctly. As for the spreadsheet needing to be opened in Access and saved. I'll take a look tomorrow. ... View more

Click on "Use advanced editor"  (upper right above the Comment window). At the lower left of the comment window you will see "Attach". Please attach your spread sheet. Preferably a copy that has not been opened in Access and Saved. The number you are seeing is the max 4 byte integer. Why it's there, well we will have to take a look. ... View more

Our current target is to release the File Geodatabase API 1.5 by the end of January 2017. ... View more

I'll review your data when you post it.  ... View more

Can you please post the Excel table? We would like to take a look to better understand your issue and improve the software. ... View more

We recommend you use ArcCatalog to copy file geodatabase data because you can destroy your data when copying with Windows Explorer. There is no recovery. ArcCatalog handles that most common problems and avoids data loss. If you are sure that no process is using any part of the data you are unlikely to have any problems. ... View more

There is also a limit of 10 for field name widths. You have several fields that are 11 wide. Also we don't support field names that start with a number, which you have several of. CORRECTION: I reviewed our support for leading numbers in field names and I'm incorrect. We have no problem with leading numbers in shapefile field names and handle it when copy/pasting or exporting into another datasource that does not support leading numbers in field names.  ... View more

I plan on updating the documentation Post 10.5. Support of SQL Correlated Subqueries is not currently planned for the fGDB, but if a persuasive business case is submitted we will consider it. ... View more

File Geodatabase does not support correlated subqueries, ... View more

Have you run into problems with SQLite databases? If, so can you describe them? ... View more

Copying a feature class creates a new feature class and copies the contents. Copying the file geodatabase does a system copy of the contents of the file geodatabase. The most likely problem is that the file header of the feature class, which contains the count of features, has somehow got out of sync with the data. We have seen this a a few sites, but have never been able to reproduce the issue. It shouldn't be possible. If you see this issue again, please post the workflow and any information that you can. ... View more

We don't support VS2015 with version 1.4 of the file geodatabase API. We will be supporting VS2015 in the 1.5 version of the API sometime before the end of 2016. You could try using the redistributable for the version of the API you built with (VS2013?). ... View more

Copy the data. Does this resolve the problem? ... View more