user_mobilelogo

Jack and Laura Dangermond founded Esri in 1969 as a small research group focused on land-use planning. The company's early mission was to organize and analyze geographic information to help land planners and land resource managers make well-informed environmental decisions. Esri inspires and enables people to positively impact their future through a deeper, geographic understanding of the changing world around them. Esri has cultivated collaborative relationships with partners who share our commitment to solving Earth’s most pressing challenges with geographic expertise and rational resolve. Esri pursues mapping and spatial analysis for understanding our world with visionary products and services that define the science of GIS. ArcGIS is a complete system for designing and managing solutions through the application of geographic knowledge. Esri helps you build and manage great information products by providing the ultimate platform for geospatial integration and application.


 


Digital Data Services is a Silver Partner for Esri and offers a wide-variety of Esri based software and service solutions. More information about DDS's Esri based solutions can be found at digitaldataservices.com.

We are moving!!

Well, my friends, the time has come! We’ve had quite a good time with you all from this little corner of the internet, but in just a few weeks, the Esri Support Services Blog will be moving to a new home.

This blog and several other Esri blogs will move from the blogs.esri.com domain to their new home on the Esri Community (GeoNet) website. This move is great for everyone–here in Support, we’ll have more opportunities to engage with you and help you further your GIS goals with the ArcGIS Platform. As blog readers, not only can you join a plethora of forum discussion topics, ideas, and community groups involving Esri, GIS, and The Science of Where, but you will have a much deeper level of engagement with blog authors and content in a single place.

So, if you are not familiar with our blog site, then perhaps this isn’t a big deal. However, if you have been a regular reader, you will want to know what this means (i.e. accessing your go-to blog posts and the like). This thread on GeoNet goes into more detail, but here are some highlights:

The “official” move date period is early to mid-October 2017. The home page URL for our new site will be https://geonet.esri.com/groups/technical-support/. Most blogs on our website will automatically redirect to their new homes on GeoNet. No need to update your bookmarks or edit your posts–we have you covered. If a blog has not been migrated (e.g., Happy Halloween 2009), you will be redirected to the Technical Support home page on GeoNet. You do *not* need a GeoNet account to access our blog content, but you will need one to post comments, like posts, and so forth.

As administrators, we have thoroughly enjoyed developing and growing our blog site over the years, and we hope you will join us on our next voyage with the Esri Community.

Greg L. and Megan S. – Esri Support Blog Admins

Original author: Greg Lehner

Copyright

© Esri

Continue reading
737 Hits

WWTSD (What Would Tech Support Do?) Part II: Data-specific Issues

This blog post is part II of the WWTSD blog series from Esri Support Services. Click here to view the first part in the series: WWTSD (What Would Tech Support Do?) Part I.

Have you ever attempted to run a geoprocessing tool, only to have the tool fail? Perhaps your data fails to publish to ArcGIS Online or draws incorrectly on your map. Maybe you are running a geoprocessing tool only to have it fail with a generic error message. You are using the same workflow you use every day with the same settings and configuration, but you can’t seem to find another cause to the problem.

You may be dealing with a data-specific issue. There are a few basic troubleshooting steps that may provide a resolution to this, but it all starts with determining if the issue is truly data-specific.

Determining if an Issue Is Data-specific

A quick test to determine if an issue is data-specific is to bring your dataset into a blank map document, map frame, or web map (depending on the environment in which you are working). If the issue does not persist in a new map, then the issue may be specific to the map document. If you experience the same issue in a new map document, the source of the problem may be the data.

Another way to determine if an issue is data-specific is to run the same process with a different dataset similar to the one that you are using. For instance, if using a point shapefile that fails to import into your file geodatabase, run the process on a different point shapefile of a similar size. If the tool or process succeeds on the new dataset, then the issue may be data-specific. Luckily, there are tools available that can help to resolve some of these data-specific issues.

If you find that the problem or error is reproducible with multiple datasets, you may want to investigate some of our additional resources to determine the source of the issue. Feel free to check out more resources from the first post in the WWTSD series (linked above).

Possible Data-specific Issues and Their Solutions

A geometry error can be one potential source of a data-specific issue that has a quick fix. ArcGIS applications require that a feature’s geometry meets certain standards. Issues can occur if any features have null or incorrect geometry. In ArcMap and ArcGIS Pro, you can determine if your dataset has any geometry errors by running the Check Geometry tool, which generates a table that lists the geometry errors found in the data. If there are errors present in the resulting table, run the Repair Geometry tool to fix the geometry errors present in the data. It is recommended to make a copy of your data prior to running this tool, as the tool may delete records with geometry errors.

If your features appear in a different location on the globe than you would expect, your data may have an issue with your data’s projection. You can view the coordinate system of your data by navigating to the properties of the layer. If the data does not have a defined projection, you may need to use the Define Projection tool to assign the correct projection (see the tool documentation here for more information). If your data has been assigned a different projection than the other layers in your map, you may need to use the Project tool (here) to alter the coordinate system of your data. For more information about when to use the Define Projection tool versus the Project tool, take a look at the blog post found here. If you do not know what projection your data should be in, please see the technical article here for more information.

Data can become corrupt for various reasons, including incorrectly copying data or  experiencing connection issues to a network drive. These issues sometimes can be resolved by exporting the data into a different format or location, such as to a different feature class or to a .tif rather than to a .png raster file. If you are working in a file geodatabase, run the Recover File Geodatabase tool, which creates a new file geodatabase with repaired versions of feature classes that the tool identifies as potentially corrupt.

Considerations for Raster Datasets

Raster datasets have many parameters and properties and therefore, many sources of data-specific issues. The following by no means addresses all potential issues with raster datasets, but does address a couple common sources of data-specific issues for rasters and troubleshooting steps to address the issues.

Bit-depth is a characteristic of a raster that defines the possible cell values allowed for the dataset (for more information, click here). If the bit-depths of two or more rasters that you are running a geoprocessing operation on do not match, you may run into errors or issues. For instance, if you create a mosaic dataset containing rasters from multiple sources, you may want to confirm that the bit-depths of the rasters are the same. You can determine the bit-depth of a raster by navigating to the raster properties. If you must change the bit-depth of your raster, you can use the Copy Raster tool to manually set the necessary bit-depth and create a new output raster with those parameters.

When adding a raster dataset to a map document or creating a new one, you are given the option to build pyramids that control how the dataset is viewed at different scale levels. If you are unable to view your raster dataset at some scale levels, but not at other levels, the raster pyramids may have become corrupt. Exporting the raster into a different format or deleting and rebuilding pyramids may help resolve this issue. If you would like more information about deleting and rebuilding pyramids, click here.

Contact Esri Support

These steps can help to begin narrowing down potential causes to an issue, but they may not resolve every potential problem. If you need additional assistance with diagnosing or resolving an issue, feel free to contact Esri Support. We are happy to assist our customers resolve any technical issue they encounter. When contacting Esri Support, please be prepared to provide the following information so that an analyst can assist you as efficiently as possible.

Software version and license level Operating system Device, if using a mobile application Synopsis of the issue Detailed workflow Error message Test data

