The File Geodatabase API 1.3 is now available for download from the resource center. (http://www.esri.com/apps/products/download/) What�??s new at 1.3:* Added support for MS Visual Studio 2012. * Fix the MutlipatchShapebuffer helper functions and correct multipatch documentation errors in the extended_shape_buffer_format.pdf.(NIM078028) * QueryEnvelope does not correctly calculate M and Z extent. (NIM082237) * Supported GCS (Geographic Coordinate System) and PCS (Projected Coordinate System) updated to match 10.1 sp1. Fixed Issues: NIM078028 Fix the MutlipatchShapebuffer helper functions. NIM082237 QueryEnvelope does not correctly calculate M and Z extent. NIM084105 MultiPartShapeBuffer::GetMs return the wrong pointer value NIM085366 Using only a null or empty geometry results in a invalid extent.

We are planning a release in the fall. I'll be posting details next week. Lance

nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

File Geodatabase API 1.3 is now available for download.

LanceShipman

The File Geodatabase API 1.3 is now available for download from the resource center. (http://www.esri.com/apps/products/download/)

What�??s new at 1.3:

Added support for MS Visual Studio 2012.
Fix the MutlipatchShapebuffer helper functions and correct multipatch documentation errors in the extended_shape_buffer_format.pdf.(NIM078028)
QueryEnvelope does not correctly calculate M and Z extent. (NIM082237)
Supported GCS (Geographic Coordinate System) and PCS (Projected Coordinate System) updated to match 10.1 sp1.

Fixed Issues:

NIM078028 Fix the MutlipatchShapebuffer helper functions.
NIM082237 QueryEnvelope does not correctly calculate M and Z extent.
NIM084105 MultiPartShapeBuffer::GetMs return the wrong pointer value
NIM085366 Using only a null or empty geometry results in a invalid extent.

Najděte více příspěvků označených jako

Accepted answers

All comments

ChristianMaire1

The Dev Summit was over three months ago. Is there any new status on the VS2015 build / next release?

LanceShipman

We will not be releasing a VS 2015 build for the 1.4 version of the API. We will include a VS2015 build in the next release. We have several priority issues ahead of this, but I expect we will release before the next Dev Summit. I'll post status when I have it.

Lance

UlrichEgger

Visual Studio 2015 is released. Have you plan to release File Geodatabase API builds for this version?

PaulAustin

1.4 seems to have solved the crash I has with sorting data and string columns

AdamDavis

Hi Lance,

Thanks for the update. Would be happy to be a beta tester for this - would hopefully help both Esri and ourselves.

Thanks,

Adam

UlrichEgger

Thanks for the reply! We keep one's fingers crossed for this!

LanceShipman

We plan on releasing the 1.4 version of the API in March 2015
VS 2013 support is in 1.4

LanceShipman

Thread support will not be changing at 1.4. We are aware of the XML library issue, but it we will not be replacing it at the 1.4 release.
ORDER BY on DATE and INTEGER columns is supported. Be aware that the ordering field must be included in the field list. This is true in ArcObjects and in the API.
We do not see a crash in windows when creating a FGDB after deleting another FGDB. Please supply example code.
We don't see a crash when invalid SQL is used. Please supply example code.
We will not be including gcc on windows at 1.4. We already support VS2010, VS2012, and VS2013. Linux 32-bit, Linux 64-bit, Both gcc and Clang on MacOS.

PaulAustin

Any chance the following will be fixed or available in the 1.4 release.

Thread support. Right now things crash if you create different file geodatabases in multiple threads. I'm not looking for full threading support for a single file geodatabase. But it would be nice to operate on different file geodatabases without having the synchronize on the whole API. I think the main issue is the XML library having shared data so you can't even use it in multiple threads.
Support for order by on date and integer columns.
Not crash on windows when creating a FGDB after deleting another FGDB.
Not completely crash if invalid SQL is issued
More meaningful errors (e.g. file xyz not found) rather than general function errors if files go missing (e.g. network failure)
A gcc compatible library on windows as well as Visual Studio

HalWatson

Thanks for the reply, that helps. Looking forward to the 1.4 release. Good luck!

LanceShipman

File Geodatabase API supports all versions of 10.x.

v 1.3 does not support reading or writing compressed data. Reading compressed data will be supported at v 1.4.

We have been buried under the 10.3 ArcGIS release and the Pro 1.0 release so haven't had a chance to finish up 1.4. We hope to have an estimate of the release date soon.

HalWatson

1. Does the v 1.3 API support access to FGDBs created with ArcGIS 10.2 ?

2. Does the v 1.3 API support access to compressed FGDBs or compressed featureclasses within a FGDB ?

Thanks, HW

__11

It would probably be helpful to update http://resources.arcgis.com/content/geodatabases/10.0/file-gdb-download, which still has v1.2

Připojte se k diskusi

Přihlášení členové mohou přispívat, sledovat aktualizace a další. Jste tu noví? Zaregistrujte si bezplatný účet.

Rychlé odkazy

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.