flumDetails API returns land use planning data for a given location. It provides information about the future land use designation, permitted uses, and development controls.
There are two types of API calls:
Point-Based Search The Point-Based Search technique allows you to retrieve FLUM-based zoning data for a specific location using one of the following parameters:
Area-Based Search The Area-Based Search technique allows you to retrieve FLUM-based zoning data for an area whose boundaries are defined using one of the following parameters:
A token needed to make API calls.
Bottom right latitude is the coordinate from the lower right corner of the area for which we want FLUM data.
Bottom right longitude is the coordinate from the lower right corner of the area for which we want FLUM data.
Top left latitude is the coordinate from the top left corner of the area for which we want FLUM data.
Top left longitude is the coordinate from the top left corner of the area for which we want FLUM data.
This parameter lets you specify the boundary of an area within which you want its FLUM data.
(lat/lng are required when using this parameter)
Specifies the search radius in meters from a point of origin defined by the latitude (lat) and longitude (lng) parameters. When lat and lng are used together with radius, they become the center point (origin) of the circular search area. The maximum allowed radius is 5,000 meters. Example: If you set lat = 40.7128 and lng = -74.0060 (around New York City) with a radius = 1000, the API will return results within a 1 km circular area centered at that point.
Gives you FLUM data for the specifiedzip code.
This parameter is optional and can have any of these values:
| Value | Description |
|---|---|
| flum | basic flum data is returned. You can pass this value in API as: output_fields=flum |
| flum_plu | API would return Permitted Land Use data, if available.You can pass this value in API as: output_fields=flum_plu |
| flum_controls | API would return controls data.You can pass this value in API as: output_fields=flum_controls |
| flum_parcel | returns information about the parcels.You can pass this value in API as: output_fields=flum_parcel |
| flum_geom | returns geometric data that defines the boundary of the zone. You can pass this value in API as: output_fields=flum_geom |
Indicates whether the request was successful or not
The link field contains the URL that corresponds to the resource or endpoint you requested. It provides a direct link to the requested resource, enabling you to quickly access or reference the specific location related to their request within the API.
This returns a JSON object with all the data sets grouped under keys defined below. The response could vary depending on the output_fields param
| Data Group | Response Item | Description | Type |
|---|---|---|---|
Meta | city_id | Unique ID for a city. | number |
city_name | Name of the city. | string | |
last_updated | Indicates the date when the zoning data was last updated in the Zoneomics data repository. | date | |
Flum | gid | Grid ID is used to identify the geometry of a zone on the map. | number |
flum_code | Represents the land use designation assigned to a zone on the Future Land Use Map (FLUM). This code serves as a quick reference to the intended use category (e.g., RES for Residential, COM for Commercial). | string | |
future_land_use_name | The full name or label of the future land use designation, as shown in the FLUM (e.g., High Density Residential). | string | |
flum_category | Categorizes similar land use types. Examples include Residential, Commercial, Industrial, Open Space, and Mixed Use. This helps users understand the general planning intent for the zone. | string | |
flum_land_use_type | A more specific classification within the broader FLUM category. It provides further detail about the nature of the land use (e.g., "Single-Family Residential" under the Residential category). | string | |
flum_land_use_sub_type | A precise designation that distinguishes between different subtypes of a land use type. For example, Multi Family. | string | |
description | A narrative summary explaining the characteristics and intended uses of the designated land use. For example, for high-density residential areas, it may describe the types of housing (e.g., multifamily buildings), allowable building height (e.g., 3–4 stories), and possible inclusion of small-scale commercial or professional uses. | string | |
zoning_code_section | A reference to the relevant section of the local zoning ordinance or municipal code that governs the allowed uses and development standards for the designated future land use. | string | |
Boundary | boundary | Returns geometric data that defines the boundary of the zone. | array |
PLU | consistent_zoning_districts | Zoning districts that are consistent with the designated future land use. These are zoning classifications that align with the intent and purpose of the FLUM designation. | string |
consistent_zoning_districts_conditions | Conditions that apply to the listed consistent zoning districts. These may include special requirements, exceptions, or limitations under which the zoning districts are considered consistent. | string | |
uses_include_primary | Land use types that are considered primary uses under the future land use designation. These are the main intended uses for the area. | string | |
uses_include_secondary | Land use types that are considered secondary. These are not the main focus but may be permitted to support or complement primary uses. | string | |
Controls | maximum_building_height_ft | The maximum allowable building height in feet. | string |
maximum_building_height_stories | The maximum number of stories (floors) permitted for buildings within the designated area. | string | |
maximum_far | The maximum Floor Area Ratio (FAR) allowed for the site. FAR is the ratio of total floor area to the size of the parcel. | string | |
minimum_far | The minimum required floor area ratio (FAR) for development | string | |
maximum_density_dwelling_units_per_gross_acre | The maximum residential density allowed, measured as dwelling units per gross acre (includes roads and open space). | string | |
minimum_density_dwelling_units_per_gross_acre | The minimum residential density required, also in units per gross acre. This encourages more dense development. | string | |
Parcels "(available for Enterprise users only.)" | lat | Latitude of the parcel. | number |
lng | Longitude of the parcel. | number | |
apn | ID of the parcel. | string | |
address | Address of the parcel. | string | |
land_use | Contains the permitted land use of the parcel. For example, Commercial, Religious. | string | |
owner_info | Displays the parcel owner's information, including the owner's name and address. | object | |
area | Area covered by the parcel. The area covered by the parcel is displayed in square yards. | number |
Find all the usecases for the api below
https://api.zoneomics.com/v2/flumDetails?bottom_right_lat=33.815813&bottom_right_lng=-118.388286&top_left_lat=33.816264&top_left_lng=-118.389892&api_key=<Your API Key>https://api.zoneomics.com/v2/flumDetails?api_key=<Your API Key>&boundary=-122.31467485427858,47.60284993754822|-122.31473922729494,47.57432539907205|-122.3566246032715,47.57548347095205|-122.31467485427858,47.60284993754822https://api.zoneomics.com/v2/flumDetails?radius=50&lat=33.43544202525436&lng=-112.64360231983706&api_key=<Your API Key>https://api.zoneomics.com/v2/flumDetails?api_key=<Your API Key>&zipcode=90277Talk to our team about API access, data coverage, pricing, and the best Zoneomics API package for your use case.
flumDetails API returns land use planning data for a given location. It provides information about the future land use designation, permitted uses, and development controls.
There are two types of API calls:
Point-Based Search The Point-Based Search technique allows you to retrieve FLUM-based zoning data for a specific location using one of the following parameters:
Area-Based Search The Area-Based Search technique allows you to retrieve FLUM-based zoning data for an area whose boundaries are defined using one of the following parameters:
A token needed to make API calls.
Bottom right latitude is the coordinate from the lower right corner of the area for which we want FLUM data.
Bottom right longitude is the coordinate from the lower right corner of the area for which we want FLUM data.
Top left latitude is the coordinate from the top left corner of the area for which we want FLUM data.
Top left longitude is the coordinate from the top left corner of the area for which we want FLUM data.
This parameter lets you specify the boundary of an area within which you want its FLUM data.
(lat/lng are required when using this parameter)
Specifies the search radius in meters from a point of origin defined by the latitude (lat) and longitude (lng) parameters. When lat and lng are used together with radius, they become the center point (origin) of the circular search area. The maximum allowed radius is 5,000 meters. Example: If you set lat = 40.7128 and lng = -74.0060 (around New York City) with a radius = 1000, the API will return results within a 1 km circular area centered at that point.
Gives you FLUM data for the specifiedzip code.
This parameter is optional and can have any of these values:
| Value | Description |
|---|---|
| flum | basic flum data is returned. You can pass this value in API as: output_fields=flum |
| flum_plu | API would return Permitted Land Use data, if available.You can pass this value in API as: output_fields=flum_plu |
| flum_controls | API would return controls data.You can pass this value in API as: output_fields=flum_controls |
| flum_parcel | returns information about the parcels.You can pass this value in API as: output_fields=flum_parcel |
| flum_geom | returns geometric data that defines the boundary of the zone. You can pass this value in API as: output_fields=flum_geom |
Indicates whether the request was successful or not
The link field contains the URL that corresponds to the resource or endpoint you requested. It provides a direct link to the requested resource, enabling you to quickly access or reference the specific location related to their request within the API.
This returns a JSON object with all the data sets grouped under keys defined below. The response could vary depending on the output_fields param
| Data Group | Response Item | Description | Type |
|---|---|---|---|
Meta | city_id | Unique ID for a city. | number |
city_name | Name of the city. | string | |
last_updated | Indicates the date when the zoning data was last updated in the Zoneomics data repository. | date | |
Flum | gid | Grid ID is used to identify the geometry of a zone on the map. | number |
flum_code | Represents the land use designation assigned to a zone on the Future Land Use Map (FLUM). This code serves as a quick reference to the intended use category (e.g., RES for Residential, COM for Commercial). | string | |
future_land_use_name | The full name or label of the future land use designation, as shown in the FLUM (e.g., High Density Residential). | string | |
flum_category | Categorizes similar land use types. Examples include Residential, Commercial, Industrial, Open Space, and Mixed Use. This helps users understand the general planning intent for the zone. | string | |
flum_land_use_type | A more specific classification within the broader FLUM category. It provides further detail about the nature of the land use (e.g., "Single-Family Residential" under the Residential category). | string | |
flum_land_use_sub_type | A precise designation that distinguishes between different subtypes of a land use type. For example, Multi Family. | string | |
description | A narrative summary explaining the characteristics and intended uses of the designated land use. For example, for high-density residential areas, it may describe the types of housing (e.g., multifamily buildings), allowable building height (e.g., 3–4 stories), and possible inclusion of small-scale commercial or professional uses. | string | |
zoning_code_section | A reference to the relevant section of the local zoning ordinance or municipal code that governs the allowed uses and development standards for the designated future land use. | string | |
Boundary | boundary | Returns geometric data that defines the boundary of the zone. | array |
PLU | consistent_zoning_districts | Zoning districts that are consistent with the designated future land use. These are zoning classifications that align with the intent and purpose of the FLUM designation. | string |
consistent_zoning_districts_conditions | Conditions that apply to the listed consistent zoning districts. These may include special requirements, exceptions, or limitations under which the zoning districts are considered consistent. | string | |
uses_include_primary | Land use types that are considered primary uses under the future land use designation. These are the main intended uses for the area. | string | |
uses_include_secondary | Land use types that are considered secondary. These are not the main focus but may be permitted to support or complement primary uses. | string | |
Controls | maximum_building_height_ft | The maximum allowable building height in feet. | string |
maximum_building_height_stories | The maximum number of stories (floors) permitted for buildings within the designated area. | string | |
maximum_far | The maximum Floor Area Ratio (FAR) allowed for the site. FAR is the ratio of total floor area to the size of the parcel. | string | |
minimum_far | The minimum required floor area ratio (FAR) for development | string | |
maximum_density_dwelling_units_per_gross_acre | The maximum residential density allowed, measured as dwelling units per gross acre (includes roads and open space). | string | |
minimum_density_dwelling_units_per_gross_acre | The minimum residential density required, also in units per gross acre. This encourages more dense development. | string | |
Parcels "(available for Enterprise users only.)" | lat | Latitude of the parcel. | number |
lng | Longitude of the parcel. | number | |
apn | ID of the parcel. | string | |
address | Address of the parcel. | string | |
land_use | Contains the permitted land use of the parcel. For example, Commercial, Religious. | string | |
owner_info | Displays the parcel owner's information, including the owner's name and address. | object | |
area | Area covered by the parcel. The area covered by the parcel is displayed in square yards. | number |
Find all the usecases for the api below
https://api.zoneomics.com/v2/flumDetails?bottom_right_lat=33.815813&bottom_right_lng=-118.388286&top_left_lat=33.816264&top_left_lng=-118.389892&api_key=<Your API Key>https://api.zoneomics.com/v2/flumDetails?api_key=<Your API Key>&boundary=-122.31467485427858,47.60284993754822|-122.31473922729494,47.57432539907205|-122.3566246032715,47.57548347095205|-122.31467485427858,47.60284993754822https://api.zoneomics.com/v2/flumDetails?radius=50&lat=33.43544202525436&lng=-112.64360231983706&api_key=<Your API Key>https://api.zoneomics.com/v2/flumDetails?api_key=<Your API Key>&zipcode=90277Talk to our team about API access, data coverage, pricing, and the best Zoneomics API package for your use case.