Hi Matt,
Thanks for your reply.
Currently we are mostly uploading LAS and OBJ files. For the LAS files it’s my understanding that the georeferencing information is a standard inclusion in the LAS file header. However, some of our LAS files come out as georeferenced 3D Tiles, and others do not. I will send you a message with example ion Asset id’s. I also have uploaded an OBJ with a metadata file, but this seems to be ignored. I’ll also send you an example of this.
I haven’t yet tried supplying the optional position property in the REST API as I wanted to understand what files would (or wouldn’t) require me to do that.
I tried following the KML example in the link by adding a .kml file alongside my OBJ, but again it didn’t seem to do anything. I’ll include a sample of this in the message.