Monthly Archives: March 2014
We are pleased to announce support for Esri’s new Geotrigger Service and have a great team ready to help developers push out useful information to people based on their locations. With more ease than ever, messages can be pushed out to mobile devices … Continue reading
I have some great news: you don’t have to be a programmer to write code! Thanks to languages like Python, coding is now available to the masses, and the GIS world is one of its newest audiences. The ArcPy site package provides access to the geoprocessing tools found in ArcGIS for Desktop. Using it can be a challenge if you are unfamiliar with Python, but with some basic knowledge, you can start using it to make your ArcGIS work flows faster and easier.
This post is broken up into sections based on different learning styles. You can choose to read, watch, or code your way into the world of Python, and each section will empower you with the knowledge for getting started with ArcPy. Here are some recommended resources I’ve used for teaching myself Python and ArcPy.
If you are a customer with an Oracle geodatabase and are planning to upgrade your enterprise geodatabase to ArcGIS 10.2.1, please read the following technical article before you upgrade, as some issues exist that directly impact the upgrading process. If you have any further … Continue reading
Registering data folders and databases with ArcGIS for Server is a new functionality in version 10.1. The purpose of registering data is to ensure your data is accessible to ArcGIS for Server or if it must be copied to the Server. When registering an enterprise database, we have the option of registering it as ArcGIS Server’s Managed Database.
If you want to copy the data over from its primary location, and your service type (a feature or web feature (WFS) service) needs an enterprise geodatabase, you will need to register an enterprise geodatabase as managed.
Using Model Builder? Looking for some quick troubleshooting tips? Try these in the order they’re listed below. You can use these to document the steps you take, and if a tech support call becomes necessary, you’ll have a better understanding of what may or may not be causing the problem.
1. Isolate the Geoprocessing tool you believe to be causing the error.
- Run the stand-alone tool outside the model. Does it work with the same inputs and outputs?
2. Isolate a section of the model that is causing the error.
- Create a new model and rebuild the troublesome section to determine if isolating a string of processes helps clarify the issue being faced. Continue reading