16
Slide 1 -- June 17, 2022 RAMONA Overview

Slide 1 -- February 24, 2016 RAMONA Overview. Slide 2 -- February 24, 2016 Project Goals Develop a functional and easy-to-use tool that will encourage

Embed Size (px)

DESCRIPTION

Slide 3 -- February 24, 2016 Acrobat FileAcrobat File ed out ed out Completed on paperCompleted on paper FAX’ed back to DNRFAX’ed back to DNR Data entered and reconciled by one personData entered and reconciled by one person Maryland and Pennsylvania

Citation preview

Page 1: Slide 1 -- February 24, 2016 RAMONA Overview. Slide 2 -- February 24, 2016 Project Goals Develop a functional and easy-to-use tool that will encourage

Slide 1 -- May 6, 2023

RAMONA Overview

Page 2: Slide 1 -- February 24, 2016 RAMONA Overview. Slide 2 -- February 24, 2016 Project Goals Develop a functional and easy-to-use tool that will encourage

Slide 2 -- May 6, 2023

Project Goals• Develop a functional and easy-to-use tool

that will encourage state and local governments to inventory their data and keep their inventories up-to-date (at least 75% don’t create metadata now)

• Provide a tool that statewide coordination councils will get behind to prevent a proliferation of systems that can’t communicate with each other

Page 3: Slide 1 -- February 24, 2016 RAMONA Overview. Slide 2 -- February 24, 2016 Project Goals Develop a functional and easy-to-use tool that will encourage

Slide 3 -- May 6, 2023

• Acrobat FileAcrobat File• E-mailed outE-mailed out• Completed on Completed on

paperpaper• FAX’ed back to FAX’ed back to

DNRDNR• Data entered Data entered

and reconciled and reconciled by one personby one person

Maryland and Pennsylvania

Page 4: Slide 1 -- February 24, 2016 RAMONA Overview. Slide 2 -- February 24, 2016 Project Goals Develop a functional and easy-to-use tool that will encourage

Slide 4 -- May 6, 2023

Metadata CreationOriginal Access Database

Query DatabasePopulate WORD

Document Using MACRO

Create Text File

Run Through “MP”

Page 5: Slide 1 -- February 24, 2016 RAMONA Overview. Slide 2 -- February 24, 2016 Project Goals Develop a functional and easy-to-use tool that will encourage

Slide 5 -- May 6, 2023

Indiana

Page 6: Slide 1 -- February 24, 2016 RAMONA Overview. Slide 2 -- February 24, 2016 Project Goals Develop a functional and easy-to-use tool that will encourage

Slide 6 -- May 6, 2023

North Carolina

Page 7: Slide 1 -- February 24, 2016 RAMONA Overview. Slide 2 -- February 24, 2016 Project Goals Develop a functional and easy-to-use tool that will encourage

Slide 7 -- May 6, 2023

Management InformationRestrict Access to Data?

29.6%

48.0%

18.4%

3.9%

Yes No Sometimes Not Sure

Restrict Redistribution of Data?

48.7%

35.5%

11.2%4.6%

Yes No Sometimes Not Sure

Charge for Data?

53.9%

28.9%

15.8%1.3%

Yes No Sometimes Not Sure

Page 8: Slide 1 -- February 24, 2016 RAMONA Overview. Slide 2 -- February 24, 2016 Project Goals Develop a functional and easy-to-use tool that will encourage

Slide 8 -- May 6, 2023

User Access

GOS PortalClearinghouse Nodes RAMONA

InternetRegistered UserPublic User

Trusted Partner

“Wrapper”

Trusted Partner

System Administrator

Page 9: Slide 1 -- February 24, 2016 RAMONA Overview. Slide 2 -- February 24, 2016 Project Goals Develop a functional and easy-to-use tool that will encourage

Slide 9 -- May 6, 2023

Required FeaturesInternet tool to inventory data (only issue is

how thoroughly we document)Provide a search capability to discover data• Develop stock/custom report formats• Create status maps• Automatically generate metadata from

inventory database and post to GOS• Automatically update the metadata forms

when changes are made to inventory

Page 10: Slide 1 -- February 24, 2016 RAMONA Overview. Slide 2 -- February 24, 2016 Project Goals Develop a functional and easy-to-use tool that will encourage

Slide 10 -- May 6, 2023

Required FeaturesIntegrate with OGC environment for

automatic data discovery and access• Maintain a professional directory (Rolodex)Track applications developmentTrack potential/future data collaboration

projects• Provide adequate security with open

architecture design

Page 11: Slide 1 -- February 24, 2016 RAMONA Overview. Slide 2 -- February 24, 2016 Project Goals Develop a functional and easy-to-use tool that will encourage

Slide 11 -- May 6, 2023

