Miami 21 research begins by preserving the zone and map code rather than jumping from a transect color to a project conclusion. The transect description, building-height entry, intensity measure, and enactment reference route the reader to distinct standards. It is not an approval.
Last checked: August 7, 2026.
Begin the transect-to-development-metrics route at Miami 21 Zoning feature layer, which supplies exact transect schema. Cross-check the selected geometry through City of Miami Office of Zoning, the route used for official zoning guidance. Before copying M21_ZONE, verify owner CityMiamiFL and accessInformation credits City of Miami Planning and Zoning and GIS Team; those markers keep the Miami 21 enactment trail tied to the intended jurisdiction and record period.
M21_ZONE and Map_Code are the doorway into Miami 21
Miami 21 exposes several representations of the same mapped framework. M21_ZONE stores the zone symbol, Map_Code supports map rendering and lookup, and Transect stores the transect or district code. Transect_D expands that code into descriptions such as Civic Space Zone, Civic Institution Zone, or Work Place District Zone. These fields should cross-check one another; they are not independent approvals. Bldg_Heigh and Intensity or FLR can hold mapped development metrics, but sampled blanks do not mean unlimited height or intensity. Enact provides an enactment identifier such as 13114, which must be retrieved and dated before it is treated as parcel-specific authority. The Miami worksheet therefore connects symbol, description, any populated metrics, enactment, and current Miami 21 text while preserving every blank as an unresolved data condition.
Transect, height, intensity, and FLR answer separate development questions
The Miami 21 enactment trail table keeps each returned label beside its displayed scope and the separate legal record still waiting to be opened. Its first checkpoint is M21_ZONE, which may appear as CS; CI; D1; from there, Open the matching Miami 21 article and table. A blank in the transect-to-development-metrics route stays visible so another reader can distinguish an empty official return from an unexamined field.
| Local field, layer, or record | What it does | Displayed value or scope | Next code or record check | Official page |
|---|---|---|---|---|
| M21_ZONE field | stores the Miami 21 zone symbol | CS; CI; D1 | Open the matching Miami 21 article and table. | Open exact record |
| Map_Code field | stores the map code used for rendering and lookup | CS; CI; D1 | Cross-check it with M21_ZONE rather than assuming every map code is a new legal category. | Open exact record |
| Transect field | stores the transect/district code | CS; CI; D1 | Use it to locate the form-based regulation set. | Open exact record |
| Transect_D field | expands the transect description | Civic Space Zone; Civic Institution Zone; Work Place District Zone | Confirm the symbol-to-description pairing before applying standards. | Open exact record |
| Bldg_Heigh field | can carry a mapped building-height value | blank in sampled rows | A blank does not establish unlimited height; consult the code and other height controls. | Open exact record |
| Intensity / FLR fields | can carry intensity and floor-lot-ratio values | blank in sampled rows | Use applicable code tables when the feature row does not supply a value. | Open exact record |
| Enact field | records an enactment identifier | 13114 | Retrieve the enactment and effective date before treating it as parcel-specific authority. | Open exact record |
Route each Miami 21 field to the provision that governs it
- Open the Miami 21 enactment trail; fix the parcel, boundary, jurisdiction, and official key before reading thematic records.
- Start the transect-to-development-metrics route by copying M21_ZONE exactly as returned, including CS; CI; D1.
- Keep Map_Code in a second Miami 21 enactment trail worksheet field because it stores the map code used for rendering and lookup.
- Test Transect independently, then mark its value, service layer, or documented blank in the transect-to-development-metrics route.
- Give Transect_D and every later item a separate row; never compress history, plans, and overlays into the Miami 21 enactment trail result.
- Attach the Miami 21 enactment trail lookup time to M21_ZONE, while preserving this separate currency clue: The ArcGIS item metadata and service modification date are data clues; the Enact record and current Miami 21 code provide legal-effect clues.
- If M21_ZONE and Map_Code conflict, send the transect-to-development-metrics route to Miami 21 Zoning feature layer and ask which enactment and standard govern the returned transect.
The Miami 21 enactment trail worksheet is complete only when another reader can reproduce the transect-to-development-metrics route from the same parcel key and official pages. Keep each source's legal role and effective date apart, then record which enactment and standard govern the returned transect as unresolved instead of selecting the most convenient output. The local currency note remains part of that audit trail: The ArcGIS item metadata and service modification date are data clues; the Enact record and current Miami 21 code provide legal-effect clues.
Work a transect result without treating Bldg_Heigh as a blanket entitlement
Suppose a hypothetical Miami feature returns M21_ZONE CS, Map_Code CS, Transect CS, Transect_D Civic Space Zone, blank Bldg_Heigh, blank Intensity or FLR, and Enact 13114. The three CS fields are compared and recorded as consistent representations rather than counted as three permissions. The Civic Space Zone description confirms the symbol-to-description pairing. Because the height and intensity fields are blank, the researcher opens the applicable Miami 21 article and tables instead of writing no limit. Enact 13114 is retrieved and its effective date and geographic scope are checked before it is connected to the parcel. The hypothetical answer can identify a mapped CS record and the next legal sources, but it cannot infer development metrics from empty cells or treat the enactment number alone as approval.
Enact supplies legal history that the service modification date cannot
| Returned local record | Record to compare | When to stop | Next decision |
|---|---|---|---|
| M21_ZONE returns CS; CI; D1 | Compare with Map_Code, which stores the map code used for rendering and lookup | Stop the transect-to-development-metrics route if Map_Code is missing, dated differently, or points to another record. | Continue through the Miami 21 enactment trail: Open the matching Miami 21 article and table. Then test whether Map_Code changes that route. |
| Map_Code returns CS; CI; D1 | Compare with Transect, which stores the transect/district code | Stop the transect-to-development-metrics route if Transect is missing, dated differently, or points to another record. | Continue through the Miami 21 enactment trail: Cross-check it with M21_ZONE rather than assuming every map code is a new legal category. Then test whether Transect changes that route. |
| Transect returns CS; CI; D1 | Compare with Transect_D, which expands the transect description | Stop the transect-to-development-metrics route if Transect_D is missing, dated differently, or points to another record. | Continue through the Miami 21 enactment trail: Use it to locate the form-based regulation set. Then test whether Transect_D changes that route. |
| Transect_D returns Civic Space Zone; Civic Institution Zone; Work Place District Zone | Compare with Bldg_Heigh, which can carry a mapped building-height value | Stop the transect-to-development-metrics route if Bldg_Heigh is missing, dated differently, or points to another record. | Continue through the Miami 21 enactment trail: Confirm the symbol-to-description pairing before applying standards. Then test whether Bldg_Heigh changes that route. |
| Bldg_Heigh returns blank in sampled rows | Compare with Intensity / FLR, which can carry intensity and floor-lot-ratio values | Stop the transect-to-development-metrics route if Intensity / FLR is missing, dated differently, or points to another record. | Continue through the Miami 21 enactment trail: A blank does not establish unlimited height; consult the code and other height controls. Then test whether Intensity / FLR changes that route. |
| Intensity / FLR returns blank in sampled rows | Compare with Enact, which records an enactment identifier | Stop the transect-to-development-metrics route if Enact is missing, dated differently, or points to another record. | Continue through the Miami 21 enactment trail: Use applicable code tables when the feature row does not supply a value. Then test whether Enact changes that route. |
| Enact returns 13114 | Compare with M21_ZONE, which stores the Miami 21 zone symbol | Stop the transect-to-development-metrics route if M21_ZONE is missing, dated differently, or points to another record. | Continue through the Miami 21 enactment trail: Retrieve the enactment and effective date before treating it as parcel-specific authority. Then test whether M21_ZONE changes that route. |
Miami, Florida date check: The ArcGIS item metadata and service modification date are data clues; the Enact record and current Miami 21 code provide legal-effect clues.
The Miami 21 Zoning feature layer defines the exact transect schema, the Office of Zoning supplies official guidance, and City Planning supplies Miami 21 code and planning context. ArcGIS item metadata and the service modification date are data-currency clues. Enact and the current Miami 21 code supply legal-effect clues. Keep those timelines separate. A service edit can correct a field without changing the underlying ordinance, and an enactment can apply only to described geography. M21_ZONE, Map_Code, and Transect should agree or produce a documented conflict; Transect_D should confirm the description. Blank Bldg_Heigh or FLR values remain blank at the feature level even when the code supplies a standard elsewhere. Miami currency is established by linking the current feature to the effective enactment and code, not by reading one metadata timestamp as law.
When an ArcGIS field and the current Miami 21 text diverge
| Local situation | What went wrong | What to retain | How to resolve it |
|---|---|---|---|
| Scenario 1 | A blank Bldg_Heigh or FLR field is reported as no limit. | Preserve Transect, the selected geometry, and both timestamps from the Miami 21 enactment trail check. | Use Miami 21 Zoning feature layer to settle which enactment and standard govern the returned transect; then Use it to locate the form-based regulation set. |
| Scenario 2 | Map_Code and Transect are counted as two independent approvals instead of cross-checking representations of the mapped code. | Preserve Transect_D, the selected geometry, and both timestamps from the Miami 21 enactment trail check. | Use Miami 21 Zoning feature layer to settle which enactment and standard govern the returned transect; then Confirm the symbol-to-description pairing before applying standards. |
If blank Bldg_Heigh or Intensity or FLR fields were reported as no limit, withdraw that conclusion, preserve the blank values, and retrieve the applicable Miami 21 tables and other height controls. If M21_ZONE, Map_Code, and Transect were counted as independent approvals, recast them as cross-checking representations and verify Transect_D. Retrieve Enact 13114 or the exact returned enactment and confirm its effective date and parcel scope. A focused Office of Zoning question is: For this parcel, which Miami 21 symbol and description currently apply, which code provisions supply height and intensity when the feature fields are blank, and does the listed Enact govern this geometry? Attach the service query and modification clues separately from the enactment date. This asks for controlling sources without converting missing data into favorable rights.
Use the feature layer, Office of Zoning, and Planning for different evidence
| Official page | What to check there | Local coverage shown |
|---|---|---|
| Miami 21 Zoning feature layer | exact transect schema | CityMiamiFL item with City Planning and Zoning attribution |
| City of Miami Office of Zoning | official zoning guidance | City department page |
| City of Miami Planning | Miami 21 planning and code context | Official planning page |
How should M21_ZONE be checked in Miami, Florida?
Open the official M21_ZONE record and capture the value inside the Miami 21 enactment trail. That record shows how M21_ZONE stores the Miami 21 zone symbol; one displayed form is CS; CI; D1. Place the copied value in the transect-to-development-metrics route, then follow its separate rule route: Open the matching Miami 21 article and table.
How should Map_Code be checked in Miami, Florida?
Open the official Map_Code record and capture the value inside the Miami 21 enactment trail. That record shows how Map_Code stores the map code used for rendering and lookup; one displayed form is CS; CI; D1. Place the copied value in the transect-to-development-metrics route, then follow its separate rule route: Cross-check it with M21_ZONE rather than assuming every map code is a new legal category.
How should Transect be checked in Miami, Florida?
Open the official Transect record and capture the value inside the Miami 21 enactment trail. That record shows how Transect stores the transect/district code; one displayed form is CS; CI; D1. Place the copied value in the transect-to-development-metrics route, then follow its separate rule route: Use it to locate the form-based regulation set.
- Selected parcel key, geometry, and responsible jurisdiction
- Every returned value from the local field table
- Page titles, URLs, lookup times, and update clues
- Opened code, plan, case, ordinance, or metadata records
- Unresolved blanks, boundary splits, dates, and competing outputs
- Proposed activity stated in code-relevant facts
- Agency contact, narrow question, reply date, and limits
The Miami 21 enactment trail does not decide title, survey boundaries, private restrictions, vested rights, building-code compliance, utilities, licensing, or permit issuance. Request a written response when the transect-to-development-metrics route leaves competing official results or when substantial reliance is planned. A useful request to Miami 21 Zoning feature layer identifies the parcel, quotes M21_ZONE and Map_Code, gives their source dates, and asks which enactment and standard govern the returned transect.
Use miami zoning map by address, zoning code vs zoning map, zoning overlays special districts only where those methods clarify the transect-to-development-metrics route. The Miami 21 enactment trail evidence linked for M21_ZONE and Map_Code remains the local starting point.
Reviewed August 7, 2026. Recheck the Miami 21 enactment trail, its cited ordinance, and the agency procedure before relying on the saved worksheet.