Weka hills Leapfrog demo project example

[JoostGevaert]

Related to #49

[JulesBlm]

When creating brgi_geodb I get KeyError: 'LocationID'. bh_location_df.columns returns Index(['HoleID', 'Easting', 'Northing', 'Elevation', 'z_on_terrain', 'Depth'], dtype='object')

WH_cpt_collar.csv shows HoleID,Easting,Northing,Elevation,z_on_terrain,Depth and WH_collar_all.csv shows LocationID,Easting,Northing,GroundLevel,FinalDepth,Phase.

I'm guessing the order of reading the csv in the folder is not deterministic.

[JoostGevaert]

A solution could be to create a dictionary with the CSV-paths in it instead of a list

[JulesBlm]

Maybe we can start thinking about a convenience function to read and convert survey CSV files in a configurable manner.
Borehole CSV's follow an informal(?) convention, with collars in one file, survey data in another.
For example, the MacPass mining borehole data set has similar CSV survey data but GroundLevel is named Elevation and Depth_m rather than Depth.

[JulesBlm]

Don't really need this cell anymore but's I think it's nice to see what's actually in the folder.

[JoostGevaert]

Shouldn't we fix the #49

When the column name in the data is the same (case insensitive) as one of the Bedrock GI standard column names, writing to a database such as GeoPackage becomes impossible. For the Weka Hills GI data this means that "Easting" & "easting" and "Northing" & "northing" cause a conflict.

issue before merging this PR?