Implementation in DelftShell
Import functionality will be provided in DelftShell as import plugin, import plugin provides available datatypes.
User should be able to make a selection from the available data to import, based on
- object type
- Cross section
- Boundary condition
- Laterals
- geographic location
- time interval
- station ?! (ask Edward)
Plugin needs to be extendable so new import formats may easily be added.
Extendability on formats (structure of data) as well as providers (file, stream, webservice, database...)
Import use cases
- Import in project as data item; import a (complete) Sobek 2.11 MDB
- user selects import from file menu
- user selects data type from available types
- user specifies data source
- user selects (parts of) the data geographically or with time interval
- (selected) data is imported into project and added to project as data item.
- Import for specific/selected data item
for selected object in project
or selected object on map ...- user specifies data source
- user selects (parts of) the data geographically or with time interval
- (selected) data is imported into project and added to project as data item.
Import existing Sobek model database (MDB)
After conferring with knowledgeable people, reviewing the source the following arguments against reuse of the Conv_sbk source were found:
- dependency to Netter
- quality of coding
- end of life of VB6
- procedural design (not OO)
- necessity to inflict serious adaptions to source for mapping to DelftShell data model
- only a fraction of the source code is of interest, namely the parts that actually read and hence have implicit knowledge of the structure of data
Hence it is decided to reimplement the 'readers' in .NET. When applicable implicit knowledge about structure from the Conv_sbk is reused.
The the tool of choice for implementing readers is LEX; contrary to existing reader implementations, with LEX we can define readers in a language independent, reusable industry standard notation.
The approach is to start with implementing a full Sobek 2.11 MDB import in a time period of 20 days (40 fpe). After this period the experience will be applied to estimate the remainder of this sub project.
Free format import
This comes second in priority
3rd Party network formats
This comes third in priority. These are the formats currently supported by Sobek.
