Statewide 2016 Lidar points colorized with 2018 NAIP imagery as a scene created by Esri using ArcGIS Pro for the entire State of Connecticut. This service provides the colorized Lidar point in interactive 3D for visualization, interaction of the ability to make measurements without downloading.Lidar is referenced at https://cteco.uconn.edu/data/lidar/ and can be downloaded at https://cteco.uconn.edu/data/download/flight2016/. Metadata: https://cteco.uconn.edu/data/flight2016/info.htm#metadata. The Connecticut 2016 Lidar was captured between March 11, 2016 and April 16, 2016. Is covers 5,240 sq miles and is divided into 23, 381 tiles. It was acquired by the Captiol Region Council of Governments with funding from multiple state agencies. It was flown and processed by Sanborn. The delivery included classified point clouds and 1 meter QL2 DEMs. The 2016 Lidar is published on the Connecticut Environmental Conditions Online (CT ECO) website. CT ECO is the collaborative work of the Connecticut Department of Energy and Environmental Protection (DEEP) and the University of Connecticut Center for Land Use Education and Research (CLEAR) to share environmental and natural resource information with the general public. CT ECO's mission is to encourage, support, and promote informed land use and development decisions in Connecticut by providing local, state and federal agencies, and the public with convenient access to the most up-to-date and complete natural resource information available statewide.Process used:Extract Building Footprints from Lidar1. Prepare Lidar - Download 2016 Lidar from CT ECO- Create LAS Dataset2. Extract Building Footprints from LidarUse the LAS Dataset in the Classify Las Building Tool in ArcGIS Pro 2.4.Colorize LidarColorizing the Lidar points means that each point in the point cloud is given a color based on the imagery color value at that exact location.1. Prepare Imagery- Acquire 2018 NAIP tif tiles from UConn (originally from USDA NRCS).- Create mosaic dataset of the NAIP imagery.2. Prepare and Analyze Lidar Points- Change the coordinate system of each of the lidar tiles to the Projected Coordinate System CT NAD 83 (2011) Feet (EPSG 6434). This is because the downloaded tiles come in to ArcGIS as a Custom Projection which cannot be published as a Point Cloud Scene Layer Package.- Convert Lidar to zlas format and rearrange. - Create LAS Datasets of the lidar tiles.- Colorize Lidar using the Colorize LAS tool in ArcGIS Pro. - Create a new LAS dataset with a division of Eastern half and Western half due to size limitation of 500GB per scene layer package. - Create scene layer packages (.slpk) using Create Cloud Point Scene Layer Package. - Load package to ArcGIS Online using Share Package. - Publish on ArcGIS.com and delete the scene layer package to save storage cost.Additional layers added:Visit https://cteco.uconn.edu/projects/lidar3D/layers.htm for a complete list and links. 3D Buildings and Trees extracted by Esri from the lidarShaded Relief from CTECOImpervious Surface 2012 from CT ECONAIP Imagery 2018 from CTECOContours (2016) from CTECOLidar 2016 Download Link derived from https://www.cteco.uconn.edu/data/download/flight2016/index.htm

Important Note: This item is in mature support as of December 2024. See blog for more information.This 3D scene layer presents OpenStreetMap (OSM) buildings data hosted by Esri. Esri created buildings and trees scene layers from the OSM Daylight map distribution, which is supported by Facebook and others. The Daylight map distribution has been sunsetted and data updates supporting this layer are no longer available. You can visit openstreetmap.maps.arcgis.com to explore a collection of maps, scenes, and layers featuring OpenStreetMap data in ArcGIS. You can review the 3D Scene Layers Documentation to learn more about how the building and tree features in OSM are modeled and rendered in the 3D scene layers, and see tagging recommendations to get the best results.OpenStreetMap is an open collaborative project to create a free editable map of the world. Volunteers gather location data using GPS, local knowledge, and other free sources of information and upload it. The resulting free map can be viewed and downloaded from the OpenStreetMap site: www.OpenStreetMap.org. Esri is a supporter of the OSM project.Note: This layer is supported in Scene Viewer and ArcGIS Pro 3.0 or higher.