Krista M. – Desktop Support Analyst

Original author: kristam_ess

Copyright

© Esri

Continue reading
913 Hits

The Esri Support Site Is Now in Spanish!

As part of our ongoing commitment to enhance the online support experience for our global user base, we are very pleased to announce the official launch of the Spanish language version of our award-winning Esri Support website.

Main Page in Spanish

Main Page in Spanish

http://support.esri.com/es/

Support site localization empowers customers to access important online support resources in their preferred language, such as:

Popular technical articles Product lifecycles Support downloads for all products in General Availability The Request Case web form The GIS Dictionary (to be completed by Q3 2017)


You can directly access the Spanish site through http://support.esri.com/es/, or by going to the English version of the site and selecting “Español” from the drop-down menu in the upper-right banner next to the Esri ID Sign In option.

Language Selection

Language Selection

As you navigate through the site, you may come across content that has not yet been translated. You can submit a translation request for this content by clicking the “Request Translation” button in the green banner at the top of the page or by filling out the site’s feedback web form in the page footer.

Request Translation

Request Translation

Our goal is to provide helpful and instructive content, and we strive to ensure this content maintains a high standard of quality. If you find any problems with the translated content or feel there are potential improvements, please use the “Translation Feedback” option (comentarios sobre la traducción) to send us your feedback.

Translation Feedback

Translation Feedback

Moving forward, we will translate the site into additional languages including Chinese, French, German, and Arabic.

Megan S. – Online Support Resources

Original author: Megan

Copyright

© Esri

Continue reading
1011 Hits

Support Services at the Esri User Conference: July 11-13, 2017

Esri Support Services will be at the 2017 Esri User Conference in San Diego (July 10-14), where we will offer GIS technical support help to answer any of your questions. Specialists in all areas of Esri software will be available to assist you.

Users attending the conference can visit our reception desk to meet with a support analyst who will be happy to discuss your concerns, issues, and questions. Appointments are not required, so feel free to stop by in between sessions or during lunch.

Just don’t forget to register first! You must be registered to gain access to the Tech Support Island, technical sessions, user stories, and demos of the latest Esri products.

Location:

In the back-center of the floor, behind Exhibit Hall B1 & B2 in the Customer Care pavilion; if you’re coming in from the main hall, look for Demo Theatre 09. Notice all the cool exhibits around us, as well!

Map of Esri User Conference 2017

Hours of Operation:

Tuesday, July 11th: 9:00 AM – 6:00 PM Wednesday, July 12th:  9:00 AM – 6:00 PM Thursday, July 13th: 9:00 AM – 1:30 PM

For more information about the User Conference, including session information, activity dates and times, and info on the Plenary, please download the Esri Events app (for Android and Apple), available now for free from the Google Play Store and iTunes Store.

We look forward to seeing you there!

Gregory L. – Online Support Resources

Original author: Greg Lehner

Copyright

© Esri

Continue reading
1021 Hits

Release of the Deprecated Features Plan for ArcGIS 10.5.1

This blog post provides the latest updates regarding deprecated features in the recent release of ArcGIS 10.5.1.

With each release, Esri assesses and adjusts the products and functionality supported in the ArcGIS Platform based on customer needs and technological trends. The purpose of the Deprecated Features for ArcGIS document is to provide as much advanced notice as possible regarding these changes.

For more information on Esri’s plans for deprecating features, refer to the following PDF document, Deprecated Features for ArcGIS 10.5.1 (this deprecation plan is also available in the following technical article from the Esri Support Knowledge Base). The documentation linked above provides additional information about each note below, in addition to recommendations of alternative workflows and applications. Information from previous releases (10.4 and 10.5) is also included in the link above.

Here are some of the major changes in ArcGIS 10.5.1:

ArcGIS Desktop 10.5.1 is the last release to support Visual Studio 2013 for the ArcObjects SDK. In the near future, the cluster functionality in the ArcGIS Server component of ArcGIS Enterprise will be deprecated in favor of individual site deployment. ArcGIS Enterprise 10.5.1 will stop bundling the portalpy module in favor of the ArcGIS API for Python. No further development is planned for this module. ArcGIS 10.5.1 will be the last release to support the PostgreSQL 9.3.x series of releases, DB2 versions 9.7 and 10.1, and the ST_Raster data type for Oracle, SQL Server, and PostgreSQL. ArcGIS 10.5.1 is the last release to support anything other than the Data Store product as a data store for a Hosting Server.

Gregory L. – Online Support Resources

This entry was posted in Announcements, ArcGIS Desktop, ArcGIS Enterprise, SDK and tagged , , , , , , , , , , , . Bookmark the permalink.
Original author: Greg Lehner

Copyright

© Esri

Continue reading
1086 Hits

Three Methods for Clipping a Network Dataset in ArcGIS Desktop

Imagine this: you’ve been assigned a project where you must find the drive times (at 5 minutes, 10 minutes, and 30 minutes) for 100 different customers and the best routes to deliver supplies to all customers. On top of that, you’ll need to do it for many different datasets. The result of each analysis, along with the underlying data used to produce those results, must be sent to the client.

ArcGIS Network Analyst is the best option, but you’ll need your own network dataset. So, you reach out to a colleague or friend. They’d be happy to give you a network dataset, but it contains data for a much larger area than needed. While it may work for your analyses, you can’t send the client the whole dataset.

A network dataset containing turn features, sign features, and/or traffic data can be difficult to clip. Using a regular Clip operation on the streets can break connectivity between the streets, as well as break the link between the network edges and the turns, signs, and traffic data.

So, the question is how can you clip the network dataset to a manageable size and keep all the connectivity between the streets, turns, signs, and even the traffic data?

There are a few ways to accomplish this, as outlined in this post.

Using Extracted Data from the Distributed Geodatabase Toolbar in ArcMap:

From the Distributed Geodatabase toolbar, select Extract Data.  In the Extract Data Wizard, check the box to ‘Show advanced options for overriding data extraction defaults when I click Next’.
Click Next. Choose the extent of the data to extract to a new geodatabase (when using an extent smaller than the full extent of the network dataset, the network dataset will be clipped to that extent during the extraction). Choose the feature classes to extract. By default, all feature classes in the map are checked, and the network dataset is one of those layers. Click Next > Finish.

Using the Consolidate Layer Geoprocessing Tool in ArcMap or ArcGIS Pro:

In the Data Management toolbox, select Package toolset > Consolidate Layer. Choose the input layers and the output folder. Choosing the network dataset layer (for example, Streets_ND) brings all source layers with it. Choose the output format. Choose the extent of the data to extract to a new geodatabase (when using an extent smaller than the full extent of the network dataset, the network dataset will be clipped to that extent during the extraction).

Create Mobile Map Packaging Tool in ArcGIS Pro:

Note: This is the best option if you plan to use routing in Navigator for ArcGIS.

