proposed version 2: nsgic broadband data model. why v2? fix minor but significant issues ease of...

13
Proposed Version 2: NSGIC Broadband Data Model

Upload: george-oneal

Post on 30-Dec-2015

217 views

Category:

Documents


4 download

TRANSCRIPT

Page 1: Proposed Version 2: NSGIC Broadband Data Model. Why v2? Fix minor but significant issues Ease of use, including shapefile compatibility Address Service

Proposed Version 2:NSGIC Broadband Data

Model

Page 2: Proposed Version 2: NSGIC Broadband Data Model. Why v2? Fix minor but significant issues Ease of use, including shapefile compatibility Address Service

Why v2?

• Fix minor but significant issues

• Ease of use, including shapefile compatibility

• Address Service Overview reporting:– MSA, RSA, CMAs

• Feds desire for state-level feature identifiers

Page 3: Proposed Version 2: NSGIC Broadband Data Model. Why v2? Fix minor but significant issues Ease of use, including shapefile compatibility Address Service

Why not stick with NOFA?

• All data requested has geographic element for validation and reporting

• Impact of NOFA Clarification on data model not explicitly provided

• Further standardization of state reporting likely to improve data aggregation efficiency

• NSGIC asked if there was a need and was encouraged to proceed

Page 4: Proposed Version 2: NSGIC Broadband Data Model. Why v2? Fix minor but significant issues Ease of use, including shapefile compatibility Address Service

Service – Address Level

Page 5: Proposed Version 2: NSGIC Broadband Data Model. Why v2? Fix minor but significant issues Ease of use, including shapefile compatibility Address Service

Service – Road Segment Level

Note: If there are different City, StateAbbr, Zip5 and / or Zip4 values for different sides of the road segment, either value may be reported.

Page 6: Proposed Version 2: NSGIC Broadband Data Model. Why v2? Fix minor but significant issues Ease of use, including shapefile compatibility Address Service

Service – Census Block Level

Note: Census 2009 geography is encouraged, but blocks should be merged to remove Suffix ID. At this time, the more detailed information is not required, but may be added in future submittals.

Page 7: Proposed Version 2: NSGIC Broadband Data Model. Why v2? Fix minor but significant issues Ease of use, including shapefile compatibility Address Service

Service – Community Anchor Institutions

Page 8: Proposed Version 2: NSGIC Broadband Data Model. Why v2? Fix minor but significant issues Ease of use, including shapefile compatibility Address Service

Service – Wireless Service Areas

Note: Since only one spectrum can be reported per polygon, providers that offer more than one type of service must have a polygon for each service. In some areas this will lead to overlapping polygons. By “service” is meant any unique combinations of TransTech and Spectrum

Page 9: Proposed Version 2: NSGIC Broadband Data Model. Why v2? Fix minor but significant issues Ease of use, including shapefile compatibility Address Service

Service – Overview/Summary Areas (MSA, CoFIPS, or CMA)

Note: Allows for reporting summary (overview) information by one of three different geographies. Guidance on which geography is preferred will be issued by the NTIA is desired.

Page 10: Proposed Version 2: NSGIC Broadband Data Model. Why v2? Fix minor but significant issues Ease of use, including shapefile compatibility Address Service

Infrastructure – Last Mile Connection Point

Page 11: Proposed Version 2: NSGIC Broadband Data Model. Why v2? Fix minor but significant issues Ease of use, including shapefile compatibility Address Service

Infrastructure – Middle Mile Connection Point

Page 12: Proposed Version 2: NSGIC Broadband Data Model. Why v2? Fix minor but significant issues Ease of use, including shapefile compatibility Address Service

Customize!• States are expected to come up with custom,

expanded schema implementations for their own work flows

• This is just one possible foundation to build upon…but also as a potential submission vehicle

• Free XRay 4.1 tools allow ESRI geodatabase design/refinement in MS Excel

http://arcscripts.esri.com/details.asp?dbid=15119

Page 13: Proposed Version 2: NSGIC Broadband Data Model. Why v2? Fix minor but significant issues Ease of use, including shapefile compatibility Address Service

Resourcescurrently at: ftp://ftp.agrc.utah.gov/Broadband

(case sensitive URL)

HTML Schema Summary

Empty, Zipped 9.3 File Geodatabase

.png Schema Summary This .ppt