|
POST
|
ArcGIS Pro 2.8, Civil 3D 2020 I added a Civil 3D DWG to a fresh, empty Scene in ArcGIS Pro. The coordinate system in C3D was defined (NAD83 HARN SP CA ZnIII US_ft), but Pro did not recognize this coordinate system. I had to define the projection for one of MANY layers brought in from the DWG, but luckily all the other layers updated in sync to the correct XY location after defining the first one. However, the elevation units do not update automatically. I know that the z-values are in US survey feet referenced to NAVD88. I just recently learned that vertical datums cannot be defined in a Civil 3D 2020 DWG - you have to get this info from the engineer or surveyor. The z values are unitless. All of the MANY CAD layers have their elevations units defaulted to meters in ArcGIS Pro 2.8. I'm guessing this is because Pro adds the default base ground elevation surface to new scenes which is in meters (WGS84), and undefined layers get the scene coordinate system applied (?). Now I have to manually change the elevation units property for each of the MANY DWG layers from meters to US_Feet. There has got to be a better way, right? Either a setting in C3D, or a different import process? Maybe create the scene first and update the scene elevation unit properties to US_feet first before importing the DWG? Or maybe there is a way to bulk update the elevation units for all the layers in a scene?
... View more
03-03-2022
10:04 AM
|
0
|
3
|
2134
|
|
POST
|
March 2022: ArcGIS Pro 2.8, Civil 3D 2020 Any update on this? I'm seeing the same behavior in Pro when importing a DWG to a fresh, empty Scene. The coordinate system in C3D was defined (NAD83 HARN SP CA ZnIII US_ft), but Pro did not recognize this coordinate system. I had to define the projection for one of MANY layers brought in from the DWG, but luckily all the other layers updated in sync to the correct XY location after defining the first one. However, the elevation units do not update automatically. I know that the z-values are in US survey feet referenced to NAVD88. I just recently learned that vertical datums cannot be defined in a Civil 3D 2020 DWG - you have to get this info from the engineer or surveyor. The z values are unitless. All of the MANY CAD layers have their elevations units defaulted to meters in ArcGIS Pro 2.8. I'm guessing this is because Pro adds the default base ground elevation surface to new scenes which is in meters (WGS84), and undefined layers get the scene coordinate system applied. Now I have to manually change the elevation units property for each of the MANY DWG layers from meters to US_Feet. There has got to be a better way, right? Either a setting in C3D, or a different import process? Maybe create the scene first and update the scene elevation unit properties to US_feet first before importing the DWG? Or maybe there is a way to bulk update the elevation units for all the layers in a scene?
... View more
03-03-2022
09:53 AM
|
0
|
0
|
2194
|
|
POST
|
Thanks Johannes. I wasn't sure if the geometry was a global attribute you could call without using Arcade, the same way you can with the field names. Since it sounds like it is not, it makes sense you have to do this in 2 steps. You first have to create an expression that declares the variable ("geo" in your example) and assigns the point coordinate ordered-pair to the expression with the geometry($feature) Arcade expression. You can then use that variable as a URL parameter in your hyperlink string.
... View more
01-24-2022
03:53 PM
|
0
|
0
|
2489
|
|
POST
|
Hopefully this is an easy one, but I haven't been able to find an answer. I'm constructing a hyperlink in the pop-up of a point feature in the (new) Map Viewer web map. This hyperlink launches a Dashboard I have constructed. I'd like the Dashboard to zoom to the feature whose pop-up I had open in the web map. I have been testing URL parameters, but the Feature Parameters in my Dashboard settings don't zoom to the features, they just filter the other indicators I have (this might be a separate issue?). I think I can solve this if I add a geometry point URL parameter. I just don't know the syntax to append the coordinates of the currently selected pop-up point to the end of the URL. Something like https://company.maps.arcgis.com/apps/dashboards/<ID>#Geo={geometry}, where 'Geo' is the name given to my URL parameter, and '{geometry}' is the coordinate attribute pair I need to pull from the feature and pass to the Dashboard.
... View more
01-21-2022
04:25 PM
|
0
|
3
|
3245
|
|
IDEA
|
Glad to see this is under consideration. It would be soooooo nice for this to work intuitively.
... View more
01-21-2022
03:23 PM
|
0
|
0
|
4877
|
|
POST
|
It's been 4 years and 1 major redesign. Does this still not work?
... View more
01-21-2022
03:21 PM
|
6
|
0
|
3925
|
|
POST
|
I'll add another vote to get this done, ASAP. I will not switch back and forth to Map Viewer Classic from a map I authored in the new Map Viewer, because I know a whole bunch of things will break. For instance, the new pop-up Arcade expressions. Instead, I'm forced to recreate all my copy layers from scratch.
... View more
01-20-2022
10:50 AM
|
5
|
1
|
4100
|
|
POST
|
Very helpful - I'll have to give it a try. Thanks! Edit: This worked perfectly. I'll be using and recommending this method going forward.
... View more
11-29-2021
08:08 AM
|
1
|
0
|
1736
|
|
POST
|
Anything special one has to do to check if this schema.ini is getting created? Will this file be visible to Windows File Explorer in the same location as my CSV? I'm having the same problem using Table to Table in Pro 2.7. I have already transformed the data in Excel, as described above, so that my ID field is text with leading zeros saved as a .CSV. I've even opened the CSV in Notepad to verify that the values are being stored with the leading zeros. When I use the Table to Table tool in ArcGIS Pro, I use Field Map->Properties to force this field to come in as type text. Even after all these steps, my leading zeros get truncated in the resultant table!
... View more
11-24-2021
01:26 PM
|
0
|
3
|
9460
|
|
POST
|
We figured out our issue - there was an in-memory join to a CSV table that the layer being used for the report had on it (for symbology purposes). Once we removed the join, the report worked and displayed our attachment pictures.
... View more
11-02-2021
12:29 PM
|
0
|
0
|
4557
|
|
POST
|
We're getting the same error. ArcMap 10.7.1. .NET 4.8.3752.0. Trying to run the report on a simple point feature class with attachments that was downloaded as a FGDB from an ArcGIS Online field collection project. We're just trying to display the first attachment picture in the report using the 'RelatedReport' control with a Picture inserted, using the DATA field which indicates BLOB as the image source, as described here. We have a corporate IT structure, so ADMIN tasks such as disabling the firewall or running Windows services that are not part of our install are not an option.
... View more
11-02-2021
11:40 AM
|
0
|
1
|
4559
|
|
IDEA
|
Currently, ArcGIS Online allows you to configure the feature and table search for maps as described here. Allowing users to be able to search by layer attributes, such as asset ID, instead of just the default Address and Places is a very helpful feature. However, when authoring web maps and apps for novice users, the user may not realize that searching for these additional feature attributes is an option when viewing the Search box. This is because the default "hint" text in the Search box is "Find Address or Place". You can add your own "hint" text for the additional fields enabled for searching as described in the instructions above, but this new hint text is only displayed when the user uses the Search drop down to switch to constraining the search to a new category. When a map is first opened, the default search category of "All" is active, but the hint text still only indicates that "Addresses or Places" are searchable, when the additional categories are also searchable by default. For instance, if a user wanted to find an asset by its ID #, they may not think they could locate it with a Search tool that can "Find Address or Place", and may not bother further investigating the search pull down. They would not assume they can just begin typing a numeric ID in a search field for "Address or Place". I would like the hint text for the default "All" category to be configurable. Even if only one "hint" text can be configured, as is the case now, I would like that hint to be applied to the "All" category instead of just the new categories.
... View more
09-23-2021
05:14 PM
|
6
|
1
|
1048
|
|
POST
|
I never would have found that. But I guess if that is the function that underlies the Query Builder embedded in the Extract By Attributes tool, that would make sense. Thanks.
... View more
09-23-2021
02:18 PM
|
0
|
0
|
2670
|
|
POST
|
Raster Calculator does work (I used the Con method). And I see that the output of the Raster Calculator (which has values of 1 or NoData) is able to be used as an input to the Extract by Attributes tool. The Query Builder lists "Rowid", "VALUE" and "COUNT" as value sources. Any idea why this would be? Is Extract by Attributes not supported on certain types of rasters? Perhaps floating point? Out of curiosity, I used Raster Calculator to pass all the value as-is to a new copy of the original raster. This new copy still can not be used as an input to Extract by Attributes. Which makes me think it has something to do with floating point versus integer, not because the raster is missing some underlying ESRI metadata.
... View more
09-23-2021
11:28 AM
|
0
|
1
|
2676
|
| Title | Kudos | Posted |
|---|---|---|
| 1 | 03-12-2026 02:09 PM | |
| 1 | 03-21-2025 03:07 PM | |
| 1 | 12-04-2025 04:57 PM | |
| 1 | 10-23-2025 04:54 PM | |
| 9 | 10-01-2025 12:20 PM |