How modify gdb

Aspose.GIS Product Family
5

Imagine that there are 20 layers in a GDB. you need copy all the layers because you only modify one feature in one layer, the performance will be very poor.
Our data is very large, there are many layers, totally hundred millions of features
Arcgis engine is 32 bits.32-bit program users can only use 2G of memory. We don’t have enough memory for complex operations at all, so we want to use aspose.gis under 64-bit.

Meanwhile, we have some feature request
1.Spatial query : VectorLayer with VectorLayer or geometry
2. In place (insert,delete) field with a layer,modify fields of layer and the name of layer.

thanks

6

@lsl,
Thank you for the details, they are really helpful.
Aspose.GIS already supports Update mode on the Dataset level. Once you open a dataset with Dataset.Open, you can create or remove its layers in-place. But on the level of a VectorLayer now there is no way to update data in-place, and I can see how this is problematic with very big data sets.

I’ve logged GISNET-348, GISNET-350 and GISNET-351 for spatial queries, in-place attribute table modifications, and layer renaming correspondingly.

7

any update? ~…~

8

Hi, @lsl

We have planned this functionality for the 4th quarter of 2020. And we will start working at the end of this month. The solution requires significant and complex work. We will add an edit mode for each vector-based format in turn.

Thanks.

9

any update? ~…~

10

We spent a few time to analyze this features. Also we implemented a “add in exist layer” possibility for the shapefile and database formats. Deletion and adding are required for editing (one of the steps). But we had to switch to other tasks (some bugs). We plan to return to these tasks.

We apologize for your inconvenience.

11

any update? …

12

@lsl,

We will get back to you with updates soon.

13

any upate? you can get some ideas from gdal which support this @Amjad_Sahi

14

The task requires a redesign of the internal architecture, so we postpone it. However, we have already taken steps to solve it, but we cannot give exact estimates.

15

any update ?

16

We are already planning for the next six months. And today we discussed your task. We got the resources to fix it.

We have made the “ToEdit” mode. However, it overwrites complete file data, which does not solve the problem. We made the “InMemory” mode, it works with the entire file in memory. We plan to make the “InFIleEdit” to solve the problem (details is underwork).

Thanks for keeping the focus on this issue.

17

Is there any update? I can help test it out

18

Thank you for your attention to the task. We have started working on it and plan to release it before the end of the year.

Best regards

19

can we have test to the task

20

@lsl could you please specify the version of Aspose.GIS you use and provide code snippet and input data to reproduce issue.

21

@Dmitriy.Sorokin
This problem has been around for so many years, when will it be solved

22

@lsl unfortunately Evgeniy.Timofeev doesn’t work in Aspose.GIS, so, if it suitable for you, could you please provide expected code sample for your task.

23

Can you view the history of this post, so you understand what I’m saying?

24

@lsl we need to review roadmap, so, we wanted to focus on the must-have features for customers. At this point, your assistance would be appreciated. If you have requests and have the vision of how this should work, could you please specify the most important features for you?