Upload
others
View
7
Download
0
Embed Size (px)
Citation preview
UC 2006 Tech SessionUC 2006 Tech Session11
Designing GIS Databases to Designing GIS Databases to Support Mapping and Map Support Mapping and Map
ProductionProductionCharlie Frye, ESRI RedlandsCharlie Frye, ESRI Redlands
Aileen Buckley, ESRI RedlandsAileen Buckley, ESRI Redlands
UC 2006 Tech SessionUC 2006 Tech Session22
Designing GIS Databases to Designing GIS Databases to Support Mapping and Map Support Mapping and Map
Production Production Charlie Frye, ESRI RedlandsCharlie Frye, ESRI Redlands
Aileen Buckley, ESRI RedlandsAileen Buckley, ESRI Redlands
UC 2006 Tech SessionUC 2006 Tech Session33
Key ConceptsKey Concepts
•• GIS base maps that support highGIS base maps that support high--quality cartographyquality cartography–– MapMap--drivendriven–– Spatially integratedSpatially integrated
•• Understanding mapsUnderstanding maps–– ThemesThemes–– Graphic marks Graphic marks
•• The multiThe multi--purpose GIS base map and cartographypurpose GIS base map and cartography–– Basic structure and schemaBasic structure and schema–– Table design (supporting symbology & labeling)Table design (supporting symbology & labeling)–– Geoprocessing (supporting symbology & labeling)Geoprocessing (supporting symbology & labeling)
•• MultiMulti--scalescale–– Incorporating scale in the base map database Incorporating scale in the base map database –– MultiMulti--scale mapscale map
UC 2006 Tech SessionUC 2006 Tech Session44
MapMap--Driven Driven
•• 1: 5,000 General 1: 5,000 General reference mapreference map
•• 1: 25,000 1: 25,000 Topographic mapTopographic map
•• 1: 2,500 Emergency 1: 2,500 Emergency services access mapservices access map
•• 1:1,250 Emergency 1:1,250 Emergency services imagery services imagery mapmap
UC 2006 Tech SessionUC 2006 Tech Session55
Organize Base Map Content Using ThemesOrganize Base Map Content Using Themes
•• Each map portrays or contains major themes of informationEach map portrays or contains major themes of information
Imagery Hypsography Hydrography Cultural AdministrImagery Hypsography Hydrography Cultural Administrative Transportative Transport
•• The base map data base, The base map data base, therefore, will have data therefore, will have data organized into major themesorganized into major themes
•• Topological relationships are Topological relationships are typically between feature typically between feature classes within themes in the classes within themes in the base mapbase map
UC 2006 Tech SessionUC 2006 Tech Session66
Organize Base Map Content Using ThemesOrganize Base Map Content Using Themes
•• Common themes:Common themes:–– TransportationTransportation–– Terrain or hypsographyTerrain or hypsography–– Surface water or hydrographySurface water or hydrography–– CulturalCultural–– ImageryImagery–– BoundariesBoundaries–– Reference systemReference system
•• RoadsRoads•• Edge of pavement Edge of pavement
polygonspolygons•• Center linesCenter lines•• CulCul de sac pointsde sac points•• Dissolved road Dissolved road
CenterlinesCenterlines•• RailroadsRailroads
•• Individual tracksIndividual tracks•• Rail linesRail lines
•• Ferry routesFerry routes
UC 2006 Tech SessionUC 2006 Tech Session77
Organize Base Map Content Using ThemesOrganize Base Map Content Using Themes
•• Common themes:Common themes:–– TransportationTransportation–– Terrain or hypsographyTerrain or hypsography–– Surface water or hydrographySurface water or hydrography–– CulturalCultural–– ImageryImagery–– BoundariesBoundaries–– Reference systemReference system
•• Digital elevation model (DEM)Digital elevation model (DEM)•• Cartographic Cartographic hillshadehillshade•• Contour linesContour lines
•• Spot elevation pointsSpot elevation points
UC 2006 Tech SessionUC 2006 Tech Session88
Organize Base Map Content Using ThemesOrganize Base Map Content Using Themes
•• Common themes:Common themes:–– TransportationTransportation–– Terrain or hypsographyTerrain or hypsography–– Surface water or hydrographySurface water or hydrography–– CulturalCultural–– ImageryImagery–– BoundariesBoundaries–– Reference systemReference system
•• Hydro areasHydro areas•• All types of surface waterAll types of surface water
•• Hydro linesHydro lines•• Includes steam channelsIncludes steam channels
•• ShorelinesShorelines•• Hydro pointsHydro points
•• WellsWells•• SpringsSprings•• GagingGaging stationsstations•• etc.etc.
UC 2006 Tech SessionUC 2006 Tech Session99
Organize Base Map Content Using ThemesOrganize Base Map Content Using Themes
•• Common themes:Common themes:–– TransportationTransportation–– Terrain or hypsographyTerrain or hypsography–– Surface water or hydrographySurface water or hydrography–– CulturalCultural–– ImageryImagery–– BoundariesBoundaries–– Reference systemReference system
•• BuildingsBuildings•• Building complexesBuilding complexes•• LandmarksLandmarks•• StructuresStructures•• etc.etc.
UC 2006 Tech SessionUC 2006 Tech Session1010
Organize Base Map Content Using ThemesOrganize Base Map Content Using Themes
•• Common themes:Common themes:–– TransportationTransportation–– Terrain or hypsographyTerrain or hypsography–– Surface water or hydrographySurface water or hydrography–– CulturalCultural–– ImageryImagery–– BoundariesBoundaries–– Reference systemReference system
•• OrthophotoOrthophoto basebase•• Aerial photosAerial photos•• Satellite imagerySatellite imagery•• etc.etc.
UC 2006 Tech SessionUC 2006 Tech Session1111
Organize Base Map Content Using ThemesOrganize Base Map Content Using Themes
•• Common themes:Common themes:–– TransportationTransportation–– Terrain or hypsographyTerrain or hypsography–– Surface water or hydrographySurface water or hydrography–– CulturalCultural–– ImageryImagery–– BoundariesBoundaries–– Reference systemReference system
•• MunicipalMunicipal•• Areas & linesAreas & lines
•• CountyCounty•• Areas & linesAreas & lines
•• StateState•• Areas & linesAreas & lines
•• ParkPark•• Areas & linesAreas & lines
•• PLSS & controlPLSS & control•• Areas & linesAreas & lines•• Points/cornersPoints/corners
•• SubdivisionsSubdivisions•• Areas & linesAreas & lines
•• ParcelsParcels•• Parcel data modelParcel data model
UC 2006 Tech SessionUC 2006 Tech Session1212
Organize Base Map Content Using ThemesOrganize Base Map Content Using Themes
•• Common themes:Common themes:–– TransportationTransportation–– Terrain or hypsographyTerrain or hypsography–– Surface water or hydrographySurface water or hydrography–– CulturalCultural–– ImageryImagery–– BoundariesBoundaries–– Reference systemReference system
•• Map series sheet centers or Map series sheet centers or extentsextents
•• Historic map seriesHistoric map series•• USGS Quad SheetsUSGS Quad Sheets•• TownshipsTownships
•• GridsGrids•• UTMUTM•• MGRSMGRS•• GraticuleGraticule•• etc.etc.
UC 2006 Tech SessionUC 2006 Tech Session1313
Hallmarks of a Multi Purpose GIS Hallmarks of a Multi Purpose GIS Base Map that Supports MappingBase Map that Supports Mapping
1.1. Rich appropriate content for all designed Rich appropriate content for all designed standard productsstandard products
2.2. All data are spatially integratedAll data are spatially integrated
3.3. Data are modeled to suit purpose Data are modeled to suit purpose
4.4. Consistent semantics and attributionConsistent semantics and attribution
5.5. Central repository for managing frequently Central repository for managing frequently shared or sensitive informationshared or sensitive information
UC 2006 Tech SessionUC 2006 Tech Session1414
Spatially Integrated Data ExampleSpatially Integrated Data Example
UC 2006 Tech SessionUC 2006 Tech Session1515
Hallmarks of a Multi Purpose GIS Hallmarks of a Multi Purpose GIS Base Map that Supports MappingBase Map that Supports Mapping
1.1. Rich appropriate content for all designed Rich appropriate content for all designed standard productsstandard products
2.2. All data are spatially integratedAll data are spatially integrated
3.3. Data are modeled to suit purposeData are modeled to suit purpose
4.4. Consistent semantics and attributionConsistent semantics and attribution
5.5. Central repository for managing frequently Central repository for managing frequently shared or sensitive informationshared or sensitive information
UC 2006 Tech SessionUC 2006 Tech Session1616
Consistent use of semanticsConsistent use of semantics
•• Organize data using consistent and easy to Organize data using consistent and easy to understand conventionsunderstand conventions
•• Use geodatabase domains to enforce consistent Use geodatabase domains to enforce consistent use appearance of informationuse appearance of information
•• Expose information based on the expectations of Expose information based on the expectations of your clientsyour clients
UC 2006 Tech SessionUC 2006 Tech Session1717
Using Consistent SemanticsUsing Consistent SemanticsCS_IDCS_IDis my is my symbolsymbolfieldfield
DomainsDomainson theon theFeat_TypeFeat_TypeandandCS_IDCS_IDfieldsfieldsenforceenforcesemanticssemantics
UC 2006 Tech SessionUC 2006 Tech Session1818
Hallmarks of a Multi Purpose GIS Hallmarks of a Multi Purpose GIS Base Map that Supports MappingBase Map that Supports Mapping
1.1. Rich appropriate content for all designed Rich appropriate content for all designed standard productsstandard products
2.2. All data are spatially integratedAll data are spatially integrated
3.3. Data are modeled to suit purpose Data are modeled to suit purpose
4.4. Consistent semantics and attributionConsistent semantics and attribution
5.5. Central repository for managing frequently Central repository for managing frequently shared or sensitive informationshared or sensitive information
UC 2006 Tech SessionUC 2006 Tech Session1919
Data Flow during Map Production Data Flow during Map Production WorkflowWorkflow
•• Data is Extracted, Data is Extracted, Transferred, and Loaded Transferred, and Loaded (ETL) from core database (ETL) from core database into map product into map product databasesdatabases
•• During production, errors During production, errors and edits are propagated and edits are propagated back to the core back to the core databasedatabase
Core
Product X
Product Y
Product Z
UC 2006 Tech SessionUC 2006 Tech Session2020
Base Map Design in Support of Base Map Design in Support of MappingMapping•• If it is not in the database, it wonIf it is not in the database, it won’’t be t be on the mapon the map
•• Data are based on and designed with full Data are based on and designed with full understanding of your standard map understanding of your standard map productsproducts
•• Without a map specification it wonWithout a map specification it won’’t be in t be in the database (or prethe database (or pre--existing analog)existing analog)
UC 2006 Tech SessionUC 2006 Tech Session2121
Example: PreExample: Pre--Existing Analog MapExisting Analog Map
•• Existing Public Safety MapExisting Public Safety Map
UC 2006 Tech SessionUC 2006 Tech Session2222
Example: Resulting MapExample: Resulting Map
•• New Design (proposed)New Design (proposed)
UC 2006 Tech SessionUC 2006 Tech Session2323
Map Specification ContentsMap Specification Contents
•• Map purpose and audienceMap purpose and audience•• Inventory of each kind of graphic markInventory of each kind of graphic mark
–– Each unique symbol and label and the Each unique symbol and label and the features they will apply tofeatures they will apply to
–– How the graphic mark gets assignedHow the graphic mark gets assigned•• ArcMap symbology method and parametersArcMap symbology method and parameters•• MaplexMaplex label placement rule and parameterslabel placement rule and parameters
–– Interrelations among graphic marksInterrelations among graphic marks•• Page layout or user interface designPage layout or user interface design
UC 2006 Tech SessionUC 2006 Tech Session2424
Graphic MarksGraphic Marks
•• “…“…primitive building blocks of pictorial primitive building blocks of pictorial representation.representation.””**–– Point markPoint mark–– Line markLine mark–– Area markArea mark–– Text labelText label–– PixelPixel–– TIN facetTIN facet
* Robinson, * Robinson, et.alet.al., ., Elements of Cartography, 6Elements of Cartography, 6thth Ed, p 318.Ed, p 318.
UC 2006 Tech SessionUC 2006 Tech Session2525
Graphic Marks Drive Detailed Data DesignGraphic Marks Drive Detailed Data Design
•• SubdivisionSubdivision–– BoundaryBoundary–– NameName
•• BuildingBuilding–– ResidentialResidential–– General caseGeneral case–– CommercialCommercial
•• RoadRoad–– EdgeEdge–– NameName–– AddressAddress
•• VegetationVegetation–– TreesTrees
•• CulturalCultural–– Recreation areaRecreation area
•• Section lineSection line
UC 2006 Tech SessionUC 2006 Tech Session2626
Graphic Marks Drive Detailed Data DesignGraphic Marks Drive Detailed Data Design
•• SubdivisionSubdivision–– BoundaryBoundary–– NameName
•• BuildingBuilding–– ResidentialResidential–– General caseGeneral case–– CommercialCommercial
•• RoadRoad–– EdgeEdge–– NameName–– AddressAddress
•• VegetationVegetation–– TreesTrees
•• CulturalCultural–– Recreation areaRecreation area
•• Section lineSection line
UC 2006 Tech SessionUC 2006 Tech Session2727
Graphic Marks Drive Detailed Data DesignGraphic Marks Drive Detailed Data Design
•• SubdivisionSubdivision–– BoundaryBoundary–– NameName
•• BuildingBuilding–– ResidentialResidential–– General caseGeneral case–– CommercialCommercial
•• RoadRoad–– EdgeEdge–– AddressAddress–– NameName
•• VegetationVegetation–– TreesTrees
•• CulturalCultural–– Recreation areaRecreation area
•• Section lineSection line
UC 2006 Tech SessionUC 2006 Tech Session2828
Graphic Marks Drive Detailed Data DesignGraphic Marks Drive Detailed Data Design
•• SubdivisionSubdivision–– BoundaryBoundary–– NameName
•• BuildingBuilding–– ResidentialResidential–– General caseGeneral case–– CommercialCommercial
•• RoadRoad–– EdgeEdge–– NameName–– AddressAddress
•• VegetationVegetation–– TreesTrees
•• CulturalCultural–– Recreation areaRecreation area
•• Section lineSection line
UC 2006 Tech SessionUC 2006 Tech Session2929
Graphic Marks Drive Detailed Data DesignGraphic Marks Drive Detailed Data Design
•• SubdivisionSubdivision–– BoundaryBoundary–– NameName
•• BuildingBuilding–– ResidentialResidential–– General caseGeneral case–– CommercialCommercial
•• RoadRoad–– EdgeEdge–– NameName–– AddressAddress
•• VegetationVegetation–– TreesTrees
•• CulturalCultural–– Recreation areaRecreation area
•• Section lineSection line
UC 2006 Tech SessionUC 2006 Tech Session3030
Graphic Marks Drive Detailed Data DesignGraphic Marks Drive Detailed Data Design
•• SubdivisionSubdivision–– BoundaryBoundary–– NameName
•• BuildingBuilding–– ResidentialResidential–– General caseGeneral case–– CommercialCommercial
•• RoadRoad–– EdgeEdge–– NameName–– AddressAddress
•• VegetationVegetation–– TreesTrees
•• CulturalCultural–– Recreation areaRecreation area
•• Section lineSection line
UC 2006 Tech SessionUC 2006 Tech Session3131
Map Specification ContentsMap Specification Contents
•• Map purpose and audienceMap purpose and audience•• Inventory of each kind of graphic markInventory of each kind of graphic mark
–– Each unique symbol and label and the Each unique symbol and label and the features they will apply tofeatures they will apply to
–– How the graphic mark gets assignedHow the graphic mark gets assigned•• ArcMap symbology method and parametersArcMap symbology method and parameters•• MaplexMaplex label placement rule and parameterslabel placement rule and parameters
–– Interrelations among graphic marksInterrelations among graphic marks•• Page layout or user interface designPage layout or user interface design
UC 2006 Tech SessionUC 2006 Tech Session3232
Table Design of Databases that Table Design of Databases that Support MappingSupport Mapping
•• SymbolizationSymbolization–– A single field that tells ArcMap the symbol for A single field that tells ArcMap the symbol for
each featureeach feature•• Keeps symbology process simpleKeeps symbology process simple•• Permits use of Permits use of ““Match to Symbols in a StyleMatch to Symbols in a Style””
–– In some cases another field, denoting priority, In some cases another field, denoting priority, may be used, for example, to set the size of may be used, for example, to set the size of symbolssymbols
UC 2006 Tech SessionUC 2006 Tech Session3333
Match to Symbols in a StyleMatch to Symbols in a Style
UC 2006 Tech SessionUC 2006 Tech Session3434
Table Design of Databases that Table Design of Databases that Support MappingSupport Mapping
•• SymbolizationSymbolization–– A single field that tells ArcMap the symbol for A single field that tells ArcMap the symbol for
each featureeach feature•• Keeps symbology process simpleKeeps symbology process simple•• Permits use of Permits use of ““Match to Symbols in a StyleMatch to Symbols in a Style””
–– In some cases another field, denoting priority, In some cases another field, denoting priority, may be used, for example, to set the size of may be used, for example, to set the size of symbolssymbols
UC 2006 Tech SessionUC 2006 Tech Session3535
Table Design of MultiTable Design of Multi--Purpose Purpose Databases that Support MappingDatabases that Support Mapping
•• Text PlacementText Placement–– Useful fields to add have:Useful fields to add have:
•• Label StringLabel String: Pre: Pre--calculated to avoid performancecalculated to avoid performance--detracting detracting label expressionslabel expressions
•• Shape TypeShape Type: For polygon features to help : For polygon features to help MaplexMaplex differentiate differentiate between curved and horizontal placementbetween curved and horizontal placement
•• Label LengthLabel Length: Help : Help MaplexMaplex: set up for overrun or place outside : set up for overrun or place outside options (really useful when annotation is not an option): options (really useful when annotation is not an option): Len([<field>])Len([<field>])
–– Use on short streets (spurs) or small polygons (lakes, cultural Use on short streets (spurs) or small polygons (lakes, cultural areas, etc.)areas, etc.)
•• Label TypeLabel Type: For example, restricted access highways need to : For example, restricted access highways need to know type of shieldknow type of shield
UC 2006 Tech SessionUC 2006 Tech Session3636
Scale and Information Themes on MapsScale and Information Themes on Maps
•• Different kinds of features behave Different kinds of features behave differently as scale changesdifferently as scale changes–– Goal: represent features as geographic, not Goal: represent features as geographic, not
geometric geometric (when you can see the vertices)(when you can see the vertices)
–– Some data will be used in multiple products Some data will be used in multiple products and at a wider range of scalesand at a wider range of scales
MapMapInformationInformation
ThemeThemeRoadsRoads
1:1,000 Map Scale 1:1,000 Map Scale 1:10,000,0001:10,000,000
BoundariesBoundaries
HydrographyHydrography
UC 2006 Tech SessionUC 2006 Tech Session3737
Making Sense of MultiMaking Sense of Multi--ScaleScale
•• MultiMulti--Scale vs. Scale Range: Scale vs. Scale Range: –– MultiMulti--scale is multiple predefined scales or Zscale is multiple predefined scales or Z--heights heights
(i.e., discreet)(i.e., discreet)–– Scale range is all scales between a defined minimum Scale range is all scales between a defined minimum
and maximum scale or Zand maximum scale or Z--height (i.e., continuous)height (i.e., continuous)
•• ESRIESRI’’ss products and functionality are multiproducts and functionality are multi--scalescale–– Design your data to so that scale is managed or Design your data to so that scale is managed or
assigned as a characteristic of a feature classassigned as a characteristic of a feature class•• As a highly tuned/optimized singleAs a highly tuned/optimized single--scale datasetscale dataset•• As a highly tuned/optimized dataset for use within a range of As a highly tuned/optimized dataset for use within a range of
scalesscales
UC 2006 Tech SessionUC 2006 Tech Session3838
MultiMulti--Scale Map DesignScale Map Design
•• A multiA multi--scale map is an ordered sequence of scale map is an ordered sequence of singlesingle--scale mapsscale maps–– Each singleEach single--scale map mustscale map must
•• Stand on its own (store as a group layer)Stand on its own (store as a group layer)•• Have a consistent density of informationHave a consistent density of information
–– Avoid changing convention or style between mapsAvoid changing convention or style between maps•• If possible keep important features stable (not moving around)If possible keep important features stable (not moving around)•• MaplexMaplex: use same font and placement strategies at each scale: use same font and placement strategies at each scale•• Use same colors, particularly for area fill symbols and textUse same colors, particularly for area fill symbols and text
•• There are scales when the themes of information There are scales when the themes of information on the map will change to accommodate more on the map will change to accommodate more detailed informationdetailed information–– EvolveEvolve cartographic strategies at these pointscartographic strategies at these points
UC 2006 Tech SessionUC 2006 Tech Session3939
MultiMulti--Scale Example 1Scale Example 1
UC 2006 Tech SessionUC 2006 Tech Session4040
MultiMulti--Scale Example 1Scale Example 1
UC 2006 Tech SessionUC 2006 Tech Session4141
MultiMulti--Scale Example 1Scale Example 1
UC 2006 Tech SessionUC 2006 Tech Session4242
MultiMulti--Scale Example 1Scale Example 1
UC 2006 Tech SessionUC 2006 Tech Session4343
MultiMulti--Scale Example 1Scale Example 1
UC 2006 Tech SessionUC 2006 Tech Session4444
Annotation for StabilityAnnotation for Stability
UC 2006 Tech SessionUC 2006 Tech Session4545
Annotation for StabilityAnnotation for Stability
UC 2006 Tech SessionUC 2006 Tech Session4646
Annotation for StabilityAnnotation for Stability
UC 2006 Tech SessionUC 2006 Tech Session4747
Annotation for StabilityAnnotation for Stability
UC 2006 Tech SessionUC 2006 Tech Session4848
Annotation for StabilityAnnotation for Stability
UC 2006 Tech SessionUC 2006 Tech Session4949
Annotation for StabilityAnnotation for Stability
UC 2006 Tech SessionUC 2006 Tech Session5050
Annotation for StabilityAnnotation for Stability
UC 2006 Tech SessionUC 2006 Tech Session5151
Annotation for StabilityAnnotation for Stability
UC 2006 Tech SessionUC 2006 Tech Session5252
Annotation for StabilityAnnotation for Stability
UC 2006 Tech SessionUC 2006 Tech Session5353
Annotation for StabilityAnnotation for Stability
UC 2006 Tech SessionUC 2006 Tech Session5454
Annotation for StabilityAnnotation for Stability
UC 2006 Tech SessionUC 2006 Tech Session5555
Annotation for StabilityAnnotation for Stability
UC 2006 Tech SessionUC 2006 Tech Session5656
Labeling: Not as StableLabeling: Not as Stable
UC 2006 Tech SessionUC 2006 Tech Session5757
Labeling: Not as StableLabeling: Not as Stable
UC 2006 Tech SessionUC 2006 Tech Session5858
Labeling: Not as StableLabeling: Not as Stable
UC 2006 Tech SessionUC 2006 Tech Session5959
Labeling: Not as StableLabeling: Not as Stable
UC 2006 Tech SessionUC 2006 Tech Session6060
Labeling: Not as StableLabeling: Not as Stable
UC 2006 Tech SessionUC 2006 Tech Session6161
Labeling: Not as StableLabeling: Not as Stable
UC 2006 Tech SessionUC 2006 Tech Session6262
Scale StrategyScale Strategy•• Binary works for more Binary works for more
focused maps that will not focused maps that will not function well if too much function well if too much information is shown; good information is shown; good for thematic or special for thematic or special purpose mapspurpose maps
•• Content driven adds Content driven adds information at earliest information at earliest natural opportunity, and is natural opportunity, and is susceptible to more susceptible to more traditional cartographic traditional cartographic challenges; good for challenges; good for reference or topographic reference or topographic mapsmaps
1:1,0001:1,0001:2,0001:2,0001:4,0001:4,0001:8,0001:8,000
1:16,0001:16,0001:32,0001:32,0001:64,0001:64,000
1:125,0001:125,0001:250,0001:250,0001:500,0001:500,000
1:1,000,0001:1,000,0001:2,000,0001:2,000,0001:4,000,0001:4,000,0001:8,000,0001:8,000,000
1:16,000,0001:16,000,0001:32,000,0001:32,000,0001:64,000,0001:64,000,000
•• Natural or Natural or Content DrivenContent Driven
1:1,0001:1,0001:2,5001:2,5001:5,0001:5,0001:7,5001:7,500
1:10,0001:10,0001:15,0001:15,0001:20,0001:20,0001:25,0001:25,0001:30,0001:30,0001:40,0001:40,0001:50,0001:50,0001:75,0001:75,000
1:100,0001:100,0001:175,0001:175,0001:250,0001:250,0001:325,0001:325,0001:400,0001:400,0001:500,0001:500,0001:750,0001:750,000
1:1,000,0001:1,000,000
150015002500250025002500250025005000500050005000500050005000500050005000
1000010000100001000025,00025,00025,00025,00075,00075,00075,00075,00075,00075,000
100,000100,000250,000250,000250,000250,000
•• Binary Binary ProgressionProgression
UC 2006 Tech SessionUC 2006 Tech Session6363
Thank youThank you
•• QuestionsQuestions
•• Please fill out your surveysPlease fill out your surveys——we appreciate we appreciate your feedback.your feedback.