Israel Zoning Plans - Land Use, Status & Documents avatar

Israel Zoning Plans - Land Use, Status & Documents

Pricing

from $10.00 / 1,000 zoning plans

Go to Apify Store
Israel Zoning Plans - Land Use, Status & Documents

Israel Zoning Plans - Land Use, Status & Documents

Search Israel's official zoning plan database by block (gush), parcel (helka), plan number or city. Returns plan number, city, description, approval status and date, plus links to the official regulations, site-plan and GIS documents.

Pricing

from $10.00 / 1,000 zoning plans

Rating

0.0

(0)

Developer

Swerve

Swerve

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

2 days ago

Last modified

Categories

Share

Israel Zoning Plans Scraper - Tabaot by Block, Parcel or City

Search Israel's official national zoning-plan database (תכניות בניין עיר) and get clean structured data: plan number, city, what the plan permits, its approval status and date, and direct links to the binding regulations, the site plan and the GIS files.

This is the data that decides what may be built on a piece of land. Appraisers, developers, land investors, architects and lawyers check it before every deal.

Why this instead of the government site

The government search returns at most 150 plans per query and picks which 150. This Actor detects that limit and splits the query automatically, so a dense block returns everything. On block 3946 the official site shows 150 plans; this Actor returns 226.

The government search stops at 150 plans; this Actor returns 226

What you get

One row per zoning plan, with the fields returned

FieldExample
planNumber, planId, planUrl"416-0447284", "4023472", link to the official page
city, description"רעננה", "רע/מק/1010א - תכנית בסמכות ועדה מקומית מכוח סעיף 23 לתמ״א 38"
status, statusDate, isApproved"פרסום לתוקף בעיתונים", "2019-11-22", true
regulationsUrlDirect PDF of the binding regulations (takanon)
sitePlanUrlDirect PDF of the site plan drawing (tasrit)
gisFilesUrlZIP of the plan's GIS layers, for mapping software
documents[]Every published file: { kind, name, url }
queryBlock, queryParcel, queryCityWhich of your search targets returned this plan

Dates are normalized to YYYY-MM-DD. isApproved is true when the plan is in force, false while it is still in process, and null when the status is one we do not recognize, so an unknown status never silently looks rejected.

Input

FieldWhat it does
blocksThe reliable way to get complete results. "6586" for a whole block, "6586/450" for one parcel. These numbers appear on every Israeli title deed and sale record.
planNumbersExact plan numbers, e.g. "רע/2000/ב" or "507-0829788".
citiesCity names in Hebrew. Capped at 150 by the source, see below.
statusesDeposited, objections, decision to approve, approved.
fromStatusDate / toStatusDateFilter by when the current status was set. Applied by this Actor after fetching, because the source accepts date filters but ignores them.
maxItemsOptional cost cap. Blank returns everything that matches.
includeDocumentsOn by default. Adds the document links at no extra requests.

Example: everything on one parcel

{ "blocks": ["6586/450"] }

Example: three blocks, approved plans only

{ "blocks": ["6586", "6213", "7104"], "statuses": ["approved"] }

How it works

One search request per target against the government plan-search API. Results are de-duplicated by plan id across all your targets, and pushed to the dataset as they arrive, so a stopped run keeps everything already collected. When a block comes back at the source's 150-row limit, the Actor re-queries that block once per plan type and merges the results, which is how it returns more than the website does.

Limits, stated honestly

  • City searches are capped by the source at 150 plans, no matter how many exist. The run logs how many the source says exist and how many are therefore missing, and it tells you to search by block instead. It never pretends a capped city search was complete.
  • The source ignores date filters, so this Actor applies them itself after fetching. A plan whose date cannot be read is kept rather than dropped.
  • Plans are published in Hebrew and returned in Hebrew, exactly as the government publishes them.
  • Very dense blocks can still hit the limit inside a single plan type. The run warns and tells you to narrow to a parcel.

Export formats

JSON, CSV, Excel, XML or HTML, from the Console or the API (/v2/datasets/{datasetId}/items?format=csv).

Use cases

  • Due diligence before a purchase: pull every plan touching the block and parcel, and read the binding regulations.
  • Development potential: find blocks with recently approved plans that raise building rights.
  • Appraisal: cite the plan number, status and date behind a valuation.
  • Monitoring: run weekly on your blocks and diff to catch newly deposited or approved plans.
  • Israel Land Tenders - state land auctions with reserve prices, deadlines and the winning bidders. Each lot carries its zoning plan number, which you can feed straight into this Actor.
  • Israel Sold Property Prices - recorded sale transactions, searchable by the same block and parcel numbers.