Latest Contributions by DEWright_CA

‎05-08-2019

You can never go wrong with more RAM; that is a great place to consider. Also consider the HDD; since Arc using a fGDB for it's scratch space the more you have that is faster (SDD) gives you some good flexibility.

‎05-03-2019

The current version of ArcGIS Monitor does not work well in a vertical context monitor; in the case where you have a 20"/24" wide-angle monitor: but have it vertical and have the monitor vertical then the navigation at the top becomes inconsistent; and access to the content area gets blocked by the obscured navigation. Now when you try to access content areas such as the ArcGIS Block: Now you will need the top navigation is gone; the menus have shifted below and the ability to expand/navigate the content tree in the left panel is lost.

‎04-17-2019

This would be a great addition; with users losing functions from ArcPad; and not wanting to build new in AppBuilder; getting this basic function set in Pro would help fill a good gap where Tracking-Analyst is way overkill.

‎04-01-2019

The drawback here is that with AGS/Portal being principally Java-Servlets you will find these are not easily able to write to the Windows Event Log. Short of that; it would be good to have a better logging mechanism that will support viewing the logs for Server and Portal outside of the Web-Interface which isn't very flexible for searching.

‎04-01-2019

I would be worried about this proposal; with each version of Pro being tied to the current/latest version of Enterprise you might find that a location built in Pro 2.4 not being fully supported backwards to 10.6.1. I have found that comparing the Locator template xml file shows some major differences.

‎01-31-2019

Sadly there is not a great answer for this issue. You are correct in noting that the default workaround from #ESRI is to export the view to a FeatureClass so you take out the performance hit of the view/joins to smooth things. One way I mitigated this in MSSQL was to build a Spatial-Index on my view; this help immensely. The other option I would recommend for you is to throw as much RAM at the SQL server as possible; as the Server instance caches data in memory; the more memory it has available to keep from paging back out will help you in the long run.

‎11-27-2018

Major points to consider; unless you have very deep pockets and have very large pipes to Azure; performance will always be an issue. The typical LAN/WAN interface will be 1GB between desktops to switches to your RDBMS server. Once you start trying to take the volume of data you would typically have in the eGDB and put in in the cloud; now you are going through things like firewalled or VPN connections, multi-hop connections between ISPs and finally the M$FT cloud. Make sure the data you are wanting to work with there is designed for that purpose; the more data you have, the more reads/caching will happen and this will slow you down. Also, consider that some of the Azure & AWS data hosting solutions also charge for throughput, so if you are working with large datasets and will be doing lots of reads/writes that bump that number you might see costs skyrocket....

‎11-27-2018

I would also consider looking at your Performance Monitor; get a look a the amount of memory each SOC is using and the amount of total SOCs running. Considering the performance hit of apps/service hitting the local pagefile; you may also be seeing a memory/swap contention type issue. I usually shoot to have 128-256mb of RAM for each expected SOC; and when I am looking at setting up services for things like GeoProc I will have these create/write/delete a intermediary fGDB and avoid using InProc layers/features.

‎11-21-2018

What kind of services are you running that you see this issue with? Composite Geocoders can cause a larger load due to the nested data access. Also various Geoprocessing tools can cause a spike after various OS patches to address security exploits from earlier this year. Also consider taking a look at your Anti-Virus software; some configurations can see each time a service or its data is accessed that a AV scan of the data/files will be triggered which can cause the service to spin in a waiting-to-load state.

‎10-19-2018

@Alessando_Valra , sure thing. You site builder builds the machine with everything running local. You will need to go into IIS Manager application, then user your Machine\Sites you will see the "Default Web Site" in the left hand tree-nav, select it and you will see the actions block on the right side of the screen update. Here you will see the option for "Bindings" , here you can set the alternate host names for access of the web, assign it to port 80/443 and configure your certificates. Here is the main docs for it.. Adding a Default Binding | Microsoft Docs

‎10-18-2018

This is handled by adding/updating the appropriate configuration in your webserver. If you are using IIS this is just additional aliases with matching certs; in Apache it's a bit more complex but totally possible.

‎06-28-2018

