Latest Contributions by jessemaps

Is the masking feature supposed to work with Tiled Map Service layers such as World Hillshade? The Masking menu is available for this layer, yet the mask is not created when selecting the vector layer to mask with. It does work with local TIF files and Raster service layers such as TopoBathy3D, but not tiled basemap layers such as World Imagery or World Hillshade - is this supported? I'm using Pro v2.5.2. ... View more

Is there a place we can submit errors specifically with the routing service such as height restrictions or one-way streets? ... View more

The free/basic version of GeoJobe's Admin Tools for ArcGIS℠ Online tool lets you view and sort items by size. ... View more

Related idea: https://community.esri.com/ideas/12311 ... View more

At least as of version 10.3 bmp, emf, png, jpeg, jpg and gif file types are supported as picture marker symbols. ... View more

Yes, please! It's unnecessary clutter when there's no other layers in the list to choose. Or at the minimum let us change the text to something besides "Select the layer you want to swipe". ... View more

There's an idea related to this to vote on here: https://community.esri.com/ideas/6548 ... View more

I'm having the same issue Andy. I get to the window that warns me "If you overwrite this service you will lose access to the associated feature service data, including any changes that were made to the data after the service was initially published. Are you sure you want to continue?" and I hit "Yes" and the publishing "crashes" and it takes me back to my map like nothing happened. I get that too. The only workaround I have for it is to delete the feature service and re-publish the whole thing again. As long as you name everything the same and have all the layers in the same order as before, any web maps that reference the original data will reference the new data once it's uploaded. Web maps reference the data by REST URL, not AGOL item ID. Also, is there a way to overwrite an existing feature service (created by an uploaded shapefile) while still keeping the same item ID? We have a super popular layer for our DOT Cameras that is being used on many maps that we can't break, but have a bunch of (100+) new cameras to add (that I already have in a shapefile). Similarly, when you upload the shapefile and create the feature service, that feature service's REST URL is what's used in your web maps. To update the data, delete the feature service, update the shapefile in AGOL, then re-publish the feature service from the updated shapefile. Your web map won't need updating because the REST url won't change. ... View more

While not exactly the solution you're looking for (Image Service), you can achieve a similar outcome by converting your DEM to a polygon feature class using the Raster to Polygon tool. Publish that polygon layer as a feature service in addition to publishing the DEM as a tile layer. Then add the tile layer to your web map and enable a popup using the feature service as the reference. For smaller scales you might also want to use the Raster to Point tool to create a point layer from the DEM and add that to your feature service. Make sure to build the tiled layer with multiple layers for different map scales, even if it's the same data. Then you can configure the pop-ups to use different layers (point vs polygon) for different scales. ... View more

A note on removing the quotes from the field names in the expression... After removing quotes from field names you will still get the error if you "verify" in the Query Builder, but when you run the tool it will execute successfully despite the warning in Query Builder. ... View more

This took me a few tries to get this to work, so I'm just going to post a couple things that helped me in case it helps someone else. 1. Make sure the ArcGIS Online item you're updating is in your root folder - thanks to dpettittva here. 2. While you fetch the web map's data with the item data url, http://www.arcgis.com/sharing/rest/content/items/ITEM_ID/data the update is done on the web map, not the web map data url. So my update POST url was: http://www.arcgis.com/sharing/rest/content/users/USER_ID/items/ITEM_ID/update ... View more

I also found that once I add my attribute table widget, changes to the source web map are not reflected in the web app. My solution to fix this is as follows: Change your WAB theme to something like "Billboard Theme" that lets you remove the attribute table widget completely (not just hide it). Then re-add the attribute table widget and it pulls in the latest layer info from the source web map. After re-adding the attribute table to the Billboard Theme, switch back to your original theme. You'll probably have to re-do any customizations on your attribute table such as field order and alias names. ... View more

In case anyone is looking for a workaround, here's what I do to get around this. Create the custom legend or symbol in a graphics application like Illustrator and save as PNG. Create an empty feature class and add it to your MXD. Assign symbology of the empty feature class to the custom PNG graphic. Publish map as tile package. Base64 encode the custom legend PNG with a site like this: http://base64.wutils.com/encoding-online/image-to-base64/ Open the tile package contents with 7zip without actually unzipping (if you unzip to edit, you have to re-zip in a specific way – I believe without compression – or the tile package won’t work in AGOL). Navigate to here: \servicedescriptions\mapserver\ Edit the mapserver.json file: Find the legend item and update the following with your new image data "imageData":"" (in between the quotes will go your Base64 text string) Edit the "height" and "width" properties to match the custom graphic’s dimensions. If you’re re-publishing an existing tile package, you’ll also have to update the "url": property with a new guid because I think AGOL stores each image as an object in AGOL that it just references. Upload this edited tile package to AGOL and add it to the web map. ... View more

I had the same error when attempting to publish from a shapefile data source that had # symbols in the attribute names. Just changing the field aliases didn't help - I had to move all the attributes to new fields without # symbols in the name and delete the old fields and then it worked. ... View more