Libraries tagged by map tools

A CakePHP plugin around geocoding tools and helpers.

Go to Download

Course Hero's Assetic tools bundle

Go to Download

A CakePHP plugin around geocoding tools and helpers.

Go to Download

A collection of complete tools for working with PHP arrays.

Go to Download

A PHP tool to map your classes and methods, so you can execute them from the comfort of your command line interface.

Go to Download

An immersive 3D visualization tool for Laravel applications that maps architecture, dependencies, and test coverage in real-time.

Go to Download

One checkout flow for both fulfillment modes: Pickup + Delivery, with date + time slot/window selection. Availability is always real: location-based hours, blackout dates, cutoff times, and lead-time rules drive what customers can pick. Delivery includes service-area validation plus distance-based fees (Google Maps support + fallback distance calculation). Flexible delivery pricing: flat rate, per-km, or tiered distance bands. One operations layer for office + kitchen + drivers: every order becomes a trackable fulfillment task. One status lifecycle from order creation to ready / out for delivery / completed, with rescheduling tools when plans change. Built for multi-location businesses that need schedule accuracy, operational control, and clean execution.

Go to Download

Unified store location manager with Google Maps integration Combined pickup/delivery hours, blackout calendar, and capacity rules REST APIs powering pickup, delivery, and fulfillment workflows Admin geocode tools, inline hours editor, and ACL-secured menus

Go to Download

Command-line tool to check for ambiguous class names with Composer's generated class map.

Go to Download

The Engine API is an HTTP API served by Docker Engine. It is the API the Docker client uses to communicate with the Engine, so everything the Docker client can do can be done with the API. Most of the client's commands map directly to API endpoints (e.g. `docker ps` is `GET /containers/json`). The notable exception is running containers, which consists of several API calls. # Errors The API uses standard HTTP status codes to indicate the success or failure of the API call. The body of the response will be JSON in the following format: ``` { "message": "page not found" } ``` # Versioning The API is usually changed in each release, so API calls are versioned to ensure that clients don't break. To lock to a specific version of the API, you prefix the URL with its version, for example, call `/v1.30/info` to use the v1.30 version of the `/info` endpoint. If the API version specified in the URL is not supported by the daemon, a HTTP `400 Bad Request` error message is returned. If you omit the version-prefix, the current version of the API (v1.43) is used. For example, calling `/info` is the same as calling `/v1.43/info`. Using the API without a version-prefix is deprecated and will be removed in a future release. Engine releases in the near future should support this version of the API, so your client will continue to work even if it is talking to a newer Engine. The API uses an open schema model, which means server may add extra properties to responses. Likewise, the server will ignore any extra query parameters and request body properties. When you write clients, you need to ignore additional properties in responses to ensure they do not break when talking to newer daemons. # Authentication Authentication for registries is handled client side. The client has to send authentication details to various endpoints that need to communicate with registries, such as `POST /images/(name)/push`. These are sent as `X-Registry-Auth` header as a [base64url encoded](https://tools.ietf.org/html/rfc4648#section-5) (JSON) string with the following structure: ``` { "username": "string", "password": "string", "email": "string", "serveraddress": "string" } ``` The `serveraddress` is a domain/IP without a protocol. Throughout this structure, double quotes are required. If you have already got an identity token from the [`/auth` endpoint](#operation/SystemAuth), you can just pass this instead of credentials: ``` { "identitytoken": "9cbaf023786cd7..." } ```

Go to Download

The Engine API is an HTTP API served by Docker Engine. It is the API the Docker client uses to communicate with the Engine, so everything the Docker client can do can be done with the API. Most of the client's commands map directly to API endpoints (e.g. `docker ps` is `GET /containers/json`). The notable exception is running containers, which consists of several API calls. # Errors The API uses standard HTTP status codes to indicate the success or failure of the API call. The body of the response will be JSON in the following format: ``` { "message": "page not found" } ``` # Versioning The API is usually changed in each release, so API calls are versioned to ensure that clients don't break. To lock to a specific version of the API, you prefix the URL with its version, for example, call `/v1.30/info` to use the v1.30 version of the `/info` endpoint. If the API version specified in the URL is not supported by the daemon, a HTTP `400 Bad Request` error message is returned. If you omit the version-prefix, the current version of the API (v1.41) is used. For example, calling `/info` is the same as calling `/v1.41/info`. Using the API without a version-prefix is deprecated and will be removed in a future release. Engine releases in the near future should support this version of the API, so your client will continue to work even if it is talking to a newer Engine. The API uses an open schema model, which means server may add extra properties to responses. Likewise, the server will ignore any extra query parameters and request body properties. When you write clients, you need to ignore additional properties in responses to ensure they do not break when talking to newer daemons. # Authentication Authentication for registries is handled client side. The client has to send authentication details to various endpoints that need to communicate with registries, such as `POST /images/(name)/push`. These are sent as `X-Registry-Auth` header as a [base64url encoded](https://tools.ietf.org/html/rfc4648#section-5) (JSON) string with the following structure: ``` { "username": "string", "password": "string", "email": "string", "serveraddress": "string" } ``` The `serveraddress` is a domain/IP without a protocol. Throughout this structure, double quotes are required. If you have already got an identity token from the [`/auth` endpoint](#operation/SystemAuth), you can just pass this instead of credentials: ``` { "identitytoken": "9cbaf023786cd7..." } ```

Go to Download

Laravel CLI tool that visualizes database structure as a map.

Go to Download

30+ ready-to-use content elements for TYPO3 14 LTS: sliders, galleries, accordions, tabs, timelines, pricing tables, testimonials, team, maps and more. Part of the Connetation TYPO3 Web Toolkit (T3WTK). Live demo: https://demosite.connetation.at

Go to Download

Contao Content Element: Karte (OpenStreetMap/Leaflet, OpenFreeMap oder Google Maps) mit mehreren Markern, Tooltips und Routing-Link zu Google/Apple Maps

Go to Download

A toolkit for working with maps.witnessdata.org inside Filament

Go to Download