Your SlideShare is downloading. ×
0
Making data storage more efficient
Making data storage more efficient
Making data storage more efficient
Making data storage more efficient
Making data storage more efficient
Making data storage more efficient
Making data storage more efficient
Making data storage more efficient
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Making data storage more efficient

121

Published on

Notes for the Advanced GIS class in the Advanced Geographic Sciences Program at COGS

Notes for the Advanced GIS class in the Advanced Geographic Sciences Program at COGS

Published in: Education, Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
121
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
0
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. Making GDB-Domiciled Data More Efficient Using Coded-Value Domains In Lieu Of Look-Up Tables (COGS – AdvGeos – Advanced GIS)
  • 2. Replace Verbosity with Efficiency • This example takes the 44 889 rows of European Railroad lines with two 40- character-wide fields, and replaces them with two 1-character-wide fields that each have coded-value domains • Disk space required for storage: – Initially: 7 Mb – Finally: 5.7 Mb
  • 3. Initial Data Contents
  • 4. Final Data Contents
  • 5. Properties > Fields:
  • 6. Geodatabase Properties > Domains
  • 7. ModelBuilder Trick • To calculate one field based on the first N characters of another, use !field![N-1]
  • 8. Sources • Data (European Railroads) from Esri • Images from ArcGIS (ArcCatalog) • Results are stored on the COGS SDE SQL Server nscccods2 instance

×