User Profile and Data Documentation

• User Profile (15 to 30 minutes)– Organization and contact information– GIS and systems information – Data distribution policies– Internet mapping services

• Data Profile (2 to 5 minutes per layer)– Consistent questions on all layers– Additional questions on select layers

Page 12: Slide 1 -- February 24, 2016 RAMONA Overview. Slide 2 -- February 24, 2016 Project Goals Develop a functional and easy-to-use tool that will encourage

Slide 12 -- May 6, 2023

Layers Assigned to ISO Headings

Locations & Geodetic Networks Geographic Coordinates Data Base (GCDB)

  Horizontal Control Monuments

  Locations Name File (GNIS)

  Vertical Control Monuments

Imagery, Base Maps & Land Cover Digital Raster Graphics

  Impervious Surfaces

  Land Cover

  Orthoimagery

  Rectified Imagery

Elevation & Derived Products Bathymetric Contours

  Digital Elevation Model

  Digital Terrain Models

  Spot Elevations

  Topographic Contours

  Triangulated Irregular Network

ISO Heading Layer Name

Page 13: Slide 1 -- February 24, 2016 RAMONA Overview. Slide 2 -- February 24, 2016 Project Goals Develop a functional and easy-to-use tool that will encourage

Slide 13 -- May 6, 2023

Consistent Required Information for Every Data Layer

Scale Choices1:1200

1:2400

1:4800

1:7200

1:12000

1:14400

1:19200

1:24000

1:30000

>1:30000

For This Layer What is the Completion Status? Complete Coverage  

  Partial Coverage  

  No Coverage  

What Was the Source Material For this Layer? Uncorrected Photography  

  Orthophotography  

  Hardcopy Maps  

  LIDAR  

  IFSAR  

  Satellite Imagery  

  Field Survey/GPS  

  Other (Please List) Free Text

What is the Approximate Scale for this Layer? See Table at Right  

What is the Date of the Source Material for this Layer? Free Text 4-digit year  

What is the Date of Production of this Layer? Free Text 4-digit year  

Page 14: Slide 1 -- February 24, 2016 RAMONA Overview. Slide 2 -- February 24, 2016 Project Goals Develop a functional and easy-to-use tool that will encourage

Slide 14 -- May 6, 2023

Required Information Continued

Scale Choices

1:1200

1:2400

1:4800

1:7200

1:12000

1:14400

1:19200

1:24000

1:30000

>1:30000

What is Your Update Frequency? Continually  

  Daily  

  Weekly  

  Monthly  

  Quarterly  

  Semi-Annually  

  Annually  

  As Required  

  Irregularly  

  None Planned  

  Other (Please List) Free Text

What Type of Metadata Do You Produce for this Layer? FGDC Compliant  

  Locally Defined  

  Data Dictionary  

  Other (Please List) Free Text

  None  

What is the Publication Scale for this Data Layer? See Table at Right  

How is This Data Layer Attributed? GIS Attributes  

  Text Annotations  

  Graphic Text Labels  

  Other (Please List) Free Text

  No Attributes  

Page 15: Slide 1 -- February 24, 2016 RAMONA Overview. Slide 2 -- February 24, 2016 Project Goals Develop a functional and easy-to-use tool that will encourage

Slide 15 -- May 6, 2023

Unique Information for Select Data Types

If Your Jurisdiction Creates DEM or Topographic Data, Please Answer the Following Questions.

What Post Spacing Was Used in Your DEM's? See Table at Right

 What Contour Interval Does

Your Data Support? See Table at Right

  Do You Have Breaklines? Yes

    No

 Do You Have Control

Monuments? Yes

    No

 

If Yes, Were They Established With GPS? Yes

    No

 

What is the Date Range That Your Monuments Were Set?

Free Text (years to years prompt)

<1 meter

~1 meter

~2 meter

~3 meter

~4 meter

~5 meter

~6 meter

~7 meter

~8 meter

~9 meter

~10 meter

~15 meter

~20 meter

>20 meter

1'

2'

3'

4'

5'

6'

7'

8'

9'

10'

>10'

Page 16: Slide 1 -- February 24, 2016 RAMONA Overview. Slide 2 -- February 24, 2016 Project Goals Develop a functional and easy-to-use tool that will encourage

Slide 16 -- May 6, 2023

Expected Headaches• Unique Identifier Numbers to exchange data with

Census (TED), FEMA (MIPS), NDOP, etc.• Providing a comprehensive list of layers so that they

are always available in “drop down” form for consistency (Currently ~259 data layers)

• Must “reconcile” Clearinghouse records with RAMONA records to produce meaningful status maps and management reports (1 record for 1 data set)

• Training curve to bring community partners (likes states or counties) on-board

• Quickly managing change when it’s required