SPECIFICATIONS FOR G.I.S. DATA/INFORMATION PROVIDED TO ONE-CALL

Transcription

1 SPECIFICATIONS FOR G.I.S. DATA/INFORMATION PROVIDED TO ONE-CALL Digital Mapping Files that we can accept: 1. G.I.S. dataset formats that we can accept: FORMAT AutoCad File Latest Releases ESRI Arc/Info - Export File ESRI Arc/Info - Generate File ESRI Arc/Info - Shape File Facet Files Geographic Data Management System (GDMS) File Google Earth Plus Data Exchange Format IDRISI Vector Format Integraph/Microstation Design File MapGuide SDL *MapInfo Format MapInfo Interchange Format PenMetrics GRD PHOCUS Phodat Spatial Archive Interchange Format Spatial Data Transfer Standard USGS Digital Line Graph USGS TIGER Line Format Vector Markup Language Whitestar Geographix CDF FILE EXTENSION(S) (*.dwg, *.dxf) (*.e00) (*.gen) (*.shp, *.shx, *.dbf, *.prj) (*.xdr) (*.gdms) (*.kml) (*.vct, *.vdc, *.vlx, *.mdb, *.adc) (*.dgn) (*.adl) (*.tab *.dat, *.map, *.id, *.ind) (*.mid, *.mif) (*.grd) (*.pdt) (*.saf, *.zip) (*.ddf) (*.dlg) (*.rt1, *.bw1) (*.vml) (*.cdf) 2. Projections/Datum that we can accept (all digital data must be in a projection or datum) PROJECTIONS /DATUM Universal Transverse Mercator (UTM) (NAD27, NAD83, WGS84) (Must provide the UTM Zone with your data) U.S. State Planes (NAD27, NAD83) (Must provide the Zone and Units with your data) Latitude/Longitude (NAD27, NAD83, WGS72, WGS84, *Generic MapInfo) Many other projections/datum can be accepted as well. Please call for more information. *Preferred Format *IMPORTANT: When sending your coverage(s), you must specify what projection/datum your coverage is in, as well as if it is in U.S. feet or meters. If any of the above formats are provided to us, we will attempt to translate them into a MapInfo format. However, we cannot guarantee that they can be translated. We cannot accept data that has streets, towns, county boundaries, text, or any other information other than that of your underground plant. ONLY PROVIDE US WITH POLYGONS AND/OR LINES THAT REPRESENT WHERE YOU WANT TO BE NOTIFIED. Each station code should be in one file & on one layer ONLY. If you are providing point or linear data (lines), you must specify the buffer width you wish to have, and it must be at least 50 feet on each side of the line. Coverages with multi-polygons, a.k.a. polygons within polygons, or donuts will not be accepted. Page 1 of 5

2 GPS Coordinate Formats that we can accept: GPS Data can be supplied to us if they meet the following criteria: They must be placed either in an Excel Spreadsheet or be delimited ASCII. Some other electronic databases formats are acceptable. Call for more details. They must be supplied in decimal degrees to at least the thousandths place. <Degrees/Minutes/Seconds will not be accepted.> You must specify projection/datum your coordinates are in as well as if it is in U.S. feet or meters. The coordinate pairs need to be in consecutive order as if we were going to connect the dots. Longitude (or East/West coordinate) must be in the first column and Latitude (or North/South coordinate) should be placed in the second column. These columns must be formatted as General before you enter them into the spreadsheet. No directionals should be used, i.e W, N. They should be in this format: , <or for State Plane, UTM etc.> , Note that the longitudes in the western hemisphere, and latitudes in the southern hemisphere, are denoted with negatives. Here is an example of a pipeline with four nodes: Note: No column headings should be used. PLEASE SPECIFY WHETHER YOUR COVERAGE IS A POINT, LINEAR, OR POLYGONAL COVERAGE IN THE FILENAME OF THE SHEET. Point Coverages: points can all be in the same spreadsheet and order does not matter. Line/Polygon Coverages: points should be ordered consecutively so as to connect the dots. Separate spreadsheets are needed for a coverage that is not contiguous or continuous like the example below. ***Please specify a buffer width if your coverage contains linear or point data (non-polygonal). Page 2 of 5

3 Paper Maps that we can accept: 1. Maps which we have printed for you to mark on: All of our maps have 4 sets of real-world coordinates which act as control points so that we can accurately digitize your underground plant. If you choose to do this, we will provide you with a guidelines sheet which will help you to mark these maps. 2. Maps which you have provided to us describing where your underground plant is located: Must have a set of coordinates in all four corners of the map. These coordinates must be in decimal degrees and accurate to at least one-thousandth of a degree. We will also need to have the county/region name and the name of your utility printed on these maps. You must specify projection/datum your control points are in as well as if it is in U.S. feet or meters. If you provide point or linear (lines) coverage, you must specify the buffer width you wish to have, and it must be at least 50 feet on each side of the line. Here is an example: Page 3 of 5

4 Public Land Survey Information that we can accept (PLSS is n/a in all states): 1. Text with the location of your underground plant using PLSS (Public Land Survey Sections) Township & Range Section Information: The text should be in this format: Twp + Twp Direction + Rng + Rng Direction + s + Section + : + <Tab> + QtrSections (2 s 123 w s 10 : sw ) You must follow these conventions for this to work: No zeroes should be placed in front of single digit numbers. Examples: 2S123WS10 should be used instead of 02S123WS10, 24N12ES5 should be used instead of 24N12ES05. Use 1 Tab between the colon and the quartersections. Notice that if you want the entire section notified that you must put in all four quarter sections: ne,nw,se,sw. Township direction, Range Direction, s, and quarter sections must all be in lower case letters. *IMPORTANT: You must split up this information by county and save it to it s own *.txt file. If your coverage is in 6 counties, you will have 6 files with the PLS data separated by county. If you have a file for station code GX in PLS format in Adams County, North Dakota, for example, then the file should be saved as PLSS_GX_NDAdams.txt. EX: PLSS + _ + Station Code ID + _ + State Abbreviation + County Name +.txt Page 4 of 5

5 Default Municipality/County Information that we can accept (Not Yet Available): 1. Text with the location of your underground plant using Defaults which cover all of the area within the boundaries of a particular municipality or county: The text should be in this format for individual municipalities you want to be notified in: The text should be in this format if you want to be notified in every town within a particular county: You must follow these conventions for this to work: The municipality MUST be spelled correctly. If you want every municipality in a county to be notified then you only need to type the word ALL. *IMPORTANT: You must split up this information by county and save it to it s own *.txt file. If you have defaults in 6 counties, you will have 6 files with the name of the municipalities in it separated by county. If you have a file for station code GX in Default format in Adams County, North Dakota, for example, then the file should be saved as Default_GX_NDAdams.txt. EX: Default + _ + Station Code ID + _ + State Abbreviation + County Name +.txt 11/15/06 Page 5 of 5