Unable to run within when different SRID generated

[grimzy]

Unable to run within when different SRID generated

[grimzy]

I'm working on a PR for this task srid.

[grimzy]

Thank you for reporting this.

I agree, we have to handle SRIDs when fetching and comparing spatial data.
As you mentioned, to fix this issue we should update how all fields types are represented in queries, for example:

ST_GeomFromText("POINT(0 -10)")
ST_GeomFromText("POLYGON((40 -10,-10 -10,-10 40,40 40,40 -10))")

become:

ST_GeomFromText("POINT(0 -10)", 4326)
ST_GeomFromText("POLYGON((40 -10,-10 -10,-10 40,40 40,40 -10))", 4326)

(or an SRID different than 4326, depending on what is stored)

I think this issue is also related to #47 (how the package fetches the binary data from the database).

And yes, PRs are greatly appreciated! And unit tests to fasten a release event more! 👍

[kotasjan]

So if I comprehended it well, there is currently no option how to save POINT object with SRID different than 0. Am I right? I was trying to find a way for a week without success. When I tried to use SRID = 0 all the spatial functions returned me really weird data so I assume it is caused by this. :(

[sikhlana]

@grimzy is there any update on adding support for SRID?

[grimzy]

@sikhlana To be honest, no.

Currently we do this: https://github.com/grimzy/laravel-mysql-spatial/blob/master/src/Types/Geometry.php#L55:

public static function fromWKB($wkb)
    {
        // mysql adds 4 NUL bytes at the start of the binary
        $wkb = substr($wkb, 4);
        $parser = new Parser(new Factory());
        return $parser->parse($wkb);
    }

Literally: we remove the srid info from the WKB, then parse it. This code is to make the parser "compatible" with MySQL's WKB (meh... it just uses the default: 4326).

In any case, I've tried other parsers, tried to decode myself; but no dice.

Any help is greatly appreciated!!! Last time I pushed something for this was in the srid branch. I think the rest of the commits in that branch have every other change needed.

[grimzy]

@kotasjn sorry :(

[sikhlana]

@grimzy I'm checking if integrating with https://github.com/libgeos/php-geos does any trick. Will let you know.