Organizations often ask for a per-log price before the source material and required deliverables have been defined. In practice, well log digitization cost depends on what must be recovered, the condition of the records and how the resulting data will be used. A clear quotation connects those requirements to a measurable scope.<\/p>\n\n\n\n
The same archive can support very different projects. One team may need a single curve across a target formation. Another may need every usable curve, associated headers and consistent filenames for hundreds of wells. Both are digitization projects, but their budgets and schedules should reflect different workloads. This guide explains how to plan that scope, compare estimates and establish practical delivery expectations.<\/p>\n\n\n\n
Before counting pages, describe the decision the digitized data will support. Are you preparing a correlation study, recovering historical measurements for interpretation or making an archive reusable? Identify the wells, logging runs, curves and depth intervals necessary for that purpose. This prevents a quotation from including unnecessary work or omitting information that later becomes essential.<\/p>\n\n\n\n
Also distinguish scanning from digitization. A scan preserves the appearance of a paper record. Curve digitization converts the plotted information into numerical values that software can use. An attractive PDF therefore does not provide the same deliverable as a structured curve dataset. If paper scanning is needed, identify it separately and confirm who will prepare the source images.<\/p>\n\n\n\n
GAEA\u2019s well log digitization service page<\/a> lists a preliminary rate as low as $0.60 per 100 curve feet. Curve feet are calculated from the number of curves and the digitized depth range. The estimator is not a binding quote; minimum charges, setup, difficult sources, metadata entry or special handling may affect the final amount.<\/p>\n\n\n\n For an illustrative project with three curves over 2,000 feet, the quantity is 6,000 curve feet. Applying that preliminary rate gives 6,000 \u00f7 100 \u00d7 $0.60 = $36. This arithmetic is a planning example, not an offer to complete that project for $36. Ask for confirmation of currency, applicable taxes, inclusions and the final project price before approving work.<\/p>\n\n\n\n Calculate different intervals separately. If one curve covers 2,000 feet and another covers only 800 feet, their combined scope is 2,800 curve feet. Counting both across the full interval would overstate the quantity. Similarly, do not enter metre-based depths into a feet-based estimate without conversion. Keep the quantity calculation with the inventory so another reviewer can understand and reproduce it.<\/p>\n\n\n\n Clean, legible images reduce uncertainty. Faded lines, skewed scans, compression artifacts, folds and handwritten corrections make it harder to distinguish the original trace. A low price calculated from length alone cannot describe that extra effort. Two wells with identical curve-foot quantities may require different amounts of preparation and review.<\/p>\n\n\n\n Source completeness matters as much as sharpness. A cropped trace may look clear while excluding the scale needed to interpret it. Missing headers can leave uncertainty about the well or logging run. Before commissioning rescanning, ask which records need improvement and why. Targeted rescanning of poor originals can be more useful than increasing resolution across an entire archive indiscriminately.<\/p>\n\n\n\n Select quotation samples that represent the collection honestly. Include ordinary records and difficult examples, rather than choosing only the cleanest page. For a mixed archive, group sources by age, format or condition and provide an example from each group. That helps reveal whether one production assumption can reasonably apply to the whole collection.<\/p>\n\n\n\n A single continuous trace is easier to specify than several overlapping traces with changing scales. Identify curve names where known, and point out intervals containing breaks, repeat sections or annotations. State whether separate logging runs should remain separate. Combining records without a defined rule can create an apparently continuous dataset that hides important differences in the source.<\/p>\n\n\n\n The requested sampling interval is another specification to settle early. More closely spaced output values may support a particular import workflow, but they do not create detail that the original image cannot resolve. Choose an interval appropriate to the source and intended analysis. Ask how gaps and unreadable sections will be represented, rather than assuming every requested depth will contain a valid measurement.<\/p>\n\n\n\n Keep digitization distinct from geological interpretation. Recovering a plotted measurement is different from assigning formation tops, reconciling conflicting records or judging which historical run is technically preferable. If those additional tasks are required, describe them separately so responsibilities, methods and charges can be discussed explicitly.<\/p>\n\n\n\n A numerical curve without a reliable well identifier can create substantial work after delivery. Decide which header fields are essential and which are optional. Consider identifiers, run references and any project-specific naming rules. If coordinates or elevations are required, identify their source and reference system; do not assume an unlabeled number can be safely standardized.<\/p>\n\n\n\n GAEA describes its standard geophysical digitization output as LAS 3.0, with scoped curves and available header information. Confirm compatibility with your receiving software. Requests for spreadsheets, database loading, other formats or additional interpretation should be agreed separately rather than assumed to be included. See the service specifications<\/a> for current details.<\/p>\n\n\n\n Provide a sample naming convention and identify any mandatory fields before production. For example, a project may require filenames based on a stable well identifier and run date rather than the scanned page name. Test a representative output in the receiving application early. A readable file and a successful import are related checks, but they answer different questions.<\/p>\n\n\n\n A useful quote should let both parties recognize when the agreed work is complete. Request enough detail to compare scope without turning the document into an unnecessarily complicated specification. The following checklist provides a practical starting point:<\/p>\n\n\n\n Ask how additions will be managed. Discovering more wells, requesting extra curves or changing the sampling specification can alter the workload. A simple written change process protects the budget and avoids confusion over which version of the scope applies. It also helps distinguish correction of an agreed deliverable from a new request.<\/p>\n\n\n\n GAEA notes that small projects with clear, consistent sources may take hours or days, while larger or more difficult collections require scheduling after inspection. Treat this as general guidance, not a guaranteed completion window. Confirm timing through the project quotation.<\/p>\n\n\n\n For planning purposes, separate production time from the complete project timeline. Source preparation, internal approval, transfer, customer questions and final import checks can all sit outside the time spent tracing curves. A deadline should account for those activities, particularly when a technical reviewer is available only intermittently. Assigning one contact for scope questions can reduce avoidable delays.<\/p>\n\n\n\n For a substantial archive, propose an initial sample delivery followed by agreed batches. Review that sample promptly for naming, units, interval coverage and import behavior. Correcting a convention at the beginning is easier than changing it after the entire collection is produced. Confirm whether staged delivery is available and whether milestones depend on customer acceptance.<\/p>\n\n\n\n Acceptance should assess whether the files meet the agreed specification and remain traceable to the supplied records. Avoid relying only on file counts or a successful import message. Choose representative wells and include examples with more challenging source conditions. Record the checks so a later reviewer understands what was examined.<\/p>\n\n\n\n Distinguish a delivery error from a limitation already present in the original. An illegible interval should remain identifiable as uncertain; it should not become an apparently precise value simply to make the dataset look complete. Agree how questions and corrections will be submitted, who will resolve them and how revised files will be distinguished from earlier versions.<\/p>\n\n\n\n The most useful savings usually come from better scope and preparation. Remove confirmed duplicates, prioritize wells needed for an immediate decision and identify the curves that matter. Preserve the inventory of deferred records so a later phase can be commissioned deliberately. Reducing scope should be an informed technical choice, not an accidental consequence of incomplete instructions.<\/p>\n\n\n\n When comparing internal digitization with a service quotation, include preparation, checking and rework in the internal estimate. Staff time spent locating records and repairing inconsistent output is part of the project cost. Likewise, compare external quotations against the same deliverable requirements. A lower headline rate may cover fewer curves, less metadata or a different review process.<\/p>\n\n\n\n Create a concise inventory, select representative source records and describe the intended use. Include your preferred output requirements, target date and the person responsible for technical review. Identify uncertainties directly, such as an approximate curve count or missing pages. It is better to resolve those assumptions during quotation than after production begins.<\/p>\n\n\n\n For proprietary material, confirm the transfer method and any confidentiality requirements before sending the complete archive. Keep the source inventory, accepted quotation and delivery correspondence together as the project record. That makes future additions easier to specify and helps your organization understand exactly what was recovered.<\/p>\n\n\n\n Ready to establish a realistic budget?<\/strong> Review GAEA\u2019s well log digitization service and preliminary estimator<\/a>, then contact GAEA<\/a> to arrange a representative source review. A defined scope provides the strongest basis for agreeing cost, turnaround and deliverables before work begins.<\/p>\n","protected":false},"excerpt":{"rendered":" Understand the factors that influence well-log digitization pricing, delivery schedules, quality control and digital output formats.<\/p>\n","protected":false},"author":1,"featured_media":91717,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_jetpack_memberships_contains_paid_content":false,"footnotes":""},"categories":[975],"tags":[],"class_list":["post-92964","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-geoscience-data-digitization"],"yoast_head":"\nSource quality can change the effort substantially<\/h2>\n\n\n\n
Curve complexity, depth intervals and sampling<\/h2>\n\n\n\n
Metadata and file requirements belong in the scope<\/h2>\n\n\n\n
What a professional quotation should include<\/h2>\n\n\n\n
\n
What determines turnaround time?<\/h2>\n\n\n\n
Define how you will accept the deliverables<\/h2>\n\n\n\n
\n
Control cost without weakening the result<\/h2>\n\n\n\n
Prepare a quotation package that answers the key questions<\/h2>\n\n\n\n