IDEA
|
When an attribute table from a layer in say Map 1 is opened, the table remains visible even after switching to another map (say Map 2). If both Map 1 and Map 2 have the same layer name it can become quite confusing as to which table is linked to which layer in which map. In certain circumstances it would be useful to link the table display to the active map, so that switching between maps also changes the table display (or no table if an attribute table hasn't been opened in a map). This would certainly remove the ambiguity of always displaying the attribute table/s regardless of the active map. I can see the benefits of allowing attribute tables from various maps to always remain visible, so there should be the flexibility to define this. Perhaps the ability to dock an attribute table within the map frame itself, while keeping the existing table functionality, is all that is required?
... View more
11-08-2023
07:15 PM
|
0
|
0
|
403
|
IDEA
|
When creating a new Pro project, or saving a project started with the "start without a template" option, a Project default FGDB is sometimes not required. In this case, the "same default geodatabase for all projects" geodatabase is all that is required. The option to change between creating a new FGDB and using an existing FGDB is made in Pro Options, which requires several clicks to update. My idea is to add a toggle or checkbox to the "Create a New Project" and "Save Project As" dialogs to easily switch between the "same default geodatabase for all projects" and "New default geodatabase for each project" options. Similar to the "Create a new folder for this project" checkbox. Here's an example of what the dialog could like like: We're finding that all these unnecessary blank FGDB's that are being created are cluttering our file servers and Sharepoint sites. Something like this would help reduce the clutter. Regards -David
... View more
11-06-2023
04:50 PM
|
13
|
1
|
542
|
IDEA
|
I agree. It doesn't make sense to have to go to Geoprocessing=>Data Management Tools=>Projections and Transformations=>Define Projections when in ArcCatalog it was Properties=>Apply.
... View more
02-16-2023
08:34 PM
|
0
|
0
|
214
|
IDEA
|
Hi Scott As an example, when applying for certain types of mining tenements a datum/origin is required. This is marked on the ground with a post and on the application form as the start point for a list of coordinates for each vertex. If the polygon isn't created correctly, or the datum has to change due to a feature on the ground, altering the polygon origin with this tool makes it much easier to do. Regards David
... View more
11-06-2022
03:56 PM
|
0
|
0
|
733
|
IDEA
|
ArcMap, with the Production Mapping extension, has a tool called Set Origin Vertex which allows you to change the origin vertex of a polygon feature. https://desktop.arcgis.com/en/arcmap/latest/extensions/production-mapping/set-origin-vertex.htm This tool is missing in Pro and there doesn't appear to be an equivalent. Can this tool please be carried across to Pro, preferably as a general tool and not part of an extension.
... View more
11-02-2022
04:48 PM
|
3
|
5
|
815
|
IDEA
|
Hi Russell Pro 2.9.3 treats layers from feature and map services differently. In a map service it will use the map service CRS In a feature service it will use the layer source CRS. For example if I add the same GDA2020 map service (with layer data source WGS84) to Pro as a map service and feature service, it will read the layers from the map service as GDA2020 and the layers from the feature service as WGS84. I can check this by setting the transformation method in Pro to "none", and the data no longer overlaps. So maybe to make the experience consistent in Pro, this idea should be "Make all map services use the layers source CRS" so that when a map service is added to Pro, it uses the CRS of the layer and not the service.
... View more
09-26-2022
10:13 PM
|
0
|
0
|
462
|
IDEA
|
In Australia we are moving to a new datum, GDA2020. The previous datum, GDA94, was for all intents and purposes identical to WGS84 so if the user forgot to set a transformation the data would still align. With GDA2020 there is an approximate displacement of 1.8m, so in order to reduce risk it's important that as much of our Australian data is in GDA2020 as users aren't infallible when it comes to setting transformations. Easy I thought, just create a new feature service in GDA2020 with the transformations already built in, so that the SDE source layers (in WGS84) will be available in GDA2020. As the SDE source layers are global, they need to be kept in WGS84 so can't be transformed to GDA2020. This is where things unravel. As shown below, ArcMap will honour the GDA2020 service spatial reference for both map and feature services. Pro will honour the GDA2020 service spatial reference for the map service. Pro will not honour the GDA2020 service spatial reference for the feature service, instead it uses the source spatial reference WGS84. So feature services in Pro is the anomaly when it comes to spatial reference. This anomaly appears to be "as designed" by Esri Inc, as recorded in this bug https://my.esri.com/#/support/bugs/BUG-000134342. The alternate solution is to reproject the data source, which is not practical. Strangely the status is non-reproducible. So my ArcGIS Idea is to have Pro use the service spatial reference like it does for map services, instead of the source spatial reference. Or at least provide the option of using either service spatial reference or source spatial reference.
... View more
07-13-2022
09:23 PM
|
2
|
2
|
557
|
IDEA
|
Make web map bookmarks available in Survey123. Instead of unnecessarily creating multiple basemaps a simple web map bookmark would suffice and would be a great time saver. Additionally, if the bookmark could be applied from a Survey123 form question this would help the survey user too.
... View more
02-23-2022
12:53 AM
|
11
|
2
|
477
|
IDEA
|
Report templates for survey123.arcgis.com can only be uploaded by the survey owner or site administrator/s. Ideally anyone should be able to upload a template, either with the Publisher role or have a role criteria that could be checked on to allow users to upload a template.
... View more
02-10-2022
03:36 PM
|
3
|
1
|
775
|
IDEA
|
The ArcCatalog Options has the ability to add file types that will display in the Contents. For example you could add PDF and see them listed in ArcCatalog. Clicking on it would open the file in the associated program. This would be handy to have in Pro. This came about because I noticed that aprx's weren't showing up in Catalog (I found this idea for that) and thought I could add it as a file type.
... View more
02-26-2021
12:00 AM
|
40
|
18
|
2872
|
IDEA
|
Unfortunately it's not in 2.7. If you "Start without a template" it still asks to save as a folder and not an aprx. ☹️ I don't understand why if you use Save As on an existing aprx it will save it it as another aprx, but starting without a template requires saving as a folder. The functionality is obviously there.
... View more
12-16-2020
09:04 PM
|
0
|
0
|
3244
|
IDEA
|
The New Layout gallery cannot be customised, so metric countries and organisations see non-ISO layouts and vice-versa. This makes the gallery cluttered. It would be useful to hide the layouts that aren't required. The second part of this idea is that there are two places in the ribbon interface to bring in a layout - New Layout (which includes Import Layout) and Import Layout. This is a bit confusing having two locations to add a layout. However the Import Layout gallery is customisable. Ideally these two should be merged so that the New Layout and the Import Layout are in the same gallery and are fully customisable. But also keep the ability to choose another pagx to import if required.
... View more
11-25-2020
12:04 AM
|
3
|
2
|
664
|
IDEA
|
This really is a no brainer. Why would you need to create a new folder just to save your aprx? It's a bit of a pain to save the aprx, close Pro, go to file explorer, move the aprx then delete the folder created by Pro.
... View more
07-24-2019
10:36 AM
|
4
|
0
|
3286
|
IDEA
|
When exporting to Excel (xlsx or csv) from AGOL, Enterprise or Survey123 only the field alias is exported. Can an option be given to export the field name or the field alias to the xlsx/csv file. For example using Survey123 can produce a number of fields with the same alias, so when exporting to xlsx or csv it gets very confusing. And it is impossible to append data due to the field mapping between the Excel file and data. Using Pro or ArcMap isn't always an option as users may not be GIS proficient.
... View more
03-18-2019
12:05 AM
|
22
|
3
|
1262
|
IDEA
|
When exporting to Excel (xlsx or csv) from AGOL, Enterprise or Survey123 only the field alias is exported. Can an option be given to export the field name or the field alias to the xlsx/csv file. For example using Survey123 can produce a number of fields with the same alias, so when exporting to xlsx or csv it gets very confusing. And it is impossible to append data due to the field mapping between the Excel file and data. Using Pro or ArcMap isn't always an option as users may not be GIS proficient.
... View more
03-18-2019
12:05 AM
|
19
|
1
|
879
|
Title | Kudos | Posted |
---|---|---|
13 | 11-06-2023 04:50 PM | |
3 | 11-02-2022 04:48 PM | |
2 | 07-13-2022 09:23 PM | |
3 | 02-10-2022 03:36 PM | |
11 | 02-23-2022 12:53 AM |
Online Status |
Offline
|
Date Last Visited |
01-08-2024
12:55 AM
|