Choose the input map(s) and the output location. Optional: Choose an input locator. If you want to use data in Navigator for ArcGIS, you must use an input locator other than the World Geocoding Service or the default XY locator. Choose the appropriate extent (when using an extent smaller than the full extent of the network dataset, the network dataset will be clipped to that extent during the extraction). Check the box to Clip Features.

With all methods above, your data will still allow routing and other network analysis, but will now be a much more manageable size for sharing with others.

Rachel A. – Desktop Support Analyst

Original author: Rachel

Copyright

© Esri

Continue reading
912 Hits

JavaScript Debugging Tips Part III – Advanced Google Chrome Developer Tools

This blog post is the third in a series of JavaScript debugging tips and tricks to help you on your way. See JavaScript Debugging Tips Part I  and also JavaScript Debugging Tips Part II for our previous segments.

In the past two JavaScript Debugging Tips posts on the Esri Support blog, we looked at the Network Tab and the Console Tab as part of the Google Chrome Developer Tools. While most modern browsers have some form of developer tools, here we use Chrome for our examples.

Our goal for this third blog post in the series is to introduce more advanced tips and tricks to enable you to more effectively debug and troubleshoot your JavaScript code. Specifically, we will focus on three areas: enhanced messaging to the console, better ways to set breakpoints using conditions specified at runtime, and a more efficient way of stepping through breakpoints in the Sources tab with a method called blackboxing.

Part 1: Console.table

Console.log is our primary debugging function, but this function’s output can be a bit difficult to read (especially when viewing a lot of data). One way to enhance our console log messaging and view data more easily is to display a list of objects as a table, which is accomplished using the console.table function. This function takes one mandatory argument, which must be an array or an object, and one additional optional parameter. Each element in the array is a row in the table.

Let’s take a look at the Console Table sample.

1. Open the Chrome Developer Tools by using shortcut keys (Windows: Control + Shift + I, and Mac: Command + Option + I), or by navigating to the top right-hand pane of the browser, clicking the three grey vertical dots, and choosing “More tools” > “Developer tools”.

2. Select the console tab.

3. Click “Perform Query” in the sample application. This performs a query task to view all counties in Connecticut. The code uses the console.table to print the results in a table as shown below.

console.table

Every row in the table shows all attributes for a specific county. Next, we use the console.log to compare the console.log and console.table. This function will print a line with an array of objects.

console.log

Once we expand the array, we can view the objects in a list.

console.log expanded

To view the attributes, we must expand the objects in the list.

console.log expanded with attributes

While we can access the attributes of one feature when using console.log, we can view all attributes for all features at once using console.table! The image below shows both functions in the console window.

console.table & console.log

Part 2: Conditional Breakpoints

In JavaScript Debugging Tips Part II, we talked about setting a breakpoint in the Sources tab, refreshing the application, and pausing the application at that line of code. This is a great way to examine your code and how functions are called, and where potential areas of trouble could arise.

However, sometimes we don’t want the breakpoint to be reached every time. Sometimes we only want the breakpoint to be reached if certain conditions are met. While we could write some logic code in the form of a loop to check for values, there is an easier way to do this at runtime.

For example, let’s look at a sample.

1. Open the Edit Features sample and the Chrome Developer Tools.

2. Navigate to the Sources tab, and left-click line 301 to set a breakpoint there.

3. After the breakpoint is set, right-click the breakpoint and select “Edit breakpoint…”.

Edit Breakpoint

Note: We could also get here by first right-clicking line 301 and selecting “Add conditional breakpoint…”.

Add Conditional Breakpoint

4. Set a condition whereby the breakpoint will be reached only if the user inputs “test” into the “Contact:” field when updating a feature. Here is the code: editFeature.attributes["Incident_Address"] == “test”

Note: We do not want to use “=” because this assigns a value and thus always returns true, so we must use “==”.

Breakpoint Expression

5. If we input “test” for the “Contact:” and click “Update incident info”, the breakpoint will be reached and the application pauses.

Condition Met

These conditional breakpoints can be useful for testing when you want to ensure data is sent back to the server correctly, or for error handling when you want the application to pause so you can inspect the object(s) of interest rather than letting your error handling code take over.

Part 3: Blackboxing

While setting breakpoints is a great way to make friends and go through your code, this process can occasionally kick you out of the file of interest and into another source file or into a third-party JavaScript library.

For example, let’s look at a sample.

1. Open the Query SceneLayerView sample to follow along (this is similar to the sample found on developers.arcgis.com).

2. Open the Chrome Developer Tools, select the Sources tab, and left-click line 49 to set a breakpoint.

3. Refresh the page so the debugger pauses on line 49. From here, a “Paused in debugger” message appears (next to a ”Play” button and a “Step Over” button). See below for a screenshot.

Paused At Line 49

4. If you click the “Step Over” button about five times, you exit out of the main .html file and into the init.js file of the ArcGIS API for JavaScript. You can explore the init.js file, but we want to focus on the code that we wrote. Click the “Play” button to get home safely.

Debugger in init.js file

Enter blackboxing to save the day. Blackboxing is a method to exclude files and libraries from the debugger, so that your focus remains on your file(s) of interest. Let’s take a look at how we can blackbox the ArcGIS API for JavaScript library so we can just step through the main file of interest.

1. With the Developer Tools open, click the three vertical dots in the far right-hand pane of the window and select Settings.

Developer Tool Settings

Developer Tool Settings

2. On the left-hand side of the window, click “Blackboxing” to open the “Framework Blackbox Patterns”.

Blackboxing

3. Click the “Add pattern…” button, and enter this framework pattern: js.arcgis.com.*\.js

Blackboxing Pattern

4. Click “Add” and check the box above the pattern input to “Blackbox content scripts”.

5. Close the Settings window and return to the Sources tab.

6. Refresh the page so the debugger pauses on line 49.

7. If you click the “Step Over” button about five times, you exit out of the main .html file and into the debugger:///VM file (this is an empty function which you can safely ignore, or read more about here), as well as complete one more “Step Over” operation into the application. Now rather than debugging unnecessary, ancillary libraries, you can focus on debugging the code you wrote or are trying to understand.

One last point worth mentioning is that blackboxing applies to the browser, not just to the webpage or web app of interest. After testing completes, feel free to remove the blackboxed pattern(s) to ensure a conventional web browsing experience.

This concludes our blog about advanced tips for using the Google Chrome Developer Tools with examples from the ArcGIS API for JavaScript. We hope you found the above tips useful and entertaining. For more information about debugging tips with JavaScript applications, here are a couple additional resources from the past several years:

Additional Resources

Join us next time as we continue to delve ever deeper into Developer Tools and learn some valuable lessons. Happy debugging!

Artemis F. and Noah S. – Esri SDK Support

Original author: Noah

Copyright

© Esri

Continue reading
1002 Hits

Declining Decimal Degrees in Survey123 for ArcGIS

Whether you are a new user or a power user of Survey123 for ArcGIS, you know it is an extremely useful and powerful tool for collecting data in a form-based environment. In typical workflows, Survey123 for ArcGIS is used to store a spatial component of your data. In this post, I’ll provide a brief introduction for using calculations in Survey123 for ArcGIS to convert decimal degrees (DD) to degrees-minutes-seconds (DMS) and extend the application to better fit all survey requirements.

