Up

Feature is actively developed on branch integrate_gis_data, will ship it to the release soon
Sneak peak:

When trying to check the validity of geom records, there are some records failed the check
MySQL

SELECT *
FROM vn_gis vg 
WHERE ST_IsValid(gis_geom) IS FALSE;

The result is the same for Microsoft SQL Server, so we need to take time looking into the faulty geo record issue.

Using PostGis ST_IsValidReason reveal the following problem to the multipolygon

SELECT vn_gis.code, vn_gis."level", ST_IsValidReason(gis_geom)
FROM vn_gis
WHERE ST_IsValid(gis_geom) IS FALSE;

Validity rule of a Polygon

Some of the rules of polygon validity feel obvious, and others feel arbitrary (and in fact, are arbitrary).
- Polygon rings must close.
- Rings that define holes should be inside rings that define exterior boundaries.
- Rings may not self-intersect (they may neither touch nor cross themselves).
- Rings may not touch other rings, except at a point.
- Elements of multi-polygons may not touch each other.

Checking further, the self intersection look like this on the map

List of invalid geo_gis items:

SELECT *
FROM vn_gis vg 
WHERE code IN ('617','184','515','516','511','512','62','645','646','639','660','661','666','667','86');