Background: Sometimes users/publishers/ArcGIS Enterprise administrators reach out to GIS administrators that they cannot log in to ArcGIS Portal or the application is not reachable via browser. Users might observe that ArcGIS Server services are not working, or they cannot load hosted feature layers in their web maps. In those scenarios the GIS Administrator should do the following preliminary checks.Continue reading
Background: GIS administrators are routinely required to do maintenance activities on their ArcGIS Enterprise High Availability setup. Examples of a maintenance activity can be: Installing Microsoft patches or Esri patches, or resizing instances etc. Before the maintenance is initiated, GIS administrators should know the exact status of the ArcGIS Enterprise setup so that a workflow can be finalized (that is, whether the application on the machine is assigned a Primary or a Standby role). If this is not taken into account, the architecture may become unstable. For example, if the Primary is shutdown first and then the Standby is shutdown, and the Standby is fired up and then the Primary, then the two machines may end up in a scenario where there is confusion as to which machine is the Primary machine.Continue reading
How to make your ArcGIS Enterprise environment robust
Target audience: Enterprise architects often face the question of how to make their IT infrastructure more robust, the aim being to have an environment which is more resilient to failures as well as being able to handle extra load in case the need arises. If you are a GIS enterprise architect or even a GIS administrator and wondering how to do the same, please continue reading.Continue reading
Supporting Imagery and Lidar in the ArcGIS platform has been around for a long time. In the ArcGIS Server Space, Image Server became available at 9.3.1. Since then it has evolved to Mosaic Datasets, Image Services, Raster Functions and now raster analytics. Now imagery is really an integral part of the ArcGIS platform. However, it is only as performant when the imagery is managed and configured optimally.
I often get asked,
- what format should I store my imagery in?,
- How many images can be in a Mosaic Dataset?
- How should I structure my imagery? and
- what is the maximum number of images per folder?
When answering these questions I have drawn on past experience and advice from Esri. Now though Esri have compiled all this information into an Excellent Centralised resource Imagery Workflows – Best Practices https://doc.arcgis.com/en/imagery/workflows/best-practices/what-are-best-practices.htm
In the Imagery formats and Performance section it details topics such as:
- File format suitability
- Recommended imagery formats
- Reformatting imagery
- Working with large mosaics
- Storage system performance
If you’re going to be managing imagery and lidar I recommend you reads these documents. They are comprehensive and invaluable. I must admit I have been doing this for 12 years now and there is information on Lidar management that I did not know about.
This is just one component of the ArcGIS Imagery Workflows documentation Esri has just produced.
When registering a SQL Server database connection in ArcGIS Server the following error appears:
“The connection property set was missing a required property or the property value was unrecognized.”
“The connection property set was missing a required property or the property value was unrecognized. Connection was attempted with an older version of SQL Server client communications software that is not compatible with the SQL Server database server.”
It is known that the SQL Server client communications software is up to date and compatible with the SQL Server database server.
With the delivery of ArcGIS Pro 2.2 and ArcGIS 10.6.1 Esri now supports GDA2020 NTv2 grid files out of the box. However, they are not installed with the product. We have had several reports now of customers deploying the latest product and the NTv2 transformations not being available.
In my role at Esri Australia resolving Enterprise and Developer support issues, there’s rarely a day that goes by where it’s not immensely useful to investigate communication between the different parts of a system. When a component of a GIS is not behaving as expected, forming a complete picture of the behaviour across the system is often instrumental in understanding the underlying cause. This article will focus on the special case of intercepting HTTP requests generated by applications running on top of Microsoft IIS, such as ArcGIS Web Adaptor and the Esri Resource Proxy.
Recently in the Australian media there has been a lot of commentary around the impending update to Australia’s primary datum. From GDA94 to GDA2020. It has even made the British media http://www.bbc.com/news/technology-36912700.
At Esri Australia this has prompted a lot of questions from clients in regards to the support of the new datum GDA2020 in ArcGIS. Will ArcGIS support GDA2020 and when will ArcGIS support GDA2020?
Before we start to answer these questions I think it is important we understand exactly what the new datum is and why Geoscience Australia is moving towards a new datum.
Have you ever wanted to include capabilities files with your OGC Service? An OGC service exposes service-level metadata through its capabilities file. The capabilities file is the XML response that clients receive when they make a GetCapabilities request on the service. Below is my step by step guide on how to complete this process for a WMS Service. To use external capabilities files with OGC services in ArcGIS, you will need to create the files for use with the service. In my situation I want my WMS service to support different versions of WMS protocols – for example 1.0.0, 1.1.0, 1.1.1 and 1.3.0. To do this I must create one capabilities file for each version of WMS.
Although there has been a great blog on this subject already (see: http://esriaustralia.wordpress.com/2011/02/17/the-new-arcgis-runtime/ ) there still seems to be a bit of confusion over what the ArcGIS Runtime actually is and what you can do with it. First of all ArcGIS Runtime is actually a series of 6 runtimes, each based on a specific platform. These cover IOS, Android, Windows Phone, Windows Mobile, Windows and Linux. So we have 4 runtimes for mobile and 2 runtimes for ArcGIS Desktop. When people refer to the “New ArcGIS Runtime”, most are referring to the Desktop version(s) and this is where I will focus this blog.
So what is it for?
ArcGIS Runtime will enable developers to build custom applications that can be easily distributed to users. Such applications may be required to deliver custom interfaces and/or automate of a set of tasks . Additionally there is a LOT of functionality within ArcGIS Desktop, but most users use only a fraction of it. Being able to strip out unrequired buttons, menus and the underlying code, libraries etc is a big bonus. Not only does this make an application more intuitive and streamlined, it also has the potential to reduce the size of the installation footprint and decrease licensing costs. Continue reading