Create a new location with automatic elevation and timezone enrichment
name is required. latitude and longitude are expected for most workflows; the deprecated lat/lng aliases are still accepted but should not be used for new integrations.elevation is omitted, it is auto-fetched from an elevation service based on coordinates.timeZone and timeZoneName) is always auto-detected from coordinates in the response.weatherData object in the request body to create and link a weather data record in a single call. This follows the legacy creation pattern — for more control, create weather data separately via POST /weatherdata and associate it by locationId.streetAddress, ashrae (ASHRAE climate zone index), farShading (horizon profile), and soiling (monthly soiling factors).GET /locations/{location_id} to retrieve the created location.POST /weatherdata or POST /weatherdata/fetch to create weather data independently.