Latest Contributions by BillFox

if you are going HA, hopefully you have the option to build the new environment from scratch like @SimonSchütte_ct mentions, a migration to that world is a very deep dive that can break a lot of things ... View more

ok, similar to a mr. sid mosaic tool how about using the "Mosaic datasets" along with this "Export or convert datasets" workflow? https://pro.arcgis.com/en/pro-app/latest/help/data/imagery/mosaic-datasets.htm# https://pro.arcgis.com/en/pro-app/latest/help/data/imagery/export-or-convert-raster-datasets.htm ... View more

does making a mosaic dataset from your las dataset get you there? ... View more

yes indeed, example, what’s the maximum service name for an arcgis image server elevation service In ArcGIS Image Server, the maximum length of a service name, including for an elevation service, is tied to the constraints of the ArcGIS Enterprise system and its underlying components, such as the GIS Server and the REST endpoint naming conventions. However, there isn’t a single, explicitly documented "maximum service name length" specifically for an ArcGIS Image Server elevation service in Esri's public documentation. Instead, we can infer the practical limit based on related ArcGIS conventions and system behavior. ### Key Considerations 1. **Service Name in ArcGIS Enterprise**: - When you publish a service (e.g., an elevation service) to ArcGIS Image Server, the service name is defined in the ArcGIS Server Manager or ArcGIS Pro during the publishing process. - The name becomes part of the REST URL, such as: `https://<server>/arcgis/rest/services/<ServiceName>/ImageServer` - ArcGIS Server imposes a practical limit on the length of the service name to ensure compatibility with web standards, file systems, and database constraints. 2. **Practical Maximum Length**: - Based on ArcGIS Server’s general conventions and testing by users, the **maximum length of a service name** is typically **120 characters**. This aligns with the maximum length allowed for map service names and other hosted services in ArcGIS Enterprise. - This limit includes only the `<ServiceName>` portion of the URL (not the full path). For example, in `MyElevationService`, the limit applies to "MyElevationService" (18 characters). 3. **Additional Constraints**: - **Characters**: The service name must use alphanumeric characters (A-Z, a-z, 0-9) and underscores (_). Special characters like spaces, slashes, or periods are not allowed, as they conflict with URL encoding or file system rules. - **Folder Structure**: If the service is published within a folder (e.g., `rest/services/MyFolder/MyElevationService/ImageServer`), the folder name and service name combined must still fit within URL length limits (typically 260 characters total for the full path in Windows-based systems, though web browsers may support more). - **Database Limits**: If the service is backed by an enterprise geodatabase, internal database field length limits (e.g., 255 characters in SQL Server) might indirectly influence naming, but this rarely affects the service name itself. 4. **Elevation Service Specifics**: - An elevation service is a type of image service optimized for terrain data (e.g., DEMs or DSMs). There’s no evidence that elevation services have a different naming limit compared to other image services in ArcGIS Image Server. The same 120-character limit applies. ### Official Guidance Esri’s documentation (e.g., ArcGIS Server and Image Server help pages as of February 2025) doesn’t explicitly state a maximum service name length for image services. However, the 120-character limit is a widely accepted practical boundary based on: - Consistency with map services and feature services. - Community feedback and testing on forums like Esri Community. - Compatibility with REST API endpoints and client applications. ### Practical Recommendation - **Maximum Service Name Length**: **120 characters**. - **Best Practice**: Keep service names concise and descriptive (e.g., "Region1_DEM_Elevation" or "CityDSM_2025") to avoid hitting limits, improve readability, and ensure compatibility across tools like ArcGIS Pro, Scene Viewer, and web apps. ### Example - Valid: `"NationalParkElevationService2025"` (32 characters). - Valid but pushing the limit: A 120-character string like `"ElevationServiceForNorthernRegionWithHighResolutionDEMDatasetCoveringMultipleCountiesAndNationalParksIn2025Version2"`. - Invalid: A name exceeding 120 characters or containing spaces/special characters (e.g., "My Elevation/Service"). If you need a definitive test, you could attempt to publish a service with a very long name in your ArcGIS Image Server environment and observe where it fails—though 120 characters is the safest bet based on current standards as of February 21, 2025. "grok"   ... View more

a few items here I found for esri and California: Web Content Accessibility Guidelines (WCAG) 2.0 Level AA Web Content Accessibility Guidelines (WCAG) 2.0 Level AA Esri Accessibility articles and blogs Esri Accessibility Esri Legal Accessibility Accessibility Conformance Reports Accessibility Accessibility essentials for GIS and mapping Designing and testing for accessibility in GIS and mapping Accessible Labels with ArcGIS Web Apps Writing accessible ArcGIS StoryMaps content Getting started with accessible storytelling Using Alternative Text for Equitable Storytelling   Accessibility | CA State Lands Commission State of California www.slc.ca.gov   ... View more

hi @Bud  I see that is an option at Pro 3.4.3, not sure when it came to be maybe users are ok setting it or maybe your organization can set that when they install the Pro software? or maybe you are hoping to get similar included in the mosaic dataset properties dialog? or does you organization have the option to publish image services that reference the mosaic datasets?   ... View more

roads are a lack of parcels, so dissolve the parcels and cookie cut them through a "pizza" dough polygon, then split as needed to meet your pavement management system crew's street maintenance needs ... View more

hi @RobChasan  I'm with @DavidSolari in the (it works for me category) I've seen what you are asking for in the add rasters to mosaic dataset tool the list by details and show full path options are useful for me too https://pro.arcgis.com/en/pro-app/latest/tool-reference/data-management/add-rasters-to-mosaic-dataset.htm     ... View more

some rough results: batch calc stats twice as fast on xeon batch build pyramids twice as fast on i9   ... View more

and network bandwidth, storage space / access speed / cpu & gpu compute resources to grind out the Batch Build Statistics, Batch Build Pyramids, seam lines, boundary, foot prints, overviews, etc. if these are DEM/DSM geotiff files,  the cache generation chores too ... View more

maybe begin registering and rectifying to reference the usgs quad sheets ... View more

and this one? https://community.esri.com/t5/arcgis-pro-questions/converting-from-ellipsoidal-to-orthometric-height/td-p/1412362   ... View more

@JPowellhave you already been through this thread? https://community.esri.com/t5/arcgis-field-maps-ideas/measure-the-orthometric-height-in-field-maps/idi-p/1058895#comments   ... View more

Hi @Brownschuh  are you getting several formats delivered of the same area of interest delivered such as geotiff, lidar, slpk? ... View more