2010 VA Information Technologies Agency (VITA)/VA Geographic Information Network (VGIN) Lidar: Eastern Shore, VA (Accomack and Northampton Counties)
OCM Partners
Data Set
(DS)
| ID: 50124
| Published / External
Created: 2017-11-15
|
Last Modified: 2022-08-09
Project (PRJ) | ID: 49401
ID: 50124
Data Set (DS)
* Discovery• First Pass
» Metadata Rubric
Item Identification
* » Title | 2010 VA Information Technologies Agency (VITA)/VA Geographic Information Network (VGIN) Lidar: Eastern Shore, VA (Accomack and Northampton Counties) |
---|---|
Short Name | va2010_vita_eastern_shore_m2634_metadata |
* Status | Completed |
Creation Date | |
Revision Date | |
• Publication Date | 2014-07 |
* » Abstract |
The Virginia Geographic Information Network (VGIN) contracted with Sanborn to provide LiDAR mapping services for Accomack and Northampton counties on the eastern shore of Virginia in the March of 2010. Utilizing multi-return systems, Light Detection and Ranging (LiDAR) data in the form of 3-dimensional positions of a dense set of mass points was collected for approximately 1090 square miles. Of this 1090 sq mile area, 663 sq miles are over land. Collection and delivery of the lidar data were required to meet the USGS LiDAR Guidelines and Base Specifications, version 13 classification scheme. The data available for download from the NOAA Digital Coast are classified as follows: 1 (Unclassified), 2 (Ground), 7 (Low Point/Noise), 9 (Water), and 10 (Ground points in close proximity to breaklines). This project was a cooperative effort funded by The Nature Conservancy (TNC) - Virginia Office, the University of Virginia's Virginia Coast Long-Term Ecological Research Project (VCR/LT ER) and the U.S. Geological Survey (USGS). Users should be aware that this data was not required to be collected at low tide, therefore, there are some flightlines that were collected at low tide and adjacent flightlines that were not collected at low tide. Original contact information: Contact Name: John A. Scrivani Contact Org: Virginia Information Technologies Agency (VITA) Phone: 804.416.6207 Email: john.scrivani@vita.virginia.gov |
* Purpose |
This LIDAR operation was designed to provide a high density set of masspoints within the defined areas. The data set is suitable for the development of contours for use in hydraulic/hydrologic model development, and for assessing environmental impacts. Typical uses for the data set include: flood plain map modernization, map updates, watersheds and other hydro studies per USGS specifications, county mapping projects which include several uses, in addition to flood mitigation assessment, and mapping projects that include accuracy verification, reporting and metadata. |
Notes |
10768 |
Other Citation Details | |
• Supplemental Information |
The Sanborn Report of Survey may be accessed at: ftp://ftp.coast.noaa.gov/pub/DigitalCoast/lidar1_z/geoid18/data/2634/supplemental/va2010_vita_eastern_shore_m2634_survey_report.pdf The Dewberry QA Report may be accessed at: ftp://ftp.coast.noaa.gov/pub/DigitalCoast/lidar1_z/geoid18/data/2634/supplemental/va2010_vita_eastern_shore_m2634_qa_report.pdf A footprint of this data set may be viewed in Google Earth at: ftp://ftp.coast.noaa.gov/pub/DigitalCoast/lidar1_z/geoid18/data/2634/supplemental/va2010_vita_eastern_shore_m2634.kmz |
DOI (Digital Object Identifier) | |
DOI Registration Authority | |
DOI Issue Date |
Keywords
Theme Keywords
Thesaurus | Keyword |
---|---|
ISO 19115 Topic Category | elevation |
None | Drainage Area |
None | Hydraulic |
None | Hydrographic |
None | Hydrology |
Temporal Keywords
Thesaurus | Keyword |
---|---|
* Spatial Keywords
Thesaurus | Keyword |
---|---|
Stratum Keywords
Thesaurus | Keyword |
---|---|
Instrument Keywords
Thesaurus | Keyword |
---|---|
Platform Keywords
Thesaurus | Keyword |
---|---|
Physical Location
• » Organization | Office for Coastal Management |
---|---|
• » City | Charleston |
• » State/Province | SC |
• Country | |
• » Location Description |
Data Set Information
* Data Set Scope Code | Data Set |
---|---|
• Data Set Type | |
• Maintenance Frequency | |
Maintenance Note |
None planned |
» Data Presentation Form | |
• Entity Attribute Overview | |
Entity Attribute Detail Citation | |
Entity Attribute Detail URL | |
Distribution Liability |
Any conclusions drawn from the analysis of this information are not the responsibility of the Virginia Information Technologies Agency (VITA), Sanborn Map Company, Inc., the Office for Coastal Management or its partners. VITA does not warrant these data for any particular use and is not responsible for any damages resulting from the use of the data. Contact VITA for more details. |
Data Set Credit | Acknowledgement of VITA appreciated in products derived and used from the data. VITA asks to be credited in derived products. Also credit The Nature Conservancy - Virginia Office, the University of Virginia's Virginia Coast Reserve Long-Term Ecological Research Project (VCR/LT ER), and the U.S. Geological Survey (USGS). |
Support Roles
* » Support Role | Data Steward |
---|---|
* » Date Effective From | 2014-07 |
Date Effective To | |
Organization | NOAA Office for Coastal Management (NOAA/OCM) |
Address |
2234 South Hobson Ave Charleston, SC 29405-2413 |
Email Address | coastal.info@noaa.gov |
Phone | (843) 740-1202 |
Fax | |
Mobile | |
URL | https://coast.noaa.gov |
Business Hours | |
Contact Instructions |
* » Support Role | Distributor |
---|---|
* » Date Effective From | 2014-07 |
Date Effective To | |
Organization | NOAA Office for Coastal Management (NOAA/OCM) |
Address |
2234 South Hobson Ave Charleston, SC 29405-2413 |
Email Address | coastal.info@noaa.gov |
Phone | (843) 740-1202 |
Fax | |
Mobile | |
URL | https://coast.noaa.gov |
Business Hours | |
Contact Instructions |
* » Support Role | Metadata Contact |
---|---|
* » Date Effective From | 2014-07 |
Date Effective To | |
Organization | NOAA Office for Coastal Management (NOAA/OCM) |
Address |
2234 South Hobson Ave Charleston, SC 29405-2413 |
Email Address | coastal.info@noaa.gov |
Phone | (843) 740-1202 |
Fax | |
Mobile | |
URL | https://coast.noaa.gov |
Business Hours | |
Contact Instructions |
* » Support Role | Point of Contact |
---|---|
* » Date Effective From | 2014-07 |
Date Effective To | |
Organization | NOAA Office for Coastal Management (NOAA/OCM) |
Address |
2234 South Hobson Ave Charleston, SC 29405-2413 |
Email Address | coastal.info@noaa.gov |
Phone | (843) 740-1202 |
Fax | |
Mobile | |
URL | https://coast.noaa.gov |
Business Hours | |
Contact Instructions |
* » Support Role | |
---|---|
* » Date Effective From | |
Date Effective To | |
* » Contact | |
* Contact Instructions |
* » Support Role | |
---|---|
* » Date Effective From | |
Date Effective To | |
* » Contact | |
* Contact Instructions |
* » Support Role | |
---|---|
* » Date Effective From | |
Date Effective To | |
* » Contact | |
* Contact Instructions |
Extents
Currentness Reference | Ground Condition |
---|
Extent Group 1
Extent Description |
---|
Extent Group 1 / Geographic Area 1
* » W° Bound | -76.03791 |
---|---|
* » E° Bound | -75.240122 |
* » N° Bound | 38.044868 |
* » S° Bound | 37.072363 |
* » Description |
Extent Group 1 / Vertical Extent
EPSG Code | |
---|---|
Vertical Minimum | |
Vertical Maximum |
Extent Group 1 / Time Frame 1
* » Time Frame Type | Range |
---|---|
* » Start | 2010-03-21 |
End | 2010-03-28 |
Alternate Start As Of Info | |
Alternate End As Of Info | |
Description |
Spatial Information
Spatial Resolution
Angular Distance | |
---|---|
Angular Distance Units | |
Horizontal Distance | |
Horizontal Distance Units | |
Vertical Distance | |
Vertical Distance Units | |
Equivalent Scale Denominator | |
Level of Detail Description |
Spatial Representation
Grid Representation Used? | |
---|---|
Vector Representation Used? | Yes |
Text / Table Representation Used? | |
TIN Representation Used? | |
Stereo Model Representation Used? | |
Video Representation Used? |
Grid Representation
Dimension Count | |||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Cell Geometry | |||||||||||||
Transformation Parameter Available? | |||||||||||||
Axis Dimension |
|||||||||||||
|
|||||||||||||
Axis Dimension |
|||||||||||||
|
Vector Representation
Topology Level | |
---|---|
Complex Object Present? | |
Complex Object Count | |
Composite Object Present? | |
Composite Object Count | |
Curve Object Present? | |
Curve Object Count | |
Point Object Present? | |
Point Object Count | |
Solid Object Present? | |
Solid Object Count | |
Surface Object Present? | |
Surface Object Count |
Reference Systems
Reference System
EPSG Code | |||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Horizontal Resolution |
|||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||
Vertical Resolution |
|||||||||||||||||||||||||||||
|
Access Information
Data License | |
---|---|
Data License URL | |
Data License Statement | |
* » Security Class | Unclassified |
* Security Classification System | |
Security Handling Description | |
• Data Access Policy | |
» Data Access Procedure |
This data can be obtained on-line at the following URL: https://coast.noaa.gov/dataviewer/#/lidar/search/where:ID=2634 This data set is dynamically generated based on user-specified parameters.; |
• » Data Access Constraints |
None |
• Data Use Constraints |
Users should be aware that temporal changes may have occurred since this data set was collected and some parts of this data set may no longer represent actual surface conditions. Users should not use these data for critical applications without a full awareness of its limitations. |
Metadata Access Constraints | |
Metadata Use Constraints |
Distribution Information
Start Date | |
---|---|
» Download URL | https://coast.noaa.gov/dataviewer/#/lidar/search/where:ID=2634 |
Distributor | |
File Name | Customized Download |
Description |
Create custom data files by choosing data area, product type, map projection, file format, datum, etc. |
File Date/Time | |
File Type (Deprecated) | |
Distribution Format | |
File Size | |
Application Version | |
Compression | |
Review Status |
Start Date | |
---|---|
» Download URL | https://noaa-nos-coastal-lidar-pds.s3.amazonaws.com/laz/geoid18/2634/index.html |
Distributor | |
File Name | Bulk Download |
Description |
Simple download of data files. |
File Date/Time | |
File Type (Deprecated) | |
Distribution Format | |
File Size | |
Application Version | |
Compression | |
Review Status |
Start Date | |
---|---|
End Date | |
» Download URL | |
Distributor | |
File Name | |
Description | |
File Date/Time | |
File Type | |
FGDC Content Type | |
File Size | |
Application Version | |
Compression | |
Review Status |
Start Date | |
---|---|
End Date | |
» Download URL | |
Distributor | |
File Name | |
Description | |
File Date/Time | |
File Type | |
FGDC Content Type | |
File Size | |
Application Version | |
Compression | |
Review Status |
Start Date | |
---|---|
End Date | |
» Download URL | |
Distributor | |
File Name | |
Description | |
File Date/Time | |
File Type | |
FGDC Content Type | |
File Size | |
Application Version | |
Compression | |
Review Status |
URLs
URL | https://coast.noaa.gov/dataviewer |
---|---|
Name | |
URL Type | Online Resource |
File Resource Format | |
Description |
URL | https://coast.noaa.gov |
---|---|
Name | |
URL Type | Online Resource |
File Resource Format | |
Description |
URL | ftp://ftp.coast.noaa.gov/pub/DigitalCoast/lidar1_z/geoid18/data/2634/supplemental/va2010_vita_eastern_shore_m2634.kmz |
---|---|
Name | Browse Graphic |
URL Type | Browse Graphic |
File Resource Format | kmz |
Description |
This graphic shows the lidar coverage of the Virginia Eastern Shore data set. |
URL | |
---|---|
Name | |
URL Type | |
File Resource Format | |
Description |
URL | |
---|---|
Name | |
URL Type | |
File Resource Format | |
Description |
URL | |
---|---|
Name | |
URL Type | |
File Resource Format | |
Description |
Activity Log
Activity Time | 2016-05-23 |
---|---|
Activity Type | |
Responsible Party | |
Description |
Date that the source FGDC record was last modified. |
Activity Time | 2017-11-14 |
---|---|
Activity Type | |
Responsible Party | |
Description |
Converted from FGDC Content Standard for Digital Geospatial Metadata (version FGDC-STD-001-1998) using 'fgdc_to_inport_xml.pl' script. Contact Tyler Christensen (NOS) for details. |
Activity Time | 2018-02-08 |
---|---|
Activity Type | |
Responsible Party | |
Description |
Partial upload of Positional Accuracy fields only. |
Activity Time | 2018-03-13 |
---|---|
Activity Type | |
Responsible Party | |
Description |
Partial upload to move data access links to Distribution Info. |
Activity Time | |
---|---|
Activity Type | |
Responsible Party | |
Description |
Activity Time | |
---|---|
Activity Type | |
Responsible Party | |
Description |
Activity Time | |
---|---|
Activity Type | |
Responsible Party | |
Description |
Issues
Issue Date | |
---|---|
Author | |
Issue |
Issue Date | |
---|---|
Author | |
Issue |
Issue Date | |
---|---|
Author | |
Issue |
Technical Environment
Description |
|
---|
Data Quality
Representativeness | |
---|---|
Accuracy | |
Analytical Accuracy | |
Horizontal Positional Accuracy |
N/A; Quantitative Value: 0.15 meters, Test that produced the value: 15 cm RMSE. United States Geological Survey (USGS) LiDAR Specifications |
Vertical Positional Accuracy |
Dewberry did an independent Qualitative Assurance of the lidar data. Dewberry surveyed 68 checkpoints for the project area extent. One checkpoint was not used in the vertical accuracy testing because it was improperly located on sloped terrain. According to USGS Lidar Guidelines and Base Specifications, v. 13, the consolidated vertical accuracy (CVA) must be 36.3 cm (1.2 ft) or less when computed with the 95th percentile method and the fundamental vertical accuracy (FVA) must be 24.5 cm (0.82 ft) or less when computed with RMSEz (12.5 cm or 0.4 ft) x 1.9600. In the first delivery, the CVA passed with a value of 0.61 ft, but the FVA failed with a value of 1.25 ft. Sanborn then performed numerous edits to the lidar data, including re-calibrations. The second delivery (and all subsequent deliveries) of the data passed vertical accuracy. The FVA tested 0.43 ft (13.1 cm), the RMSE (Root Mean Square Error) is 0.22 ft (6.7 cm). The Dewberry Lidar Quality Assurance (QA) Report - Eastern Shore Virginia (ESVA) Lidar Project may be viewed at: ftp://ftp.coast.noaa.gov/pub/DigitalCoast/lidar1_z/geoid18/data/2634/supplemental/va2010_vita_eastern_shore_m2634_qa_report.pdf Sanborn also did a Quality Assurance on the lidar data. The lidar data was evaluated using 15 GPS checkpoints. The FVA tested 0.343 ft (10.5 cm). The Sanborn Lidar Campaign (Accomack, VA) Report of Survey may be viewed at: ftp://ftp.coast.noaa.gov/pub/DigitalCoast/lidar1_z/geoid18/data/2634/supplemental/va2010_vita_eastern_shore_m2634_survey_report.pdf; Quantitative Value: 0.067 meters, Test that produced the value: 6.7 cm RMSE in open terrain. |
Quantitation Limits | |
Bias | |
Comparability | |
Completeness Measure | |
Precision | |
Analytical Precision | |
Field Precision | |
Sensitivity | |
Detection Limit | |
Completeness Report |
None |
Conceptual Consistency |
None |
» Quality Control Procedures Employed |
Data Management
» Have Resources for Management of these Data Been Identified? | |
---|---|
» Approximate Percentage of Budget for these Data Devoted to Data Management | |
» Do these Data Comply with the Data Access Directive? | |
» Is Access to the Data Limited Based on an Approved Waiver? | |
» If Distributor (Data Hosting Service) is Needed, Please Indicate | |
» Approximate Delay Between Data Collection and Dissemination | |
» If Delay is Longer than Latency of Automated Processing, Indicate Under What Authority Data Access is Delayed |
|
» Actual or Planned Long-Term Data Archive Location | |
» If World Data Center or Other, Specify | |
» If To Be Determined, Unable to Archive, or No Archiving Intended, Explain |
|
» Approximate Delay Between Data Collection and Archiving | |
» How Will the Data Be Protected from Accidental or Malicious Modification or Deletion Prior to Receipt by the Archive? |
|
Lineage
» Lineage Statement |
---|
Sources
Citation Title | |
---|---|
Contact Role Type | |
Contact Type | |
Contact Name | |
Publish Date | |
Extent Type | |
Extent Start Date/Time | |
Extent End Date/Time | |
Citation URL | |
Citation URL Name | |
Citation URL Description | |
Scale Denominator |
Citation Title | |
---|---|
Contact Role Type | |
Contact Type | |
Contact Name | |
Publish Date | |
Extent Type | |
Extent Start Date/Time | |
Extent End Date/Time | |
Citation URL | |
Citation URL Name | |
Citation URL Description | |
Scale Denominator |
Citation Title | |
---|---|
Contact Role Type | |
Contact Type | |
Contact Name | |
Publish Date | |
Extent Type | |
Extent Start Date/Time | |
Extent End Date/Time | |
Citation URL | |
Citation URL Name | |
Citation URL Description | |
Scale Denominator |
Process Steps
Process Step Number | 1 |
---|---|
» Description |
Data Collection: Using an Optech 3100 Light Detection And Ranging (LiDAR) system, 101 flight lines of standard density (1.4 meter ground sample distance) data were collected over areas in Accomack, VA (approximately 1090 square miles). Multiple returns were recorded for each laser pulse along with an intensity value for each return. The data acquisition occurred in 6 missions between March 25, 2010 and March 30, 2010. (NOTE: The data received by the Office for Coastal Management had time stamps in GPS seconds of the week instead of adjusted GPS seconds as required by the USGS version 13 specification. The acquisition report stated that the collections occurred between March 25, 2010 and March 30, 2010. An analysis of the flight IDs and the GPS seconds of the week time stamps suggested this was not correct. The GPS seconds of the week increased with each flight line ID as would be expected until the week restarted on flight 101. Flight 1 GPS seconds of the week indicated a Sunday flight and flight 100 indicated a Saturday flight. GPS times were changed from seconds of the week to adjusted GPS times by assuming flights 1-100 were during GPS week 1576 and flight 101 was during GPS week 1577, covering March 21, 2010 to March 28, 2010). During the LIDAR campaign, the Sanborn field crew conducted a GPS field survey to establish final coordinates of the ground base stations for final processing of the base-remote GPS solutions. |
Process Date/Time | 2010-03-01 00:00:00 |
Process Contact | |
Phone (Voice) | |
Email Address | |
Source |
Process Step Number | 2 |
---|---|
» Description |
Airborne GPS Processing: Airborne GPS data was differentially processed and integrated with the post processed IMU data to derive a Smoothed Best Estimate of Trajectory (SBET). The SBET was used to reduce the LiDAR slant range measurements to a raw reflective surface for each flight line. Airborne GPS is differentially processed using the GrafNAV V7.50 software by Waypoint Consulting of Calgary, Alberta, Canada. |
Process Date/Time | 2010-05-01 00:00:00 |
Process Contact | |
Phone (Voice) | |
Email Address | |
Source |
Process Step Number | 3 |
---|---|
» Description |
IMU data Processing: IMU data provides information concerning roll, pitch and yaw of collection platform during collection event. IMU information allows the pulse vector to be properly placed in 3D space allowing the distance from the aircraft reference point to be properly positioned on the elevation model surface. The IMU data is processed using the PosPac V4.2 software by Applanix Corporation of Richmond Hill, Ontario, Canada. The reflective surface is derived using the ALS Post Processor software by Leica Geosystems GIS & Mapping Division of Atlanta, Georgia. |
Process Date/Time | 2010-06-01 00:00:00 |
Process Contact | |
Phone (Voice) | |
Email Address | |
Source |
Process Step Number | 4 |
---|---|
» Description |
LIDAR Point Classification The classification and quality control (QC) of LiDAR data is carried out using TerraScan software by Terrasolid Limited of Helsinki, Finland. |
Process Date/Time | 2010-07-01 00:00:00 |
Process Contact | |
Phone (Voice) | |
Email Address | |
Source |
Process Step Number | 5 |
---|---|
» Description |
The NOAA Office for Coastal Management downloaded the las data from William and Mary in LAS 1.2 format. The data had GPS time issues and there was confusion on the dates of collection. The data downloaded by the Office for Coastal Management had time stamps in GPS seconds of the week instead of adjusted GPS seconds as required by the USGS version 13 specification. The acquisition report stated that the collections occurred between March 25, 2010 and March 30, 2010. An analysis of the flight IDs and the GPS seconds of the week time stamps suggested this was not correct. The GPS seconds of the week increased with each flight line ID as would be expected until the week restarted on flight 101. Flight 1 GPS seconds of the week indicated a Sunday flight and flight 100 indicated a Saturday flight. GPS times were changed from seconds of the week to adjusted GPS times by assuming flights 1-100 were during GPS week 1576 and flight 101 was during GPS week 1577, covering March 21, 2010 to March 28, 2010. NOAA OCM was able to fix the GPS time issues and from this information, was able to determine the date of collection. There was also some discrepancy in the Geoid used by Sanborn to convert from ellipsoid to NAVD88 elevations. Contacted Sanborn and confirmed that Geoid03 was used. The las files contained lidar elevation and intensity measurements. The data were in VA State Plane South, FIPS 4502, NAD83 coordinates, referenced to NAVD88 (Geoid03) vertical datum in feet. OCM performed the following processing for data storage and Digital Coast provisioning purposes: 1. The data were converted from VA State Plane South coordinates to geographic coordinates. 2. The data were converted from NAVD88 heights to ellipsoid heights using Geoid03. 3. The data were converted from vertical units of feet to meters. 4. The data were filtered for elevation outliers. 5. The data were zipped to laz format. |
Process Date/Time | 2014-06-20 00:00:00 |
Process Contact | |
Phone (Voice) | |
Email Address | |
Source |
Process Step Number | |
---|---|
» Description | |
Process Date/Time | |
Process Contact | |
Phone (Voice) | |
Email Address | |
Source |
Process Step Number | |
---|---|
» Description | |
Process Date/Time | |
Process Contact | |
Phone (Voice) | |
Email Address | |
Source |
Process Step Number | |
---|---|
» Description | |
Process Date/Time | |
Process Contact | |
Phone (Voice) | |
Email Address | |
Source |
Acquisition Information
Instruments
Instrument Unavailable Reason |
---|
Identifier | |
---|---|
Docucomp UUID | |
Instrument / Gear | |
Instrument Type | |
Description |
Identifier | |
---|---|
Docucomp UUID | |
Instrument / Gear | |
Instrument Type | |
Description |
Identifier | |
---|---|
Docucomp UUID | |
Instrument / Gear | |
Instrument Type | |
Description |
Platforms
Platform Unavailable Reason |
---|
Identifier | |||||||
---|---|---|---|---|---|---|---|
Docucomp UUID | |||||||
Description | |||||||
Mounted Instruments |
|||||||
|
Identifier | |||||||
---|---|---|---|---|---|---|---|
Docucomp UUID | |||||||
Description | |||||||
Mounted Instruments |
|||||||
|
Identifier | |||||||
---|---|---|---|---|---|---|---|
Docucomp UUID | |||||||
Description | |||||||
Mounted Instruments |
|||||||
|
FAQs
Date | |
---|---|
Author | |
Question | |
Answer |
Child Items
Rubric scores updated every 15m
Score | Type | Title |
---|---|---|
Related Items
Item Type | Relationship Type | Title |
---|---|---|
Catalog Details
Catalog Item ID | 50124 |
---|---|
Metadata Record Created By | Anne Ball |
Metadata Record Created | 2017-11-15 15:24+0000 |
Metadata Record Last Modified By | SysAdmin InPortAdmin |
» Metadata Record Last Modified | 2022-08-09 17:11+0000 |
Metadata Record Published | 2022-03-16 |
Owner Org | OCMP |
Metadata Publication Status | Published Externally |
Do Not Publish? | N |
Metadata Workflow State | Published / External |
Metadata Last Review Date | 2022-03-16 |
Metadata Review Frequency | 1 Year |
Metadata Next Review Date | 2023-03-16 |
Tags |
---|