Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
geocloud:dataformatfirstconsiderations:geocloudgs3ddetails [2023/01/06 09:11] – san | geocloud:dataformatfirstconsiderations:geocloudgs3ddetails [2023/01/13 08:48] (current) – external edit 127.0.0.1 | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | ====== | + | ====== |
+ | |||
+ | This section will go through the tables and fields to make the database compatible with both GeoCloud and GeoScene3D. | ||
- | This section will go through the dataformats to make the database compatible with both GeoCloud and GeoScene3D jupiter format. | ||
==== Data Format ==== | ==== Data Format ==== | ||
The following picture shows the expected data type of the fields in {{: | The following picture shows the expected data type of the fields in {{: | ||
- | [[https:// | + | [[https:// |
{{ : | {{ : | ||
- | If the data is supposed to work local with GeoScene3D as well as being uploaded to GeoCloud it is important to follow the formatting that GeoScene3D requires. The coordinates must be given in UTM, position of the top of the drilling is in elevation, the top and bottom of a lithology or screen is in depth and the water level is in elevation. The rocksymbol have to follow the order of a secondary file which can also be created in GeoScene3D or manually. | + | If the data is supposed to work local with GeoScene3D as well as being uploaded to GeoCloud it is important to follow the formatting that GeoScene3D requires. The position of the top of the drilling is in elevation, the top and bottom of a lithology or screen is in depth and the water level is in elevation. |
- | When the database | + | When the database |
{{ : | {{ : | ||
Line 18: | Line 19: | ||
For uploading this data type to GeoCloud click here: [[: | For uploading this data type to GeoCloud click here: [[: | ||
- | For importing boreholes into GeoScene3D | + | For importing boreholes into GeoScene3D |