<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Peter Biffar</title>
	<atom:link href="https://terradex.com/wp-author/pbiffar/feed/" rel="self" type="application/rss+xml" />
	<link>https://terradex.com/wp-author/pbiffar/</link>
	<description></description>
	<lastBuildDate>Mon, 11 May 2026 18:08:29 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	

<image>
	<url>https://terradex.com/wp-content/uploads/2023/12/Favicon-150x150.png</url>
	<title>Peter Biffar</title>
	<link>https://terradex.com/wp-author/pbiffar/</link>
	<width>32</width>
	<height>32</height>
</image> 
	<item>
		<title>Finding What Matters: Turning Volumes of Data Into Tailored LandWatch Alerts</title>
		<link>https://terradex.com/wp-finding-what-matters-turning-volumes-of-data-into-tailored-landwatch-alerts/</link>
		
		<dc:creator><![CDATA[Peter Biffar]]></dc:creator>
		<pubDate>Mon, 11 May 2026 18:00:00 +0000</pubDate>
				<category><![CDATA[Behind the Alerts]]></category>
		<guid isPermaLink="false">https://terradex.com/?p=13323</guid>

					<description><![CDATA[<p>In our first Behind the Alerts blog, Data: The Core Ingredient, we described how LandWatch gathers and monitors data to support site oversight. The next step turns that data into actionable alerts. LandWatch alerts leverage volumes of data to identify activities that may affect site conditions or interfere with land use restrictions, including activities that [&#8230;]</p>
<p>The post <a href="https://terradex.com/wp-finding-what-matters-turning-volumes-of-data-into-tailored-landwatch-alerts/">Finding What Matters: Turning Volumes of Data Into Tailored LandWatch Alerts</a> appeared first on <a href="https://terradex.com">Terradex</a>.</p>
]]></description>
										<content:encoded><![CDATA[<div id="modal-ready">		<div data-elementor-type="wp-post" data-elementor-id="13323" class="elementor elementor-13323" data-elementor-post-type="post">
				<div class="elementor-element elementor-element-3308c6b e-flex e-con-boxed e-con e-parent" data-id="3308c6b" data-element_type="container" data-e-type="container">
					<div class="e-con-inner">
				<div class="elementor-element elementor-element-091a586 elementor-widget elementor-widget-text-editor" data-id="091a586" data-element_type="widget" data-e-type="widget" data-widget_type="text-editor.default">
				<div class="elementor-widget-container">
									<p><span style="font-weight: 400;">In our first Behind the Alerts blog, </span><a href="https://terradex.com/wp-data-core-ingredient/"><span style="font-weight: 400;">Data: The Core Ingredient</span></a><span style="font-weight: 400;">, we described how </span><a href="https://terradex.com/wp-landwatch/"><span style="font-weight: 400;">LandWatch</span></a><span style="font-weight: 400;"> gathers and monitors data to support site oversight. The next step turns that data into actionable alerts.</span></p><p><span style="font-weight: 400;">LandWatch alerts leverage volumes of data to identify activities that may affect site conditions or interfere with land use restrictions, including activities that could disturb residual contamination, compromise a physical protective structure, or result in noncompliance with institutional controls (ICs). In practice, this means finding data early, swiftly evaluating it, and quickly sending LandWatch alerts to help avoid compliance or safety issues.</span></p><p><b>LandWatch Data Capture and Processing</b></p><p><span style="font-weight: 400;">Bringing together enormous volumes of data from multiple sources involves complex operations. Sources and formats vary, key details may be missing, and location information is often incomplete. Terradex LandWatch leverages its tailored workflows and data structure to standardize the data capture and alerting process, while allowing flexibility to expand as new data sources are incorporated. Our systems clean incoming data, review for duplicates, recognize previously captured records, and identify data elements that have changed since earlier runs.</span></p><p><span style="font-weight: 400;">After capturing and structuring data, it needs to be characterized by type because different data types (e.g., permits, parcel data) trigger different evaluations and alert conditions. Each type of data, or &#8220;event,&#8221; needs an identifier, relevant dates, and, where available, a point of contact.</span></p><p><span style="font-weight: 400;">Equally important is location. LandWatch alerts depend on understanding where an activity occurs at a site or its protected IC areas. While some data includes precise coordinates, much of it does not. In many cases, location information must be geocoded, refined, or supplemented. A clean address can often be resolved directly, but incomplete or low-precision data may require multiple steps, such as linking a parcel identifier to an address before geocoding. Once the data is structured, cleaned, and geolocated, LandWatch can evaluate it for alerting.</span></p><p><b>LandWatch Data Filtering to Create Alerts</b></p><p><span style="font-weight: 400;">For each LandWatch-monitored site, the system filters relevant events, evaluates their proximity to the site (or to subsections of the site), and compares event attributes against site-specific alert criteria. Based on this analysis, the system flags potential alert situations.</span></p><p><span style="font-weight: 400;">This process—filtering data &#8220;events&#8221; against tailored alert criteria—provides LandWatch alerts that reflect a set of conditions indicating whether an activity actually impacts site conditions or compliance requirements, based on proximity, activity type, and site-specific criteria.</span></p><p><span style="font-weight: 400;">The process of customizing alert criteria reflects client preferences and site-specific concerns, ensuring that LandWatch alerts align with each organization&#8217;s compliance obligations and risk management criteria. For instance, many clients only want to be alerted if an excavation is below a certain depth, potentially due to underground engineering controls or contaminated groundwater plumes. Terradex&#8217;s processing sets parameters to validate excavation tickets and allow alerts only for excavations beyond a certain depth, ensuring that only the most meaningful tickets become alerts.</span></p><p><b>LandWatch Verification for Further Alert Refinement</b></p><p><span style="font-weight: 400;">While tailored data operations improve efficiency, ensuring accurate LandWatch alerts requires even more attention. The LandWatch process also involves human operators who review each flagged event, validate details, refine the location when necessary using multiple geocoding approaches or unstructured descriptions, and issue alerts in accordance with client-specific preferences. This verification step helps reduce false positives and provides additional confidence that the alert reflects a real condition that may require attention.</span></p><p><b>LandWatch Alert Visibility and Presentation</b></p><p><span style="font-weight: 400;">Alerts can be distributed to multiple stakeholders, including property owners, environmental managers, regulators, and other affected parties. The alerts present details about the activity at issue and, within navigable maps, juxtapose the alert and site details. This intuitive, shared visibility helps ensure that potential issues are identified and addressed early, thereby supporting the continued protection of the IC.</span></p><p><b>Timely Alerts Provide Long-Term Protection</b></p><p><span style="font-weight: 400;">The value of an alert lies not just in what it identifies, but in when it is identified. Early visibility into site activity allows clients to evaluate issues before site conditions are disrupted or they escalate into compliance problems or operational delays. This is particularly important for sites with ICs, where managing ongoing activities is critical to ensure contamination remains contained and protective measures remain effective over the long term.</span></p><p>****</p><p><i><span style="font-weight: 400;">To learn more about how </span></i><a href="https://terradex.com/wp-watch-video-landwatch/"><i><span style="font-weight: 400;">LandWatch</span></i></a><i><span style="font-weight: 400;"> alerts work, you can </span></i><a href="https://terradex.com/wp-request-a-demo/"><i><span style="font-weight: 400;">Request a Demo</span></i></a><i><span style="font-weight: 400;"> or reach out to us directly at </span></i><a href="mailto:info@terradex.com"><i><span style="font-weight: 400;">info@terradex.com</span></i></a><i><span style="font-weight: 400;">.</span></i></p>								</div>
				</div>
					</div>
				</div>
				</div>
		</div><p>The post <a href="https://terradex.com/wp-finding-what-matters-turning-volumes-of-data-into-tailored-landwatch-alerts/">Finding What Matters: Turning Volumes of Data Into Tailored LandWatch Alerts</a> appeared first on <a href="https://terradex.com">Terradex</a>.</p>
]]></content:encoded>
					
		
		
			</item>
		<item>
		<title>Data: The Core Ingredient</title>
		<link>https://terradex.com/wp-data-core-ingredient/</link>
		
		<dc:creator><![CDATA[Peter Biffar]]></dc:creator>
		<pubDate>Fri, 17 Oct 2025 05:47:44 +0000</pubDate>
				<category><![CDATA[Behind the Alerts]]></category>
		<guid isPermaLink="false">https://terradex.com/?p=12906</guid>

					<description><![CDATA[<p>The core ingredient for LandWatch® is data. But what exactly does LandWatch “watch”? Just as a security guard watches people, cars, behavior, and movement, Terradex watches (monitors) data continuously. The data we monitor includes land-use records, environmental permits, regulatory notices, property transfers, and other sources that reveal changes and activities that could affect institutional controls, [&#8230;]</p>
<p>The post <a href="https://terradex.com/wp-data-core-ingredient/">Data: The Core Ingredient</a> appeared first on <a href="https://terradex.com">Terradex</a>.</p>
]]></description>
										<content:encoded><![CDATA[<div id="modal-ready">		<div data-elementor-type="wp-post" data-elementor-id="12906" class="elementor elementor-12906" data-elementor-post-type="post">
				<div class="elementor-element elementor-element-3308c6b e-flex e-con-boxed e-con e-parent" data-id="3308c6b" data-element_type="container" data-e-type="container">
					<div class="e-con-inner">
				<div class="elementor-element elementor-element-091a586 elementor-widget elementor-widget-text-editor" data-id="091a586" data-element_type="widget" data-e-type="widget" data-widget_type="text-editor.default">
				<div class="elementor-widget-container">
									<p><span style="font-weight: 400;">The core ingredient for </span><a href="https://terradex.com/wp-landwatch/"><span style="font-weight: 400;">LandWatch</span></a><span style="font-weight: 400;">® is data. But what exactly does LandWatch “watch”? Just as a security guard watches people, cars, behavior, and movement, Terradex watches (monitors) data continuously. The </span><b>data we monitor</b><span style="font-weight: 400;"> includes land-use records, environmental permits, regulatory notices, property transfers, and other </span><a href="https://terradex.com/wp-our-toolbox/"><span style="font-weight: 400;">sources</span></a><span style="font-weight: 400;"> that reveal changes and activities that could affect institutional controls, land use restrictions, or otherwise pose compliance or environmental risks at individual properties or other defined areas of interest.</span></p><p><span style="font-weight: 400;">Because it serves as the foundation of LandWatch, the data we rely on must be accurate, relevant, comprehensive, and collected continuously to avoid gaps. This </span><b>data collection process requires a clear understanding of what matters</b><span style="font-weight: 400;"> for compliance and redevelopment, and the persistence to track it down.</span></p><p><b>Accessing the various data</b><span style="font-weight: 400;"> sources we need requires both technical and substantive know-how. Much of the data we depend on cannot be easily found on commercial platforms and, instead, involves deep reaches into public sources. While some datasets can be downloaded directly, many others require Freedom of Information Act (</span><a href="https://www.foia.gov/faq.html"><span style="font-weight: 400;">FOIA)</span></a><span style="font-weight: 400;"> requests. Each agency has its own procedure, sometimes requiring parcel-level detail, and there is no standard form to follow. Other sources must be accessed through APIs or retrieved using custom code.</span></p><p><span style="font-weight: 400;">During the LandWatch site setup process, the Terradex team identifies the </span><b>specific data types needed</b><span style="font-weight: 400;"> for each site and the sources that can provide them. We then implement operational procedures to ensure a consistent and current data supply, typically aligned with each data source’s refresh frequency, usually ranging from daily to monthly.</span></p><p><span style="font-weight: 400;">Creating this</span><b> continuous flow of data </b><span style="font-weight: 400;">presents challenges. New information needs to arrive quickly, completely, and without interruption. Think of it like tracking the changing price of a flight to New York each day, rather than a one-time flight search. However, very little of the data we use is automatically “pushed” to us through established delivery systems. Instead, most follow a “pull” model, meaning the Terradex team must actively initiate each collection cycle, submitting FOIA requests or taking other steps to retrieve the data.</span></p><p><span style="font-weight: 400;">Herein lies the value of LandWatch. The complexity of this process, which involves tracking dozens of sources that update at different intervals and in various formats, makes automation and consistency critical. </span><b>Maintaining this flow </b><span style="font-weight: 400;">of timely, verified data allows LandWatch to alert clients the moment a new risk or regulatory change appears, often long before it becomes an issue on the ground.</span></p><p><span style="font-weight: 400;">Our operational systems sustain that flow. LandWatch configures each site with procedures that match the cadence of its data sources, ensuring that </span><b>updates are captured, processed, and delivered with minimal delay</b><span style="font-weight: 400;">. With this foundation in place, LandWatch continuously monitors for changes that signal potential risks or compliance concerns, helping clients stay informed and ready to act.</span></p><p><span style="font-weight: 400;">****</span></p><p><i><span style="font-weight: 400;">To learn more about the different types of data we monitor, visit our </span></i><a href="https://terradex.com/wp-our-toolbox/"><i><span style="font-weight: 400;">Toolbox</span></i></a><i><span style="font-weight: 400;"> page or </span></i><a href="https://terradex.com/wp-request-a-demo/"><i><span style="font-weight: 400;">Request a Demo</span></i></a><i><span style="font-weight: 400;"> to see how Terradex LandWatch can support your projects.</span></i></p>								</div>
				</div>
					</div>
				</div>
				</div>
		</div><p>The post <a href="https://terradex.com/wp-data-core-ingredient/">Data: The Core Ingredient</a> appeared first on <a href="https://terradex.com">Terradex</a>.</p>
]]></content:encoded>
					
		
		
			</item>
	</channel>
</rss>