See the NZ Elevation Layer for more information on the NZ Elevation layerThe NZ Elevation - Metadata layer provides information about the data used for the NZ Elevation layer. You can identify what areas use 1m or 2m DEM's derived from LiDAR and what areas use the 8m DEM provided by LINZ. You can also find information, whenever available, about capture dates, point cloud density and links to the layer's in the LINZ Data Service.The NZ Elevation layer is an elevation surface for use in 3D applications in the NZTM projection. By adding this layer to a Scene in ArcGIS Pro or in the Scene Viewer it will be define the base height in your application.NZTM Basemaps can be used on top of this service, providing it shares the same tiling scheme. When combining it with the NZ Basemaps provided by Eagle Technolgy, make sure to use the raster basemaps with the updated tiling scheme or one of the vector basemaps. All the compatible basemaps can be found in this group. When creating your own basemap or tiled layer make sure to use the tiling scheme provided here.The elevation service is made up of the available publicly-owned 1m and 2m dems. For areas where 1m/2m elevation data is not available the 8m dem provided by LINZ is being used. Outside of the coverage of the 8m dem, a 0m dem is used for visual purposes.This service is offered by Eagle Technology (Official Esri Distributor). Eagle Technology offers layers and maps that can be used in the ArcGIS platform. The Content team at Eagle Technology updates the layers on a regular basis and regularly adds new content to the Living Atlas. By using this content and combining it with other data you can create new information products quickly and easily.If you have any questions or remarks about the content, please let us now at livingatlas@eagle.co.nz

The arrival of ArcGIS Pro has brought a challenge to ArcMap users. The new software is sufficiently different in architecture and layout that switching from the old to the new is not a simple process. In some ways, Pro is harder to learn for ArcMap users than for new GIS users, because some workflows have to be unlearned, or at least heavily modified. Current ArcMap users are pressed for time, trying to learn the new software while still completing their daily tasks, so a book that teaches Pro from the start is not an efficient method.Switching to ArcGIS Pro from ArcMap aims to quickly transition ArcMap users to ArcGIS Pro. Rather than teaching Pro from the start, as for a novice user, this book focuses on how Pro is different from ArcMap. Covering the most common and important workflows required for most GIS work, it leverages the user’s prior experience to enable a more rapid adjustment to Pro.AUDIENCEProfessional and scholarly; College/higher education; General/trade.AUTHOR BIOMaribeth H. Price, PhD, South Dakota School of Mines and Technology, has been using Esri products since 1991, teaching college GIS since 1995 and writing textbooks utilizing Esri’s software since 2001. She has extensive familiarity with both ArcMap/ArcCatalog and Pro, both as a user and in the classroom, as well as long experience writing about GIS concepts and developing software tutorials. She teaches GIS workshops, having offered more than 100 workshops to over 1,200 participants since 2000.Pub Date: Print: 2/14/2019 Digital: 1/28/2019 Format: PaperbackISBN: Print: 9781589485440 Digital: 9781589485457 Trim: 8 x 10 in.Price: Print: $49.99 USD Digital: $49.99 USD Pages: 172Table of ContentsPreface1 Contemplating the switch to ArcGIS ProBackgroundSystem requirementsLicensingCapabilities of ArcGIS ProWhen should I switch?Time to exploreObjective 1.1: Downloading the data for these exercisesObjective 1.2: Starting ArcGIS Pro, signing in, creating a project, and exploring the interfaceObjective 1.3: Accessing maps and data from ArcGIS OnlineObjective 1.4: Arranging the windows and panesObjective 1.5: Accessing the helpObjective 1.6: Importing a map document2 Unpacking the GUIBackgroundThe ribbon and tabsPanesViewsTime to exploreObjective 2.1: Getting familiar with the Contents paneObjective 2.2: Learning to work with objects and tabsObjective 2.3: Exploring the Catalog pane3 The projectBackgroundWhat is a project?Items stored in a projectPaths in projectsRenaming projectsTime to exploreObjective 3.1: Exploring different elements of a projectObjective 3.2: Accessing properties of projects, maps, and other items4 Navigating and exploring mapsBackgroundExploring maps2D and 3D navigationTime to exploreObjective 4.1: Learning to use the Map toolsObjective 4.2: Exploring 3D scenes and linking views5 Symbolizing mapsBackgroundAccessing the symbol settings for layersAccessing the labeling propertiesSymbolizing rastersTime to exploreObjective 5.1: Modifying single symbolsObjective 5.2: Creating maps from attributesObjective 5.3: Creating labelsObjective 5.4: Managing labelsObjective 5.5: Symbolizing rasters6 GeoprocessingBackgroundWhat’s differentAnalysis buttons and toolsTool licensingTime to exploreObjective 6.1: Getting familiar with the geoprocessing interfaceObjective 6.2: Performing interactive selectionsObjective 6.3: Performing selections based on attributesObjective 6.4: Performing selections based on locationObjective 6.5: Practicing geoprocessing7 TablesBackgroundGeneral table characteristicsJoining and relating tablesMaking chartsTime to exploreObjective 7.1: Managing table viewsObjective 7.2: Creating and managing properties of a chartObjective 7.3: Calculating statistics for tablesObjective 7.4: Calculating and editing in tables8 LayoutsBackgroundLayouts and map framesLayout editing proceduresImporting map documents and templatesTime to exploreObjective 8.1: Creating the maps for the layoutObjective 8.2: Setting up a layout page with map framesObjective 8.3: Setting map frame extent and scaleObjective 8.4: Formatting the map frameObjective 8.5: Creating and formatting map elementsObjective 8.6: Fine-tuning the legendObjective 8.7: Accessing and copying layouts9 Managing dataBackgroundData modelsManaging the geodatabase schemaCreating domainsManaging data from diverse sourcesProject longevityManaging shared data for work groupsTime to exploreObjective 9.1: Creating a project and exporting data to itObjective 9.2: Creating feature classesObjective 9.3: Creating and managing metadataObjective 9.4: Creating fields and domainsObjective 9.5: Modifying the table schemaObjective 9.6: Sharing data using ArcGIS Online10 EditingBackgroundBasic editing functionsCreating featuresModifying existing featuresCreating and editing annotationTime to exploreObjective 10.1: Understanding the editing tools in ArcGIS ProObjective 10.2: Creating pointsObjective 10.3: Creating linesObjective 10.4: Creating polygonsObjective 10.5: Modifying existing featuresObjective 10.6: Creating an annotation feature classObjective 10.7: Editing annotationObjective 10.8: Creating annotation features11 Moving forwardData sourcesIndex

