Data Importer Onboarding Training Mark Holmes GISP DTMB Center for Shared Solutions May 12 2022 Statewide 911 GIS Repository Roles NG911 GIS Data Readiness Repository Data Requirements Repository follows current NENA NG911 Data Schema ID: 1002436
Download Presentation The PPT/PDF document "Michigan Statewide 911 GIS Repository" is the property of its rightful owner. Permission is granted to download and print the materials on this web site for personal, non-commercial use only, and to display it on your personal computer provided you do not modify the materials and that you retain all copyright notices contained in the materials. By downloading content from our website, you accept the terms of this agreement.
1. Michigan Statewide 911 GIS RepositoryData Importer Onboarding TrainingMark Holmes, GISP – DTMB Center for Shared SolutionsMay 12, 2022
2. Statewide 911 GIS Repository Roles
3. NG911 GIS Data Readiness
4. Repository Data RequirementsRepository follows current NENA NG911 Data SchemaRecommendations for moving to new schemaHighly recommended- adopt current NENA NG911 Data Schema for your GIS dataOption 2 – add key fields for NG911 GIS data readinessLimited Term Option – have minimum required fields with plan to move towards new schema (this requires a lot of coordination with DTMB)Need to have mandatory fields completed in your source data
5. Repository Data Requirements Loading FeaturesOnly load features within your jurisdictional areas. If you have additional data outside of your area, you need to remove those featuresMay need to coordinate with neighboring authoritative data maintainer on who is loading which featuresDownload tools will be using County fields to extract data from repository so those are key mandatory fields along with Discrepancy Agency ID and Unique ID
6. Repository Data Requirements Structure PointsMinimum (Mandatory) required fields – Structure PointsUnique IDAddress NumberStreet Pre-DirectionalStreet NameStreet TypeStreet Post DirectionalMunicipality (city, township)County, Country, StateDate UpdatedDiscrepancy Agency ID (domain of organization maintaining data e.g. co.name.mi.us)
7. Repository Data Requirements Road CenterlinesMinimum (Mandatory) required fields – Road CenterlinesUnique IDStreet Pre-DirectionalStreet NameStreet TypeStreet Post DirectionalMunicipality (city, township)Left From and To RangesRight From and To RangesCounty, Country, State (Left and Right)Date UpdatedDiscrepancy Agency ID (domain of organization maintaining data e.g. co.name.mi.us)
8. Road Centerline Attributes – Road NamesNG911 Fields (CLDXF Model)Legacy FieldsSt_PreModSt_PreDirNorthLSt_PreDirNST_PReTypSt_PreSepST_NameMainLSt_NameMAINSt_PostTypStreetLSt_TypeSTST_PostDIrLSt_PosDirSt_PosMod
9. Required FieldsMinimum required fields – Unique IDMake sure it is staticRecommendation is ID include discrepancy agency ID to separate from other numeric IDs from other contributorsExample of NG911 Schema Unique IDs
10. Road Name FormatsNENA NG911 Data SchemaNG911 Street Name Fields and Legacy FieldsNG911 Street Name Fields Use CLDXF FormatsStreet Name Pre Types and Street Name Post Types (nena.org)https://cdn.ymaws.com/www.nena.org/resource/resmgr/standards/nena-sta-006.1.1-2020_ng9-1-.pdfhttps://cdn.ymaws.com/www.nena.org/resource/resmgr/Standards/NENA-STA-004.1.1-2014_CLDXF.pdfExample of NG911 Schema Street Names
11. Road Centerline Attributes – Road Names RecommendationNG911 Fields (CLDXF Model)Legacy FieldsSt_PreModSt_PreDirNorthLSt_PreDirNST_PReTypSt_PreSepST_NameMainLSt_NameMAINSt_PostTypStreetLSt_TypeSTST_PostDIrLSt_PosDirSt_PosModOption 2 – Add street name NG911 Fields to your schema and update road names into new CLDXF formatsRecommendation- Migrate to new NG911 geodatabase schema and update road names into new CLDXF formats
12. Road Centerline Attributes – Road Names Short Term OptionNG911 Fields (CLDXF Model)Legacy FieldsSt_PreModSt_PreDirNLSt_PreDirNST_PReTypSt_PreSepST_NameMAINLSt_NameMAINSt_PostTypSTLSt_TypeSTST_PostDIrLSt_PosDirSt_PosModShort Term Option - Add NG911 Fields to your schema and use your current road names in both with plan to format NG911 field values to CLDXF Model
13. Road Centerline Attributes – Road Names ExampleNG911 Fields (CLDXF Model)Legacy FieldsSt_PreModOldSt_PreDirNorthLSt_PreDirST_PReTypSt_PreSepST_NameChurchLSt_NameOLD NORTH CHURCHSt_PostTypStreetLSt_TypeSTST_PostDIrLSt_PosDirSt_PosMod
14. Road Centerline Attributes – Road Names Example (2)NG911 Fields (CLDXF Model)Legacy FieldsSt_PreModSt_PreDirLSt_PreDirST_PReTypAvenueSt_PreSepST_NameALSt_NameAVENUE ASt_PostTypStreetLSt_TypeSTST_PostDIrLSt_PosDirSt_PosMod
15. Road Centerline Attributes – Road Names Example (3)NG911 Fields (CLDXF Model)Legacy FieldsSt_PreModSt_PreDirLSt_PreDirST_PReTypBoulevardSt_PreSepof theST_NameAlliesLSt_NameBLVD OF THE ALLIESSt_PostTypLSt_TypeST_PostDIrLSt_PosDirSt_PosMod
16. Road Centerline Attributes – Road Names Example (4)NG911 Fields (CLDXF Model)Legacy FieldsSt_PreModSt_PreDirLSt_PreDirST_PReTypSt_PreSepST_NameMainLSt_NameMAIN STREET NORTH EXTENSIONSt_PostTypStreetLSt_TypeST_PostDIrNorthLSt_PosDirSt_PosModExtension
17. Road Centerline Attributes – New NG911 FieldsNG911 Fields ExampleDiscrepancy Agency IDCounty.org or co.countyname.mi.usDateUpdated8/3/2021 7:35:21 PMNENA Globally Unique IDRCL_111111@county.orgCountryUSStateMICountyAny CountyIncorporated CommunityAny Township
18. Road Centerline Attributes – New NG911 Fields (2)NG911 Fields ExampleAddress Number Prefix or Suffix‘1/2’ in 321 ½ Main StreetParity LeftO=Odd, E=Even, B=Both, Z=Address Range 0-0Parity RightO=Odd, E=Even, B=Both, Z=Address Range 0-0Place TypeAirport, Bank, Office, HotelBuildingBuilding NameUnit TypeAptUnit23FloorRoom
19. Response Boundaries – Separate OutFire, Law, EMSLoaded as separate boundariesIf you have one layer for all emergency service zone, steps can be used to pull them out into separate layersFuture training sessions will be held on these layers and validationsStatewide layer will highlight areas where neighboring jurisdictions my need to perform edge-matchingPSAP boundary review period during onboarding timelineMore communication to PSAP Administrators and Data Importers
20. MiLogin – Single Sign OnData Import ToolsVia Michigan Geographic Framework Data Gateway
21. Contributor Guide to MILogin Setup for MGF Data GatewayLogin set up for Michigan Geographic Framework Data GatewayStep 1: Go to https://milogintp.michigan.gov/Step 2: Login if you have an account or sign up if you need to create an account
22. Contributor Guide to MILogin Setup for MGF Data Gateway (2)
23. Contributor Guide to MILogin Setup for MGF Data Gateway (3)
24. Contributor Guide to MILogin Setup for MGF Data Gateway (4)If you have account or once you have created a MiLogin accountStep 3: Go to https://milogintp.michigan.gov/ and sign in Step 4: At the top of the page click ‘Request Access’
25. Contributor Guide to MILogin Setup for MGF Data Gateway (5)Step 5: In the Search Application field, enter Michigan Geographic Framework Data Gateway and select.
26. Contributor Guide to MILogin Setup for MGF Data Gateway (6)Step 6: Agree to the terms and conditions.
27. Contributor Guide to MILogin Setup for MGF Data Gateway (7)Step 7: DTMB will receive an email that you are seeking approval for access to Michigan Geographic Framework Data Gateway, once accepted you can continue onto the next step.Step 8: Once you have approval. Login to MiLogin. Go to Michigan Geographic Framework Data GatewayStep 9: Select ‘Sign in with MILogin Third Party – External User’If you are having trouble with MILogin, DTMB will have a helpdesk support email that you can send questions to DTMB-NG911GIS@michigan.gov
28. Data Provisioning Info Required to Be EmailedPlease email the following information to DTMB-NG911GIS@michigan.govDiscrepancy Agency ID (agency of GIS data maintainer e.g. co.name.mi.us)GIS Data Maintainer Contact InfoFirst and Last NameAddressEmailTelephoneMiLogin user nameIf Secondary GIS Data Maintainer, please email contact info for that personGeographic extent for area being uploadedAttach agency logo (optional) will be used for Data Gateway interfaceAll of this information will be used to initialize data importing tools Importing tools will only be made available to those on permissions form submitted by PSAP Administrator
29. Repository FunctionalityDemos
30. Statewide 911 GIS Repository Import
31. Statewide 911 GIS Repository Import (2)
32. Statewide 911 GIS Repository Import Steps AvailableEssential Geometry Checks (pre-load check)Attribute Validations (pre-load check)Change Detection (upload to repository process)Fishbone Validation (periodic check)Cross Feature Validation (periodic check)Shapefiles or File Geodatabases are acceptedMust be zipped up to drag and dropMust have a unique ID on all records
33. Statewide 911 GIS Repository Import (3)
34. Repository FunctionalityEssential Geometry Checks
35. Essential Geometry ChecksThis check can be used for all geometry typesNo specific tiles for each datasetsFound in My Assignments on left side contents
36. Essential Geometry Checks (2)Drag and drop zip fileCan be shapefile or file geodatabase
37. Essential Geometry Checks (3)Set Target Class to Feature
38. Essential Geometry Checks (4)Set Geometry field and set unique ID filed to UniqueIDThen Click Continue
39. Essential Geometry Checks (5)
40. Essential Geometry Checks (6)
41. Essential Geometry Checks (7)
42. Essential Geometry Checks (8)
43. Essential Geometry Checks (9)
44. Essential Geometry Checks (10)
45. Essential Geometry Checks (11)
46. Essential Geometry Checks (12)
47. Essential Geometry Checks (13)
48. Essential Geometry Checks (14)
49. Essential Geometry Checks (15)Submissions not closed can be accessed in top rightIf submissions are left open after 24 hours will produce error message
50. Repository FunctionalityAttribute Validations
51. Attribute ValidationsSpecific tile per datasetMust map fields first time then you can save mapping
52. Attribute Validations (2)Drag and drop zip fileThen click continue
53. Attribute Validations (3)Set Target Class to Road_CenterlinesMap other target fieldsContributor’s source fields on left and repository schema in dropdowns on right
54. Attribute Validations (4)Things to note in attribute field mappingIf you only have 4 traditional street name fields, map them to the NG911 CLDXF equivalentsRecommendation is having both the traditional street name fields as legacy fields in your source data along with the new NG911 CLDXF fields to be able to map all field in attribute and change detection stepsMake sure you check all fields mapped twice after mapping to make sure they are correctSave your schema mapping
55. Attribute Validations (5)Once field are mapped you can save schema mapping
56. Attribute Validations (6)Type in Mapping Name and click Save MappingYou can save up to five mappingsYou can delete by clicking on Remove mapping
57. Attribute Validations (7)
58. Attribute Validations (8)
59. Attribute Validations (9)
60. Attribute Validations (10)Things to note in attribute checksFor mandatory fields – Nulls are flagged as not validFor conditional and optional – Nulls are not flagged but empty fields areFor DateUpdate field – check your date field prior to loading into Data GatewayMake sure each field has a date with at least 12/12/2022 formatIf it only has time it will error out, should be cleaned upUnique IDs, make sure they are unique, zero is not validInclude discrepancy agency ID in the unique Global GUID value that you develop (e.g. SSAP12345@mijackson.org)
61. Attribute Validations (11)You can download Output file to computer to bring into GIS software
62. Repository FunctionalityChange Detection(Actual Upload Step to NG911 Repository)
63. Change DetectionThis phase commits data into NG911 repository database
64. Data Considerations Before Submitting Data Via Change DetectionOnly data within your jurisdiction boundary can be submittedDo not submit additional data outside your boundary if another jurisdiction is authoritative source maintaining dataIf your PSAP extends into another county and the other county is maintaining that GIS data, other county will contribute and your PSAP data exporter can download from the repositoryRun Essential Geometry Check and Attribute Validation Checks as many times as needed to ensure all Mandatory fields and records are valid (Parity is exception for now)Make sure IDs are unique within your database
65. Change Detection (2)This phase commits data into NG911 repository database
66. Change Detection (3)This phase commits data into NG911 repository database
67. Change Detection (4)
68. Error Reporting
69. Error Reporting (2)If error occurs during processing, download log file and email to DTMB-NG911GIS@michigan.gov
70. Data Import Metrics
71. Data Import Metrics (2)
72. Data Import Metrics (3)
73. Data Import Metrics (4)
74. Statewide 911 GIS Repository Roles (2)
75. NG911 GIS RepositoryTraining and Data Onboarding
76. Upcoming ActivitiesActivityScheduleVerify PSAP RolesBegan December 2021 - OngoingAssign PermissionsBegan December 2021 - OngoingFinal User TestingJanuary – March 2022Training Sessions/DocumentsApril 2022Onboarding Data to New SystemWebinar Overview of OnboardingApril 19 and April 26Training- April 28th pilot groupMay 12 and May 24 appointments to be sentOnboarding to Upgraded 911 GIS Repository
77. Permissions Formwww.michigan.gov/snc
78. Permissions Form (2)
79. Statewide 911 GIS Repository User RolesPSAP Administrator – This role is established for the person who will be managing the accounts for the users with a specific PSAP jurisdiction.Alternate PSAP Administrator – This role is established for a person to provide a backup role to the PSAP Administrator for assigning logins or accounts.Data Importer(s) – This role is established for a person who will be providing GIS data updates to the repository system. (can be multiple PSAP or county individuals depending on who is maintaining data, can be a vendor)Data Exporter (s) – This role is established for a person who will be extracting GIS data from the repository for 911 purposes. (e.g. person integrating GIS data with CAD system)
80. Statewide 911 GIS Repository User Roles (2)
81. Requested Information to Setting PermissionsPSAP Administrators complete and submit user request form Email to Lyndsay Stephens - StephensL5@michigan.govIn same email include list of PSAPs you initially grant data download accessIf you have submitted form but not PSAP download access for other jurisdictions, please email those PSAP names to Lyndsay Stephens
82. Requested Information to Setting Permissions (2)As of May 11, 2022
83. Upcoming Activities (2)Outreach about onboarding to upgraded repositoryConfirming PSAP rolesConfiguring permissionsTraining sessionsWebinars April 19th and 26th – Overview of onboarding and systemTraining sessions April 28th (pilot group), May 12th and May 24thWeb site for programDTMB - Michigan Statewide NG911 GIS RepositoryOnboarding and updating data uploadsRoad centerlines - Training Phase 1Site structure points – Training Phase 1Emergency Response Boundaries – TBD Future TrainingPSAP Boundary reviews – Training Phase 1Coordination between 911 and GIS teams
84. NENA GIS Standards DocumentsNENA Standard for NG911 GIS Data Model - NENA-STA-006.1.1-2020Synchronizing GIS Databases with MSAG and ALI – NENA 71-501NENA Development of Site/Structure Address Points for 911 – 014.1.2015NENA Standards for the Provisioning and Maintenance of GIS data to ECRF and LVFs – NENA STA 005.1.1-2017NENA Information Document for GIS Data Stewardship for NG911 – NENA INF – 028.1-2020
85. QuestionsMGF Data Gateway and NG911 Repository Support HelpdeskDTMB-NG911GIS@michigan.govPermission Forms for RolesLyndsay StephensCertification Section SpecialistMichigan State Police State 911 OfficeStephensL5@michigan.gov517-375-4402