Replacing Outdated dbf File

[dusko23]

I decided to submit this proposal after gaining loads of experience creating a converter from XLS, XLSX, XLSB, and CSV to Shape File. The process goes in two steps. The first one is to write all the data to the SQLite database. Providing all kinds of controls and checkings before the SQLite database is populated. Calculating maximum data width for each column is included (needed when defining DBF structure) for example. This is how Gui to create sqlite database looks like. Nealy 500,000 rows and everything works like a breeze.

From sqlite database, users can create all flavors of shape types. Including Polygons with holes. The time stamp for each point is included if XLS(X,B, CSV) File contains a valid Date and Time Column. It was a mini-epic journey indeed.

Creating all this stuff I definitely realized that the time to replace outdated DBF files with SQLite DB files is long due. It would also open loads of possibilities because users would be able to add their own Tables to the same DB file and keep business logic tidy. Not to mention all kinds of rendeders under the same roof. And getting rid of short names and value strings. Although I am not a C# programmer I am prepared to contribute my knowledge and experiences using SQLite DB in many projects. I could say that the .NET SQLite library is rock solid, has not been changed for ages (there was no need to) and it really shines for this type of project. I am convinced that shape file technology would regain a completely new perspective and refine shape file standards.