Latest Contributions by SallieVaughn

Did you get a resolution to this issue? We are having the same issue with Map and Feature Services hosted on ArcGIS Server that I recently upgraded to the ArcGIS Pro runtime. ... View more

What sort of workshop do you want to develop? How many hours/days might it be? Virtual or in person, or both? Do you need printed materials, sample datasets, etc? I personally like to work through an example for things like this, especially since GIS people are generally people who learn by seeing and doing. ... View more

I'd love to know what you find out about this. There used to be some functionality to export XML schemas from SDE and then import them into Access or Visio, but I haven't tried that in years and don't know the current feasibility. That would at least get you a raw schema that you could then mark up. With NG-911 looming in my near future, this is a huge issue for us. I'm basically going to implement a policy of only adding additional columns and not attempting to rename any. The result is huge, unwieldly tables, but the number of staff impacted by that is far less than staff, apps, citizens, workflows, etc., that would be impacted by simply renaming a column. ... View more

If you have GIS layers for all the spatial constraints you mentioned (Township, Section, Range, park, etc.) and the desired identifiers are stored in those layers, you could use the Attribute Assistant to calculate those IDs for you. I do think 15 characters is a little ambitious for what you are trying to accomplish. https://solutions.arcgis.com/shared/help/attribute-assistant/ There are a lot of unknowns here. For example, how many data editors do you have? Is there a risk that someone in public works could add an ID to a water fountain in a park and then someone from parks and rec duplicates the effort? Also, information that defines each feature could be stored in more than 1 field. For a given transportation asset, you could have 1 field for the PLSS information, a second field for additional location information, a third field for unique ID, etc. To me, that makes more sense. ... View more

I ran into this issue with the June 2019 version of Web App Builder, so the issue with the widget has not been fixed. However, I was able to overcome the issue with the "Find Me" tool by changing the visible scales of the map. Using Web App Builder, go to the Map Tab, under Customize visible scales click Customize... and delete any scales that are below what you'd like the user to see.  ... View more

So I finally my own question and thought I'd update the thread. This applies to: ArcGIS for desktop 10.6.1 and SQL 2014. To change Configuration Keywords which controls storage defaults: 1. Export dbtune using the Export Geodatabase Configuration Keywords tool in ArcToolbox. 2. Make a copy of dbtune 3. In a text editor, open the file you just exported and look for "GEOMETRY_STORAGE." 4. Change the value to SDEBINARY to make SDEBINARY the default storage for the database and save your changes. 5. Using the Import Geodatabase Configuration Keywords tool, import the modified DBTUNE back to the DB. 6. Test the changes by adding a new feature class and/or copy and pasting a feature class to see if the default is indeed SDEBINARY. Note that SDEBINARY is going away and tools to create and manage Views are no longer provided with ArcGIS for Desktop. You'll have to go and download the command line tools for Arc 10.2.2 to manage views on SDEBINARY databases. Adapted from ESRI help documentation: http://desktop.arcgis.com/en/arcmap/latest/extensions/workflow-manager/adding-a-configuration-keyword-to-the-geodatabase-in-postgresql-for-the-workflow-manager-workspace.htm ... View more

David, It's been a few years, but did you find a resolution to this? The PrintPlus widget was not providing the tick marks or the red box, among other things. I'm having the exact same issue and just can't work around it. Thanks! ... View more

Initially, yes. And I did not add the 2013_Imagery there. It was already listed in the list of basemaps. After downloading the app, I also changed configurations in the previously attached .json file but did't see 2013_Imagery in there to make the desired changes. ... View more

Echoing what Joe said, the LGIM is a great starting point. If the data you currently have is in terrible shape, the LGIM is a good place to go. I did a similar thing with my current organization (transitioning from multiple copies of the same data, all with different levels and qualities of attribution) to the LGIM. The task was not easy and took quite a bit of time. To manage the task, I made a series of Excel spreadsheets showing the schema of each layer in the LGIM. For layers we were planning on using, I placed that schema along side the LGIM schema and drew lines from our existing fields to the LGIM fields. That way, when I was working on the project and got interrupted, I'd know where I was, what I was doing, and where to go back to when I had free time again. I'm happy to share those spreadsheets with you. Since this time, I've appended/added to the LGIM to work better for our organization in terms of additional columns in some layers as well as additional layers. Also, downloading the sample data from Naperville really helped me understand what sort of data went into each layer and how the data is used by other LGIM products. That would be a great starting point. ... View more

I have used the General Purpose and Imagery Reference Overlay maps and have found them helpful as a starting point for a lot of maps and applications we've created. We did have to make some modifications though to work with our data. For these details, some sort of documentation would have been nice. Symbology on the streams/lakes layers included a special class for labeling the DuPage River. We had to modify that to work with our data since we don't have a DuPage River. Finding those little details required that I look at each label class SQL query which was a bit infuriating. We also had to tweak the definition queries to use different feature areas for displaying certain features at certain levels of zoom. Basemaps were created on a file GDB. We run SQL Server with ESRI Binary Data type... others are using one of the Microsoft data types. Each of those back-end database options changes the name of the fields that auto-calculate distance and area. Once re-pathed to our data, the downloaded basemaps wouldn't render any features with a definition query on area or a labeling query on area. I was able to find a script to help me out, but perhaps having different versions for different database back-ends would be nice -- or a least a note somewhere telling you about it and linking to the script or an X-Ray tool, perhaps? These base maps have been a great way to provide visual consistency between our printed and digital products and have decreased the amount of time it takes for us to make custom maps. However, I have had some sort of operational issues with them. For example, both the general purpose and imagery reference basemaps include parcels and roads. For our particular organization, those data layers change on a daily basis. That would force us to recreate caches daily in order to keep our web applications up to date with actual feature geometry. That method just isn't sustainable or recommended. Also, the suggestion to use "Best" for Anti-Aliasing when publishing a basemap is in direct opposition to what your Server team recommends, especially if the cache needs to be rebuilt (Accelerating map cache creation—Documentation (10.3 and 10.3.1) | ArcGIS for Server). It might be a good idea to run a full implementation of one of these base maps from download to web application and involve members of each of the involved teams in the implementation to replicate their use by local governments. ... View more

We've found similar with our implementation. However, our issues come with our close integration with our 911 Dispatching software. That software requires each of those components be in separate fields so we simply added the fields and use the Attribute Assistant to populate those extra fields for us. The core schema remains unchanged, so components of the LGIM aren't affected. ... View more

Thanks for the response! Actually, I wound up changing the width for the Search Container in the browser.css file. Apparently, the number of pixels I had specified in the headers was more than was allowed by the style sheet. ... View more