Results 1 to 3 of 3

Thread: texture.txt inside .kmz

  1. #1
    Junior Member
    Join Date
    Sep 2007
    Location
    Armenia
    Posts
    6

    texture.txt inside .kmz

    Hi All,

    Actually, I don't understand the purpose of the texture.txt file inside .kmz files. Why not to refer to image files directly from within .dae files? Why should we refer to texture.txt file first and then fetch the image file name from there?


    Thanks in advance.
    Your answers would be appreciated very much.
    --
    Arman

  2. #2
    Senior Member
    Join Date
    Jan 2006
    Location
    Foster City, CA
    Posts
    540
    I don't understand it either. I'd love to know what Google/Keyhole's rationale was for doing it that way. If you're really curious you might want to ask on one of their forums. The design of the .kmz format has nothing to do with Collada.

  3. #3
    Junior Member
    Join Date
    Jun 2006
    Location
    Morrison, CO
    Posts
    22
    I believe I read somewhere that it could be used to override interpreted texture locations. So a server based image could be replaced with a local one, or vice versa. Sorry I don't really have time to check into this more right now, but I'm keeping an eye on two computers & 8 complete rebuilds going on right now Just doing some light surfing while I'm waiting for compiles to complete (~20 minutes).

    ... I'm back ... should've just Googled it the first time. See this page for details: http://code.google.com/apis/kml/documen ... odels.html

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •