|
2. Questions about Specific
Fields
.
1. Requirements for Electronic Data Deliverable
Q: |
What is an acceptable SRP ID? |
A: |
The SRP ID can be either the site id or the
case id. Acceptable formats are provided below.
For more information, contact the assigned case
manager.
- Incident Number: An example of the Incident Number is 98-01-31-1422-35. This format represents YY-MM-DD, followed where available by HH-MM-SS where YY = Year, MM = Month, DD = Day, HH = Hours in military time, MM = Minutes, and SS = Seconds. Dashes may be omitted.
- TMS Closure Number :A TMS closure number (ie C98-0001, N98-0001) is acceptable.
- ISRA Number: A former ISRA number, E##### (ie : E99001 or E20040122)
- EPA Number: EPA numbers (ie NJD######### or NJL#########) are acceptable.
- Preferred ID: Sometimes referred to as SRP ID. Excepted formats are 012345 and G000012345. Preferred IDs are always 6 characters or 10 characters long. Preferred IDs that are 10 characters long always begin with a “G”.
|
Q:
|
What is a
"mandatory field?"
|
A:
|
A mandatory field is a field where data must be provided. The data must adhere to the valid value entries specified in Appendix 2 and Appendix 3 of the SRP-EDI manual.
Refer to the Mandatory Fields page of the EDI Manual for details.
|
Q:
|
Must my table
include a column for fields that are not mandatory?
|
A:
|
Yes, each table submitted must include a column for each field in the SRP-EDI Manual, even if that column includes little or no data. Those fields that are NOT marked "mandatory" by SRP can still provide valuable information (however SRP was not able to make them mandatory in all instances). In some cases, the SRP representative may require the data in "non-mandatory" fields to be submitted. SRP encourages providing information for as many fields as possible. Additionally, EDSA7 processes the fields in the order specified, so all fields must appear in the order specified even if they are empty. If any field is out-of-place, it will result in multiple errors
|
Q:
|
What is the
field length for the "Sample Memo field" in
the HZSAMPLE file?
|
A:
|
The SAMPNOTE (Sample Memo) has been changed to a 254-character field. If notes exceed 254-characters, contact SRP for instructions as to how to submit an equivalent document in XML format.
|
Q:
|
What information
must be provided for TICs in the HZRESULT file?
What do I enter for the "analytical parameter"
name for a TIC? What do I enter for the CAS
# for a TIC?
|
A:
|
If the laboratory is able to identify the TIC at 95% or greater confidence, the actual contaminant name should be used in the ANALTPARAM field, the qualifier "T" (for TIC) should be entered into the RESULT TYPE field, and the contaminant CAS # should be entered into the CAS field.
If confidence is less that 95%, then the TIC should be identified in the ANALTPARAM as an Unknown, followed by the contaminant class (i.e. VO, BN, etc.), analytical method, and retention time in minutes and hundredths of minutes. “Retention time is now entered in the RETEN_TIME field. For example "UNK Benzene Isomer, VO, Method 624 is entered into the ANALTPARAM field and 22.34 is entered into RETEN_TIME.
The Analytical Method must be provided. Without knowing the analytical method, information regarding TICs is useless. For the CAS #, use terms such as UNK1, UNK2, etc. Lastly, the qualifier "T" (for TIC) should be entered into the RESULT TYPE field.
|
Q:
|
How do I report
on a Method Detection Limit (MDL) or Quantification
Type and Quantification Level for a TIC?
|
A:
|
Since the MDL and Quantification
Type/Level are not meaningful numbers for TICs,
these fields should be completed as "NA" (not
applicable), or you may enter the Analytical
Detection Limit for that method (as measured
on the instrument) for that run, or you may
enter the same number detected for the TIC itself.
|
Q:
|
What are acceptable
unit formats for soil and water data?
|
A:
|
The SRP prefers that soil data
be reported in ppm and ground water data be
reported in ppb. However, correct and equivalent
values will be accepted.
|
Q: |
How do I know
whether my location information is correct? |
A: |
The easiest and most accurate way to check your coordinate information is the KML Application on the SRP EDD web site. This application uses spatial software to show you a map of your coordinate locations based on the information in your dataset. The KML Application is integrated into EDSA7 and checks your coordinate information automatically.
Another way would be to review the coordinates shown below. These coordinates define the boundaries of the state of New Jersey. If your location coordinates are within these boundaries, then the location information should be within the state of New Jersey.
Using NJ State
Plane Coordinate System (units US Feet)
SP-X
(Easting) |
SP-Y
(Northing) |
|
193624 |
919467 |
(upper left) |
659481 |
919467 |
(upper right) |
659481 |
35035 |
(lower right) |
193624 |
35035 |
(lower left) |
Using Latitude
and Longitude
Longitude |
Latitude |
|
75° 35' 14.301905"
W |
41° 21' 8.751679"
N |
(upper left) |
73° 53' 25.298142"
W |
41° 21' 21.430150"
N |
(upper right) |
73° 54' 42.068621"
W |
38° 55' 40.992380"
N |
(lower right) |
75° 32' 57.401336"
W |
38° 55' 29.352235"
N |
(lower left) |
NOTE: Location information must be provided using NAD 83 datum. Information provided using NAD 27 is incorrect and unacceptable.
NOTE: SRP prefers that State Plane Coordinates be used whenever possible
|
Q: |
My latitude
and longitude are within the boundary coordinates,
but the data are still being rejected. Why? |
A: |
Make sure the minutes and
seconds are being entered for both latitude
and longitude. Do not use "leading zeros" when
entering the data. In other words, do not enter
the data as "07," enter them as just "7."
|
Q: |
What information
must be included in the HZSAMPLE file for Method
Blanks and Field Blanks? |
A: |
First, it is necessary to select "BLANK" as both the MATRIX and SAMPTYPE. Then, for Method Blanks and Field Blanks, the following mandatory fields do not need to be completed: Latitude/Longitude or State Plane Coordinates, and Depth_Top. |
3. Questions
Regarding EDSA7 Error Report
|