PDSLIB.CUP_STATIONS

Metadata:

• Identification_Information
• Data_Quality_Information
• Spatial_Data_Organization_Information
• Spatial_Reference_Information
• Entity_and_Attribute_Information
• Distribution_Information
• Metadata_Reference_Information

Identification_Information:

Citation:

Citation_Information:

Originator: St. Johns River Water Management District

Title: PDSLIB.CUP_STATIONS

Geospatial_Data_Presentation_Form: vector digital data

Publication_Information:

Publication_Place: Palatka, Florida

Publisher: St. Johns River Water Management District

Online_Linkage:

Server=earth; Service=esri_sde; User=pdslib; Version=SDE.DEFAULT

Description:

Abstract:

This data represents the locations of wells and pumps that correspond to permit applications received by the St. Johns River Water Management District. This layer refers to both wells and pumps as stations. The location for these wells and pumps is supplied by the applicant, usually in the form of a location map with with wells and pumps delineated by the applicant by placing an X or a dot on the location map. These location maps are generally 1:24,000 USGS quadrangles. In some instances, the District has obtained GPS positions of the stations. When this more accurate position information is available, the station data has been updated to reflect the improved position and documented as a GPS'ed location in the attribute informtion.

Purpose:

This layer is used to evaluate applicant permit requests, to spatially record and track permits issed by the District, and to assist in District environmental assesements such as ground water modeling.

Supplemental_Information:

Some of the attributes in this layer are automatically populated from the Global Regulatory System (GRS). Scripts to populate the fields are run nightly as a crontab on the server earth.
This layer is also exported nightly to \\interweb\data\explib for copying to the external data download site. The export script is run through a scheduled script on Ellen Dean's PC.
This layer is considered to be the master location for CUP points; RIM staff actively maintain and update location through ArcMap. In order to keep the Oracle station header table (Stn_et) up to date, an Oracle process updates Stn_et automatically. See the Oracle DBA for more info about this particular process.

Time_Period_of_Content:

Time_Period_Information:

Multiple_Dates/Times:

Single_Date/Time:

Calendar_Date: unknown

Time_of_Day: unknown

Single_Date/Time:

Calendar_Date: October 22, 2007

Currentness_Reference: publication date

Status:

Progress: Complete

Maintenance_and_Update_Frequency: Weekly

Spatial_Domain:

Bounding_Coordinates:

West_Bounding_Coordinate: -82.471149

East_Bounding_Coordinate: -80.316597

North_Bounding_Coordinate: 30.764157

South_Bounding_Coordinate: 27.458394

Keywords:

Theme:

Theme_Keyword_Thesaurus: SJRWMD-GIS Metadata Thesaurus

Theme_Keyword: Water Use Permits

Theme_Keyword: Regulatory

Theme_Keyword: Consumptive Use Permits

Theme_Keyword: Wells

Place:

Place_Keyword_Thesaurus: SJRWMD-GIS Metadata Thesaurus

Place_Keyword: Florida

Place_Keyword: St. Johns River Water Management District

Place_Keyword: Counties

Place_Keyword: Alachua County

Place_Keyword: Baker County

Place_Keyword: Bradford County

Place_Keyword: Brevard County

Place_Keyword: Clay County

Place_Keyword: Duval County

Place_Keyword: Flagler County

Place_Keyword: Indian River County

Place_Keyword: Lake County

Place_Keyword: Marion County

Place_Keyword: Nassau County

Place_Keyword: Okeechobee County

Place_Keyword: Orange County

Place_Keyword: Osceola County

Place_Keyword: Putnam County

Place_Keyword: Seminole County

Place_Keyword: St. Johns County, Volusia County

Access_Constraints: None

Use_Constraints:

The St. Johns River Water Management District prepares and uses information for its own purposes and this information may not be suitable for other purposes. This information is provided "as is". Further documentation of this data can be obtained by contacting: St. Johns River Water Management District, Division of Integrated Application Systems, Post Office Box 1429, Palatka, Florida, 32178-1429, (386) 329-4500.

Point_of_Contact:

Contact_Information:

Contact_Organization_Primary:

Contact_Organization: St. Johns River Water Management District

Contact_Person: Sandra Jones

Contact_Position: Data Management Specialist, Permit Data Services

Contact_Address:

Address_Type: mailing address

Address: P.O Box 1429

City: Palatka

State_or_Province: FL

Postal_Code: 32178-1429

Contact_Voice_Telephone: (386) 329-4566

Contact_Electronic_Mail_Address: gis_support@sjrwmd.com

Hours_of_Service: 0800 - 1700 EST

Browse_Graphic:

Browse_Graphic_File_Name: <http://intraweb/gisdoc/cf/smms0/gifimages/>

Browse_Graphic_File_Type: GIF

Native_Data_Set_Environment:

Microsoft Windows 2000 Version 5.2 (Build 3790) Service Pack 2; ESRI ArcCatalog 9.3.1.1850

Data_Quality_Information:

Completeness_Report:

This layer includes locations for all permitted wells and pumps in the District, however it does not include wells that have been plugged.

Lineage:

Process_Step:

Process_Description:

Within three days of receiving an application, the Division of Resource Information Management maps the location of the well or pump.

Source_Used_Citation_Abbreviation: C:\Temp\xml376.tmp

Process_Step:

Process_Description:

The LAT_NO and LONG_NO fields have been modified from originally being updated nightly from the equivalent fields in the station header table on PROD (ingres.stn_et@PROD), to instead being updated (calculated) from the DEC_LAT and DEC_LONG fields respectively.
The DEC_LAT and DEC_LONG fields are currently being updated through an ST_GEOMETRY function running with other updates in the nightly update scripts.
The LAT_NO and LONG_NO fields are then updated through the following SQL:
update cup_stations set lat_no= (trunc(dec_lat) * 10000) -- degrees * 10000 + (trunc((dec_lat-trunc(dec_lat)) * 60) * 100) -- minutes * 100 + ( ((dec_lat - trunc(dec_lat)) * 60) - trunc((dec_lat-trunc(dec_lat)) * 60) ) * 60 -- seconds /
update cup_stations set long_no= (trunc(abs(dec_long)) * 10000) -- degrees * 10000 + (trunc((abs(dec_long)-trunc(abs(dec_long))) * 60) * 100) -- minutes * 100 + ( ((abs(dec_long) - trunc(abs(dec_long))) * 60) - trunc((abs(dec_long)-trunc(abs(dec_long))) * 60) ) * 60 -- seconds /

(Ellen Dean -- December 28, 2009)

Process_Date: December 28, 2009

Process_Step:

Process_Description:

Two fields, SEQ_NO and PROJ_STTS_NM, were added on 4/21/2011, following a meeting on 4/20/2011 with RIM staff, Marlise and others. Marlise provided SQL query on PROD tables to populate the SEQ_NO field, and then the PROJ_STTS_NM is updated from the SJR.DIM_PERMIT.PERMIT_STATUS table/field on DISC, by joining with the "offcl_prmt_id" and "seq_no"fields. These fields are updated nightly through scripts.

Process_Step:

Process_Description:

Historical CUP station data was added to this feature class on September 22, 2011. This data was created from joining historical CUP data from PROD (earlier seq_no for a given offcl_prmt_id in the CUP_STATIONS layer), using steps as outlined below.
Before this historical data was loaded, two new fields were added: "ARCHIVE" and "PROD_LOADED". The "ARCHIVE" field identifies (Y or N) whether this is a current CUP record (ARCHIVE='N') or an historical CUP record (ARCHIVE='Y'). THE "PROD_LOADED" field was added to identify those records (ad infinitum) which were loaded originally from this historical data load (i.e. were not in the original CUP_STATIONS layer prior to the historical data being added).
Below are the steps used for added the CUP station history data to the CUP_STATIONS layer (from the ascii file: "adding_hist_cup_stations_SDE.txt" on \\sjrwmd.com\Private\sjrx\\IR\GISWork\edean\projects\CUP_ERP_STM\PDS_Update_Queries\Update_CUP_Layers\Adding_Historical_Data_into_CUP_Aug2011):
-- -- Earlier test versions used data from TEST (reguser.proj_stn@TEST and ingres.prmt_rltd_hist@TEST) as -- the proj_stn table is a new structure had not yet implemented on PROD (implemented 4/29/2011).
-- This final version using reguser.proj_stn@PROD, ingres.prmt_rltd_hist@PROD and pdslib.cup_stations@SDE.


connect pdslib/pdslib@sde
drop trigger cup_stations_t1 /


/* ************************************************************************************************************ */ /* First creating a table of all offcl_prmt_id, seq_no and stn_id combinations from Oracle (PROD) whose seq_no */ /* are earlier sequences for a given offcl_prmt_id (i.e. represent historical versions of existing cup permits */ /* in the cup_stations layer) */ /* ************************************************************************************************************ */

