Industry Context — Common BS Fingerprints in Software, SaaS & Tech Products
PostGIS
(https://postgis.net) 📸 Data Snapshot: May 24, 2026Analyze the raw signals below. How would a machine score this business’s credibility?
Here are the exact signals captured from up to six pages of the site — the same raw inputs the evaluation engine analyzed. They are grouped by signal type so you can weigh each the way the machine does.
🏗️ Semantic Structure — heading hierarchy & page identity (Info Density · Commodity Fingerprint)
HOMEPAGE PostGIS (https://postgis.net)
PostGIS
NAV_HEADING_REPEATED_BODY Source Code | PostGIS (https://postgis.net/development/source_code/)
Source Code | PostGIS
Where to find the source repository and released source code
HEADING_REPEATED_BODY PostGIS Patch Releases | PostGIS (https://postgis.net/2026/04/PostGIS-Patch-Releases/)
PostGIS Patch Releases | PostGIS
The PostGIS development team is pleased to provide bug fix and security releases for PostGIS 3.2 – 3.6.
NAV_HEADING News | PostGIS (https://postgis.net/news/)
News | PostGIS
📝 The Narrative — clean text per page (Info Density · Semantic Coherence)
HOMEPAGE (https://postgis.net) PostGIS
[H1] About PostGIS PostGIS extends the capabilities of the PostgreSQL relational database by adding support for storing, indexing, and querying geospatial data. PostGIS features include: Spatial Data Storage: Store different types of spatial data such as points, lines, polygons, and multi-geometries, in both 2D and 3D data. Spatial Indexing: Quickly search and retrieve spatial data based on its location. Spatial Functions: A wide range of spatial functions that allow you to filter and analyze spatial data, measuring distances and areas, intersecting geometries, buffering, and more. Geometry Processing: Tools for processing and manipulating geometry data, such as simplification, conversion, and generalization. Raster Data Support: Storage and processing of raster data, such as elevation data and weather data. Geocoding and Reverse Geocoding: Functions for geocoding and reverse geocoding. Integration: Access and work with PostGIS using third party tools such as QGIS, GeoServer, MapServer, ArcGIS, Tableau. [H2] Latest News [H3] PostGIS Patch Releases The PostGIS development team is pleased to provide bug fix and security releases for PostGIS 3.2 - 3.6. Read more gdoc_arrow_right_alt
SUB-PAGE (https://postgis.net/development/source_code/) Source Code | PostGIS
Home / Development / Source Code [H1] Source Code [H2] Current Releases The current source code releases are: postgis-3.6.3.tar.gz [ md5 | Release Notes ] postgis-3.5.6.tar.gz [ md5 | Release Notes ] postgis-3.4.6.tar.gz [ md5 | Release Notes ] postgis-3.3.10.tar.gz [ md5 | Release Notes ] postgis-3.2.10.tar.gz [ md5 | Release Notes ] postgis-3.1.13.tar.gz EOL [ md5 | Release Notes ] postgis-3.0.12.tar.gz EOL [ md5 | Release Notes ] Older releases are available directly from the source download directory. Refer to our version and end-of-life policy for details on code life cycle. Logos are available in the logo directory. [H2] Source Code Repository The official PostGIS GIT repository is hosted at OSGeo. https://gitea.osgeo.org/postgis/ Changes pushed to the official repository will be replicated to the two mirror repository sites. Changes committed to the mirror sites will be over-written the next time a changes are synced from OSGeo. GitHub mirror: https://github.com/postgis/postgis/ GitLab mirror: https://gitlab.com/postgis/postgis/ Codeberg mirror: https://codeberg.org/postgis/postgis/
SUB-PAGE · THIN (https://postgis.net/2026/04/PostGIS-Patch-Releases/) PostGIS Patch Releases | PostGIS
Home / News / PostGIS Patch Releases The PostGIS development team is pleased to provide bug fix and security releases for PostGIS 3.2 - 3.6. 3.6.3 source md5 NEWS docs: en 3.5.6 source md5 NEWS docs: en 3.4.6 source md5 NEWS docs: en 3.3.10 source md5 NEWS docs: en 3.2.10 source md5 NEWS docs: en Please refer to the links above for more information about the issues resolved by these releases.
SUB-PAGE (https://postgis.net/news/) News | PostGIS
Home / News The PostGIS development team is pleased to provide bug fix and security releases for PostGIS 3.2 - 3.6. Read more gdoc_arrow_right_alt The PostGIS development team is pleased to provide bug fix releases for PostGIS 3.0 - 3.6. These are the End-Of-Life (EOL) releases for PostGIS 3.0.12 and 3.1.13. If you haven’t already upgraded from 3.0 or 3.1 series, you should do so soon. Read more gdoc_arrow_right_alt The PostGIS Team is pleased to publish PostGIS 3.6.1. This is a bug fix release that includes bug fixes since PostGIS 3.6.0. This version requires PostgreSQL 12 - 18, Proj 6.1+, and GEOS 3.8+. To take advantage of all features, GEOS 3.12+ is needed. SFCGAL 1.4+ is needed to enable postgis_sfcgal support. To take advantage of all SFCGAL features, SFCGAL 2.2+ is needed. [H3] 3.6.1 source download md5 NEWS PDF docs: en HTML Online en ja fr zh_Hans Cheat Sheets: postgis: en ja fr zh_Hans postgis_raster: en ja fr zh_Hans postgis_topology: en ja fr zh_Hans postgis_sfcgal: en ja fr zh_Hans address standardizer, postgis_tiger_geocoder: en ja fr zh_Hans Read more gdoc_arrow_right_alt The PostGIS Team is pleased to release PostGIS 3.5.4. This version requires PostgreSQL 12 - 18beta1, GEOS 3.8 or higher, and Proj 6.1+. To take advantage of all features, GEOS 3.12+ is needed. SFCGAL 1.4+ is needed to enable postgis_sfcgal support. To take advantage of all SFCGAL features, SFCGAL 1.5+ is needed. [H3] 3.5.4 source download md5 NEWS PDF docs: en This release is a bug fix release that includes bug fixes since PostGIS 3.5.3. Read more gdoc_arrow_right_alt The PostGIS Team is pleased to release PostGIS 3.6.0! Best Served with PostgreSQL 18 Beta3 and recently released GEOS 3.14.0. This version requires PostgreSQL 12 - 18beta3, GEOS 3.8 or higher, and Proj 6.1+. To take advantage of all features, GEOS 3.14+ is needed. To take advantage of all SFCGAL features, SFCGAL 2.2.0+ is needed. [H3] 3.6.0 source download md5 NEWS HTML Online en ja sv fr zh_Hans PDF docs: en ja, sv, zh_Hans, fr Cheat Sheets: postgis: en ja sv fr zh_Hans postgis_raster: en ja sv fr zh_Hans postgis_topology: en ja sv fr zh_Hans postgis_sfcgal: en ja sv fr zh_Hans address standardizer, postgis_tiger_geocoder: en ja sv fr zh_Hans This release includes bug fixes since PostGIS 3.5.3 and new features. Read more gdoc_arrow_right_alt The PostGIS Team is pleased to release PostGIS 3.6.0rc2! Best Served with PostgreSQL 18 Beta3 and recently released GEOS 3.14.0. This version requires PostgreSQL 12 - 18beta3, GEOS 3.8 or higher, and Proj 6.1+. To take advantage of all features, GEOS 3.14+ is needed. To take advantage of all SFCGAL features, SFCGAL 2.2.0+ is needed. [H3] 3.6.0rc2 source download md5 NEWS HTML Online en ja sv fr zh_Hans PDF docs: en ja, sv, zh_Hans, fr Cheat Sheets: postgis: en ja sv fr zh_Hans postgis_raster: en ja sv fr zh_Hans postgis_topology: en ja sv fr zh_Hans postgis_sfcgal: en ja sv fr zh_Hans address standardizer, postgis_tiger_geocoder: en ja sv fr zh_Hans This release is a beta of a major release, it includes bug fixes since PostGIS 3.5.3 and new features. Read more gdoc_arrow_right_alt The PostGIS Team is pleased to release PostGIS 3.6.0rc1! Best Served with PostgreSQL 18 Beta3 and soon to be released GEOS 3.14. This version requires PostgreSQL 12 - 18beta3, GEOS 3.8 or higher, and Proj 6.1+. To take advantage of all features, GEOS 3.14+ is needed. To take advantage of all SFCGAL features, SFCGAL 2.2.0+ is needed. [H3] 3.6.0rc1 source download md5 NEWS HTML Online en ja sv fr zh_Hans PDF docs: en ja, sv, zh_Hans, fr Cheat Sheets: postgis: en ja sv fr zh_Hans postgis_raster: en ja sv fr zh_Hans postgis_topology: en ja sv fr zh_Hans postgis_sfcgal: en ja sv fr zh_Hans address standardizer, postgis_tiger_geocoder: en ja sv fr zh_Hans This release is a beta of a major release, it includes bug fixes since PostGIS 3.5.3 and new features. Read more gdoc_arrow_right_alt The PostGIS Team is pleased to release PostGIS 3.6.0beta1! Best Served with PostgreSQL 18 Beta2 and soon to be released GEOS 3.14. This version requires PostgreSQL 12 - 18beta2, GEOS 3.8 or higher, and Proj 6.1+. To take advantage of all features, GEOS 3.14+ is needed. To take advantage of all SFCGAL features, SFCGAL 2.2.0+ is needed. [H3] 3.6.0beta1 source download md5 NEWS HTML Online en ja sv fr zh_Hans PDF docs: en ja, sv, zh_Hans, fr Cheat Sheets: postgis: en ja sv fr zh_Hans postgis_raster: en ja sv fr zh_Hans postgis_topology: en ja sv fr zh_Hans postgis_sfcgal: en ja sv fr zh_Hans address standardizer, postgis_tiger_geocoder: en ja sv fr zh_Hans This release is a beta of a major release, it includes bug fixes since PostGIS 3.5.3 and new features. Read more gdoc_arrow_right_alt The PostGIS Team is pleased to release PostGIS 3.6.0alpha1! Best Served with PostgreSQL 18 Beta1 and GEOS 3.13.1. This version requires PostgreSQL 12 - 18beta1, GEOS 3.8 or higher, and Proj 6.1+. To take advantage of all features, GEOS 3.12+ is needed. To take advantage of all SFCGAL features, SFCGAL 2.1.0+ is needed. [H3] 3.6.0alpha1 source download md5 NEWS HTML Online en ja fr zh_Hans PDF docs: en ja, zh_Hans, fr Cheat Sheets: postgis: en ja fr zh_Hans postgis_raster: en ja fr zh_Hans postgis_topology: en ja fr zh_Hans postgis_sfcgal: en ja fr zh_Hans address standardizer, postgis_tiger_geocoder: en ja fr zh_Hans This release is an alpha of a major release, it includes bug fixes since PostGIS 3.5.3 and new features. Read more gdoc_arrow_right_alt The PostGIS Team is pleased to release PostGIS 3.5.3. This version requires PostgreSQL 12 - 18beta1, GEOS 3.8 or higher, and Proj 6.1+. To take advantage of all features, GEOS 3.12+ is needed. SFCGAL 1.4+ is needed to enable postgis_sfcgal support. To take advantage of all SFCGAL features, SFCGAL 1.5+ is needed. [H3] 3.5.3 source download md5 NEWS PDF docs: en HTML Online en ja fr zh_Hans Cheat Sheets: postgis: en ja fr zh_Hans postgis_raster: en ja fr zh_Hans postgis_topology: en ja fr zh_Hans postgis_sfcgal: en ja fr zh_Hans address standardizer, postgis_tiger_geocoder: en ja fr zh_Hans This release is a bug fix release that includes bug fixes since PostGIS 3.5.1. Read more gdoc_arrow_right_alt
🛡️ Trust Signals — reviews, proof links, trust-theatre flag (Trust & Proof)
| Page | Reviews | Proof links |
|---|---|---|
| / (home) | 0 | 0 |
| /development/source_code/ | 0 | 0 |
| /2026/04/PostGIS-Patch-Releases/ | 0 | 0 |
| /news/ | 0 | 0 |
🔗 Identity & Technical Layer — schema JSON-LD: identity chains, entity gaps (Identity & Authority)
Homepage schema
{
"@context": "http://schema.org",
"@type": "WebSite",
"name": "PostGIS",
"url": "https://postgis.net/",
"license": "CC BY-SA 4.0",
"inLanguage": "en"
}
/development/source_code/
{
"@context": "http://schema.org",
"@type": "TechArticle",
"articleSection": "Development",
"name": "Source Code",
"url": "https://postgis.net/development/source_code/",
"headline": "Source Code",
"description": "Where to find the source repository and released source code",
"wordCount": "144",
"license": "CC BY-SA 4.0",
"inLanguage": "en",
"isFamilyFriendly": "true",
"mainEntityOfPage": {
"@type": "WebPage",
"@id": "https://postgis.net/development/source_code/"
},
"copyrightHolder": "PostGIS",
"copyrightYear": "2022",
"dateCreated": "2022-02-01T00:00:00.00Z",
"datePublished": "2022-02-01T00:00:00.00Z",
"dateModified": "2022-02-01T00:00:00.00Z",
"publisher": {
"@type": "Organization",
"name": "PostGIS",
"url": "https://postgis.net/",
"logo": {
"@type": "ImageObject",
"url": "https://postgis.net/brand.svg",
"width": "32",
"height": "32"
}
}
}
/2026/04/PostGIS-Patch-Releases/
{
"@context": "http://schema.org",
"@type": "TechArticle",
"articleSection": "News",
"name": "PostGIS Patch Releases",
"url": "https://postgis.net/2026/04/PostGIS-Patch-Releases/",
"headline": "PostGIS Patch Releases",
"description": "The PostGIS development team is pleased to provide bug fix and security releases for PostGIS 3.2 - 3.6.",
"wordCount": "64",
"license": "CC BY-SA 4.0",
"inLanguage": "en",
"isFamilyFriendly": "true",
"mainEntityOfPage": {
"@type": "WebPage",
"@id": "https://postgis.net/2026/04/PostGIS-Patch-Releases/"
},
"keywords": [
"release",
"3.6",
"3.5",
"3.4",
"3.3",
"3.2"
],
"copyrightHolder": "PostGIS",
"copyrightYear": "2026",
"dateCreated": "2026-04-14T00:00:00.00Z",
"datePublished": "2026-04-14T00:00:00.00Z",
"dateModified": "2026-04-14T00:00:00.00Z",
"publisher": {
"@type": "Organization",
"name": "PostGIS",
"url": "https://postgis.net/",
"logo": {
"@type": "ImageObject",
"url": "https://postgis.net/brand.svg",
"width": "32",
"height": "32"
}
}
}
/news/
{
"@context": "http://schema.org",
"@type": "TechArticle",
"articleSection": "News",
"name": "News",
"url": "https://postgis.net/news/",
"headline": "News",
"wordCount": "0",
"license": "CC BY-SA 4.0",
"inLanguage": "en",
"isFamilyFriendly": "true",
"mainEntityOfPage": {
"@type": "WebPage",
"@id": "https://postgis.net/news/"
},
"copyrightHolder": "PostGIS",
"copyrightYear": "2026",
"dateCreated": "2026-04-14T00:00:00.00Z",
"datePublished": "0001-01-01T00:00:00.00Z",
"dateModified": "2026-04-14T00:00:00.00Z",
"publisher": {
"@type": "Organization",
"name": "PostGIS",
"url": "https://postgis.net/",
"logo": {
"@type": "ImageObject",
"url": "https://postgis.net/brand.svg",
"width": "32",
"height": "32"
}
}
}
Your Diagnosis
Before revealing the machine’s verdict, predict the BS score for each signal. Higher = more BS (more fluff, less verifiable substance). Drag each slider, then submit to compare your judgment against the engine.
Stuck? Reveal the heuristic lens — how the deterministic page-auditor reads each signal (no AI, pure pattern rules)
These are the structural rules a local, deterministic auditor applies — the same lens you can use to judge each signal. They describe what to look for, not this company’s result.
Classify each sentence as substantive or hollow. Grounding markers — numbers, currencies, dates, technical units, named entities — outweigh marketing adjectives. When fluff sits right next to hard evidence, the fluff is forgiven.
Pull the main entities out of the H1, then check whether they actually recur through the body. A page that announces one thing and then talks about another drifts. Headings with no real sentences underneath read as pseudo-substance.
Count trust words (review, testimonial, rating, verified) against real outbound proof links (Google, Trustpilot, Clutch, G2, Yelp). Lots of trust language with zero verification links is trust theatre. Unlinked logo galleries count against it.
Look at how much sentence length varies. Natural writing varies its rhythm; templated or mass-produced copy is statistically uniform. Very low variation reads as commodity content — unless unique named entities break the pattern.
Inspect the JSON-LD. Is there an Organization or Person schema, and does it carry sameAs links to real external profiles (LinkedIn, socials)? Missing schema or no identity declaration signals an anonymous entity.
Want to apply this lens yourself? The free BS Indicator Chrome extension runs these heuristic checks live on any page. Bear in mind it is a single-page, deterministic tool — it relies only on pattern rules for the page in front of it and does not perform the cross-page semantic correlation this audit uses, so its readout is a starting lens, not the full verdict.
Based on 1130 businesses audited.
PostGIS has 30.2 points less BS than the average for Software, SaaS & Tech Products.
Software, SaaS & Tech Products BS: PostGIS (postgis.net)
PostGIS provides a masterclass in low-BS technical communication. It ignores modern SaaS marketing tropes in favor of raw technical utility, version transparency, and verifiable source code availability.
1. Integrate Person schema for core project steering committee members to provide a human authority layer to the ‘development team’ claims. 2. Append sameAs links in the Organization schema to the official OSGeo foundation project page. 3. Consider adding a section for ‘Verified Integrations’ with links to the official documentation of mentioned partners like QGIS and GeoServer to further strengthen the proof path.
The site perfectly aligns with the Software and Tech Products industry, specifically focusing on open-source geospatial extensions for databases. The content is heavily focused on technical specifications, version control, and dependency requirements rather than marketing-led sales cycles.
“The score of 3 is one of the lowest possible, driven by the site's total rejection of industry jargon, its high density of technical specifics, and its alignment between homepage signals and sub-page code releases. Only minor points were added for the lack of individual person-level schema and the use of basic page templates.”
This training module utilizes a snapshot of public data from PostGIS, captured on May 24, 2026, to demonstrate how machine logic evaluates different types of business narratives.
Purpose: This data is presented under “Fair Use” / “Educational Exception” for the purpose of forensic semantic analysis, allowing users to compare human intuition against machine-generated evaluations.
Notice to PostGIS: This analysis is part of a non-adversarial audit conducted by 1 Euro SEO. The results provided by 1EuroSEO are intended as professional feedback to help improve any website’s machine-readability and authority signals. The 1EuroSEO BS Detection Tool is a free tool, and anyone can test any company to see how their content is interpreted by AI models.
Any company can use the insights for free and improve its voice by comparing it to industry clichés or competitors. When a company has updated its content, it can always submit a new audit request, which will be reflected in a new current score.
To all users: You are encouraged to visit the live site at https://postgis.net to view the most current version of its content and learn from the source what this company is about and what it offers.