The EarthScope Consortium streams three-dimensional GNSS high rate (1Hz) position time series from nearly a thousand GNSS stations to study earthquakes, volcanos, tsunamis, hydrologic loads, and glaciers. The data is made available via the National Data Platform pilot project.

The EarthScope Consortium streams three-dimensional GNSS high rate (1Hz) position time series from nearly a thousand GNSS stations to study earthquakes, volcanos, tsunamis, hydrologic loads, and glaciers. The data is made available via the National Data Platform pilot project.

Global Navigation Satellite System (GNSS) Station unavco/gnss/Cascadia/NDAP/7880/L0/00:00:01 Name: NDAP_SCGN_CS2000_1HZ Processing Level: L0 measurement_technique: gnss variable_measured: position creator:UNAVCO data_start_time:2016-06-25T07:12:19 data_stop_time:2018-03-22T05:59:59 GPS/GNSS instrumentation records broadcast signals from the GPS and other satellite constellation, and these raw data are converted into standard daily RINEX files suitable for processing. GPS/GNSS data are recorded at 15-s or 30-s intervals. Several hundred stations of the PBO network also supply downloaded or streamed 1-s data for archiving and distribution. In addition highrate data of 1 Hz or 5 Hz may be Custom Data Requested in association with an event such as a significant earthquake. For data of all rates UNAVCO translates to RINEX and quality checks the data using teqc. GAGE Analysis Centers process data for all 1100 sites in the PBO GPS/GNSS network and for other sites, including most of the sites in COCONet in the Caribbean region and an additional 500 sites distributed across North America, most of which are operated by other institutions. The final, processed products are SINEX solutions, position ti Web Service Link ['The hydrologic models are surface-loading displacement time series calculated at GAGE-processed sites from hydrological data. Soil moisture, snow-water equivalent from snowpack, and water stored in vegetation exert a load on the Earth's surface that is modeled to obtain displacements at GPS/GNSS sites. Outputs GPS crustal motion velocity field estimates. '] Web Service Link [ 'Results from daily GPS station position solutions are combined to generate long-term velocity estimate solutions of stations in IGS08 and NAM08 (North America fixed) reference frames. Station offsets due to earthquakes and equipment changes are estimated and low-quality outliers due to snow, for example, are removed from the velocity estimate solutions ']

Global Navigation Satellite System (GNSS) Station unavco/gnss/Nucleus/NDAP/843/L1/00:00:15 Name: NDAP_SCGN_CS2000 Processing Level: L1 measurement_technique: gnss variable_measured: position creator:UNAVCO data_start_time:2000-12-30T07:01:00 data_stop_time:2018-03-22T05:59:45 GPS/GNSS instrumentation records broadcast signals from the GPS and other satellite constellation, and these raw data are converted into standard daily RINEX files suitable for processing. GPS/GNSS data are recorded at 15-s or 30-s intervals. Several hundred stations of the PBO network also supply downloaded or streamed 1-s data for archiving and distribution. In addition highrate data of 1 Hz or 5 Hz may be Custom Data Requested in association with an event such as a significant earthquake. For data of all rates UNAVCO translates to RINEX and quality checks the data using teqc. GAGE Analysis Centers process data for all 1100 sites in the PBO GPS/GNSS network and for other sites, including most of the sites in COCONet in the Caribbean region and an additional 500 sites distributed across North America, most of which are operated by other institutions. The final, processed products are SINEX solutions, position ti Web Service Link ['The hydrologic models are surface-loading displacement time series calculated at GAGE-processed sites from hydrological data. Soil moisture, snow-water equivalent from snowpack, and water stored in vegetation exert a load on the Earth's surface that is modeled to obtain displacements at GPS/GNSS sites. Outputs GPS crustal motion velocity field estimates. '] Web Service Link [ 'Results from daily GPS station position solutions are combined to generate long-term velocity estimate solutions of stations in IGS08 and NAM08 (North America fixed) reference frames. Station offsets due to earthquakes and equipment changes are estimated and low-quality outliers due to snow, for example, are removed from the velocity estimate solutions ']

Global Navigation Satellite System (GNSS) Station unavco/gnss/PBO-Nucleus High Rate/NDAP/2467/L0/00:00:00.2 Name: NDAP_SCGN_CS2000_5HZ Processing Level: L0 measurement_technique: gnss variable_measured: position creator:UNAVCO data_start_time:2007-03-30T06:00:00 data_stop_time:2014-04-03T15:59:59 GPS/GNSS instrumentation records broadcast signals from the GPS and other satellite constellation, and these raw data are converted into standard daily RINEX files suitable for processing. GPS/GNSS data are recorded at 15-s or 30-s intervals. Several hundred stations of the PBO network also supply downloaded or streamed 1-s data for archiving and distribution. In addition highrate data of 1 Hz or 5 Hz may be Custom Data Requested in association with an event such as a significant earthquake. For data of all rates UNAVCO translates to RINEX and quality checks the data using teqc. GAGE Analysis Centers process data for all 1100 sites in the PBO GPS/GNSS network and for other sites, including most of the sites in COCONet in the Caribbean region and an additional 500 sites distributed across North America, most of which are operated by other institutions. The final, processed products are SINEX solutions, position ti Web Service Link ['The hydrologic models are surface-loading displacement time series calculated at GAGE-processed sites from hydrological data. Soil moisture, snow-water equivalent from snowpack, and water stored in vegetation exert a load on the Earth's surface that is modeled to obtain displacements at GPS/GNSS sites. Outputs GPS crustal motion velocity field estimates. '] Web Service Link [ 'Results from daily GPS station position solutions are combined to generate long-term velocity estimate solutions of stations in IGS08 and NAM08 (North America fixed) reference frames. Station offsets due to earthquakes and equipment changes are estimated and low-quality outliers due to snow, for example, are removed from the velocity estimate solutions ']

This dataset contains number of crimes filed under each category of the Indian Penal Code (IPC), number of victims of those crimes, and average crime rate. The data is presented separately by IPC category and sub-category. Data are available at the state/UT level for 2018.

● 7060_source_data.csv: The raw data from the source with original administrative dimensions. This dataset may have already been restructured by scraping PDFs, combining files, or pivoting tables to fit the proper tabular format used by NDAP, but the actual data values remain unchanged. ● NDAP_REPORT_7060.csv: The final standardised data using LGD geographic dimensions as seen on NPAP. ● 7060_metadata.csv: Variable-level metadata, including the following fields: ❖ VariableName: The full variable name as it appears in the data ❖ VariableCode: A unique variable code that is used as a short name for the variable during internal processing and can be used for simplicity if desired ❖ Type_Of_Variable: The classification of the column, whether it is a dimension or a variable (i.e. indicator) ❖ Unit_Of_Measure: ❖ Aggregation_Type: The default aggregation function to be used when aggregating each variable ❖ Weighing_Variable_Name: The weight assigned to each variable that is used by default when aggregating ❖ Weighing_Variable_ID: The weighting variable id corresponding to the weighing variable name ❖ Long_Description: A more descriptive definition of the variable ❖ Scaling_factor: Scaling factor from source ● 7060_KEYS.csv: The key which maps source administrative units to the standardised Local Government Directory (LGD) dimensions. This file also contains pre-calculated weights for every constituent unit mapped from the source dimensions into the LGD. You can interpret each row as describing what fraction of the source unit is mapped to a corresponding LGD unit. This file includes the following fields: ❖ src[Unit]Name: The administrative unit name as it appears in the source data. Depending on the dataset, that may include State, District, Subdistrict, Block, Village/Town, etc. ❖ [Unit]Name: The standardised administrative unit name as it appears in the LGD. Depending on the dataset, that may include State, District, Subdistrict, Block, Village/Town, etc. ❖ [Unit]Name: The standardised administrative unit code corresponding to the unit name in the LDG. ❖ Year: The year in which the data was collected or reported. Depending on the dataset, any other temporal variables may also be present (Quarter, Month, Calendar Day, etc.) ❖ Number_Of_Children: The number of LGD units associated with the mapping described by an individual row. Units from the source that have undergone a split will contain multiple children. ❖ Number_Of_Parents: The number of source units associated with the mapping described by an individual row. Units from the source that have undergone a merge will contain multiple parents. ❖ Weighing_Variables: Households, Population, Male Population, Female Population, Land Area (Total, Rural, and Urban versions of each). For each weighing variable there are the following associated fields: ■ Count: the total count of households, population, or land area mapped from the source unit to the LGD unit for that particular row (NumberOfHouseholds, TotalPopulation, LandArea). ■ Mapping_Error: the percentage error due to missing villages in the base data, meaning what fraction of the weighing variable is dropped because the microdata could not be mapped to the LGD. ■ Weighing_Ratio: the weighing ratio for that constituent match of source unit to LGD unit for each particular row. This is the fraction applied to the source data to achieve the LGD-standardised final data