OverviewGuidesDataAPIContact
Get API Key

Fetching Property Data

Learn how to retrieve comprehensive information for a single property using geographic coordinates.

Understanding syte's Data Model

Properties, Parcels, and Buildings

syte's data model consists of three main entities: buildings, parcels, and properties. Buildings and parcels come directly from cadastral systems. Properties are intelligently constructed by syte to create a consistent data structure.

Since buildings can span multiple cadastral parcels, syte creates "virtual" properties by grouping parcels in a way that ensures each building is fully contained within a single property. This provides a clean, hierarchical data model where properties contain buildings, avoiding complex overlapping relationships.

Note: These syte properties are optimized for spatial analysis and don't necessarily reflect legal ownership boundaries, which remain private in official land registries (Grundbuch).

Single Property Data APIs

syte provides two APIs to fetch data for a single property, all returning the same GeoJSON objects with 2D property geometry and comprehensive attributes about the building, including the relationship to the parcels and buildings:

EndpointParameterUse CaseDocs

/api/cadastral/property

syte parcel or property identifier

When you already have the property/parcel ID

View

/api/cadastral/property-at

Exact geo-coordinate

Find property at specific coordinates

Recommended

View

Example Workflow

Step 1: Geocode the Address

First, convert your address to coordinates. See the geocoding guide for details.

Step 2: Fetch Property Data

Use the property-at API with your coordinates to find the property at that location:

Fetch Property at Coordinates
Step 3: Understanding the Response

The API returns a GeoJSON object that can be directly processed by most mapping and GIS applications. The response contains references to all buildings and parcels:

{ "type": "Feature", "id": "PROPERTY-DENW49AL00009b0D", "geometry": { "type": "MultiPolygon", "coordinates": [[[[7.591943, 51.991067], ...]]] // Property boundaries }, "properties": { "identifier": "PROPERTY-DENW49AL00009b0D", "parcel_identifiers": ["DENW49AL00009b0D"], "building_identifiers": [ "DENW49AL00009XBy", "DENW49AL00009XB8" ], "address": "Fernholzstraße 31 a", "postal_code": "48159", "city": "Münster", "origin": "1984-01-01", "area": 266.87, "built_surface_area": 96.06, "floors": 3, "floorspace": 168.79, "volume": 544.1037, "grz": 0.35992762, "grz1": 0.27904385, "grz2": 0.08088375, "gfz": 0.27904385, "bmz": 2.0388072, "street_access": true, "usage_group": ["Wohnbaufläche"], "energy_demand_label": "E", "heating_system_estimate": "gas", "construction_year_estimate": 1983, // ... 50+ more attributes } }

View the complete list of available attributes in the property-at API documentation.

Visualizing Property Data

You can visualize the GeoJSON response using geojson.io, which will show the property boundaries on a map:

Visualize Property on Map

Next Steps

Once you have the property data:

  • Use the property identifier for subsequent API calls

  • Access building data for the buildings on the property using the building identifiers in the response

  • Fetch additional analysis like building development potential

Additional Resources

  • Fetching Building Data

    Learn how to fetch data for individual buildings

  • Interactive API Documentation

    Explore all property data endpoints

  • Geocoding Guide

    Convert addresses to coordinates