drop table cup_stations_hist_id /

-- The SQL was based on the query provided by Nishith Chaturvedi in his e-mail on 4/26/2011
create table cup_stations_hist_id as select distinct b.cur_prmt_id, b.offcl_prmt_id, b.seq_no, a.stn_id from reguser.proj_stn@PROD a, ingres.prmt_rltd_hist@PROD b where a.cur_id = b.cur_prmt_id and b.offcl_prmt_id in (select offcl_prmt_id from pdslib.cup_stations@sde) and NOT EXISTS (select 'x' from pdslib.cup_stations@sde c where c.offcl_prmt_id=b.offcl_prmt_id and c.seq_no=b.seq_no) order by b.cur_prmt_id, b.offcl_prmt_id,b.seq_no, a.stn_id /


/* ************************************************************************************************************ */ /* Next, creating an attribute table with structure identical to the cup_stations layer (minus the shape field) */ /* This will then be populated by attributes on PROD and DISC for all historical records found in the above */ /* step using the same process as these fields are currently updated nightly for the cup_stations layer. */ /* ************************************************************************************************************ */

drop table cup_stations_hist_id_attr /

create table cup_stations_hist_id_attr as select cur_prmt_id , offcl_prmt_id , seq_no , stn_id , stn_alias_nm , prmt_proj_nm , determination_method , gps , stnhdr_determination_method , stn_tp , stn_stts , proj_stts_nm , well_csng_dpth , well_cur_dpth , well_csng_dmtr , qa_code , sect_id , twnshp_id , rng_id , county , source , max_cap_qty , lat_no , long_no , edit_date , objectid , editor , dec_lat , dec_long from cup_stations where rownum < 2 /
truncate table cup_stations_hist_id_attr /

insert into cup_stations_hist_id_attr select k.cur_prmt_id ,k.offcl_prmt_id ,k.seq_no --seq_no ,k.stn_id ,a.stn_nm --stn_alias_nm ,g.prmt_proj_nm --prmt_proj_nm ,NULL --determination_method ,NULL --gps ,h.tp_dsc --stn_hdr_determination_method ,lower(d.tp_dsc) --stn_tp ,e.tp_dsc --stn_stts ,NULL --proj_stts_nm ,b.totl_well_csng_dpth_qty --well_csng_depth ,b.cur_well_dpth_qty --well_cur_depth ,b.nomnl_csng_dmtr_qty --well_csng_dmtr ,NULL --qa_code ,a.sect_id ,a.twnshp_id ,a.rng_id ,NULL --county, updated later from st_geometry intersection with gislib.bnd_024k_county ,f.srce_offcl_nm --source -- ,c.max_pmp_cap_qty --max_cap_qty ,c.pmp_max_cap_qty --max_cap_qty ,a.lat_no ,a.long_no ,NULL --edit_date ,0 --objectid ,'ORACLEPROD' --editor ,NULL --dec_lat ,NULL --dec_long from cup_stations_hist_id k LEFT OUTER JOIN ingres.stn_et@prod a ON (k.stn_id = a.stn_id) LEFT OUTER JOIN ingres.well_et@prod b ON (k.stn_id = b.stn_id) -- LEFT OUTER JOIN ingres.srfc_wtr_pmp_et@prod c ON (k.stn_id = c.stn_id) LEFT OUTER JOIN ingres.sjr_abbr_def_et@prod d ON (a.stn_tp_cd = d.tp_id) LEFT OUTER JOIN ingres.sjr_abbr_def_et@prod e ON (a.stn_stts_cd = e.tp_id) LEFT OUTER JOIN ingres.wtr_srce_et@prod f ON (a.srce_id = f.srce_id) INNER JOIN ingres.prmt_rltd_hist@prod w ON (k.offcl_prmt_id = w.offcl_prmt_id and k.seq_no = w.seq_no) LEFT OUTER JOIN ingres.wtr_use_prmt_proj_et@prod g ON (w.cur_prmt_id = g.prmt_proj_id) LEFT OUTER JOIN ingres.sjr_abbr_def_et@prod h ON (a.mthd_dtrmn_cd = h.tp_id) INNER JOIN reguser.proj_stn@prod c ON (k.stn_id = c.stn_id and c.cur_id = w.cur_prmt_id) order by k.stn_id /
commit /
create index idx_cup_stn_hist_id_attr_prmt on cup_stations_hist_id_attr(offcl_prmt_id);
create index idx_cup_stn_hist_id_attr_stnid on cup_stations_hist_id_attr(stn_id);
create index idx_cup_stn_hist_id_attr_prmts on cup_stations_hist_id_attr(offcl_prmt_id,seq_no);

