1"use strict";(globalThis.webpackChunkvrgs_docs_v_3_1=globalThis.webpackChunkvrgs_docs_v_3_1||[]).push([[10654],{16890(t,e,i){i.r(e),i.d(e,{assets:()=>u,contentTitle:()=>a,default:()=>l,frontMatter:()=>n,metadata:()=>r,toc:()=>c});const r=JSON.parse('{"id":"tutorial/quick-tips/qt060-attributes","title":"Creating Attributes","description":"<iframe","source":"@site/versioned_docs/version-3.3/tutorial/quick-tips/qt060-attributes.md","sourceDirName":"tutorial/quick-tips","slug":"/tutorial/quick-tips/qt060-attributes","permalink":"/docs/3.3/tutorial/quick-tips/qt060-attributes","draft":false,"unlisted":false,"editUrl":"https://github.com/vrgeoscience/vrgs_docs_v3/tree/master/versioned_docs/version-3.3/tutorial/quick-tips/qt060-attributes.md","tags":[],"version":"3.3","sidebarPosition":1,"frontMatter":{"sidebar_position":1},"sidebar":"docs","previous":{"title":"Using Orthopanels","permalink":"/docs/3.3/tutorial/quick-tips/qt050-orthopanels"},"next":{"title":"Hardware Requirements","permalink":"/docs/3.3/general/setup-system/hardware-requirements"}}');var s=i(74848),o=i(28453);const n={sidebar_position:1},a="Creating Attributes",u={},c=[];function d(t){const e={h1:"h1",header:"header",p:"p",...(0,o.R)(),...t.components};return(0,s.jsxs)(s.Fragment,{children:[(0,s.jsx)(e.header,{children:(0,s.jsx)(e.h1,{id:"creating-attributes",children:"Creating Attributes"})}),"\n",(0,s.jsx)("iframe",{width:"640",height:"360",src:"https://www.youtube.com/embed/rgzzg2U-2Uk",frameborder:"0",allow:"autoplay; encrypted-media",allowfullscreen:!0}),"\n",(0,s.jsx)(e.p,{children:"This quick tip shows you how to create attributes from your digital outcrop models. These attributes make interpretation and classification easier by enhancing information in the model. VRGS provides an extensive suite of attributes to choose from. You can use these for both manual and automated interpretation techniques."})]})}function l(t={}){const{wrapper:e}={...(0,o.R)(),...t.components};return e?(0,s.jsx)(e,{...t,children:(0,s.jsx)(d,{...t})}):d(t)}},28453(t,e,i){i.d(e,{R:()=>n,x:()=>a});var r=i(96540);const s={},o=r.createContext(s);function n(t){const e=r.useContext(o);return r.useMemo(function(){return"function"==typeof t?t(e):{...e,...t}},[e,t])}function a(t){let e;return e=t.disableParentContext?"function"==typeof t.components?t.components(s):t.components||s:n(t.components),r.createElement(o.Provider,{value:e},t.children)}}}]);
Line numbers count LF bytes from the start of the resource, as the search results do. Vendor segments are library code the classifier recognised; they are stored but not indexed. Bytes are shown as Latin1 characters, one per byte.