{
 "culture": "en-US",
 "name": "",
 "guid": "",
 "catalogPath": "",
 "snippet": "https://apps.deq.virginia.gov/mapper_ext/DataFactSheets/Tribal_Contacts/DEQFactSheetTribalContacts.pdf\n\nThe Tribal Contacts dataset focuses on creating and managing county boundary\ndata for integration into the Environmental Data Mapper (EDM) where Virginia\nTribes have historic interest for permit review and consultation. The FIPS codes for\nall counties and county equivalents in Virginia are listed using the VGIN 2024\nVirginia Administrative Boundaries dataset. Counties and cities are then matched\nwith each tribe\u2019s identified areas and contacts are shown accordingly.\nTribal counties are selected and used to create individual tribal layers. An\nadditional layer is created to list all counties with true/false values indicating the\npresence of each tribe, and all tribe names are concatenated into a single column\nfor easier reference. The tribal layers are incorporated into the DEQ Environmental\nData Mapper, and a lookup widget is provided, allowing users to find tribal contact\ninformation based on an address lookup. This dataset provides a comprehensive\nview of tribal boundaries and associated contact details, facilitating permittee\ncommunication with the appropriate tribal representatives.",
 "description": "<DIV STYLE=\"text-align:Left;\"><P><SPAN>https://apps.deq.virginia.gov/mapper_ext/DataFactSheets/Tribal_Contacts/DEQFactSheetTribalContacts.pdf<\/SPAN><\/P><P><SPAN /><\/P><P><SPAN /><\/P><P><SPAN>The Tribal Contacts dataset focuses on creating and managing county boundary data for integration into the Environmental Data Mapper (EDM) where Virginia Tribes have historic interest for permit review and consultation. The FIPS codes for all counties and county equivalents in Virginia are listed using the VGIN 2024 Virginia Administrative Boundaries dataset. Counties and cities are then matched with each tribe\u2019s identified areas and contacts are shown accordingly.<\/SPAN><\/P><P><SPAN /><\/P><P><SPAN>Tribal counties are selected and used to create individual tribal layers. An additional layer is created to list all counties with true/false values indicating the presence of each tribe, and all tribe names are concatenated into a single column for easier reference. The tribal layers are incorporated into the DEQ Environmental Data Mapper, and a lookup widget is provided, allowing users to find tribal contact information based on an address lookup. This dataset provides a comprehensive view of tribal boundaries and associated contact details, facilitating permittee communication with the appropriate tribal representatives.<\/SPAN><\/P><\/DIV>",
 "summary": "https://apps.deq.virginia.gov/mapper_ext/DataFactSheets/Tribal_Contacts/DEQFactSheetTribalContacts.pdf\n\nThe Tribal Contacts dataset focuses on creating and managing county boundary\ndata for integration into the Environmental Data Mapper (EDM) where Virginia\nTribes have historic interest for permit review and consultation. The FIPS codes for\nall counties and county equivalents in Virginia are listed using the VGIN 2024\nVirginia Administrative Boundaries dataset. Counties and cities are then matched\nwith each tribe\u2019s identified areas and contacts are shown accordingly.\nTribal counties are selected and used to create individual tribal layers. An\nadditional layer is created to list all counties with true/false values indicating the\npresence of each tribe, and all tribe names are concatenated into a single column\nfor easier reference. The tribal layers are incorporated into the DEQ Environmental\nData Mapper, and a lookup widget is provided, allowing users to find tribal contact\ninformation based on an address lookup. This dataset provides a comprehensive\nview of tribal boundaries and associated contact details, facilitating permittee\ncommunication with the appropriate tribal representatives.",
 "title": "MonacanNation",
 "tags": [
  "tribes",
  "DEQ"
 ],
 "type": "",
 "typeKeywords": [],
 "thumbnail": "",
 "url": "",
 "minScale": 150000000,
 "maxScale": 5000,
 "spatialReference": "",
 "accessInformation": "",
 "licenseInfo": "",
 "portalUrl": ""
}