|
IDEA
|
I'd just like to take a moment (while Adobe continues to try to open my exported map) to add my voice to this frustration. ArcMap worked so nicely, we didn't even know how good we had it. I have been trying various configurations over the course of the last two days, to try to export a big map book (99 pages at 11" x 17", with a lot of layers). My initial export attempt resulted in a 3,558,818 KB file (yes, that's 3.55 GB). There are too many layers to practically make 'generalized' copies of them. Most of my PDF outputs have been so big that Adobe cannot open them...occasionally I get an error from Adobe about 'damaged file'...'being repaired' but it just hangs until I have to use Windows to 'End Task'. My current strategy is to export my map pages in 20-page chunks, then try to reduce the file size and combine them all in Adobe at the the end...not my ideal work-around.
... View more
01-23-2023
09:37 AM
|
0
|
0
|
2028
|
|
POST
|
Indeed, I can confirm this work-around works: must be a feature layer. Still, it's a little disappointing that you can't do a very basic filter/definition query, just because it's a map service.
... View more
12-30-2022
10:54 AM
|
2
|
0
|
3991
|
|
POST
|
Thanks @AndreasHall , this seems promising. I’ll give it a check soon. Thanks for your work on this!!
... View more
12-23-2022
01:55 PM
|
0
|
0
|
4016
|
|
POST
|
I appreciate the attempt, but doing this does not filter the layers displayed on the map.
... View more
12-20-2022
01:05 PM
|
1
|
0
|
4037
|
|
POST
|
Hi, I have a web map that contains a Map Image Layer of crime incident points. In my web map, my layer has a definition query (filter) omitting all records where [MyLatitudeColumn]='48.00' (all records that had '0' or Null latitudes were field-calculated to this nice rounded-off number in order to handle them and keep them within the full set of features). So, in my web map, these features are not displayed, which is how I want it. The web map also has a duplicate layer in its table of contents that does not omit these same records (contains the full set of features), but it is not visibly displayed on the map (this is how I want it). Web map: However, I have created a dashboard from my web map and, as soon as I configure a 'Selector' in the dashboard, it seems to then ignore the web map's filter on my display layer, and the previously omitted features display. When I initially add the web map to my dashboard, it seems to be honoring the filter...it only ignores the filter when I build a 'Selector' widgit that utilizes the layer. Is this expected behavior? Is there some way to work around this?
... View more
12-19-2022
12:38 PM
|
1
|
5
|
4071
|
|
POST
|
Nope, that just removes the seconds altogether (anything less than a full minute). So neighboring labels would both read: 46°42' I need to be able to display/label half-minutes or quarter-minutes.
... View more
11-08-2022
10:57 AM
|
0
|
0
|
2481
|
|
POST
|
I have a graticule overlaid on my layout and I've chosen to set the coordinate display format as degrees decimal minutes (DDM). I have a graticule 'interval' set for half a minute (0°0.5') for the grid lines, the tick marks, and the labels. Am I wrong to expect the labels to display nice rounded lat/longs at the half-minute, like: 46°1.5' 46°2.0' 46°2.5' 46°3.0' 46°3.5' etc... Why are they set at such close-but-not-quite intervals? I tried changing the map frame coordinate system to WGS Auxiliary Sphere, changing the map units to DDM, etc., but nothing seemed to resolve the issue. I also tried changing the graticule format to decimal degrees and that resulted in similar labels. If I set the graticule to use degrees minutes seconds, then the labels show with nice rounded seconds (either 0" or 30", as expected). I assume this is something simple that I'm overlooking. As you might imagine, I can't send a map like this out and expect anyone to make use of the graticule.
... View more
11-08-2022
09:46 AM
|
0
|
4
|
2521
|
|
POST
|
I've confirmed: Running Office 365, v.2209, click-to-run, 32-bit have MS Access db engine 2016, 32-bit, silently installed have .NET Desktop runtime 6.0.5.31215 x86, silently installed The weird thing is, I've been on ArcGIS Pro 3.x since July (3 months now) and haven't had any issues with Excel tables until the last week or so.
... View more
10-19-2022
07:33 AM
|
0
|
0
|
2339
|
|
POST
|
I quickly found a workaround, but am so frustrated with the fact that ArcGIS Pro can't seem to to 'see' an Excel worksheet through the "Add Data" dialog. When I click into the workbook (xlsx), the dialog just spins and spins and spins....then canceling or closing down the application often requires an "End Task" in the Task Manager. Things I've tried: - check the Excel workbook for correct formatting (there are only two simple columns, both named with text names and containing simple integers). - tried both .xlsx and .xls - tried moving the Excel file to a different location in the directory - tried updating ArcGIS Pro 3 to the latest patch (3.0.2). - tried rebooting the computer - while Pro was spinning its wheels, I launched ArcMap (10.7) and added the Excel worksheet without issue Anyone else experiencing this? Attached: .xlsx file
... View more
10-18-2022
02:04 PM
|
0
|
4
|
2393
|
|
POST
|
I reported this to Esri and they were able to reproduce the issue and logged it as a bug: BUG-000151759
... View more
08-22-2022
06:55 PM
|
0
|
0
|
2980
|
|
POST
|
FYI: I tested this using data from a file geodatabase and some of the behavior was similar, but overall it worked slightly better. The software did corrupt the Python syntax while the join was on, but after the join was removed, it was correctly reverted back to a working expression. The program did not uppercase the word 'in', and it did successfully revert the expression back to valid Python syntax after the join was removed, but while the join was on, the syntax was bad. Label expression before the join (labels work as expected): ' '.join(str(i) for i in ([ANUMBERPRE], [ANUMBER], [ANUMBERSUF], [LST_PREDIR], [LST_NAME], [LST_POSTYP], [LST_POSDIR]) if i) Label expression during the join (labels do not work, bad Python syntax): ' adp.'.joadp.in(str(i) adp.for i adp.in ([ANUMBERPRE], [ANUMBER], [ANUMBERSUF], [LST_PREDIR], [LST_NAME], [LST_POSTYP], [LST_POSDIR]) adp.if i) Label expression after the join (labels work again, as expected): ' '.join(str(i) for i in ([ANUMBERPRE], [ANUMBER], [ANUMBERSUF], [LST_PREDIR], [LST_NAME], [LST_POSTYP], [LST_POSDIR]) if i)
... View more
08-11-2022
05:44 AM
|
0
|
0
|
3009
|
|
POST
|
Thanks for testing this in 2.9.3! FYI: I forgot to mention I'm using 3.0.0.
... View more
08-10-2022
11:53 AM
|
1
|
1
|
3023
|
|
POST
|
I'm using python label expressions to label address points. They concatenate various address element fields using python's .join() function. If I apply an attribute join to my address point feature class (in an enterprise geodatabase) my python label expressions are altered by the program and they no longer work. Here is the python label expression before applying the join (works great like this): ' '.join(str(i) for i in ([ANUMBERPRE], [ANUMBER], [ANUMBERSUF]) if i) Here is the same expression after applying the join, Pro has altered it (the syntax is bad / does not work): ' sde.SL.address.'.josde.SL.address.IN(str(i) sde.SL.address.for i sde.SL.address.IN ([ANUMBERPRE], [ANUMBER], [ANUMBERSUF]) sde.SL.address.if i) In the above, you can see that it mishandled the original python expression. It did not handle the opening parenthesis correctly and it upper-cased all instances of python 'in' to (SQL?) 'IN', even in the word 'joIN'. Also, I don't know why the letters 'jo' were appended to 'sde', which is the database instance. Finally, here is the same python expression after I have removed the table join and the program has tried (unsuccessfully) to revert it back to its original syntax: ' '.joIN(str(i) for i IN ([ANUMBERPRE], [ANUMBER], [ANUMBERSUF]) if i) Notice the two instances of capitalized 'IN'. Python doesn't like these. I'm thinking this should be logged as a bug that needs to get fixed?
... View more
08-10-2022
07:04 AM
|
1
|
8
|
3091
|
|
IDEA
|
@JeremiahLindemann: thanks for your response. I'm aware of ways I can utilize the USNG in my own workflows and use-cases....but my 'Idea' was submitted more in the hopes that the USNG would be institutionalized as the defacto grid system in Esri's off-the-shelf solution.
... View more
08-02-2022
07:40 AM
|
0
|
0
|
1244
|
| Title | Kudos | Posted |
|---|---|---|
| 1 | 07-16-2024 07:49 AM | |
| 1 | 05-20-2024 06:15 AM | |
| 1 | 07-28-2025 05:05 AM | |
| 1 | 07-28-2025 05:10 AM | |
| 1 | 07-25-2025 09:51 AM |
| Online Status |
Offline
|
| Date Last Visited |
05-12-2026
06:03 PM
|