Repository navigation
Expand file tree
/
Copy pathmethodology.html
More file actions
254 lines (238 loc) · 12.7 KB
/
Copy pathmethodology.html
File metadata and controls
254 lines (238 loc) · 12.7 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="UTF-8" />
<meta name="viewport" content="width=device-width, initial-scale=1.0" />
<title>GeoIP Methodology, Data Sources, Validation and Release Process | ProdIPData</title>
<meta name="description" content="Review the ProdIPData GeoIP methodology, source inputs, validation approach, and monthly release process for CSV, Parquet, and MMDB datasets." />
<link rel="canonical" href="https://geoiplocations.com/methodology.html" />
<link rel="icon" type="image/png" href="assets/img/prodipdata-mark.png" />
<link rel="stylesheet" href="assets/css/styles.css" />
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "BreadcrumbList",
"itemListElement": [
{
"@type": "ListItem",
"position": 1,
"name": "Home",
"item": "https://geoiplocations.com/"
},
{
"@type": "ListItem",
"position": 2,
"name": "Methodology",
"item": "https://geoiplocations.com/methodology.html"
}
]
}
</script>
<meta property="og:url" content="https://geoiplocations.com/methodology.html" />
<script type="application/ld+json" data-wave3-schema="breadcrumb-methodology-html">
{
"@context": "https://schema.org",
"@type": "BreadcrumbList",
"@id": "https://geoiplocations.com/methodology.html#breadcrumb",
"itemListElement": [
{
"@type": "ListItem",
"position": 1,
"name": "Home",
"item": "https://geoiplocations.com/"
},
{
"@type": "ListItem",
"position": 2,
"name": "Methodology",
"item": "https://geoiplocations.com/methodology.html"
}
]
}
</script>
</head>
<body data-page="methodology">
<header class="site-header">
<div class="container">
<div class="navbar glass">
<a class="brand" href="index.html">
<div class="brand-mark">◎</div>
<div>
GeoIP Locations
<small>Powered by ProdIPData</small>
</div>
</a>
<nav class="nav-links" aria-label="Primary navigation">
<a href="platform.html" data-nav="platform">Platform</a>
<a href="coverage.html" data-nav="coverage">Coverage</a>
<a href="methodology.html" data-nav="methodology">Methodology</a>
<a href="downloads.html" data-nav="downloads">Downloads</a>
<a href="docs.html" data-nav="docs">Documentation</a>
<a href="news.html" data-nav="news">News</a>
<a href="contact.html" data-nav="contact">Contact</a>
</nav>
<div class="header-cta">
<a class="btn btn-secondary" href="downloads.html">Monthly Release</a>
</div>
<button class="menu-button" type="button" data-menu-toggle aria-expanded="false" aria-label="Open menu">Menu</button>
</div>
<nav class="mobile-nav glass" data-mobile-nav>
<a href="platform.html" data-nav="platform">Platform</a>
<a href="coverage.html" data-nav="coverage">Coverage</a>
<a href="methodology.html" data-nav="methodology">Methodology</a>
<a href="downloads.html" data-nav="downloads">Downloads</a>
<a href="docs.html" data-nav="docs">Documentation</a>
<a href="news.html" data-nav="news">News</a>
<a href="contact.html" data-nav="contact">Contact</a>
</nav>
</div>
</header>
<main>
<section class="page-hero">
<div class="container">
<div class="page-panel glass">
<div class="eyebrow page-kicker">Methodology</div>
<h1>How ProdIPData builds each monthly GeoIP release.</h1>
<p class="page-intro">
Each monthly release is assembled from curated source data, validated against quality controls, packaged into reusable files,
and published in a consistent format. The objective is to keep country, ASN, registry, and reference datasets clear, traceable, and easy to reuse.
</p>
<p class="page-intro seo-links">After reviewing the workflow, you can inspect the <a href="coverage.html">coverage dashboard</a>, explore the <a href="platform.html">platform overview</a>, open the <a href="releases/2026-04/index.html">current release overview</a>, browse the <a href="releases/index.html">release archive</a>, or open the <a href="downloads.html">monthly GeoIP release indexes</a>.</p>
</div>
</div>
</section>
<section class="section">
<div class="container">
<div class="timeline">
<div class="step glass">
<div class="step-num">1</div>
<h3>Extract</h3>
<p class="card-text">Curated source data is assembled into country, ASN, registry, download, and reference datasets for the monthly release.</p>
</div>
<div class="step glass">
<div class="step-num">2</div>
<h3>Validate</h3>
<p class="card-text">Each release is checked for structure, completeness, consistency, and packaging quality before it is published.</p>
</div>
<div class="step glass">
<div class="step-num">3</div>
<h3>Publish</h3>
<p class="card-text">Approved assets are versioned, packaged, and published as a static monthly release for browser access and file download.</p>
</div>
<div class="step glass">
<div class="step-num">4</div>
<h3>Document</h3>
<p class="card-text">Release notes, dataset definitions, and methodology statements are maintained so users can interpret the files and reuse them with confidence.</p>
</div>
</div>
</div>
</section>
<section class="section">
<div class="container">
<div class="split-panel glass content">
<h2>What is updated every month</h2>
<p>
Each monthly release is refreshed around a controlled snapshot so users can work from a stable, documented version of the data. The emphasis is on freshness, clarity, and consistency across the published files and pages.
</p>
<ul>
<li>Release snapshot labels such as 2026-04, 2026-04, and subsequent monthly versions.</li>
<li>Country, ASN, RIR, and concentration datasets used by the website tables, metrics, maps, and comparison views.</li>
<li>Download packages, manifests, checksums, and release-linked publication assets for local use.</li>
<li>Release notes, methodology clarifications, and supporting publication pages when relevant.</li>
</ul>
</div>
</div>
</section>
<section class="section">
<div class="container story-grid">
<div class="split-panel glass content">
<h2>How release pages fit the publication model</h2>
<p>
A monthly release page acts as the connective layer between methodology and distribution. It explains what belongs to a given publication month, links to the CSV, Parquet, and MMDB package indexes, and gives users one page that summarizes scope, supporting notes, and where to go next.
</p>
<ul>
<li>The <a href="releases/index.html">release archive</a> is the long-term navigation layer.</li>
<li>The <a href="releases/2026-04/index.html">current release page</a> is the release-level summary layer.</li>
<li>The format-specific package indexes remain the detailed download surfaces.</li>
</ul>
</div>
<div class="split-panel glass content">
<h2>Recommended reading order</h2>
<p>
Users who need the clearest path should review methodology first, then open the monthly release page, then move into the package indexes or the coverage view depending on whether the next question is operational download or analytical exploration.
</p>
<ul>
<li><a href="platform.html">Platform overview</a> for the product context.</li>
<li><a href="releases/2026-04/index.html">Release 2026-04 overview</a> for the current month.</li>
<li><a href="coverage.html">Coverage</a> and <a href="downloads.html">Downloads</a>
<a href="docs.html" data-nav="docs">Documentation</a> for deeper exploration.</li>
</ul>
</div>
</div>
</section>
<section class="section">
<div class="container">
<div class="split-panel glass content">
<h2>Licensing and attribution</h2>
<p>
Unless otherwise stated, the datasets and metadata published through GeoIP Locations are made available under <a href="licensing.html">CC BY 4.0</a>. That means users may copy, share, adapt, and reuse the published material, including for commercial purposes, provided appropriate credit is given to ProdIPData and any material changes are indicated.
</p>
<ul>
<li>Preferred attribution: <strong>Source: ProdIPData — https://geoiplocations.com/ — CC BY 4.0</strong></li>
<li>The dataset notice applies to published datasets and metadata unless a page or file states otherwise.</li>
<li>Third-party source rights, trademarks, and website code are not relicensed by this dataset notice unless explicitly stated.</li>
</ul>
</div>
</div>
</section>
<section class="section">
<div class="container story-grid">
<div class="split-panel glass content">
<h2>Accuracy and interpretation</h2>
<p>
GeoIP data is most useful when it is interpreted at the right level. Country-level results are generally more reliable than
attempts to infer exact city placement or precise coordinates, and internet address space can change over time as networks evolve.
</p>
<ul>
<li>Read the published data as structured geographic and network context, not as an exact physical address.</li>
<li>Use country, ASN, and registry views together for a stronger interpretation of the visible footprint.</li>
<li>Expect changes over time as allocations, routing, and network ownership shift.</li>
</ul>
</div>
<div class="split-panel glass content">
<h2>Why monthly releases matter</h2>
<p>
The monthly release model gives users a stable snapshot for comparison, download, and local reuse. It creates a controlled
reporting rhythm so teams can work from a documented version instead of a constantly shifting live view.
</p>
<ul>
<li>Each release is easier to reference in reports, workflows, and historical comparison.</li>
<li>Published files, website views, and metadata stay aligned to the same release month.</li>
<li>Users can download and retain local snapshots for repeatable analysis.</li>
</ul>
</div>
</div>
</section>
<!-- WAVE4:core-discovery-links START -->
<section class="section" data-wave4-block="discovery-links">
<div class="container">
<div class="split-panel glass content">
<h2>Explore deeper release and entity pages</h2>
<p>
The monthly release archive connects the current dataset to focused country, registry, and ASN pages. Use the <a href="releases/index.html">monthly release archive</a> for time-based navigation, open <a href="country/index.html">country profiles</a> for country-level footprint context, review <a href="rir/index.html">RIR pages</a> for registry-level coverage, and open <a href="asn/index.html">ASN profiles</a> for visible network entities in the current release. For package access, continue through <a href="downloads.html">GeoIP CSV, Parquet, and MMDB downloads</a>, and for source quality and caveats, review <a href="methodology.html">GeoIP methodology and validation</a>.
</p>
</div>
</div>
</section>
<!-- WAVE4:core-discovery-links END -->
</main>
<footer class="site-footer">
<div class="container site-footer-inner">
<div>© <span data-current-year></span> GeoIP Locations · ProdIPData</div>
<div><a href="licensing.html">Datasets and metadata: CC BY 4.0</a></div>
<div>Engineered and published by the ProdIPData team.</div>
</div>
</footer>
<script src="assets/js/site.js" defer></script>
</body>
</html>