When we create our surveys in Survey123 Connect, the desktop application, we have the option to choose the display format of the coordinate. We can do this for both the preview map and the detailed map. However, this is solely a display functionality because the data is saved to ArcGIS Online. The default coordinate system for services published by Survey123 is WGS 1984 Web Mercator, meaning all data is saved in DD regardless of how it appears in our map viewer. While DD may look nice and evenly spaced online, we in the GIS world know that this doesn’t always meet every need.

There is no way to change our coordinate system of the data in ArcGIS Online hosted feature services, and the the pulldata(”@geopoint”) function will only capture DD. However, we can take full advantage of the Survey123 for ArcGIS’s calculation fields to determine both DMS and decimal minutes (DDM) coordinates for our data. Since we determine DDM and DMS values in our survey, we can create this information on-the-fly and save it into the form response. While this process doesn’t change the coordinate format, you can save valuable time should you need this information.

As these calculations can be quite complex, here’s a sample survey that does everything for you! Copy and paste the sections you need to add DDM or DMS values to your survey. On your survey form, a new field depicting the value you want appears. Due to how the application is making these calculations, all our in-between steps appear in the data. Happy survey-ing!

Sample Survey

Andy S. – Desktop Support Analyst

This entry was posted in ArcGIS Mobile and tagged , , . Bookmark the permalink.
Original author: ashoemaker

Copyright

© Esri

Continue reading
1047 Hits

Recover Lost Licenses from My Esri

Nobody likes to talk about it, but sometimes computers can crash.  Yup, the entire thing just fails and nothing at all can be recovered (if you haven’t backed up your data, go do it now!) Or what if your laptop is stolen, or you flipped your kayak and your machine sank to the bottom of Lake Superior?  You just don’t have it anymore and there is absolutely nothing you can do to get it back. When these types of things happen, any Esri licenses that were authorized on the machine may be lost, too.

In the past, an authorized maintenance contact had to call Esri Technical Support to submit a license appeal and recover the lost licenses.  Now, this functionality is built in to My Esri, empowering your organization with self-service functionality and enabling you to get back up and running quickly.

I wanted to make sure that our customers are aware of this great new functionality and walk through how you’d go about getting your licenses back in the event of a catastrophic failure or loss as described above – though I really hope that never happens.

To perform the following steps, you will either need “Esri Admin” permission or the “Take Licensing Actions” permission. Sensitive information such as machine IDs, license numbers, and other personal information have been replaced with asterisks in the following screenshots.

First, log in to My Esri and click the My Organizations tab.

Please note that I’m demonstrating the steps in a QA environment and that your experience won’t include the green QA…

My Esri's My Organization Tab

Click the Licensing tab.

Licensing Overview

This will bring up the Licensing Overview page and if you have the correct permissions, you should see the Recover Lost Licenses option both in the Licensing panel as well as a card.

Next, click Recover Lost Licenses.

The Recover Lost Licenses screen explains that this is a process to retrieve licenses from a machine that is no longer accessible due to system failure, system loss, or destruction. The License Recovery process requires the signature of the organization’s License Administrator in a Certificate of Destruction. This process is irreversible and should only be used as the absolute last option when all other solutions to rectify the problem have failed.

An example of when you would not use the Recover Lost Licenses option is if you can still access the machine and deauthorize the licenses normally. The instructions provided describe how to perform standard license deauthorization:

Once you’ve determined that it really isn’t feasible to scuba dive to the bottom of Lake Superior to recover your machine (and hence, its licenses), follow the steps outlined below to complete the recovery.

Step 1: Find Your Machine

To proceed with license recovery, select how you would like to find the machine. There is an option to search by products on the machine or use the machine’s UMN IDs if you know those.

Step 1. Find Your Machine

Step 2

Option A: Search for machine by product

Search for the machine by populating the dropdown boxes.

Search For Machine

Click Search.

We see that the search for ArcGIS Desktop Advanced Concurrent Use licenses for this organization returns five machines.

Selecting the machine from which the licenses need to be recovered will take you to Step 3.

Option B: Select Machine using the UMN

Enter the UMN for the machine and click Search.  Since the UMN by definition is associated with a single machine, you should get only one result in this case, as opposed to searching for a machine by product.

Click Select to take you to Step 3.

Step 3: Review Selected Machine

This step will show you a list of products our records show were activated for the selected machine.

After reviewing the selected machine, you have the option to go back if this is not the correct machine or proceed with the license recovery process.

Step 4: Accept Terms and Conditions

Review and agree to the terms and conditions, and click Next.

Step 4. Accept Terms and Conditions

Step 5: Summary to process License Return

This step gives you another opportunity to fully review the selected licenses to return. If the selection is correct, click the “Process Return” button near the bottom of the page.

You’ll receive a confirmation screen showing the status of each license return.

And that’s it.  You are now able to authorize these licenses on a new, dry machine!

In the event that not all licenses are returned successfully, you will be presented with a summary of which licenses were returned and which were not. These should be exceptions; not the norm. In these cases, please work with Esri Customer Service or your local distributor to finalize the recovery process.

Kory K. – Customer Advocacy Lead

Original author: Kory K

Copyright

© Esri

Continue reading
1181 Hits

Creating a Custom Widget for Web AppBuilder for ArcGIS using the Report Class

Creating a Custom Widget for Web AppBuilder for ArcGIS using the Report Class | Support Services Blog

Esri is an equal opportunity employer (EOE) supporting diversity in the workforce.

DCSIMG
Original author: Artemis F.

Copyright

© Esri

Continue reading
1342 Hits

Esri Support Update: Using My Esri and the Request Case form

As always, Esri Support aims to make your time with us as simple and pleasant as possible. We are constantly reviewing the ways we interact with you and making improvements so that you receive the best possible support from our highly qualified team of analysts.

Starting on April 3rd, we are deprecating the This email address is being protected from spambots. You need JavaScript enabled to view it. email address as a method for creating an Esri Support ticket. Instead, we request that all Email and Chat cases be created through the Support website.A courtesy message may appear, stating that:

This email address is being protected from spambots. You need JavaScript enabled to view it. is on a permanent vacation. For even better assistance, log into My Esri.”

Many customers already use the website to request new cases. Clicking the “Request Case” link on the Support site prompts you to sign in and then opens the Request Case web form. You can use this web form to describe the issue you are facing and the Esri software product you are using. By using the preformatted web form, rather than an email, we can quickly route your case to a specialized Support Analyst who can begin helping you right away.

Support cases can also be opened from the Support page on My Esri. This means that all Support resources will be in one place – the creation, tracking, and history of case work all occurs through My Esri. When a case is requested through the web form, the process of creating the case and routing it to the right analyst is optimized and streamlined, so customers will be connected faster than they would if emailing directly.

We’re very excited for the changes and updates being made to our Support website, and we’re looking forward to providing even better support as a result!

Melissa Q. & Joseph M. – Support Services

Original author: Joe

Copyright

© Esri

Continue reading
1439 Hits

