Datasets

Filters
wms Espoon kaupungin kaupunkiympäristön toimiala

17 datasets found

    Data related to Espoo’s nature and environment can be accessed through the city’s WFS and WMS geographic data interfaces. The datasets include nature reserves, traditional landscapes, nature trails and valuable...

    Cities
    WFS
    WMS

    This dataset provides borders of real estates owned by city of Espoo. It also contains real estates that have been granted or rented internally. The dataset is provided by the Public Works Department of Espoo....

    Cities
    WMS

    This dataset provides borders of real estates in Espoo. It is updated on a weekly basis. The dataset is provided by the Public Works Department of Espoo. API addresses: WMS:...

    Cities
    WFS
    WMS

    This dataset provides the orthophotographs of Espoo and Kauniainen from 1950, 1969, 1976, 1996 2001, 2005, 2007, 2009, 2011, 2013, 2015, 2017, 2019, 2021 and 2023. API address: WMS:...

    Cities
    WMS

    The Espoo base map, which is the same data that is also used in the up-to-date 3D city model, shows all the important elements of design and construction, such as buildings, transport routes, terrain patterns,...

    Cities
    WMS

    The confirmed town plan of Espoo includes the valid plan symbol at each location. However, the exact meanings of the plan symbols vary between town plans. Therefore, the reader of the confirmed town plan must find out...

    Cities
    WMS
    GEOTIFF

    The weekly updated accurate water areas in color. Together with wide streams and ditches. Pier structures are visible. The recommended scale is 1:1000-1:10000. Coordinate systems: Maintained in ETRS-GK25 (EPSG:3879)...

    Cities
    WFS
    WMS

    Georeferenced printed map. 1:20 000. The map is based on aerial photographs from 1956. API address: WMS: https://kartat.espoo.fi/teklaogcweb/wms.ashx API description (in Finnish):...

    Cities
    WMS

    This dataset provides the plan maps of the City of Espoo. The weekly updated Index Map of detail plans in a simple format that can be opened with several GIS programs. In addition, an Index Map is provided of detail...

    Cities
    WFS
    WMS

    Materials related to Espoo's traffic routes can be accessed through the city's WFS and WMS spatial data interfaces. At the Liikenne -layer, the edges of the streets are visible, while at the GIS: Keskilinjat -layer,...

    Cities
    WFS
    WMS

    The guide map of Espoo and Kauniainen is a dataset with a fairly generalised position accuracy, which is made to give a wide overview of the entire cities and to guide people to a specific address. The optimum...

    Cities
    WMS

    The address map of Espoo is a location-specific terrain map. It shows property boundaries, addresses, buildings, water bodies and the largest forms of terrain. NOTE: The data can be opened for example with QGIS...

    Cities
    WMS

    Guide Map of Espoo 1976. Georeferenced printed map. 1:20 000 scale. API address: WMS: https://kartat.espoo.fi/teklaogcweb/wms.ashx API description (in Finnish):...

    Cities
    WMS

    Guide Map of Espoo 1973. Georeferenced printed map. 1:20 000. API address: WMS: https://kartat.espoo.fi/teklaogcweb/wms.ashx API description (in Finnish):...

    Cities
    WMS

    The weekly updated land-use map describes the land use according to the detail plans. The map is colored. The graphic layer is suitable for presentation in scales 1:1000 to 1:4000. Coordinate systems: Maintained in...

    Cities
    WFS
    WMS

    This dataset provides information on buildings as polygons in Espoo. Weekly updating, position-accurate buildings are available in the WMS and WFS interfaces. In the data available in the WMS interface, the area...

    Cities
    WFS
    WMS

    The geoenergy map portrays the suitability of soil and bedrock for geoenergy production. The map is based on soil maps of the City of Espoo, soil and bedrock data of the Geological Survey of Finland, map data of the...

    Cities
    WMS
    GEOTIFF
You can also access this registry using the API (see API Docs).