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

Python parser for geometries in delimited text layers #19939

Open
qgib opened this issue Nov 19, 2014 · 2 comments
Open

Python parser for geometries in delimited text layers #19939

qgib opened this issue Nov 19, 2014 · 2 comments
Labels
Data Provider Related to specific vector, raster or mesh data providers Feature Request

Comments

@qgib
Copy link
Contributor

qgib commented Nov 19, 2014

Author Name: Joshua Arnott (@snorfalorpagus)
Original Redmine Issue: 11695

Redmine category:data_provider/delimited_text_


Currently delimited text layers support three options for geometries:

  1. Point coordinates (X and Y fields, optionally in DMS)
  2. Well Known Text (WKT)
  3. No geometry (attribute table only)

It is common in the United Kingdom to receive coordinates which use the British National Grid system.

http://en.wikipedia.org/wiki/Ordnance_Survey_National_Grid

For example, SP513061 is interpreted as x=451300, y=206100. It's relatively easy to do this conversion using a bit of Python:

http://snorf.net/blog/2014/08/12/converting-british-national-grid-and-irish-grid-references/

My proposal is for a 4th geometry option in the delimited text layer, that could pass a field or fields to a user-editable Python function, which would return either the x,y coordinates, or even a geometry object. Ireland has a similar grid system, so it would also be useful there, but I'm sure users could find even more interesting/obscure uses for this.

Of course, this could be written as an individual plugin, but it would involve significant duplication of existing functionality already in the delimited text layer feature.

@qgib
Copy link
Contributor Author

qgib commented Nov 19, 2014

Author Name: Nathan Woodrow (@NathanW2)


Now that is a nifty idea indeed.


  • fixed_version_id was configured as Future Release - Nice to have

@qgib
Copy link
Contributor Author

qgib commented Apr 30, 2017

Author Name: Giovanni Manghi (@gioman)


  • easy_fix was configured as 0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Data Provider Related to specific vector, raster or mesh data providers Feature Request
Projects
None yet
Development

No branches or pull requests

1 participant