The NJDEP considers all beach areas to be environmentally significant, and has included them in a separate layer to be used in the Cross Acceptance process. Beaches were mapped as part of the 1995/97 LU/LC dataset. Descriptions of the specific beach categories mapped are given in: http://www.state.nj.us/dep/gis/digidownload/metadata/lulc95/anderson.html. All polygons given a TYPE95 code of BEACHES in that 1995/97 LU/LC were selected and put in a separate data layer for processing. To simplify this layer for use in Cross Acceptance, and additional attribute (BEACH) was added to the .PA of the beach coverage. All valid beach polygons were given a BEACH code of 'Y'. The beach layer was dissolved on the BEACH code, and all resultant polygons with a BEACH code of 'Y' selected for inclusion in the BEACH_CA layer.

Supplemental_Information:

Contact John Tyrawski (609-777-0151) with any questions regarding the cross-acceptance data.

The ITUM land use/land cover theme and the FWW theme were mapped as independent projects for different purposes. From early on, the NJDEP planned to integrate the two layers even though the standard for FWW
mapping was much tighter. The integration of these two data layers was completed in 1997. The specific process used to perform the integration of the ITUM land use/land cover theme and the FWW theme into the LULC theme is discussed in more detail in the METHODS.TXT file. A brief description follows:

The ITUM land use/land cover layer served as the base layer because it represented a more complete data layer since all areas within the state were mapped. The FWW theme was used to add detail to the ITUM theme because the FWW was produced at a larger mapping scale with extensive fieldwork and with smaller minimum polygon size. Therefore the detailed non-tidal wetland FWW delineations were integrated in their entirety into the ITUM land use/land cover layer for each county, and the original non-tidal ITUM wetland delineations were eliminated. The resultant theme is the LULC.

All of the detail of the polygon FWW maps, both in the linework (polygons), and coding (Cowardin classification) has been retained in the LULC product. (The single line freshwater wetland features are not included in this integration). However, since the ITUM land use/land cover layer was classified according to the modified Anderson et al. (1976) classification system, the wetland FWW polygons have been given a more general Anderson (4 digit) classification code in the LULC theme. If needed, the LULC freshwater wetland polygons can be interpreted at a level of detail similar to the surrounding non-wetland areas.

The integration process does create some special problems in the final data layer. The most notable problem is that sliver polygons are created. Slivers under .25 acres have generally been eliminated since these are, in most cases, results of the processing and not real features of either original data layer. Possible slivers over .25 acres, however, have been left in the final themes. While many of these should be merged into adjacent polygons, others are real features that are correctly classified. Most sliver polygons need to be analyzed on a case by case basis before it is determined whether or not they should be eliminated, re-coded or retained. As the LULC theme is updated, sliver polygon problems will be investigated and corrected. The overall aerial extent of the slivers should not greatly alter the use of these data if they are not analyzed individually.

The Anderson et al. 1976 (modified 1999) classification system is a hierarchical system based on four digits. The four digits represent three levels of classification: Level I, general; Level II, descriptive; and Level III, detailed. Therefore the first digit in the code is the Level I general classification. The first two digits reveal the Level II descriptive code and the four digits represent the detailed Level III code. The LULC theme is generally a Level II classification but some level III detail is included.

For example the code 1110 represents:

1---Urban
11--Urban, Residential
1110--Urban, Residential, High Density or Multiple Dwelling

This file is included in the downloadable zip file and once unzipped can be accessed through ArcView. In ArcView, after the LULC shapefile has been added to a view, make the LULC theme active and double click on it to open the legend editor. Select Load, which opens the load legend. Locate the unzipped landuse.avl file, select it, and click OK. When the load legend prompts for Field selection, chose Leveli and click OK. This will change the Values Field in the legend editor to Leveli and assign standard colors to the label attributes. Click Apply to implement these changes. The landuse.avl file included with each county's LULC shape file is the same, so if downloading multiple county LULC files, only one copy of landuse.avl needs to be saved.

ANDERSON.TXT Land use / land cover 4-digit code descriptions in text format

ANDERSON.DOC Land use / land cover 4-digit code descriptions in Word 6.0 format

FWW.TXT Wetlands Cowardin alpha-numeric classification system in text format

