This is probably a duplicate of #70, right?

I managed to solve this by looking at the #71 PR.

I added this code:

                $point = new Point($geocoded['latitude'], $geocoded['longitude']);
                $address->geometries['location'] = $point;
                $address->attributes['location'] = new SpatialExpression($point);

This shouldn't be necessary, but it solves the problem temporarily.

@pelmered Thanks for the workaround! I’ve just stumbled upon the same issue while trying to assign a default value to a Point when creating a model…

static::creating(function (self $model) {
    if (is_null($model->location)) {
        // Throws MySQL error: Numeric value out of range blah blah blah...
        $model->location = Point($defaultLatitude, $defaultLongitude);
    }
});

The code you isolated fixes the issue 👌

static::creating(function (self $model) {
    if (is_null($model->location)) {
        $point = Point($defaultLatitude, $defaultLongitude);
        $model->geometries['location'] = $point;
        $model->attributes['location'] = new SpatialExpression($point);
    }
});

Thanks for looking at this! And sorry for responding so late.

I'll try to look at #71 soon and put all of this in a tested PR.

i'm having the same problem. is there any way instead of those two line above? as in the tutorial just new Point($lat, $lng) should be enough.
here is my code:
my Setting model:

use Grimzy\LaravelMysqlSpatial\Types\Point;
use Illuminate\Database\Eloquent\Model;
use Grimzy\LaravelMysqlSpatial\Eloquent\SpatialTrait;
protected $guarded = [];
protected $spatialFields = ['location'];
public function setSetting($data) {
$lat = $data['lat'];
$lng = $data['lng'];
$this->title = $data['title'];
$this->address = $data['address'];
$this->location = new Point($lat, $lng)
$this->save();
}

and my controller:
public function set(){
$data = $this->validateRequest();
$setting = Setting::firstOrNew(['id' => 1]);
$setting->setSetting($data);
}

and when i add "use SpatialTrait" to my model, i get this error:
PDOException: SQLSTATE[42000]: Syntax error or access violation: 1582 Incorrect parameter count in the call to native function 'ST_GeomFromText'

@M-Barari In your Setting model, try to replace this line

$this->location = new Point($lat, $lng);

by this

$point = Point($lat, $lng);
$this->geometries['location'] = $point;
$this->attributes['location'] = new \Grimzy\LaravelMysqlSpatial\EloquentSpatialExpression($point);

I can’t guarantee this will work (I cannot guess by just looking at your code) but if your issue is the same as the one described above, then it should help.

As for your PDOException: SQLSTATE[42000] error, I’m not sure if it’s related.

Welcome to GitHub, by the way. Here is a tip that you may find helpful : when writing code in comments, you can surround it by ` accents to display it with indentation and syntax highlighting. Like this:

```php
echo $hello;
```

You can replace the php part by the appropriate language if it’s different (html or css, for example). You can find more info in the GitHub help: https://guides.github.com/features/mastering-markdown/

@M-Barari I ran into the same error and was able to fix it by installing v2.0 of the library. I'm running MySQL 5.7, which according to the readme should be used with v2.0.

Facing the same issue

when trying to save

{
    [
        {
            "lat": "30.590213",
            "lng": "31.519949"
        },
        {
            "lat": "30.589770",
            "lng": "31.521848"
        }
    ]
}

I get SQL error

SQLSTATE[22003]: Numeric value out of range: 1416 Cannot get geometry object from data you send to the GEOMETRY field (SQL: update .... route_path = ST_GeomFromText(LINESTRING(31.519949 30.590213,31.521848 30.58977)), ....

i have tried the proposed solution and my code is

$lineString = new LineString($points);
$this->geometries['route_path'] = $lineString;
$this->attributes['route_path'] = new SpatialExpression($lineString);

but still not fixed

package version 2.2.3
php 7.4.2
mysql 5.7.30

Please ignore my comment

i believe the issue was because my migration was not correct

Thanks

I had this issue again now, but now it was because I didn't have SpatialTrait on my model.

I think this issue can be closed now.