| ArcGIS REST Services Directory | Login | Get Token |
| Home > services > MapServices > WhereCanYouDoIt (MapServer) > ZBLCurrentZoning > iteminfo | Help | API Reference |
| JSON |
| snippet: | This layer captures ZBL/current-zoning intersect records that match ordinance values and do not have a PDZONE value. It preserves ZBL/current zoning context and adds the same state summary bucket fields by reading hard-coded ZBL land-use fields. |
| summary: | This layer captures ZBL/current-zoning intersect records that match ordinance values and do not have a PDZONE value. It preserves ZBL/current zoning context and adds the same state summary bucket fields by reading hard-coded ZBL land-use fields. |
| accessInformation: | |
| thumbnail: | |
| maxScale: | 5000 |
| typeKeywords: | [] |
| description: | <DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>Byproduct layer from the ZBL/current-zoning intersect where the ZBL record has no PDZONE value. Source data includes SDE Zoning (sde.SDE.Zoning\sde.SDE.Zoning), SDE MTC (sde.SDE.Planning\sde.SDE.MTC), ZBL_aliased geodatabase layer, Use_Table.xlsx, and Use_Table - PD Test.xlsx. </SPAN></P><P><SPAN>Processing lineage: Created after PairwiseIntersect between ZBL_aliased and full_zoning. Records are selected where the zoning ordinance field equals the ZBL ordinance field and PDZONE is null or blank. State summary fields are calculated from the script’s ZBL_BUCKET_FIELDS list. </SPAN></P><P><SPAN>Update frequency: Regenerate after updates to SDE zoning, MTC, ZBL_aliased, standard use tables, or PD use tables. </SPAN></P><P><SPAN>Review unmatched ordinances, missing PD sheets, and warnings emitted by the Python script.</SPAN></P></DIV></DIV></DIV> |
| licenseInfo: | |
| catalogPath: | |
| title: | sde.SDE.ZBLCurrentZoning |
| type: | |
| url: | |
| tags: | ["zoning","planning","gis","base layer"] |
| culture: | en-US |
| name: | |
| guid: | |
| minScale: | 150000000 |
| spatialReference: |