{ "culture": "en-US", "name": "Map_WFL1", "guid": "52F190EF-0673-41C6-8C55-D9E4431C42EB", "catalogPath": "", "snippet": "county roads", "description": "
This is a dynamically-segmented subset of NJDOT's NJ Roadway Network, filtered to a selected set of certain routes (distinct SRIs) that exclusively represents the county road system of Middlesex County, excluding ramps. This metadata is largely authored by NJDOT as included in the metadata document for the NJ Roadway Network feature class published on June 1, 2020, but has been supplemented by the Middlesex County Office of Planning, Spatial Data Services Group (MCOP-SDSG).<\/SPAN><\/P> The jurisdiction_type_code and street_name attribute fields included in this dataset were derived from the ln_jurisdiction and ln_street_name linear referencing system (LRS) route event tables included in the NJDOT's SLD data warehouse and its associated reference network, NJ Roadway Network (June 1, 2020 edition). The jurisdiction_type_code data identifies the prevailing agency <\/SPAN>primarily<\/SPAN> responsible for the maintenance and ownership of the roadway corresponding to each distinct route segment record. The NJDOT's jurisdiction data cannot and should NOT be interpreted or assumed to be absolute along any portion of each distinct route segment in this layer. Reliance on this data is limited and extreme caution must be exercised when interpreting this data for any and all site-specific inquiries. The intended purpose of NJDOT's jurisdiction attribution is to serve high-level roadway planning and analysis functions, such as (but not limited to):<\/SPAN><\/P> Preparing summary reports of roadway mileage according to jurisdiction; and,<\/SPAN><\/P><\/LI> Creating small-scale maps, such as at a city or a regional scale; and,<\/SPAN><\/P><\/LI> Producing illustrative diagrammatic views of roadway jurisdiction information. <\/SPAN><\/P><\/LI><\/UL> NJDOT jurisdiction data is currently available in the primary inventory direction only, for all route types except for ramps. Meaning the extent of NJDOT's jurisdiction attribution is limited to the primary direction. The primary direction of a route, where segement_type = 1, carries the inventoried mileage according to its inventory direction for each route in NJDOT's network. The MCOP-SDSG staff supplemented NJDOT's primary direction jurisdiction data by creating LRS events in the secondary direction of divided routes (dual-centerlines) that correspond to the related jurisdiction data in the primary direction.<\/SPAN><\/P> The NJ Roadway Network and sld_sri_master table were filtered using SQL statements to include all county routes in Middlesex County and NJ Route 27 (ramps for all routes were excluded). Using LRS tools and methods available in Esri's ArcGIS Pro software, a route event overlay of ln_jurisdiction, ln_street_name and sld_sri_master was created in tabular format that could be dynamically segmented against the route reference of NJ Roadway Network (all 06-01-2020 versions). Null jurisdiction data in the resultant table for events on all routes in the secondary direction were manually populated with milepost data corresponding to the related limits located on the primary direction. Secondary direction routes were segmented using measure values of the secondary routes. The spatial extent of data for NJ Route 27 was trimmed to the milepost limits within the City of New Brunswick; a portion of Route 27 in New Brunswick is under county jurisdiction; inventoried by NJDOT as 00000027__ but posted on signage as County Route 644 (12000644__). The spatial extent of data for all 500-series routes was trimmed to represent the milepost limits of each route to be within the County of Middlesex. The full extent of mileage on all \"other county routes\" in Middlesex county was retained.<\/SPAN><\/P> NJDOT has adopted a new data model for their transportation network. This data model was designed using portions of the ESRI UNETRANS data model, and incorporates existing data with more recent spatial and roadway inventory data. These data will encompass the NJDOT statewide road network, as well as public roads that fall outside of the NJDOT's jurisdiction. Roads were digitized using 2002 New Jersey statewide orthophotos, which were produced at a scale of 1:2400 (1\"=200') with a 1 foot pixel resolution. The orthophotos were captured during February-April 2002, and were ortho-rectified to a +/- 4.0 foot horizontal accuracy at a 95% confidence level. Roads were digitized to the visible center of a street, within a tolerance of +/- 3 feet and then attributed using data collected for the Maintenance Management Systems and Local Road Inventory projects (2002-2005), which are both NJDOT BTDS data collection projects. Only public roads were digitized and attributed. Roads were digitized as divided where there was a visible, physical median separating carriageways for a length of greater than 600 feet. In the secondary direction, along median separated segments of roadway in the south and westbound directions, the milepost values are opposite to those in the primary direction. Ramps were digitized when the gore-to-gore distance was greater than 25 feet. This dataset does not include address range attributes. The project began in November 2003, and was completed by May 31, 2005.<\/SPAN><\/SPAN><\/P><\/DIV><\/DIV><\/DIV>",
"summary": "county roads",
"title": "Map_WFL1",
"tags": [],
"type": "Feature Service",
"typeKeywords": [
"Data",
"Service",
"Feature Service",
"ArcGIS Server",
"Feature Access",
"providerSDS"
],
"thumbnail": "thumbnail/thumbnail.png",
"url": "",
"extent": [
[
-74.6233315070442,
40.2522991590003
],
[
-74.2122344458315,
40.6017840748691
]
],
"minScale": 0,
"maxScale": 1.7976931348623157E308,
"spatialReference": "WGS_1984_Web_Mercator_Auxiliary_Sphere",
"accessInformation": "New Jersey Department of Transportation (NJDOT), Middlesex County Office of Planning, Spatial Data Services Group (MCOP-SDSG)",
"licenseInfo": " The jurisdiction_type_code data identifies the prevailing agency <\/SPAN>primarily<\/SPAN> responsible for the maintenance and ownership of the roadway corresponding to each distinct route segment record. The NJDOT's jurisdiction data cannot and should NOT be interpreted or assumed to be absolute along any portion of each distinct route segment in this layer. Reliance on this data is limited and extreme caution must be exercised when interpreting this data for any and all site-specific inquiries. The intended purpose of NJDOT's jurisdiction attribution is to serve high-level roadway planning and analysis functions, such as (but not limited to):<\/SPAN><\/P> Preparing summary reports of roadway mileage according to jurisdiction; and,<\/SPAN><\/P><\/LI> Creating small-scale maps, such as at a city or a regional scale; and,<\/SPAN><\/P><\/LI> Producing illustrative diagrammatic views of roadway jurisdiction information.<\/SPAN><\/P><\/LI><\/UL><\/DIV><\/DIV><\/DIV>"
}