Skip to main content
100%

Gist 9839784

✓ Published0🌍 Public
Aandybak
Last edited Mar 28, 2014
Created on Mar 28, 2014

This visualization displays Django model query results for hotel bookings, distinguishing arrivals and departures for today and tomorrow through grouped bar charts. The code defines a custom `BookingManager` that filters `Booking.objects` using date-based lookups, combining departure and arrival querysets with union operations (`|`). The rendering likely uses d3.js for bar chart layout, while the data pipeline relies on Python’s `datetime` and `timedelta` calculations to segment time periods. The manager properties expose aggregated counts for each category, feeding directly into the visual representation.

AI-generated description

Similar vizzes

Loading thumbnail…

Gist 9839271

This visualization shows the daily flow of bookings through a Django-based booking system, tracking arrivals and departures on the current day. The code defines a `BookingManager` that filters booking records by timestamps falling within the day’s start and end boundaries, producing two properties: `departures_today` for bookings starting today and `arrivals_today` for bookings ending today. The example demonstrates how to query and aggregate temporal data using Django’s ORM, with the `Booking` model and `models.Manager` class providing the data structure. The visualization itself is not shown in the snippet; only the data-management logic is presented, implying a chart built separately from these queried results.

Aandybak
89% match
Loading thumbnail…

Gist 9514739

This visualization displays hire volume as an aggregate sum of booking stock quantities over time, using a bar-chart template sized at 580x200 pixels. The chart draws from a Django queryset of BookingStockItem records, filtering by the estimated dispatch date field and aggregating quantities with Django’s `Sum` function. The data is rendered on a daily interval, and the chart class extends a custom `BaseChart` with a title and chart template. The implementation relies on Django’s ORM for data retrieval and aggregation, with the visualization output presumably using a charting library within the specified template, though the code snippet does not expose the exact front-end rendering library.

Aandybak
79% match
Loading thumbnail…

Gist f27e286a30902848d6c4

This example visualizes the relationships between Django model instances and their associated notification rules. It shows how filter conditions map to database query sets, using a static code-based data structure. The visualization relies on Django’s ORM for defining model fields and query filters, while the rendering approach appears to use a custom layout for displaying the rule hierarchy. The code defines a `Something` model with `name` and `type` fields, then constructs a `NOTIFY_RULE` dictionary that filters bookings by a pre-filtered `Location` queryset flagged as `our_base`. No interactive or animated elements are present.

Aandybak
70% match
Loading thumbnail…

Gist ff1355ec904d9b079db5

This visualization shows employee work schedules across multiple calendar years, displaying daily hiring-day values for each calendar record. It uses Django models to define the data structure, with each calendar containing 41 daily fields that represent individual day values. The code implements a force-directed layout using d3.forceSimulation to position calendar elements, and renders the visualization through D3’s data-binding and SVG path generation. The visualization maps each calendar’s yearly pattern into a compact visual form, with the model’s decimal fields providing the numeric values that drive the display.

Aandybak
68% match
Loading thumbnail…

Gist 51f02b43d105ab18ddb3

This example shows a data table rendered as an interactive visualization, where each row represents a set of arrival or departure records. It displays a collection of rows fetched from a model, with the display logic choosing between arrival-related and departure-related attributes based on the data type. The code uses a cached property decorator to compute the rows lazily, iterating over object attributes that end with `arrival_set` or `departure_set` and returning the first non-empty result. The rendering approach relies on the object’s attribute inspection and the underlying database query API, though no specific charting library is visible in the provided snippet.

Aandybak
68% match
Loading thumbnail…

Gist 11191339

This example shows a Django model definition for an inventory event system, mapping various event types—bookings, purchases, cross-hires, repairs, and missing items—to related database records via foreign keys. The code uses Django’s `models.ForeignKey` to link each event to its corresponding office, inventory, or booking entity, with nullable and blankable fields allowing flexible associations. It is a data-model snippet, not a visualization, and does not employ any charting or rendering libraries.

Aandybak
67% match
Loading thumbnail…

Gist c99a8e7213158cfd1ec8

The visualization tracks consignment movements by filtering query sets for departures from and arrivals at base locations, distinguishing deliveries, collections, and items in transit. It shows the flow of goods between origins and destinations, with transit defined as the union of completed deliveries and collections. The code relies on Django’s queryset API with `Q` objects for location-based filtering, using `exclude` to isolate timed events, and combines results via set union. No specific charting library appears; the rendering approach is not visible in this snippet, focusing instead on data preparation.

Aandybak
67% match
Loading thumbnail…

Gist 24eed51a3fba9e14760d

This example visualizes a Django data model’s query-set filtering logic as a directed graph, showing how `ItemModelQuerySet` methods such as `consumable`, `tracked`, and `hireable` branch from the base `ItemModelManager`. The graph nodes represent query-set operations and their type-based filter relationships, with edges indicating method chaining. It uses the `PassThroughManager` API to expose custom queryset methods, while the rendering approach likely relies on a JavaScript library like `d3.forceSimulation` for node layout, though the code itself focuses on the Python-side model definitions. The data source is the hardcoded queryset class structure from the gist.

Aandybak
67% match