Description: <DIV STYLE="text-align:Left;font-size:12pt"><P><SPAN>Bench marks set on or near a project that are connected with and published in the NSRS, and are used to densify local project control</SPAN></P><P><SPAN>monuments or develop project features. These NSRS bench marks may be established by the NGS, USACE, or other agencies. Each USACE project and water level gage should have at least one PPCP.</SPAN></P><P><SPAN /></P></DIV>
Service Item Id: 93176c80ba5f43f3b02bb7a01d5fd76a
Copyright Text: U.S. Army Corps of Engineers
Default Visibility: true
MaxRecordCount: 5000
MaxSelectionCount: 2000
Supported Query Formats: JSON, geoJSON, PBF
Min Scale: 500000.0
Max Scale: 0.0
Supports Advanced Queries: true
Supports Statistics: true
Has Labels: false
Can Modify Layer: true
Can Scale Symbols: false
Use Standardized Queries: true
Supports Datum Transformation: true
Unique Id Infos:
Type: simple
Fields: ["id"]
OID Field Contains Hash Value: true
Description: <DIV STYLE="text-align:Left;font-size:12pt"><P><SPAN>Monuments (PBMs, TBMs, hubs, etc.) used to reference project features, alignment, elevations, or construction. Monuments may be atop levees (e.g., PBMs set at levee sector "points of intersection" or PIs) or offset to the levee alignment. These monuments will usually have local X-Y-Z (SPCS) coordinates along with local project station-offset coordinates. LPCPs are usually not part of the published NSRS; however, they should be directly established from or relative to a PPCP described above. A minimum of three project control bench marks (PPCPs and/or LPCPs) are required for advertised construction plans and references to water level gages.</SPAN></P><P><SPAN /></P></DIV>
Service Item Id: 93176c80ba5f43f3b02bb7a01d5fd76a
Copyright Text:
Default Visibility: true
MaxRecordCount: 5000
MaxSelectionCount: 2000
Supported Query Formats: JSON, geoJSON, PBF
Min Scale: 500000.0
Max Scale: 0.0
Supports Advanced Queries: true
Supports Statistics: true
Has Labels: false
Can Modify Layer: true
Can Scale Symbols: false
Use Standardized Queries: true
Supports Datum Transformation: true
Unique Id Infos:
Type: simple
Fields: ["id"]
OID Field Contains Hash Value: true