A Survey: Your Esri Online Support Resources

Here at Esri Support, our goal is to provide you with a world-class support experience and ensure your success with the ArcGIS Platform–one element of this experience is online support.

Including this blog, Esri creates and maintains a vast network of online support resources, such as Support.Esri.com (which hosts a technical article knowledgebase, download links, product life cycle documentation, and more), Wiki.GIS.com, GeoNet forums (Esri Support actively uses the Esri Technical Support and ArcGIS Ideas places), the GIS Dictionary, among others.

For us to continue creating the best resources possible, we request your feedback through a brief survey: Esri Online Support Resources Survey.

Your responses will help us understand your online support preferences and how Esri can deliver the resources you need.

Thank you in advance, and we look forward to supporting you in the future!

Other Resources

Megan S. – Online Support Resources

Original author: Megan

Copyright

© Esri

Continue reading
1723 Hits

Support Services at the Esri Developer Summit: March 6 – 9, 2017

Are you going to the Esri Developer Summit this year? Perhaps you have some questions or need help and would like some special assistance from our Technical Support Analysts? Come see us at the GIS Technical Support Island (TSI) in the Esri Showcase.

The GIS Technical Support Island at Esri Dev Summit 2017

Esri Technical Support will have ten senior analysts available each day of the Developer Summit to assist customers with any technical questions or issues they may have with Esri products. These analysts are subject matter experts that span the many parts of the ArcGIS platform, so we should be able to help with most questions. However, if the problem is more complex, we will create a Support case and contact you later when you’re available. We will be stationed right next to several other Esri services, including Consulting, Training, and Cloud Management. If your questions lead us to a conversation about one of our other services, we will connect you with an expert in that area, as well.

In Support, each of the following teams and specialties will be represented:

Esri Support at Developer SummitOutside of the TSI, you can find Support Analysts throughout the summit, including at different sessions, demo theater presentations, and the Meet the Teams event.

Stop by and say hello!

Gregory L. – Online Support Resources

Original author: Greg Lehner

Copyright

© Esri

Continue reading
1781 Hits

JavaScript Debugging Tips Part II – Google Chrome and the Console Tab

This blog post is the 2nd in a series of JavaScript debugging tips and tricks to help you on your way. See JavaScript Debugging Tips Part I – Google Chrome and the Network Tab for our first segment.

The most enjoyable part of any programming assignment is right near the beginning when you sit down with a pile of tools and resources and start hammering away at raw clumps of code. The more difficult part comes when you attempt to launch the application, only to watch that tightly-written code unravel into multiple late nights staring at a computer screen. However, all is not lost, as we have an excellent recommendation for you, which is the subject of this blog: the Console tab inside your favorite browser’s Developer Tools.

If you’re feeling upset or emotional, the Console tab is the perfect choice for you. Maybe someone in your family is dealing with a difficult time, and could use some cheering up. Consider the Google Chrome Console tab (gluten free options are available). Users who like the Console tab might also enjoy the ArcGIS API for JavaScript.

I obviously do not understand homographs

I obviously do not understand homographs

As we wrote in Part I, accessing the Chrome Developer Tools is easily done using shortcut keys (Control + Shift + I) or by navigating to the top right of the browser, clicking on the hamburger and choosing “More Tools”, then “Developer tools”.

Once the Developer Tools are open (other Developer Tools are available in other browsers), there are several Tabs that become accessible to you. Here we will focus on the Console. If you want to open the Console tab in Chrome Developer Tools directly, use this keyboard shortcut: Control + Shift + J (the “J” stands for jocular). For more neat tips, please check out the official Google documentation about Chrome DevTools: Using the console.

The Console is used for two purposes: 1) to display logged information from an application’s JavaScript (usually during application development), and 2) to interrogate objects and execute JavaScript interactively. In this blog, we will look at both kinds of examples, and elaborate on some additional tips and tricks that we use in Technical Support.

The first thing we can do is to add some “console.log” statements inside our application. We will take a modified sample, hosted on GitHub, which can be found here: Sample Console Application. Feel free to follow along at home.

At lines 60-62, and again at line 66, we’ve added some of those “console.log” statements to display information about our Feature Layer. Our use case is that we are creating a web mapping application, and during our testing, we want to ensure that the data we are consuming from ArcGIS Online is the correct data to display on the map. To this end, we print out a few choice pieces of information about the Feature Layer: the title of the layer, and the URL of the layer. Since I do not know the syntax for the URL property, I use “URL” and “url” as seen below.

JavaScript console.log statements

JavaScript console.log statements

Here is a screenshot of the output of the “console.log” statements. We see the relevant information we were expecting. Also, please note that the output for “featureLayer.URL” is “undefined”. This is because items in the console are case sensitive. The valid property is “featureLater.url”, and invalid properties do not throw an error, and instead return an undefined result. This can be a tricky thing to trap, but later on in this blog we will look at some tips for dealing with this sort of issue.

JavaScript Console Output from console.log

JavaScript Console Output from console.log

With the Console still open, let’s try entering the same property values from the code:

featureLayer.title
featureLayer.URL
featureLayer.url

Notice that all of these properties now return an error, instead of an actual value (or even “undefined”). This is because the local variables are no longer in scope after the app is initialized, so even the “featureLayer” object cannot be recognized.  Here is a screenshot of the output of the new console statements.

JavaScript Console Output after App is loaded

JavaScript Console Output after App is loaded

If we had made “featureLayer” a global variable, we would then see “undefined” returned for the object in the Console (variable is known, but the details are still not accessible). The point is: only variables that are in scope can be interrogated in the Console. So can we use the Console interactively and type in property values? Let’s find out.

The next thing we can do to our sample app is to add a “debugger;” statement in the code. We will take another modified sample, hosted on GitHub, which can be found here: Sample Console Application 2. Feel free to follow along at home.

At line 60, we’ve added a “debugger;” statement to help display information about our Feature Layer in the Console.

JavaScript debugger statement

JavaScript debugger statement

How does this statement work? Click the link to run the application. Then, open the Developer Tools (Control + Shift + I or Control + Shift + J), and refresh the application. The application should pause, and you should see a “Paused in debugger” message at the top of the screen, and the “debugger” line highlighted in the Sources tab:

Paused in debugger 1

Paused in debugger 1

Now, with the application paused, we can go back to the Console tab, and try interrogating the featureLayer properties again. Here we see that we have proper scope to the variable and we can see the output:

Paused in debugger 2

Paused in debugger 2

Cool, right?

Let’s look at another option, similar to “debugger”. Back to the Sources tab, notice the line numbers to the left of the code. If we left-click on a line number, we can set a breakpoint, which will have the exact same effect as writing “debugger” in the code. Left-click on lines 56, 62, and 66 in the same application, then refresh the application.

Breakpoint 1

Breakpoint 1

The application pauses immediately at the first breakpoint. Now, we could go back to the Console tab and again inspect variables and properties to our heart’s content. Not only that, by clicking the curved arrow to the right of the Play button at the top of the screen, we can step through our application and watch the excitement as we see how the code executes step-by-step. Or, we can click the Play button at the top of the screen, and let the application run to completion, or to the next breakpoint.