-- updating the lat_no, long_no, dec_lat and dec_long fields from existing cup_stations with matching stn_id values; we are -- thus assuming that the geographic location (lat/long) of the point in cup_stations takes precedence over what is in -- station header

update cup_stations_hist_id_attr c1 set (c1.lat_no,c1.long_no,c1.dec_lat,c1.dec_long) = (select distinct c2.lat_no,c2.long_no,c2.dec_lat,c2.dec_long from cup_stations c2 where c1.stn_id = c2.stn_id) where c1.stn_id in (select stn_id from cup_stations) /
commit /
-- Now, updating all lat/long values for stn_id's that were not present in the cup_stations layer; updating these from station header
update cup_stations_hist_id_attr c1 set (c1.lat_no,c1.long_no,c1.dec_lat,c1.dec_long) = (select s.lat_no,s.long_no, ((s.lat_no - mod(s.lat_no,10000)) / 10000) + (((mod(s.lat_no,10000) - mod(s.lat_no,100)) / 100 ) / 60) + (mod(s.lat_no,100) / 3600), (((s.long_no - mod(s.long_no,10000)) / 10000) + (((mod(s.long_no,10000) - mod(s.long_no,100)) / 100 ) / 60) + (mod(s.long_no,100) / 3600) ) * -1.0 from stn_et@prod s where c1.stn_id = s.stn_id) where NOT EXISTS (select 'x' from cup_stations c where c1.stn_id=c.stn_id) /
commit /
-- Updating the proj_stts_nm field from DISC using the same SQL as for updating the current cup_stations layer -- (Note: the TSDE database does not have a remote database link to either SDE or DISC, so am instead using -- copied this table from DISC, to SDE and then to TSDE using the EDEAN account. Had to also update -- all date record fields which had a year value of "0001" to be "2001". The gislib.v_dim_permit_disc -- view will work on SDE once we are doing this "for real" on SDE with the real CUP_STATIONS and -- CUP_STATIONS_HIST layer.


update cup_stations_hist_id_attr c set c.proj_stts_nm = (select d.permit_status from sjr.dim_permit@disc d where d.offcl_prmt_id=c.offcl_prmt_id and d.seq_no=c.seq_no) where (c.offcl_prmt_id,c.seq_no) in (select offcl_prmt_id,seq_no from sjr.dim_permit@disc) /




commit /

/* ************************************************************************************************************* */ /* Creating final historical CUP stations layer: */ /* */ /* Initially created the CUP_STATIONS_HIST feature class in ArcCatalog by copying CUP_STATIONS */ /* */ /* This section will truncate this table first and then populate it. */ /* */ /* Populating from the cup_stations_hist_id_attr table (for all attribute data) and the cup_stations */ /* layer (for geom/shape only) where stn_id's match */ /* Next, populating for all other historical records (existing offcl_prmt_id, earlier seq_no's) whose */ /* stn_id's are not present in the current cup_stations layer */ /* This will get attribute data again from the cup_stations_hist_id_attr table, and */ /* the shape/geom from the gislib.stn_et_geom feature class */ /* ************************************************************************************************************* */

truncate table cup_stations_hist /
drop sequence tmp_seq /
create sequence tmp_seq start with 1 increment by 1 /
update cup_stations_hist_id_attr set objectid=tmp_seq.nextval /
commit /


insert into cup_stations_hist select a.cur_prmt_id ,a.offcl_prmt_id ,a.seq_no ,a.stn_id ,a.stn_alias_nm ,a.prmt_proj_nm ,a.determination_method ,a.gps ,a.stnhdr_determination_method ,a.stn_tp ,a.stn_stts ,a.proj_stts_nm ,a.well_csng_dpth ,a.well_cur_dpth ,a.well_csng_dmtr ,a.qa_code ,a.sect_id ,a.twnshp_id ,a.rng_id ,a.county ,a.source ,a.max_cap_qty ,a.lat_no ,a.long_no ,a.edit_date ,a.objectid ,a.editor ,a.dec_lat ,a.dec_long ,c.shape ,'Y' ,'Y' from cup_stations_hist_id_attr a, cup_stations c where a.stn_id = c.stn_id /

insert into cup_stations_hist select a.cur_prmt_id ,a.offcl_prmt_id ,a.seq_no ,a.stn_id ,a.stn_alias_nm ,a.prmt_proj_nm ,a.determination_method ,a.gps ,a.stnhdr_determination_method ,a.stn_tp ,a.stn_stts ,a.proj_stts_nm ,a.well_csng_dpth ,a.well_cur_dpth ,a.well_csng_dmtr ,a.qa_code ,a.sect_id ,a.rng_id ,a.twnshp_id ,a.county ,a.source ,a.max_cap_qty ,a.lat_no ,a.long_no ,a.edit_date ,a.objectid ,a.editor ,a.dec_lat ,a.dec_long ,sde.st_transform(s.shape,1) ,'Y' ,'Y' from cup_stations_hist_id_attr a, gislib.stn_et_geom s where a.stn_id = s.stn_id and NOT EXISTS (select 'x' from cup_stations c where a.stn_id=c.stn_id) /
commit /
create index idx_cup_stations_hist_stn_id on cup_stations_hist(stn_id);
create index idx_cup_stations_hist_prmt on cup_stations_hist(offcl_prmt_id);
create index idx_cup_stations_hist_prmts on cup_stations_hist(offcl_prmt_id,seq_no);

-- updating the county through an ST_GEOMETERY intersection with the county layer
drop table tmp_cup_stations_hist /
create table tmp_cup_stations_hist as select a.stn_id,a.county,a.shape from cup_stations_hist a where (a.stn_id,a.rowid) in (select stn_id,min(rowid) from cup_stations_hist group by stn_id) /
update tmp_cup_stations_hist a set a.county = (select b.county from gislib.bnd_024k_county b where sde.st_intersects(b.shape,a.shape)=1) /
create index idx_tmpcupstn_hist1 on tmp_cup_stations_hist(stn_id) /

update cup_stations_hist a set a.county= (select b.county from tmp_cup_stations_hist b where b.stn_id=a.stn_id) /
commit /


-- Note: be sure to use the correct sequence for this feature class (registration_id=13878 for PDSLIB.CUP_STATIONS on SDE....)
update cup_stations_hist set objectid=r13878.nextval /
commit /


-- Now, inserting into main PDSLIB.CUP_STATIONS feature class
insert into cup_stations select cur_prmt_id, offcl_prmt_id, seq_no, stn_id, stn_alias_nm, prmt_proj_nm, determination_method, gps, stnhdr_determination_method, stn_tp, stn_stts, proj_stts_nm, well_csng_dpth, well_cur_dpth, well_csng_dmtr, qa_code, sect_id, twnshp_id, rng_id, county, source, max_cap_qty, lat_no, long_no, edit_date, objectid, editor, dec_lat, dec_long, shape, archive, prod_loaded from cup_stations_hist /

commit /



create or replace trigger pdslib.cup_stations_t1 before insert or update on cup_stations for each row begin select sysdate into :new.edit_date from dual; select sys_context('USERENV','SESSION_USER') into :new.editor from dual; end; /

Process_Date: September 22, 2011

Process_Contact:

Contact_Information:

Contact_Person_Primary:

Contact_Person: Ellen Dean

Contact_Organization: St. Johns River Water Management District

Contact_Position: GIS Analyst / SDE Administrator

Contact_Voice_Telephone: (386) 227-0351

Contact_Electronic_Mail_Address: edean@sjrwmd.com

Process_Step:

Process_Description:

Sandra Jones from Regulatory Support after reviewing the historical CUP data, requested all "TCUP" records to be removed - according to Sandra, TCUP records are any permits with a 4-digit seq_no value. I subsequently removed these TCUP records.

Process_Date: September 23, 2011

Process_Contact:

Contact_Information:

Contact_Person_Primary:

Contact_Person: Ellen Dean

Contact_Organization: St. Johns River Water Management District

Contact_Position: GIS Analyst / SDE Administrator

Contact_Voice_Telephone: (386) 227-0351

Contact_Electronic_Mail_Address: edean@sjrwmd.com

Spatial_Data_Organization_Information:

Direct_Spatial_Reference_Method: Vector

Point_and_Vector_Object_Information:

Spatial_Reference_Information:

Horizontal_Coordinate_System_Definition:

Planar:

Planar_Coordinate_Information:

Planar_Coordinate_Encoding_Method: coordinate pair

Coordinate_Representation:

Abscissa_Resolution: 0.000125

Ordinate_Resolution: 0.000125

Planar_Distance_Units: meters

Geodetic_Model:

Horizontal_Datum_Name: D_North_American_1983_HARN

Ellipsoid_Name: Geodetic Reference System 80

Semi-major_Axis: 6378137.000000

Denominator_of_Flattening_Ratio: 298.257222

Vertical_Coordinate_System_Definition:

Altitude_System_Definition:

Altitude_Resolution: 1.000000

Altitude_Encoding_Method:

Explicit elevation coordinate included with horizontal coordinates

Entity_and_Attribute_Information:

Detailed_Description:

Entity_Type:

Entity_Type_Label: PDSLIB.CUP_STATIONS

Attribute:

Attribute_Label: OBJECTID

Attribute_Definition: Internal feature number.

Attribute_Definition_Source: ESRI

Attribute_Domain_Values:

Unrepresentable_Domain:

Sequential unique whole numbers that are automatically generated.

Attribute:

Attribute_Label: OFFCL_PRMT_ID

Attribute_Definition:

Global Regulatory System (GRS) Permit Identifier (system generated)

Attribute_Definition_Source: ingres.prmt_rltd_hist.offcl_prmt_id (PROD database)

Attribute:

Attribute_Label: PRMT_PROJ_NM

Attribute_Definition: Project Name

Attribute_Definition_Source:

Permit application; (Oracle (PROD dbs) account.table.field): ingres.wtr_use_prmt_proj_et.prmt_proj_nm

Attribute:

Attribute_Label: STN_ID

Attribute_Definition: System Generated Station ID (station header table)

Attribute_Definition_Source: Added and maintained in this feature class by RIM staff.

Attribute:

Attribute_Label: DETERMINATION_METHOD

Attribute_Definition: GPS Determination Method

Attribute_Definition_Source:

Values include: Control Survey, Unknown, Digitized, GPS1, GPS2, GPS3, GPS3S, GPS4; contact RIM staff for further definition; Added and maintained in this feature class by RIM staff.

Attribute:

Attribute_Label: STN_ALIAS_NM

Attribute_Definition:

Station name - either supplied by the applicant or by the permit reviewer. Equivalent to Stn_nm in the station header table.

Attribute_Definition_Source:

Permit application; (Oracle (PROD dbs) account.table.field): ingres.stn_et.stn_nm

Attribute:

Attribute_Label: STNHDR_DETERMINATION_METHOD

Attribute_Definition: Determination Method as currently in Station Header

Attribute_Definition_Source: sjr_abbr_def_et.tp_dsc ==> stn_et.mthd_dtrmn_cd@PROD

Attribute:

Attribute_Label: GPS

Attribute_Definition:

Indicates if the location is supplied by GPS measurements. Y = Yes; Used before establishment of revised determination methods, which was implemented July 2009

Attribute_Definition_Source: Added and maintained in this feature class by RIM staff.

Attribute_Domain_Values:

Enumerated_Domain:

Enumerated_Domain_Value: Y

Enumerated_Domain_Value_Definition: Yes, the location has been GPS'ed

Attribute:

Attribute_Label: STN_TP

Attribute_Definition: Type of station - Well or Pump

Attribute_Definition_Source:

GRS: Permit application; (Oracle (PROD dbs) account.table.field): ingres.sjr_abbr_def_et.tp_dsc ==> stn_et.stn_tp_cd@PROD

Attribute_Domain_Values:

Enumerated_Domain:

Enumerated_Domain_Value: well

Enumerated_Domain:

Enumerated_Domain_Value: pump

Attribute:

Attribute_Label: STN_STTS

Attribute_Definition: Status of the station at the time the application is received

Attribute_Definition_Source:

GRS: Permit application; (Oracle (PROD dbs) account.table.field): ingres.sjr_abbr_def_et.tp_dsc ==> stn_et.stn_stts_cd@PROD

Attribute:

Attribute_Label: WELL_CSNG_DPTH

Attribute_Definition: Well casing depth in feet

Attribute_Definition_Source:

GRS; Permit application; (Oracle (PROD dbs) account.table.field): ingres.well_et.totl_well_csng_dpth_qty

Attribute:

Attribute_Label: WELL_CUR_DPTH

Attribute_Definition: Total well depth in feet

Attribute_Definition_Source:

GRS; Permit application; (Oracle (PROD dbs) account.table.field): ingres.well_et.cur_well_dpth_qty

Attribute:

Attribute_Label: PRMT_PROC_STTS

Attribute:

Attribute_Label: WELL_CSNG_DMTR

Attribute_Definition: Diameter of well in inches

Attribute_Definition_Source:

GRS; Permit application; (Oracle (PROD dbs) account.table.field): ingres.well_et.nomnl_csng_dmtr_qty

Attribute:

Attribute_Label: SECT_ID

Attribute_Definition: The section the station is located in

Attribute_Definition_Source:

GRS; Permit application; (Oracle (PROD dbs) account.table.field): ingres.stn_et.sect_id

Attribute:

Attribute_Label: RNG_ID

Attribute_Definition: The range the station is in

Attribute_Definition_Source:

GRS; Permit application; (Oracle (PROD dbs) account.table.field): ingres.stn_et.range_id

Attribute:

Attribute_Label: SHAPE

Attribute_Definition: Feature geometry.

Attribute_Definition_Source: ESRI

Attribute_Domain_Values:

Unrepresentable_Domain: Coordinates defining the features.

Attribute:

Attribute_Label: SOURCE

Attribute_Definition: Aquifer if a well, waterbody or surficial aquifer if a pump

Attribute_Definition_Source:

GRS; Permit application; (Oracle (PROD dbs) account.table.field): ingres.wtr_srce_et.srce_offcl_nm

Attribute:

Attribute_Label: MAX_CAP_QTY

Attribute_Definition: Pump capacity, gallons per minute

Attribute_Definition_Source:

GRS; Permit application; (Oracle (PROD dbs) account.table.field): ingres.srfc_wtr_pmp_et.max_pmp_cap_qty

Attribute:

Attribute_Label: LAT_NO

Attribute_Definition: Latitude - degrees, minutes, seconds

Attribute_Definition_Source: Calculated from the DEC_LAT field

Attribute:

Attribute_Label: TWNSHP_ID

Attribute_Definition: The township the project is in

Attribute_Definition_Source:

GRS; Permit application; (Oracle (PROD dbs) account.table.field): ingres.stn_et.twnshp_id

Attribute:

Attribute_Label: COUNTY

Attribute_Definition: The county the project is located in

Attribute_Definition_Source:

Updated nightly from an ST_GEOMETRY intersection query with the county layer (GISLIB.BND_024K_COUNTY_STGEOM)

Attribute:

Attribute_Label: EDIT_DATE

Attribute_Definition: Date the point was last edited;

Attribute_Definition_Source:

Field updated by trigger, sets field to the sysdate at the time of the person editing

Attribute:

Attribute_Label: LONG_NO

Attribute_Definition: Longitude - degrees, minutes, seconds

Attribute_Definition_Source: Calculated from the DEC_LONG field

Attribute:

Attribute_Label: EDITOR

Attribute_Definition: Name of the SJRWMD person who last edited the point;

Attribute_Definition_Source:

Field updated by trigger, sets field to the SDE version of the person editing

Attribute:

Attribute_Label: DEC_LAT

Attribute_Definition: Latitude - decimal degrees

Attribute_Definition_Source:

ArcMap location (updated nightly using an ST_GEOMETRY SQL statement, and is within the SDE Compress script (sde_compress.sh) running on earth)

Attribute:

Attribute_Label: DEC_LONG

Attribute_Definition: Longitude - decimal degrees

Attribute_Definition_Source:

ArcMap location (updated nightly using an ST_GEOMETRY SQL statement, and is within the SDE Compress script (sde_compress.sh) running on earth)

Attribute:

Attribute_Label: CUR_PRMT_ID

Attribute_Definition_Source: Added and maintained in this feature class by RIM staff.

Attribute:

Attribute_Label: SEQ_NO

Attribute_Definition: Sequence Number

Attribute_Definition_Source: ingres.prmt_rltd_hist.seq_no (PROD database)

Attribute:

Attribute_Label: PROJ_STTS_NM

Attribute_Definition:

Project Status - status of the particular site where the station is located

Attribute_Definition_Source:

Updated nightly from sjr.dim_permit@DISC (field: permit_status); joining with this table using the offcl_prmt_id and seq_no fields in both PDSLIB.CUP_STATIONS@SDE and SJR.DIM_PERMIT@DISC

Attribute:

Attribute_Label: ARCHIVE

Attribute_Definition:

Identifies if this is a current (archive='N') or historic (archive='Y') CUP record.

Attribute_Definition_Source: Regulatory Staff maintains

Attribute:

Attribute_Label: PROD_LOADED

Attribute_Definition:

Identifies those records which were loaded from the September 22, 2011 load of historical CUP data;

Attribute:

Attribute_Label: MONITORING_WELL

Attribute_Definition: Identifies if this is a monitoring well or not.

Attribute_Definition_Source:

Updated nightly from reguser.proj_stn@prod (field mon_well_tp_cd); if a record for this station (stn_id) exists in reguser.proj_stn@prod where the mon_well_tp_cd field is not NULL, then set to 'Y', otherwise 'N'

Attribute:

Attribute_Label: SITE_ID

Attribute:

Attribute_Label: RULE_TYPE_DESC

Overview_Description:

Entity_and_Attribute_Detail_Citation:

Note: for fields being populated by values from the PROD Oracle database, these are sometimes from lookup tables which have code values used for multiple purposes.
For instance, the field "tp_dsc" from the sjr_abbr_def_et lookup table is used for station status (stn_et.stn_stts_cd = sjr_abbr_def_et.tp_id), for station type (stn_et.stn_tp_cd = sjr_abbr_def_et.tp_id), as well as for many other code values.

Distribution_Information:

Distributor:

Contact_Information:

Contact_Organization_Primary:

Contact_Organization: St. Johns River Water Management District

Contact_Position: GIS Data Manager, Information Resources Department

Contact_Address:

Address_Type: mailing address

Address: Post Office Box 1429

City: Palatka

State_or_Province: Florida

Postal_Code: 32178-1429

Country: USA

Contact_Voice_Telephone: (386) 329-4500

Contact_Electronic_Mail_Address: gis_support@sjrwmd.com

Hours_of_Service: 0800-1700 EST

Resource_Description: Downloadable Data

Distribution_Liability:

The St. Johns River Water Management District prepares and uses information for its own purposes and this information may not be suitable for other purposes. This information is provided "as is". Further documentation of this data can be obtained by contacting: St. Johns River Water Management District, Division of Integrated Application Systems, Post Office Box 1429, Palatka, Florida, 32178-1429, (386) 329-4500.

Standard_Order_Process:

Digital_Form:

Digital_Transfer_Information:

Format_Name: ARCE

Format_Version_Number: v8.2

Format_Specification: ARC/INFO Export Format - UNIX Compression

File_Decompression_Technique: Winzip

Digital_Transfer_Option:

Online_Option:

Computer_Contact_Information:

Network_Address:

Network_Resource_Name: <http://www.sjrwmd.com>

Offline_Option:

Offline_Media: CD-ROM

Fees: $40 per CD

Ordering_Instructions:

There is no charge for downloading data from the DISTRICT web site at <http://www.sjrwmd.com>. Data can be orded on CD-ROM as instructed on the web site.

Turnaround: 10 working days

Custom_Order_Process:

1. Use the DISTRICT website: <http://www.sjrwmd.com> to download data, or 2. Call or email to organizations listed under Distributor. Spatial data are in ARC/INFO interchange formats.

Technical_Prerequisites:

Internet access / Unzip, Winzip / To import coverage: ESRI ArcInfo workstation, ArcView 3.2X Import 7.1 Utility, or ArcToolBox. / To use coverage: ESRI ArcInfo, ArcView, ArcGIS 8.2, or ArcExplorer; AutoCAD 2002 Map or Land Development Desktop.

Metadata_Reference_Information:

Metadata_Date: 20110926

Metadata_Contact:

Contact_Information:

Contact_Person_Primary:

Contact_Person: Regulatory Information Management - GIS Staff

Contact_Organization: St. Johns River Water Management District

Contact_Position: GIS Analyst, Regulatory Information Management

Contact_Address:

Address_Type: mailing address

Address: Post Office Box 1429

City: Palatka

State_or_Province: Florida

Postal_Code: 32178-1429

Country: USA

Contact_Voice_Telephone: (386) 329-4566

Contact_Electronic_Mail_Address: gis_support@sjrwmd.com

Hours_of_Service: 0800-1700 EST

Metadata_Standard_Name: FGDC Content Standards for Digital Geospatial Metadata

Metadata_Standard_Version: FGDC-STD-001-1998

Metadata_Time_Convention: local time