Latest Contributions by RhettZufelt

It sounds like you are looking at the layer symbology in the TOC which shows the symbology of layers already added to the map as well as a box to toggle on/off. I believe you are looking to set a Definition Query in the Layer Properties ( SubTypeField = 'Manhole') for that layer to restrict what is being drawn. R_ ... View more

Agree.  But the OP has another similar post about records showing in the attribute table as well. Was just pointing out that your definition query solution would solve both his questions. R_ ... View more

Have not tried this, but appears to be supported in the calculate field in Field Maps. Not knowing the format of the sequential letters, not sure, but perhaps you could parse off the number(s) you need to sequence.  Split them so you can feed each to a ToCharCode() which will give you the character code for that letter.  Increment this by one and you get the next sequence letter, and so on. (would have to look at the start/end numbers for caps vs lower case, etc.). Then you could append/concatenate the individual letters together with the FromCharCode() function. var NumCode = ToCharCode('A') //returns number: 65 var NumCode = FromCharCode(NumCode) + FromCharCode(NumCode + 1) // returns text: "AB" return NumCode Like I said, have not tested, but seems like everything needed is in there, depending of course, on what the original data looks like and what output needs to be. In case it helps, R_ ... View more

the definition query as per @Bilal_Alam_GIS post not only will remove from labeling, but will remove them from the attribute table as well (as per your other post). R_ ... View more

 I copied your code and updated for street featureclass name and fields and seems to be working as expected.  Auto assigns the closest street name, but, If I change it in the attribute table (I have domain dropdown on this field), it will update to whatever street I select and stick. Only thing I really see different is that my street field names are different in my lookup street centerline layer and the target layer.  Line 15 should have the field name containing the streetname in your FeatureSetByName($datastore, "StreetCenterline") layer. MAIN_ROAD = streetname field in target layer Street_Lables_Zoom = streetname field in lookup layer R_ ... View more

Hard to follow your code as it has lost in indentation. If you edit/post code following this post, it will maintain all the indentation, etc. Inserting Code in AGOL post. R_ ... View more

I have not tried this by clobbering existing layers with the MakeFeatureLayer tool, but have used other tools/code to overwrite feature layers within my Pro project that I publish/overwrite existing services. In my case, I check the Map layer properties to Allow assignment of unique numeric IDs for sharing web layers: And, in the Geoprocessing options, Allow geoprocessing tools to overwrite exiting datasets, and un-check "Remove layers that reference data overwritten by geoprocessing tools": This way, the layers are not removed, updated, then re-added, they are updated in place and the ID assignments do not change.  I can then overwrite my feature service with the new data while maintaining item ID's. In case this helps in your scenario, R_ ... View more

I never did get cloning to work properly with map name, but if I pass the item ID, it works most of the time. have less going on than your code, but I just use a Notebook in Pro to clone one item at a time as needed. As long as I'm connected to the source and target GIS's with admin user, this will normally copy the App/Map/HFS's included. Of course, doesn't always work and I just chalk that up to the ESRI uncertainty principle 🙂 In case this helps somehow, R_   ... View more

Realized that my testing was only for Map, and not a Layout, so tested that as well. Appears to be working also. In catalog, if I look at the Raster Properties, it shows there as well, so probably correct being a 3.3 thing.  I try not to 'upgrade' until the issues fixed from previous versions gets to fewer than a dozen or so 'pages' of issues, so won't be able to test 3.3 for some time. R_ ... View more

The environment setting I refer to are for the GP Tool environment here:   But, exporting the map with the Share/Export doesn't honor this setting. However, if you set the coordinate system for the Map:   Then export the GeoTIFF, it will then be in the coordinate system of the Map and will be detected by map/pro. R_ ... View more

You can also config Pro to Not add the output layers to the map, then shouldn't lock them. (not tested with shapefiles). Could also just run it standalone outside of Pro. R_ ... View more

Did my response in your other post on this help any? Could possibly be a 3.3+ thing as I didn't test on them.   R_ ... View more

You really didn't give much info on 'how' you are exporting the map. My testing shows that the Export Map Button in the Output group on the Share tab does NOT honor the output coordinate system in the Environment settings. However, in Pro, If I change the coordinate system of the Map to GCS (even though my feature class data is in State Plane), then export to TIFF (I checked the 'Write GeoTIFF tags' box), it outputs my map as a tiff image that Pro and Map can read just fine and is aware of the GCS of the Tiff file. R_ tested with 3.2.1 and 3.1.3 ... View more

I am seeing the same thing with my jpg attachments.  No issues before the last AGOL update, now, it is hit or miss if the attachment will show the actual image or the icon like you show. For the most part, it appears as if the 'older' attachments have more issues that attachments added more recently. R_ ... View more

The spatial reference of a web map is determined by the basemap itself. Create a map in Pro that ONLY uses the Virginia State Plane data (making sure it is defined on the dataset(s)).  Share that as a tiled web layer to AGOL. Then, in map viewer, add this as the ONLY basemap in the map viewer.  Your entire map will now be in the Virginia State Plane system. R_ ... View more