On June 23, 2026, OWB posted a Request for Proposals (RFP) for Vineyard Mapping Services. Below are responses to inquiries received by potential respondents. We will update this with any additional responses as questions arise, up until the submission deadline of July 13 at 8 a.m.
Q: Do you have a rough budget or budget ceiling in mind?
A: We do not have a defined budget or ceiling at this time.
Q: What is your desired update interval for this project?
A: Annual updates are preferred.
Q: For the mapping portion of the project, do you have a preferred platform?
A: We do not have a preferred mapping platform.
Q: Change detection: Would you like to establish a 2026 baseline or incorporate historical imagery?
A: Please establish 2026 as the baseline year. You may include historical change detection as an optional component, along with any associated cost impacts.
Q: When do you hope to have the deliverables completed?
A: Deliverables should be provided as soon as feasible based on the proposed project plan.
Q: Does OWB have any data (spatial or otherwise) ready to be used?
A: OWB has a substantial collection of vineyard coordinates and addresses available for use.
Q: Do you have expectations regarding other ancillary spatial data (e.g., slope, soils, growing degree days, frost hours)?
A: Please include recommended ancillary datasets in your proposal, along with corresponding cost impacts.
Q: Must business licensing be fully complete at proposal submission?
A: Licensing in progress is acceptable at the time of proposal submission.
Q: For each mapped feature, what level of attribution would you like beyond the block geometry itself?
A: Please include the highest feasible level of attribution beyond block geometry. We welcome attribution options such as block delineation, grouping blocks into named vineyards or properties, ownership or winery association, and AVA/county tagging. Please outline the available attribution levels and provide the corresponding cost and effort impacts for each.
Q: For the public web mapping tool, who is expected to host it long-term: OWB infrastructure, oregonwine.org, or a contractor-provided host? Do you want the tool as a standalone site or embeddable within existing OWB web properties?
A: OWB is open to any long‑term hosting arrangement and welcomes your recommendation based on sustainability, performance, and total cost of ownership. The public web mapping tool may be delivered either as a standalone site or as an embeddable component within existing OWB web properties. Please outline the hosting and deployment options and provide associated cost, maintenance, and support implications for each.
Q: Is the vineyard mapping intended to replace, supplement, or feed into the existing census methodology going forward?
A: The vineyard mapping is intended to complement and work in synergy with future census methodologies, enhancing data accuracy.
Q: How will the vineyard mapping be used for marketing purposes?
A: The vineyard mapping will provide interested parties (trade, consumers) the opportunity to develop a deeper understanding of the Oregon winegrowing landscape.
