Open araichev opened 4 years ago
I guess the compatibility could be accomplished by adding a boolean option (that defaults to False
) to the multigtfs import command, e.g. use_lat_lon_order
, to import geographic coordinates in lat-lon order.
@jwhitlock any word on this? I forgot about this feature request and now need it again.
@araichev, I haven't looked closely at the GDAL change, but it sounds good to me (latitude / longitude is how I think of coordinates anyway), and your ideas for handling this transition sound good. I haven't had time to work on multigtfs for a while, and I don't see that changing this year.
@araichev If you have chance to provide PR for this issue, feel free to do so. The project will add few new maintainers to run it further. Thank you.
Currently multigtfs is not compatible with GDAL >= 3. Can we make it compatible, and is that sensible? My company is willing to fund this feature request.
As far as i can tell, the only incompatibility is that GDAL >= 3 requires WGS84 coordinates to be specified in latitude-longitude order by default; they can be specified in longitude-latitude order as is done in multigtfs, but doing so now requires a special flag; see the GDAL docs.
Creating longitude-latitude geometries with multigtfs and GDAL >= 3 appears to work at first ---no errors are thrown--- but those geometries are actually malformed and certain methods fail on them, e.g. the
transform()
method raises aGDALException
. Here's an example on Linux Mint 19.3 with Python 3.7.6, GDAL 3.0.2, and Django 2.2.10.