Use the GeographicCoordinates component to either update or add the latitude and longitudes for a stack release point. This information is required for stack release points. For those stack release points for which you don't have specific geographic coordinates for the release point itself, you can assign the facility site geographic coordinates to one or more emissions release points through the EIS Gateway.
Geographic coordinate information should not be submitted and will not be stored for portable point source facilities.
Protected data. If EPA has designated the geographic coordinate information for a facility site or emission release points as protected, the submitted data will not be accepted. Your feedback report will clearly indicate the reason and provide relevant information about the status. However, you may request that a data element that has been flagged as protected be updated by submitting a support request through the EIS Gateway.
The measure of the angular distance on a meridian north or south of the equator.
User Role AccessibilitySLT, Inventory Developer
| Number | Name | Description | Type | Severity | 156 | Latitude Measure Present | The latitude measure is required when reporting the Geographic Coordinates component. The component and all dependent data will not be stored if there are missing required data. | Present | Critical |
|---|---|---|---|---|
| 281 | Latitude Measure Data Type | This element must be reported as a decimal. | Format | Critical |
| 592 | Latitude Measure Range | Must be greater than or equal to 17 and less than or equal to 71.5. | Range | Critical |
| 594 | Release Point latitude coordinate tolerance check | Release point latitude coordinates within facility coordinate tolerance. | Range | Critical |
The measure of the angular distance on a meridian east or west of the prime meridian.
User Role AccessibilitySLT, Inventory Developer
| Number | Name | Description | Type | Severity |
|---|---|---|---|---|
| 157 | Longitude Measure Present | The longitude measure is required when reporting the Geographic Coordinates component. The component and all dependent data will not be stored if there are missing required data. | Present | Critical |
| 282 | Longitude Measure Data Type | This element must be reported as a decimal. | Format | Critical |
| 593 | Longitude Measure Range | Must be greater than or equal to -177 and less than or equal to -64. | Range | Critical |
| 595 | Release Point longitude coordinate tolerance check | Release point longitude coordinates within facility coordinate tolerance. | Range | Critical |
The 2nd measure of the angular distance on a meridian north or south of the equator.
User Role AccessibilitySLT, Inventory Developer
| Number | Name | Description | Type | Severity |
|---|---|---|---|---|
| 156 | Latitude Measure Present | The latitude measure is required when reporting the Geographic Coordinates component. The component and all dependent data will not be stored if there are missing required data. | Present | Critical |
| 281 | Latitude Measure Data Type | This element must be reported as a decimal. | Format | Critical |
| 592 | Latitude Measure Range | Must be greater than or equal to 17 and less than or equal to 71.5. | Range | Critical |
| 594 | Release Point latitude coordinate tolerance check | Release point latitude coordinates within facility coordinate tolerance. | Range | Critical |
| 598 | Fugitive 2-D Release Point Geographic Coordinate Midpoint Pair Uniqueness | Fugitive 2-D release points cannot have identical latitude AND longitude midpoint geographic coordinates. | Duplication | Critical |
The 2nd measure of the angular distance on a meridian east or west of the prime meridian.
User Role AccessibilitySLT, Inventory Developer
| Number | Name | Description | Type | Severity |
|---|---|---|---|---|
| 157 | Longitude Measure Present | The longitude measure is required when reporting the Geographic Coordinates component. The component and all dependent data will not be stored if there are missing required data. | Present | Critical |
| 282 | Longitude Measure Data Type | This element must be reported as a decimal. | Format | Critical |
| 593 | Longitude Measure Range | Must be greater than or equal to -177 and less than or equal to -64. | Range | Critical |
| 595 | Release Point longitude coordinate tolerance check | Release point longitude coordinates within facility coordinate tolerance. | Range | Critical |
| 598 | Fugitive 2-D Release Point Geographic Coordinate Midpoint Pair Uniqueness | Fugitive 2-D release points cannot have identical latitude AND longitude midpoint geographic coordinates. | Duplication | Critical |
The number that represents the proportional distance on the ground for one unit of measure on the map or photo.
User Role AccessibilitySLT, Inventory Developer
| Number | Name | Description | Type | Severity |
|---|---|---|---|---|
| 283 | Source Map Scale Number Data Type | This element must be reported as an integer. | Format | Critical |
| 1110 | Source Scale Map Number Range | Must be between 1 and 999,999, inclusive. | Range | Critical |
The horizontal measure, in meters, of the relative accuracy of the latitude and longitude coordinates.
User Role AccessibilitySLT, Inventory Developer
| Number | Name | Description | Type | Severity |
|---|---|---|---|---|
| 284 | Horizontal Accuracy Measure Data Type | This element must be reported as an integer. | Format | Critical |
| 1111 | Horizontal Accuracy Measure Critical Range | Must be between 0 and 999,999, inclusive. | Range | Critical |
The horizonal accuracy unit of measure.
User Role AccessibilitySLT, Inventory Developer
| Number | Name | Description | Type | Severity |
|---|---|---|---|---|
| 1482 | Horizontal Accuracy Unit of Measure Valid | Horizontal accuracy unit of measure must be reported in meters (m). | Code | Critical |
| 1709 | Horizontal Accuracy Measure and Unit of Measure Present | Horizontal accuracy measure and horizontal accuracy unit of measure must be reported together. | Present | Critical |
The horizontal accuracy unit of measure.
User Role AccessibilitySLT, Inventory Developer
| Number | Name | Description | Type | Severity |
|---|---|---|---|---|
| 55 | Horizontal Collection Method Code Valid | Must match value in code list. | Code | Critical |
The code that represents the reference datum used in determining latitude and longitude coordinates.
User Role AccessibilitySLT, Inventory Developer
| Number | Name | Description | Type | Severity |
|---|---|---|---|---|
| 56 | Horizontal Reference Datum Code Valid | Must match value in code list. | Code | Critical |
The code that represents the place for which geographic coordinates were established.
User Role AccessibilitySLT, Inventory Developer
| Number | Name | Description | Type | Severity |
|---|---|---|---|---|
| 58 | Geographic Reference Point Code Valid | Must match value in code list. | Code | Critical |
The calendar date when data were collected.
User Role AccessibilitySLT, Inventory Developer
| Number | Name | Description | Type | Severity |
|---|---|---|---|---|
| 285 | Data Collection Date Data Type | Date in the format of YYYY-MM-DD. | Format | Critical |
| 307 | Data Collection Date Range | The data collection date must be between 01/01/1900 to 12/31/2050. | Range | Critical |
The text that provides additional information about the geographic coordinates.
User Role AccessibilitySLT, Inventory Developer
| Number | Name | Description | Type | Severity |
|---|---|---|---|---|
| 286 | Location Comments Text Data Type | Maximum allowable width of 200 characters. Longer submissions will be truncated. | Format | Warning |
The measure of elevation (i.e., the altitude), above or below a reference datum.
User Role AccessibilitySLT, Inventory Developer
| Number | Name | Description | Type | Severity |
|---|---|---|---|---|
| 287 | Vertical Measure Data Type | This element must be reported as an integer. | Format | Critical |
| 1133 | Vertical Measure Critical Range | Must be between -1000 and 999,999; inclusive. | Range | Critical |
The vertical unit of measure.
User Role AccessibilitySLT, Inventory Developer
| Number | Name | Description | Type | Severity |
|---|---|---|---|---|
| 1483 | Vertical Unit of Measure Valid | Vertical unit of measure must be reported in meters (m). | Code | Critical |
| 1710 | Vertical Measure and Unit of Measure Present | Vertical measure and vertical measure unit of measure must be reported together. | Present | Critical |
The code that identifies the method used to collect the vertical measure (i.e., the altitude) of a reference point.
User Role AccessibilitySLT, Inventory Developer
| Number | Name | Description | Type | Severity |
|---|---|---|---|---|
| 59 | Vertical Collection Method Code Valid | Must match value in code list. | Code | Critical |
The code that represents the reference datum used to determine the vertical measure (i.e., the altitude).
User Role AccessibilitySLT, Inventory Developer
| Number | Name | Description | Type | Severity |
|---|---|---|---|---|
| 60 | Vertical Reference Datum Code Valid | Must match value in code list. | Code | Critical |
The code that represents the process used to verify the latitude and longitude coordinates.
User Role AccessibilitySLT, Inventory Developer
| Number | Name | Description | Type | Severity |
|---|---|---|---|---|
| 61 | Verification Method Code Valid | Must match value in code list. | Code | Critical |
The code that represents the party responsible for providing the latitude and longitude coordinates.
User Role AccessibilitySLT, Inventory Developer
| Number | Name | Description | Type | Severity |
|---|---|---|---|---|
| 62 | Coordinate Data Source Code Valid | Must match value in code list. | Code | Critical |
The code that represents the geometric entity represented by one point or a sequence of latitude and longitude points.
User Role AccessibilitySLT, Inventory Developer
| Number | Name | Description | Type | Severity |
|---|---|---|---|---|
| 63 | Geometric Type Code Valid | Must match value in code list. | Code | Critical |
Indicator preventing the value of the geographic coordinates from being modified.
User Role AccessibilityInventory Developer
| Number | Name | Description | Type | Severity |
|---|---|---|---|---|
| 1231 | Facility Site Geographic Coordinates Protected | If the data in the EIS for facility site geographic coordinates are protected, the data will not be stored. A request to unprotect the data can be made through the Gateway. | Conditional | Protected Warning |
SLT, Inventory Developer
| Number | Name | Description | Type | Severity |
|---|---|---|---|---|
| 1170 | Geographic Coordinates Not Present for Portable Facilities | If the county FIPS code is 777, then the geographic coordinates component will not be accepted. All data elements in the geographic coordinates component will not be stored. | Present | Critical |