New answers tagged

1

This doesn't have to do with the FileGDB API so much as Visual Studio/Windows software development. Esri ships two libraries, the link library in lib, and the runtime library in bin. The link library is just a set of stubs so the compiler knows the DLL function signatures, and the runtime library contains the actual file geodatabase functions. Actually, ...


3

Taking multiple questions out of order: The size of a raster is just the product of bit-depth/8, bands, rows, and columns plus header metadata (statistics, etc.) 32/8 x 1 x 32225 x 13417 = 173079300 bytes ~= 1710Mb 8/8 x 1 x 32225 x 13417 = 43269825 bytes ~= 438Mb ArcGIS does not report the compressed file size. Compression tools are very sensitive ...


0

Using the explode_to_points=True argument into updateCursor as suggested in this link did the work. Thanks to @klewis for the comment. However, because the updateCursor in my case works with two fields, I had to specify two arguments in the final updateRow call, as row[0] refers to the filed Floor_Number, while row[1] is the Z coordinate I need to change. ...


0

No features are actually lost. This appears to be a bug, but instead it is a part of the design. To increase efficiency and performance, the local map only caches to your current view extent.


1

Try this: mlayer = arcpy.mapping.ListLayers(mxd, "1415_LGA_SpatJ", df)[0] fn_field = 'MAPID' ....function which creates list of values a_list for each_a in a_list: whereClause = '"' + fn_field + '"' + ' = ' + "'" + each_a + "'" arcpy.SelectLayerByAttribute_management(mlayer, "NEW_SELECTION", whereClause) Assuming it works it represents just ...


0

To select a single feature class from a gdb, we query for all entities inside it: -sql "select * from FEATURE_CLASS_NAME" To generate a list of feature classes following your sample use nested FOR loops: @echo off for %%S in (01 02 03) do ( for %%F in (01 02 03) do ( echo ogr2ogr out.gdb in.gdb -sql "select * from Sec%%S_Frm%%F" ) ...


2

No it's not possible to do it directly. A workaround is to create a feature class in the gdb with the correct settings for the text fields. Import the csv data afterwards. right click the newly created feature class choose load > load data follow the wizard done!



Top 50 recent answers are included