|
POST
|
Jonah, At Pro v.2.2, elevation settings got moved from the Map properties dialog box to the Contents pane of the scene. If you tried setting the TIN as the elevation surface, it sounds like you know this already. How did you try to set the TIN as the elevation surface? This is what I did: added a TIN to a scene in Pro. It went under 2D Layers in the Contents pane (same as it did for you). At the bottom of the Contents pane, under Elevation Surfaces, I right-clicked Ground and clicked Add Elevation Source. Then browsed to the TIN dataset location on disk. Now when you identify TIN locations, the elevation units reported in the status bar next to the x,y coordinates should be the values stored in the TIN. (Whereas if you click somewhere off the TIN, elevation values in the status bar reflect the default ground surface: WorldElevation3D/Terrain3D.) In the Map Properties dialog box for the scene, you might still need to check your elevation units (on the General tab) to make sure the correct reporting units are being used. Like if your TIN elevations are in meters, this setting should also be meters.
... View more
12-18-2018
11:32 AM
|
1
|
2
|
6333
|
|
POST
|
Hi Thomas, the basic steps are: Create a project Make a folder connection to your data Add a map to the project (which happens automatically if you create a project from the Map template) Add your data as layers to the map The tutorial Dan mentioned is the first in a series. Take a look at the tutorial Add data to a project, too.
... View more
12-15-2018
11:04 AM
|
2
|
0
|
1601
|
|
POST
|
Hi Richard, it's actually the designed behavior. The layer metadata is populated from the feature class metadata and is read-only by default to keep them in synch. If you want to edit the layer metadata independently of its source metadata, open the layer properties, click the Metadata tab on the left side of the Layer Properties dialog box, and change the drop-down setting at the top to Layer has its own metadata.
... View more
12-13-2018
10:45 AM
|
1
|
1
|
5436
|
|
POST
|
Shane, did you find anything useful in the licensing doc? For instance Authorize and start ArcGIS Pro with a Single Use license—ArcGIS Pro | ArcGIS Desktop > Authorize an extension
... View more
12-07-2018
08:55 AM
|
0
|
0
|
3492
|
|
POST
|
Hi Dianne, The name of the Project pane was changed to Catalog pane. (That should make it easier to find.) If it's not open in your project, you can open it by clicking the View tab on the ribbon and clicking the Catalog Pane button.
... View more
11-21-2018
01:31 PM
|
20
|
1
|
82461
|
|
POST
|
You might take a look at the Find Areas at Risk of Flooding in a Cloudburst lesson on Learn ArcGIS. This is a tutorial on mapping flood risk under specific conditions (sudden catastrophic downpours). The author is a professor at the University of Copenhagen. The lesson is ArcMap-based, but as Chris said, the process should be the same in Pro. The tutorial data includes geoprocessing models--that helps to visualize the workflow. Anyway, it's one good starting point. It's a complicated game, as Chris also pointed out.
... View more
11-09-2018
04:51 PM
|
3
|
0
|
7236
|
|
POST
|
Nasser, the important dataset to project is the one you need to analyze: the Utah_Zipcode_Time data. The maps and basemaps don't matter, as Dan said. What projection is Utah_Zipcode_Time in? It needs to have both a GCS (datum), such as NAD 1983, and ALSO a PCS, or projected coordinate system. For your area of interest, the PCS might be UTM Zone 12N ,or one of the Utah State Plane projections, or maybe even a continental US projection like USA Contiguous Albers Equal Area. When you select a PCS for the Output Coordinate System in the Project tool, you will automatically be including a GCS along with it. The GCS will most likely be NAD 1983. The main thing for you to figure out is which PCS to use. If you don't have a better idea, or a given standard, try UTM Zone 12N. The documentation on coordinate systems in ArcMap, starting at What are map projections? may be more helpful than the ArcGIS Pro documentation.
... View more
10-09-2018
03:30 PM
|
2
|
1
|
3973
|
|
POST
|
Besides the file name difference, you mentioned that in your CSV you replaced bad coordinate pairs with blank cells. Your screenshot shows <Null> values, not blanks--at least for the Trade_name field. Did you send your co-worker a CSV with blank cells and get back a CSV with <Null> values? Not sure but still wondering if this is somehow relevant... blanks being interpreted as text and <Null> as numeric.
... View more
10-02-2018
02:14 PM
|
0
|
0
|
2614
|
|
POST
|
Not an answer but possibly a clue from the help topic Work with Microsoft Excel files in ArcGIS Pro under the Limitations heading: Excel does not enforce field types for values during data entry like standard databases do. Therefore, the field type specified in Excel is not used in determining the field type exposed in ArcGIS. Instead, field type in ArcGIS is determined by a scan of the values in rows for that field. If the scan finds mixed data types in a single field, that field will be returned as a string field, and the values will be converted to strings. I don't know if CSV files are treated the same as Excel files, but maybe the combination of numbers and blank cells in your CSV is being interpreted as a mix of data types. Not sure why it would be any different for your coworker, though.
... View more
10-02-2018
11:17 AM
|
0
|
2
|
2614
|
|
POST
|
In addition to Dan's suggestions, check out Learn ArcGIS which has tutorials oriented to specific problems. There's one called Explore Future Climate Projections that will probably interest you. And see Kory Kramer's post ArcGIS Pro Learning Resources. For your work, you might want to concentrate on learning about raster data processing and analysis. Another good resource in Learn ArcGIS is Get Started with ArcGIS Pro, which focuses on analyzing flood risk in Venice, Italy, so also has a climate-science orientation. The quick-start tutorials mentioned by Dan are a very good introduction to ArcGIS Pro; unfortunately, they're not strong on raster data analysis.
... View more
09-25-2018
09:28 AM
|
2
|
0
|
2973
|
|
POST
|
Robert is probably right. If you click the Add Data button on the ribbon--not the drop-down bottom part that you showed in your image, but the top part that opens the Add Data browser--can you see the contents of your ArcGIS Online account, as in this image? And the vector basemap in it? You should be able to select it and add it that way. If not, it seems like your software might need to be updated. At least, nothing else springs to mind.
... View more
09-24-2018
04:16 PM
|
2
|
1
|
23154
|
|
POST
|
Hm, not sure. You don't see a context menu when you right-click the Basemap? (Here's what my context menu looks like when I right-click the Basemap in the Contents pane.) What if you click the Map tab on the ribbon and click the Add Data button there?
... View more
09-24-2018
03:26 PM
|
0
|
4
|
23154
|
|
POST
|
You started by copying Esri Basemap Item, right? Then you made changes, then you clicked Update Item. The edited basemap should be saved in your ArcGIS Online content page. Like this: To add to your ArcGIS Pro project: on the ribbon > Insert tab > New Map dropdown > New Basemap. In the Contents pane, right-click the Basemap item > Add Data. In the Browse dialog, under Portal > My Content you should see it and be able to add it. Does it work? You can also add the basemap to your ArcGIS Online gallery. I think then it should be available from the list of Pro basemaps. (I haven't tried that though.)
... View more
09-24-2018
09:59 AM
|
1
|
6
|
23154
|
|
POST
|
David, Have a look at the Vector Tile Style Editor. It's beta but very usable.
... View more
09-24-2018
08:53 AM
|
3
|
8
|
23154
|
|
POST
|
Also, look up the definitions for feature class and layer in the Esri Support GIS Dictionary. The basic difference, as Dana indicated, is that the feature class is the data itself and the layer is a representation of the data in a map, with specific symbology, labels, etc. The layer defines how you want the data to look. One and the same feature class can be represented by different layers in different maps (or by different layers in the same map). A layer file (.lyr or .lyrx) saves the properties of a layer to disk so they can be reused easily. Suppose you spent an hour in ArcMap or ArcGIS Pro defining the properties of a layer in a very exact way--the symbology you want, the labels you want, and all the other settings you can make for a layer. If you're only going to use that exact set of properties once, you don't need a layer file. If you want to reuse them--like if you're establishing a standard cartographic look for your organization--then the layer file is like a template: whenever you add it to a map, all the layer properties are automatically set. Note that the layer file still requires that the feature class it represents be available. Don't make a layer file and then delete the feature class!
... View more
09-19-2018
02:11 PM
|
6
|
3
|
15404
|
| Title | Kudos | Posted |
|---|---|---|
| 1 | 08-08-2025 04:19 PM | |
| 1 | 05-21-2025 12:23 PM | |
| 1 | 04-22-2025 02:44 PM | |
| 1 | 12-06-2024 02:32 PM | |
| 1 | 01-04-2022 04:07 PM |
| Online Status |
Offline
|
| Date Last Visited |
a month ago
|