FWW.DOC Wetlands Cowardin alpha-numeric classification system in Word 6.0 format

METHODS.TXT Procedures used for combining Integrated Terrain Unit Mapping (ITUM) Land Use/Land Cover and NJ Freshwater Wetlands coverages in text format.

METHODS.DOC Procedures used for combining Integrated Terrain Unit Mapping (ITUM) Land Use/Land Cover and NJ Freshwater Wetlands coverages in Word 6.0 format.

ITUM.TXT Detailed description of the ITUM production by county with methods in text format.

ITUM.DOC Detailed description of the ITUM production by county with methods in Word 6.0 format.

Data Distribution Agreement (NJDEP) Agrees to abide by the terms and conditions of the following: I. Description of Data to be Provided The data provided herein are distributed subject to the following conditions and restrictions: Subject Data Layers For all data contained herein, (NJDEP) makes no representations of any kind, including, but not limited to, the warranties of merchantability or fitness for a particular use, nor are any such warranties to be implied with respect to the digital data layers furnished hereunder. NJDEP assumes no responsibility to maintain them in any manner or form. II. Terms of Agreement 1. Digital data received from the NJDEP are to be used solely for internal purposes in the conduct of daily affairs. 2. The data are provided, as is, without warranty of any kind and the user is responsible for understanding the accuracy limitations of all digital data layers provided herein, as documented in the accompanying Data Dictionary and Readme files. Any reproduction or manipulation of the above data must ensure that the coordinate reference system remains intact. 3. Digital data received from the NJDEP may not be reproduced or redistributed for use by anyone without first obtaining written permission from the NJDEP. This clause is not intended to restrict distribution of printed mapped information produced from the digital data. 4. Any maps, publications, reports, or other documents produced as a result of this project that utilize NJDEP digital data will credit the NJDEP's Geographic Information System (GIS) as the source of the data with the following credit/disclaimer: "This (map/publication/report) was developed using New Jersey Department of Environmental Protection Geographic Information System digital data, but this secondary product has not been verified by NJDEP and is not state-authorized." 5. Users shall require any independent contractor, hired to undertake work that will utilize digital data obtained from the NJDEP, to agree not to use, reproduce, or redistribute NJDEP GIS data for any purpose other than the specified contractual work. All copies of NJDEP GIS data utilized by an independent contractor will be required to be returned to the original user at the close of such contractual work. Users hereby agree to abide by the use and reproduction conditions specified above and agree to hold any independent contractor to the same terms. By using data provided herein, the user acknowledges that terms and conditions have been read and that the user is bound by these criteria.

ITUM land use/land cover: Frequencies run to check for invalid codes. Invalid codes corrected. Nodeerrors and labelerrors functions run and corrected. Some field checking was performed. Land use codes containing ##09 require field verification. Refer to ITUM.TXT or ITUM.DOC. FWW: Some field checking was done on each quarterquad, minimum of four points. Contractor's post-scanning mylar proof sheets, and digital files, were checked by NJDEP staff against original delineation mylars for completeness and accuracy. Line and polygon codes on proof sheets and in digital files were also checked against original delineation mylars. Errors were corrected to achieve 100% coding accuracy. LULC: Completed LULC layer was checked for valid codes, labelerrors and nodeerrors. Area calculations done on all non-tidal wetlands mapped for the FWW mapping effort to insure inclusion of all FWW polygons and FWW codes in final LULC layer. On line visual comparisons of final integrated LULC layer with original FWW and land use/land cover layers also performed. Polygons below .25 acres generated through the integration process were eliminated.

National Map Accuracy Standards (NMAS) -- Data has been systematically plotted on mylar and checked to 1986 photo basemap. Nodeerrors, labelerrors and slivers larger than .25 acres were resolved (see Section 1.2.3 SUPPLEMENTAL INFORMATION). Features are within +/- 80 feet or better from locations on the 1986 photoquads.

Land use/land cover interpreted from 1986 JSS CIR (1:58000) photos. Geology recompiled from 1906 (1:63360) Atlas Sheet. Soils recompiled from 1971 SCS Soil Survey. Floodprone areas recompiled from paper USGS flood maps (polys closed by contractor & coded as such). See Supplemental Information for additional information.

Beaches, Cross Acceptance (BEACH_CA)

Metadata: