Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CSV import could include projection configuration #635

Open
pvgenuchten opened this issue Jun 25, 2019 · 2 comments
Open

CSV import could include projection configuration #635

pvgenuchten opened this issue Jun 25, 2019 · 2 comments

Comments

@pvgenuchten
Copy link

pvgenuchten commented Jun 25, 2019

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

image

@wallw-teal
Copy link
Contributor

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
@pvgenuchten
Copy link
Author

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

Archive.zip

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants