|
POST
|
How about making a copy of the layer in your map and then opening the symbology dialog for one of the two layers. In the upper right corner, click on the 3 hamburger lines and select Import Symbology option. As long as the attribute fields are of the same type (text->text, number->number, etc), then all you should need to do is specify the attribute fields and click run. In our organization, one of our data layers recently had an attribute field re-named so fixing a broken data link wouldn't honor the original symbology. By using the import symbology trick, I'm able to restore the layer in older projects.
... View more
11-18-2024
12:33 PM
|
1
|
2
|
4763
|
|
POST
|
You haven't specified what EB environment you're working in- Portal or AGOL. If it's Portal based, you should be able to publish your own print templates and then specify that print service for the Print Widget. This link from the ArcGIS Server Help describes the process of publishing your own print templates.
... View more
11-14-2024
07:41 AM
|
0
|
6
|
2202
|
|
IDEA
|
As the Near Me widget is currently implemented, you must manually draw a feature (point/line/polygon) to define the area for analysis. Please add the option to select a feature from one of the map layers and use that shape to define the area for analysis. This option should also apply to selecting a feature from a layer imported using the Add Data widget as well. It seems counter productive to important a dataset that defines an area of interest, only to have to manually trace it using the sketch tool in order to run the analysis. Just allow me to select the feature and get going.
... View more
11-01-2024
03:54 PM
|
4
|
2
|
1367
|
|
IDEA
|
Trying to develop an EB app that will summarize census data based on the user's area of interest. Many census tables will break out the information based on multiple value ranges (3 age range classes, for example). On the web map side, this is easy since you can just create an expression using Arcade to sum up multiple field values as one. Unfortunately, if you do things this way (instead of adding a new calculated field) that expression field is not an option inside the Near Me widget's summarize section as one of the field choices. It would be a tremendous help if it was an option to include calculated expression fields in this part of the Near Me widget.
... View more
10-31-2024
02:51 PM
|
2
|
0
|
527
|
|
POST
|
ESRI has a Basemap Feedback Map where you can highlight issues for them to fix. In your description, be sure to indicate which basemap the error occurs just to make sure they fix the one that's most important to you.
... View more
10-24-2024
08:49 AM
|
0
|
1
|
1123
|
|
POST
|
What I do is right click on the value, and then select the remove value option. I do it one by one, so I'm not sure if you can select multiple and remove them in one fell swoop.
... View more
10-02-2024
01:11 PM
|
1
|
1
|
3168
|
|
POST
|
Extreme shot in the dark but I'm seeking older versions of some US Forest Service data that was previously posted to the internet in the early 2000s - 2010s. During this timeframe, each individual National Forest had a page on their website where they would post available GIS data for download. In the 2000s, the data posted was in Arc/Info Export File format (e00) and later in the 2010s they were posted as ArcMap Packages. The latter is still accessible through the Internet Archive but the older e00 versions were not archived (the data distribution page is archived but not the downloadable files). Here's the Internet Archive link from one of the 2000 era archives: https://web.archive.org/web/20110130174708/http://www.fs.fed.us/r6/data-library/gis/mthood/data-library.html These older e00 versions contain some layers which were NOT available in the 2010s. I'm interested in as many of these as possible but specifically the Quarries point dataset and the VEGIS dataset (I have a VEGIS version from the 2010s but the related tables are often blank for reasons unknown). Thanks! Steve
... View more
09-23-2024
08:17 AM
|
1
|
0
|
716
|
|
POST
|
here might be some indication of the issue if you look at the underlying print request. To do this, set the map up to the point where you would print. Now open your developer Tools in your browser (in Chrome, this is done by pressing the F12 key). In the Developer Tools window, switch to the Network tab Now in your EB app, attempt to print using the widget Switch back to the Developer Tools app and look at the activity is has logged. On the left-hand side, click on the entry that's named "execute". This should be the actual print request. You should see a number of tabs of information now on the right-hand side (Headers | Payload | Preview | Response | Initiator | Timing | Cookies) Click on the Response tab to look at its details. If there was an error while printing, it should be reflected and (briefly) described here.
... View more
09-18-2024
08:52 AM
|
0
|
1
|
884
|
|
POST
|
Ugh. You know, changing the DPI parameter was a conscious decision when I migrated the code but the manner in which it's implemented was unexpected. Changing it back to 50 yielded the same print results so thanks for pointing to that. My intent with bumping up the DPI was to increase the sharpness of the output image, much like when you bump up the DPI when exporting to a PDF. In reality, the export map function seems to have ended up just zooming into the map since the dpi I specified was doubled. Anyways, thanks again. Glad that my remaining migration issue is now solved.
... View more
09-16-2024
08:57 AM
|
0
|
0
|
2522
|
|
POST
|
I submitted an idea to get the resize method restored in the API but I finally have success using CSS. I'm still using the same approach as originally outline above but my resizePopupWindow function has changed. I'm now using the setProperty method on the style property and that finally works: resizePopupWindow(theWidth,theHeight) {
var theCssWidth = theWidth + 'px';
var theCssHeight = theHeight + 'px';
var cols = document.querySelectorAll('.esri-view-width-xlarge .esri-popup__main-container');
if (cols.length > 0) {
console.log('Adjusting the popup dimensions to ' + theWidth + ' x ' + theHeight);
for(var i = 0; i < cols.length; i++) {
cols[i].style.setProperty("maxHeight", theCssHeight,"important");
cols[i].style.setProperty("maxWidth", theCssWidth,"important");
cols[i].style.setProperty("height", theCssHeight,"important");
cols[i].style.setProperty("width", theCssWidth,"important");
}
}
} Hopefully that helps out someone else. I should note that the application I'm using this with is really designed for us in a desktop browser environment. I don't know about trying to use this approach under mobile device circumstances.
... View more
09-09-2024
10:48 AM
|
0
|
0
|
1069
|
|
POST
|
Hey Bryan, thanks for the suggestion; it was something I had not tried. Unfortunately, it did not make a difference with my output. We're running v11.1 of Portal so I don't know if is changing things in terms of our situation vs yours.
... View more
09-06-2024
03:50 PM
|
0
|
0
|
2649
|
|
POST
|
Sometimes what to do is still vague despite all the copious documentation. I remember trying to manually edit the version references in the DAML to no avail before finally figuring out it that you just change it in the app settings. Glad you got it straightened out!
... View more
09-05-2024
08:18 AM
|
0
|
0
|
3052
|
|
POST
|
I think I ran into this a few months back myself when my machine was upgraded from 3.1 to 3.3. *I think* it's as easy as changing a setting inside Visual Studio as described here: https://github.com/Esri/arcgis-pro-sdk/wiki/ProGuide-NET-8-Upgrade
... View more
09-05-2024
08:12 AM
|
1
|
0
|
3063
|
|
POST
|
I hadn't considered looking at the request.. From what I can tell, it appears to be sending the request as JSON. I looked at the print request in the 3.X API for the same print area and the header sizes are similar (37k in 3.X vs 41k in 4.X). I'm guessing I'll have to submit an ESRI support ticket to figure this out. The issues I've been describing are using the print.execute() option for printing rather than using the Print widget. I do use the Print widget in a different part of my app and that output is what I would expect-
... View more
09-05-2024
08:00 AM
|
0
|
0
|
2677
|
|
POST
|
Hey Joel, I have been playing with that setting but I don't think that's the way to go. The physical dimensions of the JPEG map export are different than the mapView's extent on screen so if you try to use scalePreserved (in concert with outScale), the resulting JPEG map won't accurately show the feature with the buffer I apply to it. Example- I was getting inconsistent print map extents, which was super frustrating. I finally re-read the API docs and the goTo() method returns a promise so I think my code was behaving more async than sync. I added a when() after using goTo and wrapped the map export process inside that function at the map extents are behaving more like I would expect. The thing I really want to resolve is the symbology and labels which get blown up out of proportion. Again, the print output is similar to what you experience inside desktop if you alter the Reference Scale property of the Data Frame. It's just that the layer & label symbology is not correctly scaling with map scale. Export output vs onscreen map example-
... View more
09-04-2024
01:38 PM
|
0
|
2
|
2718
|
| Title | Kudos | Posted |
|---|---|---|
| 1 | 03-12-2026 01:43 PM | |
| 1 | 03-12-2026 08:41 AM | |
| 2 | 03-10-2026 10:10 AM | |
| 1 | 02-18-2026 09:20 AM | |
| 3 | 01-22-2026 02:03 PM |