Is your feature request related to a problem? Please describe.
No
Describe the solution you'd like
At this point, GeoGate assumes that the exchanged fields are all in double data type. The implementation needs to be extended to be smart enough to support different data types such as float, int etc. The Python plugin implemented with Conduit is also expecting double (both import and export fields) to simplify the implementation.
Describe alternatives you've considered
N/A
Additional context
N/A
Is your feature request related to a problem? Please describe.
No
Describe the solution you'd like
At this point, GeoGate assumes that the exchanged fields are all in double data type. The implementation needs to be extended to be smart enough to support different data types such as float, int etc. The Python plugin implemented with Conduit is also expecting double (both import and export fields) to simplify the implementation.
Describe alternatives you've considered
N/A
Additional context
N/A