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

Simple Marker Data Defined Anchor Point #21754

Closed
qgib opened this issue Nov 1, 2015 · 5 comments
Closed

Simple Marker Data Defined Anchor Point #21754

qgib opened this issue Nov 1, 2015 · 5 comments
Labels
Bug Either a bug report, or a bug fix. Let's hope for the latter!

Comments

@qgib
Copy link
Contributor

qgib commented Nov 1, 2015

Author Name: Michael Knopp (Michael Knopp)
Original Redmine Issue: 13727
Affected QGIS version: 2.8.1


I am trying to use data definition to define a cliff hashmark.

I have created a style for the line with a simple marker and plan to use the vertical anchor point offset to move the marker to the proper side of the line.

I have created a string field with a width of 10 and enter "bottom" or "top" into the field. After creating the line the hashmarks are displayed correctly. However, as soon as I save the shapefile it defaults back to a centered anchor point.

I have tried changing the table and saving. I have quit QGIS and restarted. It is like it doesn't read from the shapefile correctly.


@qgib
Copy link
Contributor Author

qgib commented Nov 1, 2015

Author Name: Nyall Dawson (@nyalldawson)


To confirm, is the data getting saved corrctly into the shapefile (eg browsing the table shows your entered anchor values), or is the data definition getting lost when saving the project?


  • status_id was changed from Open to Feedback

@qgib
Copy link
Contributor Author

qgib commented Nov 2, 2015

Author Name: Michael Knopp (Michael Knopp)


Yes, the data is getting saved to the shapefile. If I open the table the data is shown exactly as entered.

Also, I have tried this on a Windows 7 SP 1 machine also running QGIS 2.8.1 and the behavior is exactly the same.

@qgib
Copy link
Contributor Author

qgib commented Nov 2, 2015

Author Name: Nyall Dawson (@nyalldawson)


I can't reproduce. Can you share a small project/sample data which shows this issue?

@qgib
Copy link
Contributor Author

qgib commented Nov 3, 2015

Author Name: Michael Knopp (Michael Knopp)


Sure. I just created a very small topo with a cut. Using only these two small shapefiles it is still doing it on my systems.

I also am including a screenshot of my installed plugins. Just in case it is some conflict with one of them.

Thanks.


  • 9265 was configured as Hachure_Test.zip
  • 9266 was configured as Installed_Plugins.png

@qgib
Copy link
Contributor Author

qgib commented Nov 3, 2015

Author Name: Nyall Dawson (@nyalldawson)


Ok, this issue was already fixed in 2.8.2. I've tested your project with 2.8.3 and it works fine.


  • resolution was changed from to fixed/implemented
  • status_id was changed from Feedback to Closed

@qgib qgib added the Bug Either a bug report, or a bug fix. Let's hope for the latter! label May 25, 2019
@qgib qgib closed this as completed May 25, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Either a bug report, or a bug fix. Let's hope for the latter!
Projects
None yet
Development

No branches or pull requests

1 participant