This deep learning model is used for extracting windows and doors in textured building data displayed in 3D views. Manually digitizing windows/doors from 3D building data can be a slow process. This model automates the extraction of these objects from a 3D view and can help in speeding up 3D editing and analysis workflows. Using this model, existing building data can be enhanced with additional information on location, size and orientation of windows and doors. The extracted windows and doors can be further used to perform 3D visibility analysis using existing 3D geoprocessing tools in ArcGIS.This model can be useful in many industries and workflows. National Government and state-level law enforcement could use this model in security analysis scenarios. Local governments could use windows and door locations to help with tax assessments with CAMA (computer aided mass appraisal) plus impact-studies for urban planning. Public safety users might be interested in regards to physical or visual access to restricted areas, or the ability to build evacuation plans. The commercial sector, with everyone from real-estate agents to advertisers to office/interior designers, would be able to benefit from knowing where windows and doors are located. Even utilities, especially mobile phone providers, could take advantage of knowing window sizes and positions. To be clear, this model doesn't solve these problems, but it does allow users to extract and collate some of the data they will need to do it.Using the modelThis model is generic and is expected to work well with a variety of building styles and shapes. To use this model, you need to install supported deep learning frameworks packages first. See Install deep learning frameworks for ArcGIS for more information. The model can be used with the Interactive Object Detection tool.A blog on the ArcGIS Pro tool that leverages this model is published on Esri Blogs. We've also published steps on how to retrain this model further using your data.InputThe model is expected to work with any textured building data displayed in 3D views. Example data sources include textured multipatches, 3D object scene layers, and integrated mesh layers. OutputFeature class with polygons representing the detected windows and doors in the input imagery. Model architectureThe model uses the FasterRCNN model architecture implemented using ArcGIS API for Python.Training dataThis model was trained using images from the Open Images Dataset.Sample resultsBelow, are sample results of the windows detected with this model in ArcGIS Pro using the Interactive Object Detection tool, which outputs the detected objects as a symbolized point feature class with size and orientation attributes.