If you take a look at the file I attached to the original question you can see a bit of a comparison. Yes, Single Address is problematic in the small sample I uploaded; I am pulling our full sample DB right now to compare our 14.5m records to look at a broader scale across the software. Yes, Standardize the street-address field for data processing separate of Geocoding; we (and 23 other states) are required to provide data in this format (link) based on the schema in Chapter 5. So having nominally standardized addresses is key. For years we have been able to use the tools in ArcGIS to meet this need and have guided other states to use the same process because it was very consistent; but we are finding more issues now and where we had thought it may have been bad data coming in; it is looking more like the changes/enhancements in ArcGIS maybe a leading impact. Yes, I am happy to sit down with your folks at UC, I believe Nathalie Smith our of the Olympia Office was already trying to schedule a meet again since it seems a annual touch-base is good for WA and your group.

‎06-27-2018

Hi Brad, 1. We had seen similar or mixed types of issues I believe with 2.1 and ArcGIS Desktop 10.5.1. I haven't tried yet running the process again in 10.6; was kind of holding for 10.6.1 to just see the most stabilized version; but also knew that before I head to UC I wanted to take and prepare some benchmark data for discussions. 2. We are required to provide CSV and Tab files quarterly for various data outputs based on ranged-street data and those structured to look the USPS formatted outputs. So we use the Standardize Address tool to format the bulk table content that we are able to then do a select distinct on the various column selections for those files.

‎06-27-2018

Here is new issue with ArcGIS Pro 2.2.x. I have a table that we run the Standardize Address tool on each month and then geocode and extract from. We are finding a interesting scenario happening. When the value going into the "Single House" or "Singe House with Subunit" locator type such as this: 399 W C ST We see the house number, the "W" PreDir, "C" StreetName, and "ST" SufType parse back. But then in the same table we have: 399 W H ST But in this case we get the "W" direction, but the "H" goes into PreType, then the "ST" into the StreetName. This is a major issue that will break many things for states that build and support Sales Tax Data. Bruce Harold‌ / Brad Niemand / Agatha Wong / Shana Britt who would run point on this question? <Update> If you look at the attached fGDB, you can see the source table; as well as the results from Desktop 10.6 and Pro 2.2; it looks like Pro 2.2 using the Single Address with SubAddress did the best job; but I will have to do a broader test tomorrow with more records to see if more scenarios show. </Update>

‎06-10-2018

So in that graphic Kory Kramer, we would need to assume the Microsoft LTSC builds of Windows 10 will not be supported for either desktop environments. Since per Microsoft, the SA and LTSC builds are very different by deployment and feature levels. It would honestly be better for ESRI to support the LTSC first; since that will represent the minimum functional version of Windows 10, with the SA supporting newer features and device sets. You can trace through the updated docs here https://www.microsoft.com/en-us/itpro/windows-10/release-information that they have some very distinct issues that at the OS and Hardware have potential impacts for all of your Enterprise level customers.

Online Status	Online
Date Last Visited	5 hours ago

My Ideas

Latest Contributions by DEWright_CA

Re: Upgrading Workstation

Responsive design/update for ArcGIS Monitor

Re: ArcGIS Pro GPS Toolbar

Re: Enhance ArcGIS Server Monitoring

Re: geocoder Suggestions list in Search should not contain addresses that don't exist

Re: Using SQL Server views from a non-geodabase in ArcMap 10.6.1 is pretty much impossible if the underlying joined tables are large. Have you found a workaround?

Re: ArcGIS in Azure and local clients

Re: ArcSOC.exe process is running at high cpu usage

Re: ArcSOC.exe process is running at high cpu usage

Re: Adding functionality for including an alias in the Enterprise Builder deployment

Re: Adding functionality for including an alias in the Enterprise Builder deployment

Re: Broken Standardized Addresses

Re: Broken Standardized Addresses

Broken Standardized Addresses

Re: Windows 10 and the LTSC and SA update cycles and support

Re: ArcGIS Data Store upgrade 11.5 to 12.1 fails

Re: Copilot instructions md file for Visual Studio...

Re: Best practice for creating the same EXB app in...

Re: Employee Leaving - Creator of Environment

Re: What are your top questions about Groups in Ar...

GIS Leadership User Group

GIS Jobs

Experience Builder Custom Widgets

Web AppBuilder Custom Widgets