Geo Calculator offers four endpoints to help you work with coordinates:
Some Common Use Cases:
Mapping and Navigation: The API enables developers to calculate accurate geo coordinates, allowing for precise mapping and navigation applications. Results can be used to find locations, plan routes, and real-time directions.
Geofencing Applications: With the API's geo fence functionality, developers can check virtual boundaries around specific locations. This is useful for applications that require monitoring and triggering actions based on entering or exiting these boundaries, such as geofencing for asset tracking, location-based notifications, or safety alerts.
Weather Applications: By utilizing the accurate geo coordinates provided by the API, developers can enhance weather forecasting applications. Real-time location data enables more precise and localized weather predictions, improving the user experience.
Astronomy and Celestial Events: The API's information about the sky, sun, moon, and eclipses is valuable for applications related to astronomy, stargazing, photography, and outdoor activities. Users can access data such as sunrise and sunset times, moon phases, moonrise and moonset times, and eclipse predictions.
Photography and Filmmaking: Photographers and filmmakers can benefit from the API's features when planning shoots. They can determine the ideal times for golden hour or blue hour, plan moonlit or starry sky shots, or even schedule specific eclipse events.
Outdoor Recreation and Adventure: Outdoor enthusiasts can use the API to check sunrise and sunset times for planning hikes, camping trips, or outdoor activities. Additionally, moonrise and moonset times can assist with moonlit hikes or moonlight photography.
Event Planning: Event organizers can incorporate the API to determine sunrise and sunset times, allowing them to schedule outdoor events at the optimal hours. They can also consider moon phases and other celestial events to enhance the overall experience
Convert the list of geo coordinates to a standard format - (latlon | utm | mgrs | ecef | epsg3857 | georef | cartesian)
Convert - Endpoint Features
Object | Description |
---|---|
Request Body |
[Required] Json |
{"coordinates":"N 39ΒΊ 48' 6.368\" W 86ΒΊ 9' 27.968\""}
curl --location --request POST 'https://zylalabs.com/api/2142/geo+calculator+api/1942/convert' --header 'Authorization: Bearer YOUR_API_KEY'
--data-raw '{
"coordinates": "39.801769 -86.157769",
"system": "latlon",
"format": "seconds"
}'
Calculate sun, moon, eclipse and sky information for the date and location.
Sky - Endpoint Features
Object | Description |
---|---|
Request Body |
[Required] Json |
{"sun":{"isUp":true,"set":"2023-06-17T01:15:59","rise":"2023-06-17T10:17:17","noon":"2023-06-17T17:46:49","altitude":48.81284808403095,"azimuth":99.6567012311506,"dawn":"2023-06-17T09:44:35","dusk":"2023-06-17T01:48:40","lastEclipse":{"hasEclipseData":true,"date":"2021-06-10T00:00:00","type":0,"partialEclispeBegin":"2021-06-10T10:19:00","aorTEclipseBegin":"0001-01-01T00:00:00","maximumEclipse":"2021-06-10T10:19:00","aorTEclipseEnd":"0001-01-01T00:00:00","partialEclispeEnd":"2021-06-10T10:35:25","aorTDuration":"00:00:00"},"nextEclipse":{"hasEclipseData":true,"date":"2023-10-14T00:00:00","type":0,"partialEclispeBegin":"2023-10-14T15:39:28","aorTEclipseBegin":"0001-01-01T00:00:00","maximumEclipse":"2023-10-14T17:02:09","aorTEclipseEnd":"0001-01-01T00:00:00","partialEclispeEnd":"2023-10-14T18:28:39","aorTDuration":"00:00:00"},"rightAscension":85.82780110902979,"declination":23.383002369277698},"moon":{"isUp":true,"set":"2023-06-17T00:16:53.155Z","rise":"2023-06-17T09:27:25.111Z","name":null,"sign":"Gemini","altitude":56.23932723895527,"azimuth":101.71183722382726,"distance":395088331.44547164,"illumination":{"fraction":0.004394041226453371,"angle":1.9970019788686353,"phase":0.9788845298393997,"phaseName":"Waning Crescent","phaseNameEnum":7},"bearing":0.0,"lastEclipse":{"hasEclipseData":true,"date":"2022-11-08T00:00:00","type":2,"penumbralEclipseBegin":"2022-11-08T08:02:00","partialEclispeBegin":"2022-11-08T09:09:00","totalEclipseBegin":"2022-11-08T10:17:00","midEclipse":"2022-11-08T10:59:00","totalEclipseEnd":"2022-11-08T11:42:00","partialEclispeEnd":"2022-11-08T12:49:00","penumbralEclispeEnd":"2022-11-08T13:56:00"},"nextEclipse":{"hasEclipseData":true,"date":"2024-03-25T00:00:00","type":0,"penumbralEclipseBegin":"2024-03-25T04:53:00","partialEclispeBegin":"0001-01-01T00:00:00","totalEclipseBegin":"0001-01-01T00:00:00","midEclipse":"2024-03-25T07:13:00","totalEclipseEnd":"0001-01-01T00:00:00","partialEclispeEnd":"0001-01-01T00:00:00","penumbralEclispeEnd":"2024-03-25T09:32:00"},"rightAscension":78.28730335981335,"declination":26.7228180688204},"event":{"zodiacSign":"Gemini","spring":"2023-03-20T21:25:53","summer":"2023-06-21T14:58:50","fall":"2023-09-23T06:51:26","winter":"2023-12-22T03:28:51","nextPerigee":"2023-07-04T22:29:26","lastPerigee":"2023-06-06T23:08:44","nextApogee":"2023-06-22T18:31:35","lastApogee":"2023-05-26T01:39:50"}}
curl --location --request POST 'https://zylalabs.com/api/2142/geo+calculator+api/1943/sky' --header 'Authorization: Bearer YOUR_API_KEY'
--data-raw '{
"date": "2023-06-17T14:47:30.9231894Z",
"coordinate": "39.801769 -86.157769"
}'
Check if a list of coordinates are inside of a fence of coordinates.
Fence - Endpoint Features
Object | Description |
---|---|
Request Body |
[Required] Json |
{"insides":[true],"distances":[13438.80200086406]}
curl --location --request POST 'https://zylalabs.com/api/2142/geo+calculator+api/1944/fence' --header 'Authorization: Bearer YOUR_API_KEY'
--data-raw '{
"fenceCoordinates": [
"39.801769 -86.157769",
"40.801769 -86.157769",
"40.801769 -87.157769",
"39.801769 -87.157769",
"39.801769 -86.157769"
],
"checkCoordinates": [
"40 -87"
]
}'
Calculate the distance between two geo coordinates.
Distance - Endpoint Features
Object | Description |
---|---|
Request Body |
[Required] Json |
{"meters":140596.58853321144,"bearing":141.94878033913545}
curl --location --request POST 'https://zylalabs.com/api/2142/geo+calculator+api/1945/distance' --header 'Authorization: Bearer YOUR_API_KEY'
--data-raw '{
"coordinate1": "39.801769 -86.157769",
"coordinate2": "38.801769 -85.157769",
"useEllipse": false
}'
Header | Description |
---|---|
Authorization
|
[Required] Should be Bearer access_key . See "Your API Access Key" above when you are subscribed. |
No long term commitments. One click upgrade/downgrade or cancellation. No questions asked.
Calculate sun, moon, eclipse and sky information for the date and location.
Calculate the distance between two geo coordinates.
Check if a list of coordinates are inside of a fence of coordinates.
Convert a list of geo coordinates to a standard format - (latlon | utm | mgrs | ecef | epsg3857 | georef | cartesian)
Mapping and Navigation: The API enables developers to calculate accurate geo coordinates, allowing for precise mapping and navigation applications. Results can be used to find locations, plan routes, and real-time directions.
Zyla API Hub is like a big store for APIs, where you can find thousands of them all in one place. We also offer dedicated support and real-time monitoring of all APIs. Once you sign up, you can pick and choose which APIs you want to use. Just remember, each API needs its own subscription. But if you subscribe to multiple ones, you'll use the same key for all of them, making things easier for you.
Prices are listed in USD (United States Dollar), EUR (Euro), CAD (Canadian Dollar), AUD (Australian Dollar), and GBP (British Pound). We accept all major debit and credit cards. Our payment system uses the latest security technology and is powered by Stripe, one of the worldβs most reliable payment companies. If you have any trouble paying by card, just contact us at [email protected]
Additionally, if you already have an active subscription in any of these currencies (USD, EUR, CAD, AUD, GBP), that currency will remain for subsequent subscriptions. You can change the currency at any time as long as you don't have any active subscriptions.
The local currency shown on the pricing page is based on the country of your IP address and is provided for reference only. The actual prices are in USD (United States Dollar). When you make a payment, the charge will appear on your card statement in USD, even if you see the equivalent amount in your local currency on our website. This means you cannot pay directly with your local currency.
Occasionally, a bank may decline the charge due to its fraud protection settings. We suggest reaching out to your bank initially to check if they are blocking our charges. Also, you can access the Billing Portal and change the card associated to make the payment. If these does not work and you need further assistance, please contact our team at [email protected]
Prices are determined by a recurring monthly or yearly subscription, depending on the chosen plan.
API calls are deducted from your plan based on successful requests. Each plan comes with a specific number of calls that you can make per month. Only successful calls, indicated by a Status 200 response, will be counted against your total. This ensures that failed or incomplete requests do not impact your monthly quota.
Zyla API Hub works on a recurring monthly subscription system. Your billing cycle will start the day you purchase one of the paid plans, and it will renew the same day of the next month. So be aware to cancel your subscription beforehand if you want to avoid future charges.
To upgrade your current subscription plan, simply go to the pricing page of the API and select the plan you want to upgrade to. The upgrade will be instant, allowing you to immediately enjoy the features of the new plan. Please note that any remaining calls from your previous plan will not be carried over to the new plan, so be aware of this when upgrading. You will be charged the full amount of the new plan.
To check how many API calls you have left for the current month, look at the βX-Zyla-API-Calls-Monthly-Remainingβ header. For example, if your plan allows 1000 requests per month and you've used 100, this header will show 900.
To see the maximum number of API requests your plan allows, check the βX-Zyla-RateLimit-Limitβ header. For instance, if your plan includes 1000 requests per month, this header will display 1000.
The βX-Zyla-RateLimit-Resetβ header shows the number of seconds until your rate limit resets. This tells you when your request count will start fresh. For example, if it displays 3600, it means 3600 seconds are left until the limit resets.
Yes, you can cancel your plan anytime by going to your account and selecting the cancellation option on the Billing page. Please note that upgrades, downgrades, and cancellations take effect immediately. Additionally, upon cancellation, you will no longer have access to the service, even if you have remaining calls left in your quota.
You can contact us through our chat channel to receive immediate assistance. We are always online from 8 am to 5 pm (EST). If you reach us after that time, we will get back to you as soon as possible. Additionally, you can contact us via email at [email protected]
To let you experience our APIs without any commitment, we offer a 7-day free trial that allows you to make API calls at no cost during this period. Please note that you can only use this trial once, so make sure to use it with the API that interests you the most. Most of our APIs provide a free trial, but some may not support it.
After 7 days, you will be charged the full amount for the plan you were subscribed to during the trial. Therefore, itβs important to cancel before the trial period ends. Refund requests for forgetting to cancel on time are not accepted.
When you subscribe to an API trial, you can make only 25% of the calls allowed by that plan. For example, if the API plan offers 1000 calls, you can make only 250 during the trial. To access the full number of calls offered by the plan, you will need to subscribe to the full plan.
Service Level:
33%
Response Time:
411ms
Service Level:
100%
Response Time:
741ms
Service Level:
50%
Response Time:
2,089ms
Service Level:
100%
Response Time:
2,088ms
Service Level:
100%
Response Time:
570ms
Service Level:
100%
Response Time:
1,191ms
Service Level:
100%
Response Time:
821ms
Service Level:
100%
Response Time:
760ms
Service Level:
100%
Response Time:
286ms
Service Level:
100%
Response Time:
115ms
Service Level:
100%
Response Time:
697ms
Service Level:
100%
Response Time:
1,551ms
Service Level:
100%
Response Time:
601ms
Service Level:
100%
Response Time:
849ms
Service Level:
100%
Response Time:
527ms
Service Level:
100%
Response Time:
111ms
Service Level:
89%
Response Time:
979ms