Skip to content

0.13.0

Choose a tag to compare

@BenMorel BenMorel released this 17 Mar 09:33

💥 Breaking changes

The case of the following class names and namespaces has changed:

  • GEOSEngine => GeosEngine
  • PDOEngine => PdoEngine
  • SQLite3Engine => Sqlite3Engine
  • RemoveZMProjector => RemoveZmProjector
  • SRIDProjector => SridProjector
  • SwapXYProjector => SwapXyProjector
  • TIN => Tin
  • GeometryIOException => GeometryIoException
  • IO\EWKBReader => Io\EwkbReader
  • IO\EWKBWriter => Io\EwkbWriter
  • IO\EWKTReader => Io\EwktReader
  • IO\EWKTWriter => Io\EwktWriter
  • IO\WKBReader => Io\WkbReader
  • IO\WKBWriter => Io\WkbWriter
  • IO\WKTReader => Io\WktReader
  • IO\WKTWriter => Io\WktWriter
  • IO\GeoJSONReader => Io\GeoJsonReader
  • IO\GeoJSONWriter => Io\GeoJsonWriter
  • IO\GeoJSON\Feature => Io\GeoJson\Feature
  • IO\GeoJSON\FeatureCollection => Io\GeoJson\FeatureCollection

The following breaking changes will only affect you if you're writing your own geometry engine:

  • GeometryEngine interface has a new method: concaveHull()
  • DatabaseEngine::executeQuery() implementations must now accept bool parameters
  • DatabaseEngine::getParameterPlaceholder() signature has changed to accept bool parameters
  • DatabaseEngine::queryGeometry() is now final

The following breaking changes may only affect you if you're writing your own engine or geometry classes:

  • GeometryException constructor signature has changed
  • Geometry has a new method: withRoundedCoordinates()

New features

  • New geometry engine: GeosOpEngine uses the geosop binary to perform geometry operations
  • New engine method: GeometryEngine::concaveHull()
  • New Geometry method: withRoundedCoordinates()

Improvements

  • All GeometryEngine methods are now properly documented with @throws GeometryEngineException

🐛 Bug fixes

  • WktParser and EwktParser now accept both MULTIPOINT (1 2, 3 4) and MULTIPOINT((1 2), (3 4)) syntaxes;
    this notably fixes interoperability issues with PostGIS