Latest Contributions by MervynLotter

That does seem to be unusual behavior.  One can create "feature-linked annotation, where the annotation will update if the attribute changes, but that is not needed in this case. Simple annotation should work fine.  Once the annotation is created, you use the Annotation edit tool from the Modify Features options. You simply select and move the annotation and the annotation remains anchored to the actual feature. Perhaps you already tried this.    Another option to explore is using the Convert Labels to Graphics tool. This is very similar and you can also manually move the label around while the leader line remains anchored to the feature.  ... View more

Try running the Repair Geometry GP tool to see if that resolves it. What happens if you add these shapefiles to a new map? Do they still not show?  ... View more

Hi Craig A relate is quite different from a join in that a relate establishes a relationship between two features or a feature and a table, but it does not physically join them (if you were to open up the attribute table, you would not see the related features). You can query relates but the link/relationship is invisible. Joins on the other hand, add the fields from one feature to another feature or table. So if you open up the attribute table, you will see attributes from both.  I have used both but generally prefer Joins for my workflows.  As for data source, I am a little less sure about what Esri were intending, but I can guess to say that the features need to exist on disk somewhere (as opposed to Event layers or layers that are in memory only). You will notice in the next release of ArcGIS Pro, one can create temporary or in memory layers.  It is also possible that data source refers to its use in Model Builder, where the layer may not yet exist if the model has not run. And lastly, if you open up an attribute table in Fields View (Data Design > Fields), you can view the attributes based on the layer names, or the Data Source, and the Join tool will need to reference the actual raw attributes in the data source and not the layer in the map (which can be renamed to almost anything, with special characters, which are a nono in GIS). But this is my guess only and I may be wrong.  Best wishes, Mervyn ... View more

It sounds like you are trying to clip a tile package, not a raster.  I dont think you can use the Clip Raster tool for that.  I am aware that you can use th Create Mobile Map Package tool to clip a tile package using a polygon. There is a good chance it may work on a .tpkx file but I have not tested it.  Do see this thread for more details.  VTPK Clip - Esri Community ... View more

This great video from John Nelson may help Bing Videos Or go to YouTube and search for "How to Make this 3D Diorama of the Straits of Mackinac" ... View more

If the above approach does not work, do consider converting it to .tif using the Copy Raster GP tool (not the Clip Raster). Set the output extent in the environment settings. MrSid imagery is not a raster type that works well in Pro. ... View more

After creating your raster mosaic, the next step would be to create a multidimensional layer using the "Make Multidimensional Raster Layer" GP tool. You will them have a set of multidimensional raster tools available to explore your data and extract the necessary information.  See Multidimensional raster data—ArcGIS Pro | Documentation  ... View more

"Summary within" is a script tool that strings together several GP tools in the background. I have previously encountered some issues with it. I prefer to use the Tabulate Intersection tool (Tabulate Intersection (Analysis)—ArcGIS Pro | Documentation) for vector overlays to calculate size and proportions. This is very similar to Summarize within. Do take a look at it to see if it meets your needs.  If you are calculating size, be mindful of choice in projection as the default size calculation in this tool is based on the projection of the layers. If you are using a projection like Web Mercator, rather use a geodesic method to manually calculate size and then sum the size field values from the geodesic calculation. Unfortunately, it does require an Advanced license.  ... View more

Hi JohnKelly If I encounter any odd behavior when working with vector data I usually run the Repair Geometry GP tool to find and fix any errors before further working with the dataset. Not sure if it is applicable to your situation but you may want to consider it. To calculate size, I always use the Geodesic area calculation unless there is a specific reason to use a planar calculation, like (1) if my organization has a policy to use a certain projection, or if (2) a local projection (and a local datum) is deemed more accurate than the geodesic method with a global datum (like WGS84). The geodesic area calculation is based on the underlying ellipsoid (model of the Earth's shape) regardless of your chosen projection.  But if your projection uses a different ellipsoid/datum, then you should get different results.  If you have time, create a point file in Web Mercator, then create a point in Canada and then buffer it, first using planar and then geodesic distances. You will be amazed at the difference in shape (and area). One should never use Web Mercator and a planar calculation method.  But don't rely on your Shape_Area value and rather use the Claculate Geometry tool to calculate the size of polygons.  Good luck. ... View more

Wonderful, thank you so much.  ... View more

This is a great new addition to the Living Atlas. Thank you! ... View more

That is unusual as this works for me. Perhaps try toggling between real-world and screen units or reapplying the symbology. Unless anyone else has some other suggestions? ... View more