[X3D-Ecosystem] 2D/3D Layouts and Querying: metadata database

John Carlson yottzumm at gmail.com
Tue Nov 12 21:13:41 PST 2024


If anyone has ideas for 2D/3D layout of tens of 3D models, or quickly
querying metadata on 19GB of models, perhaps through caching, let me know.

My current metadata database table column design is:

column_name: column_type comment
———————————————————————
object_id/relationship_id/array_id: SFString/SFInt32 (ids appear more than
once in this column)

property_id/index_id: SFString/SFInt32 (“type” or “tag” is a property_id of
an object.  These property ids can be internationalized)

object_value: SFString/SFInt32 (refers to values in the object_id column
for relationships )

string_value: SFString

color_value: SFColorRGBA

integer_value: SFInt32

boolean_value:SFBool

float_value: SFFloat

timestamp_value: SFTime

thumbnail_value:SFImage

vector_value: SFVec3f ( for speed )

null_value: SFBool

currency_value: ???

etc.

This is designed like Perl, where a variable name can have many types.
Relationships and arrays are objects (multiple rows).  I realize in a
relational database I will have lots of nulls.  I am avoiding putting table
names in rows.

Internationalization, Localization and Accessibility will be in separate
tables, at least for mapping property_id to a locale.

Note that I won’t be storing X3D Scenes in this database.

Thanks!

John
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://web3d.org/pipermail/x3d-ecosystem_web3d.org/attachments/20241112/e21ad9c9/attachment.html>


More information about the X3D-Ecosystem mailing list