Breakpoint 2

Breakpoint 2

And another Play button click brings us to the next breakpoint.

Breakpoint 3

Breakpoint 3

The point of this blog is to highlight the usefulness and functionality of the Console, but we do want to point out another usage of setting breakpoints here as well. Breakpoints allow the developer the ability to see the order in which asynchronous code executes, how functions are run and what parts get skipped or fail. For more information about debugging tips with JavaScript applications, here are a couple additional resources from the past several years:

In this installment, we learned how to access and use the Console tab inside Chrome Developer tools to reveal the properties and values of variables and objects in our JavaScript code. This information can greatly facilitate the debugging and coding of a web-based application. This concludes part two of a multi-part series on JavaScript Debugging Tips. Join us next time when we delve even deeper into some Developer Tools, and we all get raises. Happy debugging!

Noah S. and John G. – SDK Support Services

Original author: Noah

Copyright

© Esri

Continue reading
2698 Hits

WWTSD (What Would Tech Support Do?)

Tips for figuring out what is going on when things aren’t working in ArcMap

Have ever you called Esri Support Services (ESS) with one question and the analyst asks you a seemingly unrelated question? Perhaps you are trying to open a DBF in ArcMap, and we want to know what version of Excel you use. Or perhaps you cannot access printing drivers and we ask you how much memory ArcMap is using. Sometimes the questions we ask can seem random, but they help us narrow down the root cause of the problematic behavior. Most processes in ArcMap involve multiple parts and file locations, so it can be difficult to determine what drives a specific behavior without taking a systematic approach to ruling out possible causes. To that end, this post provides a series of questions that will help you narrow down what may be causing problematic behaviors.

Do you Meet the Minimum System Requirements?

This is a simple question and hopefully one that was asked prior to installation, but it is always encouraged to check, particularly if you recently upgraded your software. A quick way to check if you meet the system requirements is to use the Can You Run It tool. If your system does not meet the requirements, you may need to upgrade your system.

Does ArcMap Open?

If ArcMap does not open, or crashes when opening a new, blank map document, this indicates that either something is wrong with the installation of ArcGIS Desktop or with the local customization of the program. In this case, here are a few troubleshooting steps:

Perform a soft reset (remove local customizations including folder connections and toolbar arrangement) by renaming the “C:\Users\<USERNAME>\AppData\Roaming\ESRI” folder as “Esri_old”. When you reopen ArcMap, the folder is re-created.

Note: the AppData folder is a hidden folder, so you may need to unhide it.

Repair the software by navigating to Control Panel > Programs and Features > right click on ArcGIS Desktop > Uninstall/Change. Select the option to repair. Once the repair is finished, reboot the machine and test again.

Is the Issue MXD Specific?

When encountering a problematic behavior in ArcMap, a good place to start is to determine if the problem only occurs in a specific MXD. You can do this by opening a brand new MXD, dragging and dropping the data from the original MXD to the new one, and then trying to reproduce the issue. You can also copy and paste layout elements from one MXD to another. If the issue does not occur in the new MXD:

Use the new MXD you created to test if everything is working correctly. If you have elements that cannot be easily copied and pasted from one MXD to another, use the MXD Doctor utility.

Stay tuned for an upcoming blog on MXD troubleshooting!

Is the Issue Workflow Specific?

Many users have multi-step processes in ArcMap as a part of their workflow; however, the more steps used, the more likely it is that an error can creep in. An error early on in a multi-step process can make it difficult to determine the root cause, as the issue can be introduced several steps before being observed.

Some steps that can assist in sorting out these workflow issues are:

Write out the entire workflow from data acquisition to the step where the issue is seen. Teach the workflow to someone else. Often we only catch our mistakes when we have to explain what we did to another person. If you are using a script or model to perform a workflow, try the same workflow manually. If it works manually, break the script or model into parts and test each part individually.

Is the Issue Data Specific?

If the issue still occurs when you move the data to a new MXD, it is possible that the issue is data specific. To see if this is the case, test similar data that is stored in the same location, is in the same format, and contains similar features. For example, if you have trouble editing a shapefile containing points, edit a different point shapefile. If you do not have appropriate data to test with, you can also create a new shapefile, add some features to it, and test with that. If the issue only occurs with a specific dataset, then it is possible to take some basic data troubleshooting steps such as:

Export the file to a different format (for example, export shapefile to feature class or GRID raster to TIFF). With vector data, try the Check Geometry and Repair Geometry tools. If the data does not draw in the correct location, check the projection. If the layer was created in one projection, and the projection was not correctly assigned to the data, it can draw in unexpected locations. For more information about figuring out what projection data was collected in, see here.

Is the Issue Location Specific?

Another potential cause of unexpected behavior is the location of the data. Location includes both the physical location (local machine drive versus server) and the workspace (geodatabase or folder). If the data is being accessed over a network, any issues or restrictions on the network may affect the way the data behaves in ArcMap. Likewise, any issues or permission limitations in the geodatabase can contribute to problematic behavior. If you suspect the issue is location specific:

Move the data. If it is in an SQL database, move it to a file geodatabase or another SQL database. If it is on a network drive, move it to a local drive, then see if the issue persists. Ensure you have appropriate permissions for the location of your data.

Is the Issue Install Specific?

If the problematic behavior persists in all MXDs and with different datasets in different locations, there may be an issue with the installation. It is possible that either the installation file was corrupt or that the file was corrupted after installation. The troubleshooting steps in this case are the same as those for when ArcMap does not open at all. If you suspect the install file might have become corrupt during download, you can re-download the install file from My.Esri.com and reinstall.

A diagramatic view of the ArcGIS troubleshooting workflow

The Internet Is Your Friend (Mostly)

Most of the time, you aren’t the first person to experience a particular issue and chances are, you can unearth some relevant findings on the internet. A good starting place is always ArcGIS documentation. If an issue is particularly common, it may be documented in Esri’s Knowledge Base, a collection of technical articles written by Esri staff. Larger issues, such as troubleshooting ArcMap performance or not being able to load Esri basemaps, may have been topics on the ArcGIS Blog or Support Services blog. Additionally, Esri hosts a very active user forum, GeoNet, where developers and other members of the Esri community can ask or answer posted questions. However, if you do find a suggested workflow, always remember that what works for someone else may not work for you. Therefore, it is highly encouraged to make copies of any MXDs or data, and proceed with caution.

Call ESS

The above steps do not address all possible issues, but they are effective and thorough starting points when trying to narrow down issues in ArcMap. If you still cannot narrow it down, give Esri Support a call! Our job is to assist you with these particular issues, and we always enjoy helping our customers resolve whatever issues they may be facing! When you do have to call, we kindly ask that you have the following information available so we can route you to the best analyst for the job and ensure that analyst has the information needed to begin troubleshooting with you!

Software version and license level Operating system Device, if using a mobile application Synopsis of the issue Detailed workflow Error message Test data

Note: You can contact ESS through phone, web chat, and web form. Start here.

