esri / geospatial-center-code

A repository for helpful scripts

Geospatial-Center-Code

A repository for helpful scripts created by the Geospatial Center team (and others!). The Geospatial Center is a group of Solution Engineers across different teams within Esri. Through our day-to-day work, we often find ourselves creating helpful scripts for products across the ArcGIS software stack. This repo will hold those scripts as they become available.

For more information contact Adam Pfister ([email protected])

Contributing to the best code in the world!

If you'd like to contribute, please follow the example template for what files and details are needed.

Visual Studio Code is a great IDE to use with strong and easy-to-use GitHub integration. Generally, you can follow this workflow for contributing using VSCode:

• In VSCode
  • Cloning the repo
    • Making a local copy of the repo on your machine
  • Creating a branch
    • You’ll make your changes/additions here first
  • Adding your script(s)
    • Literally creating folders/files for your scripts
  • Staging the changes
    • For example, if you have 10 files, but only want to add 3 of them, you would “stage” only those 3 files
  • Writing a commit message
    • A short descriptive message about what’s being added/changed
  • Committing your new additions to your new branch
    • Move your additions/changes from “staged” to “committed” in your branch only
  • Push changes to your new branch to the remote repo on Github.com
    • Send the additions/changes from your local machine to the remote repo on GH.com
    • This results in creating a remote version of your branch in the remote repo on GH.com
• On Github.com
  • Create a Pull Request (commonly referred to as a “PR”) to merge your new branch into the “master” branch
    • Create a request that will merge your branch into the “master” branch
    • Comments/discussion can happen around this pull request as needed
  • Merging your changes/additions into the master branch
    • This will merge your branch into the “master” branch and make your script available to all!
• Delete your local and remote branches

Esri welcomes contributions from anyone and everyone. Please see our guidelines for contributing.

Issues

Find a bug or want to request a new feature? Please let us know by submitting an issue.

Licensing

Copyright 2020 Esri

Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at

http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.

A copy of the license is available in the repository's LICENSE file.

geospatial-center-code's Issues

Proposed Repo Structure

Folders in Repo

- arcade
  - popup
  - labeling
  - visualization
  - dashboard
  - ... [any other arcade profile](https://developers.arcgis.com/arcade/guide/profiles/)
- arcgis-pro
- javascript-api
- python
  - arcpy
  - api
- runtime-sdk
- survey123
  - forms
  - javascript
...

Example template for adding a new item to a folder

When a new script is added to a folder, the individual will create a sub-folder that will at least have a README.md that will follow the template below, along with any script files and/or supporting files, screenshots, etc.

/arcade
    |
    --> /predominance-map-lotsa-columns
         |
          --> script.js
          --> README.md
          --> screenshot.png          

---

example README.md

Create Predominance Map with a lot of columns

Original Author: Bonnie Stayer
Ever wanted to create a predominance map but had too many columns to consider? I came up with this simple script to do just that. I'm back in the NAICS industry world, so the field names and output text reflect that (you'd obviously have to swap in whatever your working with)

View it Live

Considerations:

I'd be particularly interested to see if someone has more clever way of addressing the highlighted step (how you get the column name back once you've got the highest value). That's the most cumbersome part, and you're actually returning hardcoded text rather than the real column name.

Use Case

[optional]

Dependencies or Workspace requirements

• ArcGIS Online