Download presentation
Presentation is loading. Please wait.
Published byEmilie Holte Modified over 5 years ago
1
SDSFIE Online Tools: Browse/Generate & Data Dictionary
Webinar Eastern 28 NOV 18 (Session 1) 12 DEC 18 (Session 2) Call-in toll-free number: (US) / Access Code: / Security Code: 4444 Webex: Meeting number: Meeting password: DCS: Paul Dubois, USACE Army Geospatial Center, support implementation of the SDSFIE program on behalf of: Dr. Jeff Ehman – Image Matters; Leidos – Bob Gaines First of 2 webinars on this topic, next one 12 Dec (repeat). It is the third in a series of 6 different webinars through July next year – repeating each one 2x. This is the first to provide over view of the SDSFIE Program for managers. We will be speaking today assuming the audience are not GIS technicians, but those who need to know about the DoD installation geospatial data standards because they manage or program for business areas the build or consume geospatial information. This is not a GIS technical briefing Next one may deal with contracting for SDSFIE – to include feature selection for scopes of work; and several more will focus on select technical topics to support Services who are developing adaptations and starting migration to new versions
2
SDSFIE Webinar Schedule FY 2019
☑ SDSFIE Program & Standards Overview: 11 & 24 OCT Browse/Generate, Data Dictionary: 28 NOV & 12 DEC Data Model Pre Migration: 16 JAN & 6 FEB Assessing Compliance with Validate; Adaptations with Model Builder: MAR / APR Data Model Migration: APR / MAY Metadata standards, tools and templates: MAY / JUN ☑
3
SDSFIE Overview Webinar
Agenda SDSFIE-V Concepts and Terminology SDSFIEOnline Website Online Resources Online Tools Common Workflows using SDSFIE-V: Which Tool for which Task? Data Collection Workflows, with Browse/Generate and Data Dictionary (and Model Builder) Notes: Please mute phones unless asking questions! You can also use “Chat” in WebEx or DCS to ask questions So for the agenda today we’ll provide: Background on SDSFIE-V Concepts and Terminology Provide an overview of the resources and tools available through the SDSFIE Online portal. Then take a closer look at the Browse/Generate and Data Dictionary tools. With that experience in hand, we will examine a few common workflows for users that are implementing the SDSFIE-V standard, and how the Browse/Generate, Data Dictionary, and Model Builder tools. Please mute phones unless asking; Also can use Chat window to submit questions along the way. (Demo)
4
SDSFIE-V “Models” … … SDSFIE-V 4.0
In SDSFIE-Vector, or “SDSFIE-V”, a “Model” consists of an organized set of “elements”: A set of Entities (Feature Types and/or non- spatial Object Tables) with Attributes, or characteristics, for each feature Attributes may be constrained by Enumerations Enumerations (“picklists”) have a set of Enumerants and, potentially, participate in Associations In each Version of SDSFIE-V (e.g., 3.1 or 4.0), there is a Gold model that is the root of all other models Each Service adapts the Gold model to create their own Headquarters Adaptation model Services can allow lower echelons to develop their own Sub-Adaptation All adaptations must adhere to SDSFIE-V Implementation Guidance (SVIG) SDSFIE-V 4.0 Gold Army 4.0 … Air Force 4.0 Navy Data Model 4.0 GEOFidelis 4.0 In SDSFIE, models consist of the elements that were described in the first video, entities, attributes, enumerations, enumerants, and associations. To achieve interoperability but provide flexibility for Components, there is a model hierarchy within any version of the model. The “Gold” version is at the top of this structure, with Component-specific models derived or “adapted” from the Gold parent. Components can then further tailor the model for specific elements of their organizations through the “adaptation” process, which will be explained in more detail later in this video. USACE HQ 4.0 …
5
SDSFIE-V Adaptation Approach
“SDSFIE Adaptation” defined: A formalized alteration of a model which results in another model tailored to the particular business requirements of an implementing organization. An Adaptation consists of a specific Profile and/or all the Extensions that are required to meet specific business requirements. SDSFIE Adaptation consists of three primary steps: “profiling” – removing non-mandatory elements that the implementing organization does not require Any entity other than those used in Installation CIP Any non-foundational attribute “extending” – adding required elements not found in the parent model (e.g., needed by USACE but not in Gold) “changing” – altering model, without affecting interoperability
6
SDSFIE Model “Elements”
Model “elements” include any of the following model components: Folder – a set of entities Entity (two types) Feature Type – A set of thematically equivalent geographic features with a corresponding data table of attributes Object Table – A non-spatial data table of attributes that can be linked to one or more feature types Attribute – a characteristic of an entity Enumeration – constraint on an attribute Enumerant – permissible value in an enumeration Association – establishes a relationship between two entities based on a primary key and a foreign key Before considering one additional case for not including certain portions of data in a adaptation, let’s make sure that the terminology to be used in this description is understood. SDSFIE Model “elements” include following: A folder is a set of feature types that are grouped together for database organizational purposes. There are two types of entities: feature type represents a set of thematically equivalent features which can be expressed as records, or rows in a feature attribute table, and object tables, which define a non-spatial data table that can be linked to one or more feature types. An attribute of a feature type is a characteristic of the features, and is expressed as a column in the feature attribute table. An enumeration constrains an attribute to a permissible set or numerical range of values. An enumerant is a value within a enumeration. The enumerants for a enumeration comprise the permissible set of values for that enumeration. An association is used to establish a relationship between two entities using a foreign key in on attribute table that points at the primary key of another entity.
7
SDSFIE Terminology SDSFIE Elements, and Element Properties
All SDSFIE LDM, elements have standard properties, which include: Model Name PascalCase or camelCase Alias English name Definition Succinct characterization Description Elaborate on Def. Def. References Note Deconfliction Justification SDSFIE Element-Specific Properties LDM Element Terms Physical Elements Terms, in ArcGIS Geodatabase N/A Folder Feature Dataset Default Geometry one: point, line, or area Permissible Geometry one or more of above Parent Entity [if subclass] Entity FeatureType (spatial) ObjectTable (non-spatial) Feature class Object class Entity Model Name Data Type E.g., String, Real, DateTime Length (in most cases) Constraining Enumeration attribute Field Length Enumeration Domain Enumeration Model Name enumerant (Domain) Value Parent Entity and Attribute Child Entity and Attribute Association Relationship The SDSFIE-V data “elements” has a direct correspondence to first class element objects in the ESRI geodatabase model. [Walk through each pair!] All elements have 6 “standard properties”. I bring these to your attention for a number of reasons, but for today’s topic, it should be noted that the text contained in these element properties is what is searched by the query algorithms in both Browse/Generate and Data Dictionary. Each element has properties that are specific to that entity, for example an attribute has an element-specific property that indicates the entity that it belongs to, as well as the data type (for example text, integer, or date/time) and length.
8
SDSFIE Online Overview of Tools and Resources
DEMO
9
SDSFIE Online – Homepage
After consenting, you have access to the SDSFIE Online Homepage – Provides a brief overview of SDSFIE, with links to the all parts of SDSFIE Online, with 4 main sections Consent Banner – An initial pop-up to give consent Menu Strip section – Access to all tools and pages Welcome section – A brief explanation of SDSFIE along with a “Learn More” link that will direct you to a page that explains the SDSFIE Family of Standards. What’s New? section – Highlights new developments or updated tools / documents Stakeholders section – provides links to each Component page
10
SDSFIE Online – The Menu Strip
Home – will always take you to the Welcome (Home) page SDSFIE Online – provides links to general information and how to get started Standards – provides details on each of the SDSFIE Standards Models & Workflows – provides links to each of the SDSFIE Tools, and the means to interact with the models Components - provides links to each component page (identical to the links on the Home page) Support – provides links to a FAQ page, SDSFIE User Guides and additional training The Menu Strip: Top of almost all SDSFIE Online pages (not Tools) Versatile Hover/click accesses different SDSFIE Online topics and functions
11
SDSFIE Online – “SDSFIE Online”
What is SDSFIE Online? – Provides an overview of SDSFIE Online and the SDSFIE family of standards. Getting Started – Three step process: Step 1) Register Step 2) Learn More Step 3) Get to Work Website Changelog Register User – first, create User Account Specify a Sponsor or Manager Takes hrs, normally less Log In As User – must log in to obtain access to models and tools Standard password reset and username recovery functions Learn More – See “Support” menu item.
12
SDSFIE Online – “Standards”
13
SDSFIE Online – “Components” US Army Page
To be Updated Soon! US Army HQ – model details Implementation Plan Migration Guidance and Support
14
SDSFIE Online – “Support”
SDSFIE FAQ – commonly asked questions and general information about SDSFIE and the website; accessible from the “Get Help” link at the bottom of any page User Guides and Training Videos – 4 Tool/Workflow downloadable user guides and 26 training videos (watch through YouTube, or download) Direct Contact “Help Desk” – response within 24 hrs (8:00AM-4:30PM EST Mon-Fri) Webform submission Phone: (571)
15
Support – Details, and More Resources
SDSFIE Online User Guides (5 “how-to” format) FAQ Training (26 videos) Background (4) Data Dictionary (2) Browse/Generate (5) Model Builder (8) Validation (2) Migration (5) AGC Online; Guidance; Standards; Requirements; Modeling Leidos/Image Matters Support Team Tech Support (via SDSFIE “Help Desk”) Training (webinars) Migration support (multiple 3-4 day events)
16
SDSFIE Online – “Models & Workflows”
Browse Generate – allows examination of a single model at a time and/or publishes a physical or logical data representation of that model Data Dictionary – provides multi-faceted search interface and reports across all logical data models, with saved search function Migration – supports moving data repositories to new (target) models, with capabilities for managing and registering custom data and sub-adaptations Model Builder - provides for creation and editing of logical data models, with options for interactive GUI or workbook upload for large/complex models Validate – facilitates comparison between any two models, including source to parent mode, with workbook output; shows adherence to SDSFIE rules
17
SDSFIE Online Tools: Browse/Generate
Select a single model (adaptation) from the Registry, and “browse”, in full detail, all elements in that model Find entities in the model by keyword searches that probe the property text (e.g., Definition, etc) of all element types Select entities within the chosen model, and “Generate” these different products: LDM – a logical representation of data model in two different formats, both as Excel workbooks, with options PDM – a physical representation of data model in ESRI Workspace XML format, which can be imported into a Geodatabase, with many options possible, including application of “Alternate Names” Metadata model, full or for entity/attribute section, as XML
18
SDSFIE Online Tools: Data Dictionary
Perform keyword searches against all models in the Registry, or specify selected type(s) of models to be probed Find selected type(s) or all elements in all or specified model(s) that match element property text (i.e., Model Name, Alias, Definition, Description, Note) to the search criteria Examine lists of matched elements from different models, by element type (as tabs) View all attributes constrained by an enumeration in a model Use OR and AND operators with keyword(s), as well as conduct exact phrase matching Save Search, and Execute or Edit a Saved Search, Export Search Results
19
SDSFIE Online – Common User Workflows and Required Tools
USE CASE Data Dictionary (DD) Browse / Generate (B/G) Validation Model Builder (MB) Migration Need to collect data in the field. Stipulated HQ model contains all required element concepts X Need new elements concepts that don’t have a match in the stipulated HQ model Need to plan for migration Need to know compliancy of source data Examine relevant models (e.g., “source parent” and “target parent” adaptations) Check compliancy of existing database against parent model(s) Need to migrate data to be compliant Use for inspection of inputs, intermediate results, and outputs Use Migration Workflow and Tool Need to view and/or update entity and attribute metadata Use B/G tools
20
SDSFIE Online – User Workflows Data Collection– all requirements are met by parent model (HQ Adaptation) Use Case #1
21
SDSFIE Online – User Workflows Data Collection (Standard Elements)
Scenario Setting up project involving use of drones around Corps facilities to collect data. Know you need to track authorization area and use. Inquiry to SMEs results in knowledge that new USACE HQ 4.0 Adaptation has all entities (named SUAS*) needed to capture required information about authorized drone activities. Need set of entities in geodatabase to serve as backend for web feature service accessed via handheld. Recommended Approach Save schema ArcGIS Geodatabase Browse / Generate Tool Esri XML Workspace Document Create new (empty) GDB in ArcCatalog, and Import schema Select entities, and Generate schema
22
SDSFIE Online – User Workflows Data Collection – all requirements are met by parent model (HQ Adaptation) Use Case #1 DEMO
23
SDSFIE Online Data Collection Workflow
START Identify required element concepts Identify stipulated parent adaptation Use B/G to: Generate LDM for future reference Generate PDM for ESRI GDB structure (Workspace XML document) Use B/G to: Select stipulated parent adaptation Select matched entity concepts In ESRI ArcGIS: Create empty GDB Import ESRI Workspace XML doc Use B/G to: find matching concepts in the stipulated parent adaptation GDB, ready for data! Report unmet requirements to your SDSFIE Component Lead Use MB to: Add unmatched elements that were found in other Components’ adaptation Find all? YES END NO Does your Component permit sub-adaptation? B/G = Browse/Generate Tool DD = Data Dictionary Tool MB = Model Builder Tool As with any multi-step process, a little planning is in order. In this case you need to know the element concepts that you need collect data for. Knowing the feature type and attribute concepts that you require, and the parent model that is stipulated per your Component’s Adaptation Guidance is essential to help the process go smoothly and end with the model that you need. With this information in hand, typically, you will always want to start with B/G: The path is easiest if all required concepts are found in the stipulated parent model – the HQ Adaptation of your Component. If no sub-adaptations are allowed, then you only need B/G, as only the HQ Adaptation of your Component is allowed to be accessed. If the concepts that you required are not found in your Component’s HQ Adaptation, and sub-adaptations are permitted, then you will use DD to search other models for the element concepts that your stipulated parent model lacks. NO YES Create New Adaptation in MB: Select stipulated parent adaptation Select all matched entity concepts Create new model Use MB to: Create new elements not found in stipulated parent adaptation or that of other Components’ Use DD to: Try to find unmatched elements in other Components’ models Find all? YES NO
24
SDSFIE Online – User Workflows Data Collection – not all requirements are met by parent model (HQ Adaptation) [Use Case #2] Scenario Setting up project involving use of drones around Corps facilities to collect data. Same requirements as previous scenario, geodatabase with feature classes that support drone operations *Additional need for a feature type that delineates areas with FAA airspace restrictions of non-federal UAS operations Will need the 4 USACE HQ 4.0 feature types, plus one additional feature type. Your Component allows sub-adaptations
25
Adaptation Actions – Use Case #2
Need to check for existing entity in SDSFIE! Parent Adaptation Add entity to represent FAA UAS Temporary Flight Restrictions for National Security Start with USACE HQ 4.0.2: 465 entities PROFILE (Profiled Parent) 4 entities EXTEND Child Adaptation This diagram depicts in a conceptual manner, the SDSFIE Adaptation process. An adaptation always starts with a parent adaptation shown at the upper left of the diagram. For subordinate adaptations, the parent adaptation will typically be the headquarters adaptation for your Component. The diagram then depicts the selective profiling of elements including entire feature types and object tables, as well as non-mandatory attributes and domains. The result is the intermediate “profiled parent” adaptation that appears in the center of the diagram. The next step in this process is to “extend” the profiled parent by adding elements that do not exist in the parent adaptation. These “extended elements” can be entire feature types or object tables, as well as additional attributes and or enumerations. Note that enumerant extensions for an existing enumeration will require a CR. Remove all entities except: SuasAirportBuffer SuasAirworthinessArea SuasCertificateOfAuthorzArea SuasLaunchOrLandingLocation 5 entities
26
SDSFIE Online – User Workflows Data Collection – not all requirements are met by parent model (HQ Adaptation) Use Case #2 DEMO
27
QUESTIONS???? Paul Dubois: 703-428-6742 paul.c.dubois@usace.army.mil
Dr. Jeff Ehman:
28
SDSFIE Webinar Schedule FY 2019
☑ SDSFIE Program & Standards Overview: 11 & 24 OCT Browse/Generate, Data Dictionary: 28 NOV & 12 DEC Data Model Pre Migration: 16 JAN & 6 FEB Assessing Compliance with Validate; Adaptations with Model Builder: MAR / APR Data Model Migration: APR / MAY Metadata standards, tools and templates: MAY / JUN ☑
Similar presentations
© 2024 SlidePlayer.com. Inc.
All rights reserved.