You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The underlying parser we use for WKT does not support the dataProjection and featureProjection options like some of the other parsers (such as GeoJSON). However, that should not be difficult to add.
Would you please post a sample file?
jsalankey
added a commit
to jsalankey/opensphere
that referenced
this issue
Jul 10, 2019
…nsphere:THIN-12767 to master
* commit '10b0ae7db7153b7476b6463afde9ed2c8e40c03f':
refactor(states): refactors/renames all of the state manager classes, other minor state refactors
Hi @wallw-bits, sorry about missing this conversation.
I sent you a line and a point file, the point file has a wkt-geometry in 4326 and separate x y columns in epsg:28992. The line file has a wkt field in 28992
the csv import (which works amazingly good!) with wkt seems to assume data is in epsg:4326
I'd expect an option to set a projection for the wkt column
The text was updated successfully, but these errors were encountered: