HALOWERK kartenwerk

Endpoints (20 live)

• POST /v1/ev-charging — Queries OpenStreetMap for charging stations within a radius of a point and returns each with its position, distance, operator, network, connector types with their individual power ratings and socket counts, access restrictions, fee status, opening hours and whether authentication is required. Results are sorted nearest first and can be filtered to a minimum power or a required connector type, which is the question a vehicle actually has. (0.005 USDC on Base)
• POST /v1/air-quality — Returns hourly surface concentrations from the CAMS European air-quality ensemble for a point in the cached DACH and Central Europe area. Available pollutants are CO, NO2, NO, O3, PM2.5, PM10 and SO2. Values come from the nearest 0.1 degree model cell and are labelled as a regional forecast rather than a street-level sensor reading. The local cutout is refreshed independently of paid calls, so Copernicus processing latency is not passed to the caller. (0.005 USDC on Base)
• POST /v1/flood-risk — Returns the pre-fetched GloFAS control forecast at the nearest model cell for a point in Europe. The result reports modelled river discharge, its peak and change over the requested horizon. It is deliberately not presented as a flood probability or warning because those require local river thresholds and the responsible national or regional authority. Every response carries the required CEMS attribution and warranty disclaimer. (0.005 USDC on Base)
• POST /v1/uv-solar — Returns an hourly CAMS forecast for UV Index under predicted clouds, clear-sky UV Index and surface solar irradiance. UV Index is derived from the CAMS biologically effective dose rate with the documented factor 40. Solar irradiance is de-accumulated from successive hourly surface-solar-energy fields. Values represent the nearest 0.4 degree model cell, not an on-site pyranometer. (0.005 USDC on Base)
• POST /v1/airspace-check — Combines coordinate-level current weather from Open-Meteo, nearby worldwide METAR observations and worldwide SIGMETs from the U.S. Aviation Weather Center, official FAA TFR NOTAM polygons with time and vertical limits, plus broader NOTAMs when an authorized official API is configured. FAA TFR coverage is reported separately from full NOTAM coverage. Missing coverage remains unknown rather than falsely clear. (0.008 USDC on Base)
• POST /v1/trip-metrics — Takes an ordered list of positions with timestamps, optionally carrying the battery state of charge at each fix, and returns what a fleet operator asks of a trace: total distance over ground, how much of the elapsed time the vehicle was moving and how much it stood, each individual stop with its position and duration, the mean and maximum speed, and — where a battery capacity is supplied — the energy drawn and the consumption per kilometre. (0.005 USDC on Base)
• POST /v1/flood-exposure — Returns the geometric facts that sit underneath any flood question, each with the source that produced it and the limit that applies to it. The first is height above water: the nearest watercourse or water body mapped in OpenStreetMap is located, the closest point on its geometry is computed rather than the distance to its centre, and the elevation difference between that point and the queried coordinate is read from Copernicus DEM GLO-30. (0.006 USDC on Base)
• POST /v1/tides — Returns tide predictions for a NOAA CO-OPS station: every high and low water in the window with its time and height above datum, the range between them, and which extreme comes next with the time remaining. Where the station also measures, the observed water level is fetched and compared with the prediction — wind and air pressure routinely push the real level away from the astronomical forecast, and that residual is the figure that matters for anyone near a limit, so it is returned rather than… (0.005 USDC on Base)
• POST /v1/port-congestion — Reports what actually moves through a European port and how that developed, from the quarterly Eurostat port statistics covering 837 ports, addressable by name or by UN/LOCODE. Throughput is given per quarter split into inbound and outbound, with the imbalance between the two, the change against the same quarter a year earlier, and the direction over the whole observed window. (0.005 USDC on Base)
• POST /v1/restricted-route — Collects the physical and legal restrictions recorded in OpenStreetMap within a corridor around the straight line between two points, or around a single point, and decides for each one whether it stops the vehicle described in the request. The work is in reading the values. (0.006 USDC on Base)
• POST /v1/parking-rules — Returns parking areas, street-side parking, garages and multi-storey car parks near a coordinate, each with what governs whether you may leave a vehicle there: access class, whether a fee applies and what it is where recorded, total and disabled-designated capacity, maximum stay, height restriction for covered facilities, surface, and whether it is a park-and-ride. (0.005 USDC on Base)
• POST /v1/last-mile-access — Examines the ways and barrier objects around a destination for anything that stops a vehicle getting there. Barriers such as gates, bollards, lift gates and cycle barriers are returned with their position, distance and whether they are locked. Ways carrying access tags are returned with the restriction and who it applies to, and physical limits — maximum height, weight, width and length — are compared against the vehicle dimensions you supply, so the answer is specific rather than a list to… (0.005 USDC on Base)
• POST /v1/bicycle-infrastructure — Measures how well an area is equipped for cycling from four things that can actually be counted. Separation from motor traffic is the heaviest factor and is ranked explicitly: a physically separate track, a painted lane on the carriageway and a shared bus lane are three different levels of protection, the ranking used is returned with the result, and roads carrying cycle traffic with no provision at all are counted as the fourth level. (0.006 USDC on Base)
• POST /v1/parcel-locker — Returns parcel lockers, packstations and staffed pickup points around a point, each with operator, brand, opening hours as recorded, access class, whether it is indoors, and the distance. The distinction the response insists on is between an automated locker and a staffed shop: in OpenStreetMap both frequently carry the same brand tag, and treating them as one thing promises round-the-clock collection and delivers shop hours. (0.004 USDC on Base)
• POST /v1/public-toilets — Returns public toilets within a radius of a coordinate, sorted by distance, each with what decides whether it is usable: whether a fee applies and how much, the opening hours in raw OpenStreetMap syntax, wheelchair accessibility, whether a baby changing table is present, whether it is unisex or separated, whether drinking water is available, and the operator. (0.004 USDC on Base)
• POST /v1/emergency-coverage — For a location, returns per facility type the nearest one with its distance and details, the count within the radius, and the density per square kilometre. Hospitals are additionally reported with whether they have an emergency department where that is tagged, since a hospital without one does not answer the question being asked. Defibrillators come with their access class and indoor flag, because one locked inside a closed office building at night is not available. (0.005 USDC on Base)
• POST /v1/quiet-site — Builds a noise context for a site from what surrounds it. Roads within the radius are weighted by class, by recorded speed limit and lane count where present, and by distance with a falloff, because a motorway at eight hundred metres and a residential street at twenty are different problems. Railways are counted separately with their usage class, since freight lines at night dominate what people actually complain about. (0.005 USDC on Base)
• POST /v1/emission-zone — Looks for low-emission zones, congestion charge areas and access-restricted areas around a coordinate and reports each with its type, the vehicle classes it restricts where tagged, the operator, and the distance from your point. Zones are matched by the tags actually used for this in OpenStreetMap, including boundary relations and landuse areas carrying emission tags, and the response lists which tag produced each hit so a questionable match can be judged. (0.005 USDC on Base)
• POST /v1/accessible-venue — Searches OpenStreetMap for venues of a chosen kind near a coordinate and reports accessibility as the separate facts it actually consists of: step-free entrance, accessible toilet, lift, designated parking, plus entrance width and step count where recorded. (0.005 USDC on Base)
• POST /v1/elevation-profile — Takes a list of coordinates and returns the elevation at each, the distance and gradient between consecutive points, total ascent and descent, the steepest ramp with the segment it belongs to, and the mean gradient over the whole line. An optional resample interval inserts intermediate points along the great circle between the given ones, which is what makes a steepest-ramp figure meaningful on a route described by a handful of corners. (0.005 USDC on Base)