Buildings are the foundation of any 3D city; they create a realistic visual context for understanding the built environment. This rule can help you quickly create 3D buildings using your existing 2D building footprint polygons. Create buildings for your whole city or specific areas of interest. Use the buildings for context surrounding higher-detail buildings or proposed future developments. Already have existing 3D buildings? Check out the Textured Buildings from Mass by Building Type rule.What you getA Rule Package file named Building_FromFootprint_Textured_ByBuildingType.rpk Rule works with a polygon layerGet startedIn ArcGIS Pro Use this rule to create Procedural Symbols, which are 3D symbols drawn on 2D features Create 3D objects (Multipatch layer) for sharing on the webShare on the web via a Scene LayerIn CityEngineCityEngine File Navigator HelpParametersBuilding Type: Eave_Height: Height from the ground to the eave, units controlled by the Units parameterFloor_Height: Height of each floor, units controlled by the Units parameterRoof_Form: Style of the building roof (Gable, Hip, Flat, Green)Roof_Height: Height from the eave to the top of the roof, units controlled by the Units parameterType: Use activity within the building, this helps in assigning appropriate building texturesDisplay:Color_Override: Setting this to True will allow you to define a specific color using the Override_Color parameter, and will disable photo-texturing.Override_Color: Allows you to specify a building color using the color palette. Note: you must change the Color_Override parameter from False to True for this parameter to take effect.Transparency: Sets the amount of transparency of the feature Units:Units: Controls the measurement units in the rule: Meters | FeetImportant Note: You can hook up the rule parameters to attributes in your data by clicking on the database icon to the right of each rule parameter. The database icon will change to blue when the rule parameter is mapped to an attribute field. The rule will automatically connect when field names match rule parameter names. Use layer files to preserve rule configurations unique to your data.For those who want to know moreThis rule is part of a the 3D Rule Library available in the Living Atlas. Discover more 3D rules to help you perform your work.Learn more about ArcGIS Pro in the Getting to Know ArcGIS Pro lesson

Will be updated as new data becomes availableProjectionNew Zealand Transverse Mercator 2000 (NZTM2000).Vertical DatumNew Zealand Vertical Datum 2016 (NZVD2016).The NZ Elevation layer is an elevation surface for use in 3D applications in the NZTM projection. By adding this layer to a Scene in ArcGIS Pro or in the Scene Viewer it will be define the base height in your application.See the metadata layer with information about the data here.NZTM Basemaps can be used on top of this service, providing it shares the same tiling scheme. When combining it with the NZ Basemaps provided by Eagle Technolgy, make sure to use the raster basemaps with the updated tiling scheme or one of the vector basemaps. All the compatible basemaps can be found in this group. When creating your own basemap or tiled layer make sure to use the tiling scheme provided here.The elevation service is made up of the available publicly-owned 1m and 2m dems. For areas where 1m/2m elevation data is not available the 8m dem provided by LINZ is being used. Outside of the coverage of the 8m dem, a 0m dem is used for visual purposes.This service is offered by Eagle Technology (Official Esri Distributor). Eagle Technology offers layers and maps that can be used in the ArcGIS platform. The Content team at Eagle Technology updates the layers on a regular basis and regularly adds new content to the Living Atlas. By using this content and combining it with other data you can create new information products quickly and easily.If you have any questions or remarks about the content, please let us now at livingatlas@eagle.co.nz

This map represents a research effort focused upon collecting data on the age, height, and history of each lighthouse that shines upon the Atlantic Ocean. Data were manually collected from local, national, and international libraries including Lighthouse Friends, the United States National Park Service, and Wikipedia. The map was produced in ArcGIS Pro for construction of the lighthouse dataset and initial layout, then exported to Blender (3D rendering and animation software). The 2D terrain was then extruded to become a 3D elevation model, and the Atlantic Ocean created as a simulated water surface. Each lighthouse point was transformed into a 3D light source and a true light simulation performed on the scene to render the partially-illuminated terrain and water based on the presence of lighthouses, forming a heatmap (or lightmap!) to underlay the data itself. Lighthouses are shown by height, age, and whether they still serve as a navigational aid.Other Information:The lighthouses dataset was manually assembled by the authors for a variety of sources, including Wikipedia, the National Park Service, Lighthouse Friends, travel and tourism guides, and more. Shuttle Radar Topography Mission (SRTM) 30-meter Digital Elevation Model (DEM) was used to generate the 3D elevation model and enable light and shadow simulation in Blender. Software used: QGIS, Blender, Adobe Photoshop, Adobe InDesign. Map created by Michael Huff, GISP, and Ryan Huff, 2025.