#mapping
4 APIs con questa etichetta
OpenStreetMap Community API
Live OpenStreetMap Community- und Beitragsdaten als API – die Personen und Bearbeitungen hinter der kollaborativen freien Weltkarte, bereitgestellt von der offiziellen OSM API. Rufen Sie jeden Mapper anhand seiner Benutzer-ID für sein Profil ab (Anzeigename, Kontolaufzeit, gesamte Changesets und GPS-Traces, Rollen), ziehen Sie die letzten Changesets eines Benutzers – jede Bearbeitungsgruppe mit ihrem Kommentar, dem verwendeten Editor und wie viele Kartenfunktionen erstellt, geändert oder gelöscht wurden – oder lesen Sie die offenen und gelösten Kartennotizen, die Community-Feedback-Pins, innerhalb eines geografischen Begrenzungsrahmens. Die OSM-Contributor-und-Edits-Schicht für Kartierungs-, Community- und Dashboard-Apps. Live, kein Key. Abgrenzung zu Geocoding-, Routing- und Kartenkachel-APIs, die lediglich OpenStreetMap-Daten konsumieren – dies ist die OSM-Community- und Bearbeitungsaktivität selbst.
api.oanor.com/openstreetmap-api
Coordinate Systems API
Map projections and coordinate reference systems as an API — the EPSG dataset made queryable. Every CRS, from geographic systems like WGS 84 (the GPS standard, EPSG 4326) to projected ones like Web Mercator (3857), the UTM zones and national grids, has an EPSG code. Search the dataset by name to find the code you need, then resolve any code to its full definition: name, kind (geographic, projected, …), area of use, scope, and — most usefully — the ready-to-paste PROJ.4 string and WKT definition that GIS libraries (GDAL, PROJ, PostGIS, Leaflet, OpenLayers, QGIS, GeoPandas) consume directly. Search comes from the official EPSG Registry maintained by IOGP; the PROJ.4/WKT exports come from epsg.io. A geodesy / coordinate-reference-system resource — distinct from geocoding (addresses to coordinates), geohashing and administrative-boundary APIs. Ideal for GIS, mapping, surveying, remote-sensing and spatial-data applications.
api.oanor.com/epsg-api
geoBoundaries API
Open administrative boundaries as an API, powered by geoBoundaries — the open database of political administrative boundaries built by the William & Mary geoLab. For more than 200 countries and every administrative level — ADM0 (national), ADM1 (states, provinces or regions), ADM2 (counties or districts) and on down to ADM4/ADM5 local units — get the boundary's metadata (official name, the source agency that produced it, the data licence, the year represented, the number of administrative units and the mean vertex count) together with direct download links to the geometry in full-resolution GeoJSON, a simplified GeoJSON, TopoJSON and a ZIP bundle; list every administrative level available for a country with its unit count and download link; and browse the full catalogue of countries that have boundaries. The geometry itself is delivered as standard GeoJSON/TopoJSON files at the returned URLs, ready to drop into Leaflet, Mapbox, QGIS, deck.gl or any GIS pipeline. Ideal for mapping and visualisation, choropleths, spatial joins, geofencing, election and census cartography and location analytics. ISO codes are 3-letter (DEU, USA, BRA); administrative levels are ADM0 to ADM5. Data from the geoBoundaries project (CC-BY 4.0).
api.oanor.com/geoboundaries-api
Elevation API
Terrain elevation in metres above sea level for any coordinate — a single point or a batch of up to 50 points for route and grid profiles. Ideal for hiking and outdoor apps, mapping, drone flight planning, solar siting, flood and line-of-sight analysis.
api.oanor.com/elevation-api