Data published as a feature layer must reference a single source geodatabase or database. You cannot publish data from more than one database connection in a single map.
In ArcGIS Pro, if you were to publish the data in a map as a map image and feature layer and there are multiple data sources referenced in the map you will get an error: ‘00062: Map contains data that does not use the same connection to an enterprise geodatabase’.
Web feature layers associated with a map image layer require that all layers and stand-alone tables in the service reference an enterprise geodatabase or a standard enterprise database using a single connection.
Data published only as a map service can come from multiple data sources. While it is possible to enable feature access on a map service after publishing, only the layers from a single data source referenced by the feature service would be accessible.
With almost any Portal there comes a time when you have dozens of items, created over time by different people, and you may be looking to perform a bit of a clean-up.
The problem now arises that you do not know if the Web Map made by a colleague, who since left the organisation, can be deleted or if it is being used by any other items? You might find that deleting an insignificant-looking item brings your organisation’s most-used application down.
Question What is the correct workflow to achieve a full compress in a versioned geodatabase using replicas?
Answer To achieve a full compress in a versioned geodatabase (that is, move edits from the Adds and Deletes tables to the business tables, and remove unreferenced states), perform the following workflow:
As your ArcGIS Online organization grows, so does the amount of content, and subsequently the credit consumption to store it. It is important for Creators to understand which types of items consume storage credits at a higher rate, and for administrators to identify which users and items are incurring the highest usage.
As the administrator of an ArcGIS Online organization, you have the ability to review your organization’s subscription details and credit status, manage members and licenses, monitor activity, generate usage reports and configure settings. Understanding and managing your organization’s credits may be new to you; but there is a wealth of resources available to help you navigate this task.
This article aims to provide you with a step-by-step guide of these key resources, to point you in the right direction, and ultimately get you started with managing credits in ArcGIS Online.
Esri Australia has been working with Esri and ICSM to ensure that the ArcGIS system can support clients migration from the GDA94 static datum to GDA2020 static datum. The ArcGIS system now fully supports data transformations via 7-parameter similarity transformation, or NTv2.0 transformation Grids.
As a result we are now seeing many clients migrate their authoritative datasets to GDA2020 and requiring all delivered data is in this same static datum. State and national governments are now delivering foundational open datasets in GDA2020 as well
In parallel to this migration we are also seeing more clients taking up WebGIS and delivering data via web services instead of shipping datasets or producing PDF’s. This is enabling a greater uptake web and mobile GIS, providing better informed field operators and getting live data in the hands of people who need it as they need it.
These two waves of change have presented a significant challenge. While transformations existed between WGS84 & GDA94 and GDA94 & GDA2020, there existed no direct path from GDA2020 to WGS84. If you wanted to place GDA2020 data into WebGIS you had to transform you data back through GDA94 to WGS84. Effectively moving the data back to its old location prior to publishing. Many clients asked why????
It has been termed the WGS84 Projection dilemma. So what’s changing?
Ever wanted to understand how ArcGIS can help you leverage Remotely Sensed Imagery, Drone Imagery, Aerial Imagery and Lidar data datasets. Not sure where to start or how to even get access to dataset to get started with?
Well Esri is investing in the Remote Sensing and Image Analysis. It is now core fundamental components of the ArcGIS System. You will see dynamic imagery and raster analytics soon coming to ArcGIS Online
In order to help with you get started in imagery Esri has release an excellent body of materials that step you through the full end to end workflow of imagery, imagery analysis and result presentation.
In ArcGIS Online Map Viewer, all layers in a web map inherit the coordinate system of the basemap. WGS 1984 Web Mercator (auxiliary sphere) is the spatial reference of basemap services in the default Esri basemap gallery, meaning this is the default web GIS coordinate system. Layers also have their own spatial reference and transformations defined at a service level. When you add layers to the Web Map Viewer, an on-the-fly reprojection is performed to align your data with the coordinate system of the basemap.
When publishing data to web GIS you need to consider what spatial reference will be used to store the data at a service level, how the publishing process may affect it, as well as what transformations (or lack of) will be applied when the layer is displayed in a web map with a datum.
It is also important to understand GDA2020 and its relationship with web GIS. The de facto WGS84 in web GIS brings some challenges not unique to Australia or ArcGIS. Failing to address these challenges may result in data misalignment.
When you work with spatial data in ArcGIS Pro, you add datasets as layers to a Map. The map has a defined spatial reference, and this is what ArcGIS Pro uses as it attempts to align your data to the map. It is important to understand how this behaviour works, how to ensure your data in a different datums have correct transformations applied, and what options are available to change default behaviours.