Showing posts with label ArcGIS. Show all posts
Showing posts with label ArcGIS. Show all posts

Sunday, April 27, 2014

Review of Administering ArcGIS for Server

If you are using GIS applications, you need a guide to help you install and manage a solid backbone architecture that will allow you to incorporate all the newest and most integrative GIS services.   

Administering ArcGIS for Server


Administering ArcGISfor Server (Packt Publishing, 2014) by ESRI award-winning Hussein Nasser is a clear, easy-to-follow guide which takes you all the way from installation to configuring and launching GIS services.

The first part of the book is dedicated to installing ArcGIS for Server. The text guides you through what you need in terms of a Web server as well as a GIS server. It also shows you how to test the installation track, and then how to set up a production server. You can also learn how to set up a virtualized environment, which can be very helpful if you need to run a virtual machine.

Once you’ve installed ArcGIS for Server, Nasser shows you how to configure it in order to run as a classical web service. He recommends using a standard format and discusses SOAP and REST.  Because a GIS service is a web service having a geographical element, it is important to look at the two dominant services: Esri and also Open Geospacial Consortium (OGC) services.

Nasser recommends using ArcGIS for Desktop (referred to as Desktop) as the main map services authoring tool. While one could argue that this approach may make you overly dependent on ArcGIS, both on the server side and also on the authoring tool side, but at least you can assure yourself that they are compatible.

The book is very practical. Once you’ve installed ArcGIS for Server as the backbone architecture, Nasser guides you through how to consuming services from GIS software in your system, with an emphasis on today’s main needs, which usually revolve around visualization. 

In the first part of the book, you can see how to use ArcMap, QGIS, and even Google Earth from within your configuration. The book includes a few exercises and examples, which are very helpful.

You may need to put together GIS services that run from your server. If that is the case, you will need to plan carefully in order to analyze the requirements, design the databases, optimize the database indexes, and to deploy GIS services, which include enabling a geodatabase, a world basemap and authoring custom GIS services. You’ll also need to optimize the services (pool, isolate processes, and caching). Administering ArcGIS for Server will help you do so.

You’re also guided through security so that you can protect your digital assets and intellectual property. Nasser guides you through token, key, and how to connect to a secured service.

Finally, Administering ArcGIS for Server addresses backups, documentation, logs, and optimizing the flow (finding bottlenecks, etc.). The appendices are remarkably informative – one of my favorite sections deals with the rise of ArcGIS Server and also the benefits of a 64-bit architecture.











Wednesday, March 26, 2014

Creating Quick, Responsive Web and Mobile Map Applications

It is not easy to find a GIS web app builder that takes you all the way from the basic initial steps of familiarizing yourself with HMTL, CSS, and JavaScript to fairly complicated web applications. 

Building Web and Mobile ArcGIS Server Applications with JavaScript, by Eric Pimpler and published by Packt Publishing has two main advantages: first, you can use high-quality GIS data (or at least data that is specific to your needs), and second, you can create light apps that work quickly over a number of different devices. You’re not likely to have obsolete apps using HTML 5 and JavaScript, which is what is featured here.

The book is very logically organized: you start by creating a base map, and then add layers of data to the map, and then have it all display as a web page. You’re able to add different types of data layers, which include tiled, dynamic, and feature. The section on adding data layers is very robust (as it should be), and it’s followed by adding Graphics to the Map. It’s important to keep in mind that the graphics layer sits on top of the other layers – so, some data management / housekeeping / filing protocols and customs are very helpful here. In this book, the basemaps are provided by ArcGIS Online.



For a person who does not work with GIS data or ArcGIS every day, it’s probably best to work through the examples and see how they’re being developed.  In that case, I’d look at chapter 8, “Turning Addresses into Points and Points into Addresses,” and then work through the example a couple of times. The chapter covers geocoding, which is at the heart of web mapping applications. It’s the way you turn physical addresses into latitude and longitude coordinates.  

The book clearly demonstrates how to write and test the JavaScript code in the JavaScript Sandbox, and then it gives you a chance to practice. I also like the little tips and tricks – example, use Notepad++ instead of Notepad for coding (to avoid the extraneous code problems of Word, etc.).

In addition to Geocoding, there is a very clear and easy-to-follow chapter on using Geoprocessor, which is very good for developing models.  

The appendix gives an example of using ArcGIS templates and also Dojo in order to develop user interfaces. This section alone is worth the price of the book. The instructions are very clear and the screenshots appropriate and easy to follow.

Some of the chapters contain a great deal of code and not perhaps as much detailed explanation as might be useful for people who are fairly new. It would not be a bad idea to have more callouts in the code to point to what exactly is happening.

Overall, this is a great manual – very practical and extremely timely.  

Just a last thought -- when you first read the title of the book, Building Web and Mobile ArcGIS Server Applications with JavaScript, you may immediately ask yourself two questions:  first, why ArcGIS and why not Google Earth or Google Maps integrated apps?; and second, why JavaScript?

First, ArcGIS Server is the most popular and widely-used platform for developing GIS applications for the web. It uses many different dynamic map sources, and is not tied to just one (such as Google Earth). So, if you use ArcGIS Server, you can incorporate the best possible map sources / GIS information.


Second, JavaScript works really well with modern web browsers (Internet Explorer, Firefox, Chrome, and Safari), and it works well with HTML 5. This allows maximum flexibility with mobile applications. Using JavaScript in web applications will optimize performance because the applications are dynamic and do not have to return to the server for data. As a result, they are very responsive and use-friendly, not to mention that they are also faster. 

Blog Archive