Using ArcGIS Pro to create a site layout and then manage vendors at an urban farmers' market.
The City of Windsor already has a perfectly functioning market on Pelissier St, so I'll use that as design inspiration of a new, but totally fictitious, GIS powered market located along Pitt Street West.
The workflow process consists of using ArcGIS Pro (vers. 2.7.3) to create vendor spaces, then build a data attribute table in a geodatabase to manage those vending areas, and finally use SQL inspired queries to do some basic operational management.
To start, we'd need a little bit of external data to use as a framework to build our market on. The Street Centerline shapefile from the City's Open Data Catalogue will work perfectly for that.
First I'll focus on creating the actual vendor spaces on the map. Geographically, these will be two dimensional areas that are constructed from polygons and should measure 12ft wide by 12ft deep. The market will need a central path for customers to walk along – and that'll be constructed using a buffer on the street centreline of 4 feet to the North as well as the South, for a total path width of 8 feet.
The graphic below shows the feature class result. The demonstration market is 360 feet long, and is split into individual vendor polygons using the ArcGIS Divide Polygon editing function, which contains methods for dividing a polygon feature into multiple features that have proportional or equal areas, or equal widths, and in this case 12 feet for each vendor space.
Two administrative areas (shown below in blue) will be set up at the market entryways on Ferry Street and Ouellete Ave to allow staff to manage pedestrian traffic and provide customer support. Social distancing requirements means that every other booth will be unoccupied for the time being, and I'll give those spaces a hatched line symbology. That leaves 28 vending spaces in green that are open and available to our local vendors.
Now that each vendor space is created, and relates to a specific geographic location on the map, I'll add some details to each square in their respective attribute table. These details will include: the Vendor name; type of products they are offering; how long they have rented the space for; and if they requested hydro, etc.
|Type of Vendor||Rental Duration||Hydro Requested?||Fee Paid?|
|Prepared Food||Part Season||No||No|
Now I can explore the market and get specifics on each vendor location, what they sell, and what kind of market day support they will require. An example attribute table below shows the details about our friends South Taco in Space #3:
With the virtual construction and data entry complete, now I can use GIS to help manage the market. First up is an admin task of reaching out to vendors who haven't yet paid the rental fee. A 'Select By Attributes' action can be used to construct a SQL style query on the data table, and that will make a quick list of the 4 vendors we need to see in order to complete payment. In this case we'd be looking for the fee paid is $0, or WHERE Fee = $0.
A map and table can also be created for facility staff to direct their work in laying out hydro power lines to the 15 individual spaces who requested access to power. This time I'll use WHERE Hydro = 'Yes' to locate those spaces. The spaces that are true in this query are highlighted in cyan on both the map and attribute table.
Labeling on the map can be customized to show the Vendor Name, and then on a new line, their type of product enclosed in parenthesis using the Arcade Expression Language code of:
$feature.VendorName + TextFormatting.NewLine + "(" + $feature.VendorType + ")"
Lastly, I'll publish the map to ArcGIS Online so that it's available to all staff on their mobile devices during the event. It can also be accessed by customers who may want to find specific vendors or product categories.
This example below is a fully interactive map that market staff can zoom in/out, pan, and click to see the details of each vendor. This map could be made available to reference where vendors belong on Market Day and their hydro needs, for example.