Fix bulk API postal code field; add new TZ API response fields

Author: ianthetechie

.github/workflows/python.yml

@@ -13,7 +13,7 @@ jobs:
     runs-on: ubuntu-latest
     strategy:
       matrix:
-        python-version: ["3.8", "3.9", "3.10", "3.11", "3.12"]
+        python-version: ["3.9", "3.10", "3.11", "3.12", "3.13"]
 
     steps:
       - uses: actions/checkout@v4

.openapi-generator/VERSION

@@ -1 +1 @@
-7.12.0
+7.13.0

docs/BulkRequestQuery.md

@@ -27,7 +27,7 @@ Name | Type | Description | Notes
 **locality** | **str** | The city, village, town, etc. that the place/address is part of. | [optional] 
 **county** | **str** | Administrative divisions between localities and regions. Not commonly used as input to structured geocoding. | [optional] 
 **region** | **str** | Typically the first administrative division within a country. For example, a US state or a Canadian province. | [optional] 
-**postal_code** | **str** | A mail sorting code. | [optional] 
+**postalcode** | **str** | A mail sorting code. | [optional] 
 **country** | **str** | A country code in ISO 3116-1 alpha-2 or alpha-3 format. | [optional] 
 
 ## Example

docs/GeospatialApi.md

@@ -5,7 +5,7 @@ All URIs are relative to *https://api.stadiamaps.com*
 Method | HTTP request | Description
 ------------- | ------------- | -------------
 [**elevation**](GeospatialApi.md#elevation) | **POST** /elevation/v1 | Get the elevation profile along a polyline or at a point.
-[**tz_lookup**](GeospatialApi.md#tz_lookup) | **GET** /tz/lookup/v1 | Get the current time zone information for any point on earth.
+[**tz_lookup**](GeospatialApi.md#tz_lookup) | **GET** /tz/lookup/v1 | Get time zone information for any point on earth.
 
 
 # **elevation**
@@ -92,9 +92,9 @@ Name | Type | Description  | Notes
 # **tz_lookup**
 > TzResponse tz_lookup(lat, lng, timestamp=timestamp)
 
-Get the current time zone information for any point on earth.
+Get time zone information for any point on earth.
 
-The Stadia TZ API provides time zone information, as well as information about any special offset (such as DST) in effect based on the latest IANA TZDB. Note that this API may not be accurate for timestamps in the past and does not claim to report precise nautical times in the open ocean beyond territorial waters.
+Retrieve the time zone identifier, standard UTC offset, special offset (such as DST), and the localized time in several common formats.
 
 ### Example
 
@@ -132,7 +132,7 @@ with stadiamaps.ApiClient(configuration) as api_client:
     timestamp = 56 # int | The UNIX timestamp at which the UTC and DST offsets will be calculated. This defaults to the present time. This endpoint is not necessarily guaranteed to be accurate for timestamps that occurred in the past. Time zone geographic boundaries change over time, so if the point you are querying for was previously in a different time zone, historical results will not be accurate. If, however, the point has been in the same geographic time zone for a very long time (ex: `America/New_York`), the historical data may be accurate for 100+ years in the past (depending on how far back the IANA TZDB rules have been specified). (optional)
 
     try:
-        # Get the current time zone information for any point on earth.
+        # Get time zone information for any point on earth.
         api_response = api_instance.tz_lookup(lat, lng, timestamp=timestamp)
         print("The response of GeospatialApi->tz_lookup:\n")
         pprint(api_response)
@@ -168,7 +168,7 @@ Name | Type | Description  | Notes
 
 | Status code | Description | Response headers |
 |-------------|-------------|------------------|
-**200** | The time zone metadata. |  -  |
+**200** | The time zone information and local time. |  -  |
 **404** | Time zone not found |  -  |
 
 [[Back to top]](#) [[Back to API list]](../README.md#documentation-for-api-endpoints) [[Back to Model list]](../README.md#documentation-for-models) [[Back to README]](../README.md)

docs/SearchStructuredQuery.md

@@ -11,7 +11,7 @@ Name | Type | Description | Notes
 **locality** | **str** | The city, village, town, etc. that the place/address is part of. | [optional] 
 **county** | **str** | Administrative divisions between localities and regions. Not commonly used as input to structured geocoding. | [optional] 
 **region** | **str** | Typically the first administrative division within a country. For example, a US state or a Canadian province. | [optional] 
-**postal_code** | **str** | A mail sorting code. | [optional] 
+**postalcode** | **str** | A mail sorting code. | [optional] 
 **country** | **str** | A country code in ISO 3116-1 alpha-2 or alpha-3 format. | [optional] 
 **focus_point_lat** | **float** | The latitude of the point to focus the search on. This will bias results toward the focus point. Requires `focus.point.lon`. | [optional] 
 **focus_point_lon** | **float** | The longitude of the point to focus the search on. This will bias results toward the focus point. Requires `focus.point.lat`. | [optional] 

docs/TzResponse.md

@@ -8,6 +8,9 @@ Name | Type | Description | Notes
 **tz_id** | **str** | The canonical time zone ID. In the event that multiple time zones could be returned, the first one from the Unicode CLDR timezone.xml is returned. | 
 **base_utc_offset** | **int** | The base offset, in seconds, from UTC that is normally in effect for this time zone. | 
 **dst_offset** | **int** | The special offset, in seconds, from UTC that is in effect for this time zone as of the queried timestamp (defaults to now). If no additional offsets are in effect, this value is zero. This typically reflects Daylight Saving Time, but may indicate other special offsets. To get the total offset in effect, add `dst_offset` and `utc_offset` together. | 
+**timestamp** | **int** | Integer non-leap seconds since January 1, 1970 (UNIX timestamp). If a timestamp is included with the request parameters, it will be echoed here. Otherwise, this will contain the current timestamp. | 
+**local_rfc_2822_timestamp** | **str** | The local time expressed as an RFC 2822 timestamp (e.g. Tue, 1 Jul 2003 10:52:37 +0200). If a timestamp is included in the request, it will be localized here. Otherwise, this will reflect the time of the request. | 
+**local_rfc_3389_timestamp** | **str** | The local time expressed as an RFC 3389 (ISO 8601) timestamp (e.g. 2003-06-01T10:52:37+02:00). If a timestamp is included in the request, it will be localized here. Otherwise, this will reflect the time of the request. | 
 
 ## Example
 

pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "stadiamaps"
-version = "6.2.0"
+version = "6.3.0"
 description = "Stadia Maps Geospatial APIs"
 authors = [
     { name = "Stadia Maps Support", email = "[email protected]" }
@@ -21,9 +21,9 @@ documentation = "https://docs.stadiamaps.com/sdks/python/"
 source = "https://github.com/stadiamaps/stadiamaps-api-py"
 
 [tool.poetry.dependencies]
-python = "^3.8"
+python = "^3.9"
 
-urllib3 = ">= 1.25.3, < 3.0.0"
+urllib3 = ">= 2.1.0, < 3.0.0"
 python-dateutil = ">= 2.8.2"
 pydantic = ">= 2"
 typing-extensions = ">= 4.7.1"

requirements.txt

@@ -1,4 +1,4 @@
-urllib3 >= 1.25.3, < 3.0.0
+urllib3 >= 2.1.0, < 3.0.0
 python_dateutil >= 2.8.2
 pydantic >= 2
 typing-extensions >= 4.7.1

stadiamaps/__init__.py

@@ -7,15 +7,15 @@
 
     The Stadia Maps Geospatial APIs provide you with the data you need to build awesome applications.
 
-    The version of the OpenAPI document: 9.2.1
+    The version of the OpenAPI document: 9.3.0
     Contact: [email protected]
     Generated by OpenAPI Generator (https://openapi-generator.tech)
 
     Do not edit the class manually.
 """  # noqa: E501
 
 
-__version__ = "6.2.0"
+__version__ = "6.3.0"
 
 # import apis into sdk package
 from stadiamaps.api.geocoding_api import GeocodingApi

stadiamaps/api/geocoding_api.py

@@ -5,7 +5,7 @@
 
     The Stadia Maps Geospatial APIs provide you with the data you need to build awesome applications.
 
-    The version of the OpenAPI document: 9.2.1
+    The version of the OpenAPI document: 9.3.0
     Contact: [email protected]
     Generated by OpenAPI Generator (https://openapi-generator.tech)