We look forward to hearing from you!

Rebecca R. – Desktop Support Analyst

Original author: Rebecca

Copyright

© Esri

Continue reading
3400 Hits

Gauging ArcGIS GIS Server Performance with Integrated Windows Authentication

If you want to know how much traffic your ArcGIS Server site can handle, you’ll have to thoroughly test. And because you’re probably not going to convince thousands of people to log on to your apps and services all at once, you need something like JMeter to perform load testing.

My first introduction to performance testing, and really just the JMeter in general, was with this awesome blog post from Randall Williams. I eventually started to use JMeter widely and also suggested users to run a sanity check and load test their GIS environments before moving to production.

In the enterprise world, a domain-based approach is widely used for secure authentication and authorization, where credentials of currently logged in Windows users are seamlessly passed to web applications, allowing single-sign-on. JMeter lets you emulate requests being sent from a real user by constructing relevant headers and passing them along with the request. This post focuses on configuring JMeter to perform load testing when the services are secured with Integrated Windows Authentication (IWA).

Here, I assume you have already installed JMeter and created a test plan. If you haven’t, fret not! Refer to this blog for a detailed walkthrough: Preparing for the flood: Will your GIS Server sink or swim?

Once you have modified ArcGIS Server for Windows Authentication, you can forge ahead with adjusting JMeter to handle the authentication challenge. Here are the steps:

1. Navigate to the JMeter bin directory (apache-jmeter-2.7/bin).

2. Open the file jmeter.properties in text editor and set to the following:

httpclient.parameters.file=httpclient.parameters

3. Save and close the file.

4. Open the file httpclient.parameters and set to the following:

http.authentication.preemptive$Boolean=true

5. Save and close the file.

6. You must use the HTTP Authorization Manager configuration element to construct a relevant authentication header. The Authorization Manager lets you specify one or more user logins for web pages that are restricted using server authentication.

7. Complete the HTTP Authorization Manager as follows:

Username: “User logon name” for Windows domain
Password: Windows domain password
Domain: [DOMAIN]
Other fields like “Base URL” and “Mechanism” can be left as it is.

To accurately simulate the users, you can setup each thread to login with different credentials by placing an HTTP Authorization Manager configuration element in each thread group element.

Tip: You can add a ‘View Results Tree’ listener to debug your test plan. Thus, you can review the request and response data to ensure that your test plan works well.

Below is a sample request with the Authorization Manager disabled:

Below is a properly configured HTTP Authorization Manager:

Here you can see JMeter sending authentication information in an Authorization header: NTLM.

Because the way Microsoft NTLM (also known as Windows Challenge/Response) and IWA work, the first few requests return a 401 response as part of the NTLM handshake scheme. This means that for the first request, you might encounter an unusually high response time.

This should help you understand how your services from ArcGIS Server would perform with Windows Authentication security. You may have a more complex situation if more Active Directory domains are involved (for example, domain trusts, forest trusts, complex nested groups, and so forth), or if there is a performance issue with your domain controller. Head over to your Active Directory Administrator for more information. If there’s a performance bottleneck that cannot be eased, you may want to use the other type of security scheme.

Happy load testing!

Divyam Gulati – Server Support Analyst

Original author: Divyam Gulati

Copyright

© Esri

Continue reading
2599 Hits

Tips and Tricks for Working with 3D Data on the ArcGIS Platform

3D data is becoming more ubiquitous nowadays and is especially promoted throughout the ArcGIS Platform. From web scenes, to CityEngine, to ArcGIS Pro, there are many different applications to import, manage, model, and share your 3D data. To get the output you are looking for, it may require numerous steps and tools. To navigate some of these steps and tools, here are some tips and tricks for working with 3D data in ArcGIS.

3D File Coordinate Systems

The majority of 3D formats do not store a coordinate system. GeoVRML and KML are the lone exceptions. KML will use a WGS 1984 coordinate system and meters for the unit of measurement. All other types (DAE, 3DS, OBJ) must be placed properly, otherwise they may import at “0,0″ (off the coast of Africa).

Trick #1

If you are using CityEngine, you can drag and drop your shape from the Navigator window into the scene (this workflow assumes a scene coordinate system is already set). When you export the shape to a multipatch feature class, the coordinate system is created with the data so you can bring it into another ArcGIS product.

Import Overview

Trick #2

The same workflow can be accomplished in ArcGIS Pro. Create an empty multipatch feature class, navigate to Editor > Create Features > Select Model, and click the globe to place the model.

Trick #3

Use the Replace with Model tool (ArcScene or ArcGlobe) or the Replace with Multipatch tool (ArcGIS Pro).

ArcGIS Desktop Replace with Model

ArcGIS Pro Replace with Multipatch

Trick #4

If you are using ArcScene, ArcGlobe, or ArcGIS Pro, manually place the model during an edit session using the Move, Rotate, or Scale operations.

Move, rotate, or scale a feature

Note: There is known issue with the Import 3D files tool. The placement points parameter is not honored so as of ArcGIS 10.4.1 or ArcGIS Pro 1.3, this tool is not a viable option. This issue is planned to be fixed in a future release.

Textures

To import your 3D file with textures, you must ensure the texture resides next to the 3D file, either as an individual image file or a folder with the images.

Note: Both the file and folder must have same name for the software to recognize the texture.

Trick #1

Textures are only supported in file or enterprise geodatabases. Shapefile multipatches do not support textures, so make sure to import the multipatch into a geodatabase.

Z-values

Make sure your 3D data has valid z-values. When sharing a web scene or importing the data into ArcGIS Pro, you want to make sure the elevation values are correct.

Trick #1

If your multipatch is not at the correct elevation, you can use this trick. In ArcGIS Pro,

set the multipatch data “on the ground” and use the Layer 3D To Feature Class tool. The elevation values are then embedded into the multipatch.

Trick #2

If you are using simple feature data (non-multipatch), use the Add Surface Information tool to add z-values to the data. Also, you can add z-values to an attribute table and with the Add Z Information tool, you can verify the values with the tool’s output. If the data does not have valid elevation values, see the next tip.

Tools to Create 3D Data

Understand which tools can create 3D data: Layer 3D To Feature Class, Interpolate Shape, or Feature To 3D By Attribute.

Understanding 3D Data

Understand your 3D data. Extruded 2D polygons are not true 3D features, so you must export to multipatch to make the polygon a true 3D feature. Simple point, line, and polygon features can be considered 3D data if they have the correct z-values. 2D features can also be symbolized using 3D marker symbology.

Know the difference between a z-enabled feature class and a non-z-enabled feature class with a z field in the attribute table. Feature classes must be z-enabled to display at the correct elevation. You might see a z field in the attribute table, but that does not mean the geometry has the correct z-values. This can be verified by editing the vertices or adding z-values to an attribute table, as described above.

While this blog does not cover every facet of working with 3D data, it is my hope that this will provide some valuable information for working with 3D data on the ArcGIS Platform.

Andrew J. – Desktop Support Analyst

Original author: Andrew J

Copyright

© Esri

