Scribd Logo
Upload

Welcome to Scribd!

  • 100 views

    Janelle Harrison GISG114

    Uploaded by

    janellee73
    The document describes a geodatabase design created by the author for her job as an archaeologist with the National Park Service. The design was based on her practical work experience and was intended to allow different park employees to access non-sensitive archaeological and natural resource data. The geodatabase includes feature classes for points, lines and polygons with attribute domains for standardized identification codes. It was designed to make data collection in the field more efficient and consistent through drop-down menus rather than requiring typed text.

    Copyright:

    Attribution Non-Commercial (BY-NC)
    Download as PDF, TXT or read online from Scribd

    Janelle Harrison GISG114

    Uploaded by

    janellee73
    100 views3 pages
    The document describes a geodatabase design created by the author for her job as an archaeologist with the National Park Service. The design was based on her practical work experience and was intended to allow different park employees to access non-sensitive archaeological and natural resource data. The geodatabase includes feature classes for points, lines and polygons with attribute domains for standardized identification codes. It was designed to make data collection in the field more efficient and consistent through drop-down menus rather than requiring typed text.

    Copyright

    © Attribution Non-Commercial (BY-NC)

    Available Formats

    PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    The document describes a geodatabase design created by the author for her job as an archaeologist with the National Park Service. The design was based on her practical work experience and was intended to allow different park employees to access non-sensitive archaeological and natural resource data. The geodatabase includes feature classes for points, lines and polygons with attribute domains for standardized identification codes. It was designed to make data collection in the field more efficient and consistent through drop-down menus rather than requiring typed text.

    Copyright:

    Attribution Non-Commercial (BY-NC)
    Download as PDF, TXT or read online from Scribd
    Download as pdf or txt
    100 views3 pages

    Janelle Harrison GISG114

    Uploaded by

    janellee73
    The document describes a geodatabase design created by the author for her job as an archaeologist with the National Park Service. The design was based on her practical work experience and was intended to allow different park employees to access non-sensitive archaeological and natural resource data. The geodatabase includes feature classes for points, lines and polygons with attribute domains for standardized identification codes. It was designed to make data collection in the field more efficient and consistent through drop-down menus rather than requiring typed text.

    Copyright:

    Attribution Non-Commercial (BY-NC)
    Download as PDF, TXT or read online from Scribd
    Download as pdf or txt
    You are on page 1of 3

    Janelle

     Harrison  
    GISG  114  Spring  2011  
    5/20/2011  
     
    Geodatabase  Project  
     
    INTRODUCTION  
     
      My  file  geodatabase  design  is  a  based  on  practical  work  experience  as  an  
    archaeologist  for  the  National  Parks  Service.  Originally  I  was  going  to  design  a  
    geodatabase  specifically  for  historic  structures  but  that  is  not  practical  even  though  
    a  number  of  people  that  work  for  Death  Valley  National  Park  could  benefit  form  
    having  that  data  accessible  via  a  geodatabase,  but  do  not  have  “clearance”  to  all  
    sensitive  archaeological  data  so  can  not  access  this  geodatabase.  I  concluded  that  in  
    the  real  world  situation,  with  the  park  now  having  a  new  severe  up  and  running  
    ArcGIS  10,  the  most  practical  way  to  solve  this  problem  would  be  to  create  an  
    ArcSDE  so  that  all  the  data  could  be  stored  in  one  location  and  permissions  could  be  
    granted  for  different  levels  of  access.  The  hydrologist  and  the  botanist  and  the  
    archaeologist  could  all  have  levels  of  data  access  set  so  that  there  would  be  some  
    data,  non-­‐sensitive  data,  available  to  other  employees.  So  in  designing  this  project  
    geodatabase  I  kept  this  in  mind.  The  network  does  crash  a  lot  in  Death  Valley  so  I  
    know  everyone  would  want  a  file  geodatabase  to  work  in  locally  but  then  the  data  
    could  be  uploaded  daily  to  the  ArcSDE  geodatabase  running  on  the  new  server.  
     
    DESIGN  
     
    My  geodatabase  design  takes  into  account  the  fact  that  anything  we  record  in  the  
    field  can  be  recorded  as  a  point  line  or  polygon.  There  can  be  a  point  on  a  building,  a  
    line  or  a  polygon  so  each  dataset  contains  a  feature  class  for  each  geometry.  Because  
    the  National  Parks  Service  has  a  standardized  code  system  for  record  keeping  such  
    as  assigning  an  ASMIS  (archaeological  site  management  information  system)  ID  to  
    each  site,  and  assigning  a  WACC  Number  (Western  Archaeological  Conservation  
    Center)  number  or  ID  to  most  sites  and,  that  every  site  will  be  give  a  state  Primary  
    number  these  attributes  were  created  as  domains  with  a  “TEXT”  value  assigned  to  
    them.    
     
    I  created  far  more  than  the  assignment  asked  for  but  I  felt  I  needed  to  complete  or  
    nearly  complete  the  geodatabase  I  thought  would  be  most  functional  for  the  work  I  
    did  at  Death  Valley  NP.  I  nearly  completed  all  the  conceptual  domains  and  subtypes  
    that  I  wanted  to  include  accept  I  did  not  add  the  National  Register  Eligibly  coded  
    domain  and  subtype  (yet)  that  I  mentioned  in  my  Powerpoint.    With  some  time,  in  
    the  near  future,  I  will  add  this  domain  and  the  codes.      
     
    the  design  of  my  feature  datasets  are  to  give  a  person  working  I  the  field    a  quick  
    guide  to  recording  the  resources  as  per  the  state’s  requirements  without  having  to  
    type  in  text  on  each  and  every  thing  recorded.  The  drop  down  menus  create  
    consistency  and  I  know  for  a  fact  that  my  former  co-­‐workers  would  appreciate  this  
    design  greatly  as  most  of  them  hate  to  use  the  technology  because  it’s  so  time  
    consuming  and  complicated-­‐  and  it  shouldn’t  have  to  be!      
     
    CONCLUSION  
     
    It  took  me  awhile  to  synthesize  the  design  of  my  geodatabase  but  once  I  figured  it  
    out  I  was  able  to  design  a  geodatabase  that  I  feel  is  very  user  friendly  and  will  only  a  
    few  domain  modifications  here  and  there,  it’s  a  geodatabase  design  that  could  be  
    used  as  a  standardized  design  for  all  the  National  Parks  in  California.    
     
     

    You might also like