SlideServe
Télécharger Obtenir Pro
Menu
Accueil Pro
Préférences
ApparenceLight Aide et commentaires
© SlideServe · v2026

Automated Geoprocessing Application Evaluation & Presentation

egordon avatar
egordon
6 diapositives · 333 Views · Jan 02, 2020

This project involves evaluating and presenting an automated geoprocessing application using Python script tools. The write-up includes a detailed synopsis, extended abstract, pseudocode, acknowledgements, and keywords. The presentation part requires explaining the project and showcasing a prerecorded demo. For the live demo, all necessary files are submitted for running the code, default values in GUI are set, and portability is checked. Lastly, a thumbnail image is created for the project gallery.

#automated geoprocessing application evaluation & presentation #automated geoprocessing application evaluation & presentation ppt #powerpoint #presentation
Automated Geoprocessing Application Evaluation & Presentation - slide 1
01 / 6Automated Geoprocessing Application Evaluation & Presentation
1 / 17

Télécharger la présentation

Automated Geoprocessing Application Evaluation & Presentation
Une image / un lien ci-dessous est fourni (tel quel) pour télécharger la présentation

Politique de téléchargement : le contenu du site vous est fourni TEL QUEL pour votre information et votre usage personnel ; il ne peut être vendu, concédé sous licence ni partagé sur d’autres sites sans l’accord de son auteur.Le contenu vous est fourni TEL QUEL, pour votre information et votre usage personnel uniquement. Téléchargez la présentation en cliquant sur ce lien. Lors du téléchargement, si vous ne parvenez pas à télécharger une présentation, l’éditeur a peut-être supprimé le fichier de son serveur.Pendant le téléchargement, si vous ne parvenez pas à obtenir une présentation, le fichier a peut-être été supprimé par l’éditeur.

F I N

Plus de contenu associé

Transcription de la présentation

  1. Project evaluation • Write-up (20 pts) • Presentation (20 pts) • Live demo (12 pts) • Thumbnail (3 pts) • Code evaluation (45 pts)

  2. Write-up (20 pts) • Title • Synopsis --<=4 sentences • Extended abstract: (<=300 words) • Pseudocode • Acknowledgements • Keywords

  3. Presentation (20 pts) • Two parts: • Explain the project (<=5 minutes) • Description of the problem (screen recording with voiceover for distance ed). • Include a checklist of the required and advanced functionality (met or not met). • Prerecorded demo (<=5 minutes) • Demonstration of running the code. • Both distance and traditional students prerecord a video. Jing recommended for free video screen capture

  4. Live demo (12 pts) • Submit all files needed to run code – maps, scripts, toolboxes, data, so forth • Set default values in GUI • Check for portability

  5. Thumbnail (3 pts) • image for the project gallery. • This should be a small JPEG, GIF, or PNG image file, 62 pixels wide and <=62 pixels tall. Select an image that represents the topic of your project. See project gallery for examples. The latest version of Windows Programs > Accessories > Paint allows you to resize images. • Name it userid.*

  6. Code evaluation (45 pts = 20+20+5) • Required components (20 pts): • Python geoprocessing. • Python batch processing. • Use Python script tools and script tool properties to generate an appropriate interface. • Provide a toolbar button to launch the script tool. • Inform the user of progress, using progressor and messages. • Automatically display geoprocessing output in the map. (If the output is better viewed outside of ArcMap, you must still display it automatically. But also show messages so that the user knows how to find and display the visual output in a more appropriate viewer.) • Programming style (20 pts): • use of variables; minimal hard-coding • use of data structures such as lists/dictionaries to streamline code (instead of long if/elif/elif/elif... blocks.) • lightly commented but also self-documenting (easy to guess what's happening) • use of procedures/modules to organize/streamline code so that related blocks of code are grouped and reusability is facilitated when possible. • avoid use of 'magic numbers' -- hard-coded numbers unique values with unexplained meaning and/or multiple occurrence which could (preferably) be replaced with meaningfully named variables • catch exceptions, as appropriate • lines of code <=80 chars. Achieve this by using variables to hold long string arguments and using line continuation symbols as needed. • Instructor feedback implemented. • Level of difficulty (5 pts)