Continue reading
2923 Hits

How can I use the new ArcGIS Pro PerfTools Add-in?

I’ve installed the new PerfTools add-in for ArcGIS Pro; what are some scenarios in which this new tool can help optimize performance?

Displaying and Logging Rendering Time for Specific Spatial Extents

Have you created a series of spatial bookmarks in your ArcGIS Pro project? A one-line script command (ZoomToBookmarks all) can zoom through these spatial bookmarks and log draw time, frames per second (FPS) metrics, and other timestamps. No bookmarks?  No problem…you can also specify extents by providing 2D or 3D camera positions in the same spatial coordinates as your data.

Playing and Timing Animations

Have you added an animation? Using the PlayAnimation command returns measures of total elapsed animation time, as well as average and minimum FPS.

Roaming

To build a thorough display cache or simulate navigation through large datasets without specifying bookmarks or camera positions, you can use the roaming capabilities of PerfTools. This allows you to virtually “walk” across the active view, starting from the upper left and moving row-by-row towards the lower right. The total draw time, in addition to average and minimum FPS, are logged for your reference.

Timing Spatial Selection

Moving from a file geodatabase to an enterprise geodatabase? Or have you updated your spatial index? You can examine the impacts these changes have on making spatial selections in ArcGIS Pro. The SelectFeatures command allows you to specify your selection bounding box in screen coordinates on the active 2D or 3D view. PerfTools logs a count of the features selected, as well as the selection and draw complete times.

Scripting Commands

Most power from the PerfTools add-in comes through a comprehensive scripting language that allows you to assemble several commands into a more comprehensive scenario. With this functionality, you can simulate typical user interactions with ArcGIS Pro, including creating and opening projects, panning, zooming, selecting, and so forth. You can add delays or “think time”, as well as looping commands (ForCount, ForFile, ForFolder, and ForTime) to repeat key parts of your workflow. Via script command, you can also control key aspects of logging content and structure in PerfTools.

Custom Script Commands

Not finding the script command you’re looking for? PerfTools allows you to create your own commands through leveraging the ArcGIS Pro SDK. Part of the PerfTools download includes documentation and a sample, “T1Command”, that gets you started with your own customizations.

Is PerfTools comprehensive? You bet! We’ll be taking a closer look at some of these techniques in upcoming blog posts. In the meantime, feel free to download the PerfTools AddIn and try it out for yourself!

Ian S. – Performance Engineer

About Ian Sims

Product Engineer at Esri (Redlands). Originally from Warwickshire, England. Exploring, mapping, and photographing the world are my biggest passions.
Original author: Ian Sims

Copyright

© Esri

Continue reading
3397 Hits

Geocoding Improvements and Deprecations in ArcGIS Desktop 10.5 and ArcGIS Pro 1.4

With almost every new release of ArcGIS Desktop and ArcGIS for Server, there are changes that aim to improve software quality and performance–sometimes, these changes require you to update your workflows. The improvements and deprecations made for geocoding in ArcMap 10.5 and ArcGIS Pro 1.4 may break some existing workflows or require you to prepare before installing ArcGIS 10.5. In this post, we’ll give you an overview of these changes. 

1. Address locators stored in geodatabases are no longer supported, as specified in the deprecation notice for ArcGIS 10.4 and 10.4.1. As such, you must move or copy the address locators from the geodatabase to a file folder before installing ArcGIS Desktop and ArcGIS Server 10.5. By doing this, you’ll avoid the following issues in ArcGIS 10.5:

Address locators currently stored in geodatabases do not display as inputs to tools nor are visible in ArcCatalog when viewing the geodatabase content. Starting a geocode service published from an address locator that is stored in a geodatabase fails to create an instance and returns an error in the server logs. Publishing an address locator stored in a geodatabase or an .sd file that references an address locator stored in a geodatabase directly to ArcGIS Server 10.5 will return an error in the server logs.

2. We made several improvements to the US Address locator styles, such as reordering and adding fields to the Field Map. However, these improvements break any existing workflows that use Python scripts and Model Builder models to create address locators. These issues occur without an error or warning message and render the address locators unusable. Furthermore, geocoding services created from these locators and used in web applications are impacted in ArcGIS 10.5.

To avoid these issues, update the field mapping in the scripts and models after installing ArcMap 10.5 and ArcGIS Pro 1.4 but before running the scripts and models. There are also additional output fields that display in the geocode result that are similar to the output fields of StreetMap Premium and the World Geocoding Service.

3. If it is necessary to continue using the US Address locator style from ArcGIS 10.4 to create address locators after installing ArcGIS Desktop 10.5, contact Esri Support Services to request access to the USAddress.lot.xml file.

In the near future, our teams will publish a technical article that covers more detailed solutions to the aforementioned issues.

Shana B. – Product Engineer

Original author: Megan

Copyright

© Esri

Continue reading
3149 Hits

Announcement: Errors Encountered in ArcGIS for Server and Portal for ArcGIS Web Apps after Certain Browser Updates

The forthcoming updates to the Firefox, Chrome, and Safari browsers cause errors in some web applications for ArcGIS for Server and Portal for ArcGIS when users upload content.

The following browser versions are affected:

Firefox 49 (Expected Release Date: September 20th) Chrome 54 (Expected Release Date: October 18th) Safari 10 (Expected Release Date: Fall 2016)

Note: Microsoft Internet Explorer and Microsoft Edge are not affected.

The following ArcGIS products are affected:

ArcGIS Server 10.2.x, 10.3.x, and 10.4.x Portal for ArcGIS 10.2.x, 10.3.x, and 10.4.x

The following workflows are affected:

Portal for ArcGIS Home Application

Uploading content via “My Content” > “Add Item” > “From my computer” Uploading content to the Portal for ArcGIS Map Viewer via “Add” > “Add Layer from File” Adding attachments when editing features in the Portal for ArcGIS Map Viewer Updating thumbnails on any Item Details page or via “My Organization” > “Edit Settings” > “General” Updating the banner or background images via “My Organization” > “Edit Settings” > “Home Page”

Below is an example of the error encountered when attempting to upload content in the Portal for ArcGIS home application.

An example of the error which can be seen when trying to upload content to the Portal for ArcGIS Home App

This example shows the error which can be seen when trying to upload content to Portal for ArcGIS

ArcGIS Server Manager

Uploading service definitions (SD) when publishing services Uploading SDE database connection files when registering a database as a data store Uploading SOE or SOI files when adding extensions Uploading KMZ files

Below is an example of the error encountered when attempting to upload an SD in ArcGIS Server Manager.

An example of the error seen when uploading content to ArcGIS Server Manager

This example shows the error seen when uploading content to ArcGIS Server Manager

To resolve these errors, Esri is developing software patches for ArcGIS for Server and Portal for ArcGIS. We will keep you informed as the patches become available.

Thomas E. – User Advocacy

This entry was posted in Announcements, ArcGIS for Server, High Priority and tagged , , , , , , , , , . Bookmark the permalink.
Original author: Thomas Edghill

Copyright

© Esri

Continue reading
2940 Hits