-
-
Notifications
You must be signed in to change notification settings - Fork 307
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
[Bug] v.to.rast use=attr does not convert all points #2475
Comments
For some reason every vector point had two cat values where second was sane but first was completely random indicating on an earlier failure. As I was not able to reproduce steps how garbage cat values were generated, closing as v.to.rast was just generating bad results based on bad data. |
Current code creates two cat entries for each point on the same level - one from area point is in and one matching new entry in the database. As entries in db have new cat values, old cat value points to a random or non-existing entry in the db thus causing a mess. Fixes OSGeo#2475.
For the record – the bug was in v.random and will be fixed by merging PR #2537 |
…OSGeo#2537) Current code creates two cat entries for each point on the same level - one from area point is in and one matching new entry in the database. As entries in db have new cat values, old cat value points to a random or non-existing entry in the db thus causing a mess. Fixes OSGeo#2475.
…OSGeo#2537) Current code creates two cat entries for each point on the same level - one from area point is in and one matching new entry in the database. As entries in db have new cat values, old cat value points to a random or non-existing entry in the db thus causing a mess. Fixes OSGeo#2475.
…OSGeo#2537) Current code creates two cat entries for each point on the same level - one from area point is in and one matching new entry in the database. As entries in db have new cat values, old cat value points to a random or non-existing entry in the db thus causing a mess. Fixes OSGeo#2475.
For some reason v.to.rast fails to convert all vector points if as a value source is set attribute table. Although attribute column contains 2000 not null values, only 113 raster points are generated. If value source is set to val, all 2000 points are present in output raster.
A further investigation needs to be done to determine why cat values in do_line L40 coming back from Vect_read_line are botched.
The text was updated successfully, but these errors were encountered: