You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When extracting data out of a GNDS file, we will want to have the data in natural C++ data structures (e.g., std::vector< double >, std::variant<...>, etc.). It would be good to do this in GNDStk so that each project the uses GNDStk doesn't have to do that conversion on their own.
The official GNDS documentation is based on some JSON files that contain descriptions of the contents of each of the different GNDS containers. It's possible, that these JSON files could be parsed/interpreted to automate the process so that we don't have to do a lot of work whenever GNDS changes—which it will.
Here is an example. Suppose I have a GNDStk Node representing a <values> container:
When extracting data out of a GNDS file, we will want to have the data in natural C++ data structures (e.g.,
std::vector< double >
,std::variant<...>
, etc.). It would be good to do this in GNDStk so that each project the uses GNDStk doesn't have to do that conversion on their own.The official GNDS documentation is based on some JSON files that contain descriptions of the contents of each of the different GNDS containers. It's possible, that these JSON files could be parsed/interpreted to automate the process so that we don't have to do a lot of work whenever GNDS changes—which it will.
Here is an example. Suppose I have a GNDStk
Node
representing a<values>
container:I would like to do something like this:
The exact API for this is to be determined, but something natural to C++.
In addition, being able to read the provided JSON files, we can support different versions of GNDS. I anticipate something like this:
The text was updated successfully, but these errors were encountered: