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.

Sign up for GitHub

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

Jump to bottom

Landmark Regions: Fix labeling requirement issue #453 #687

Merged
merged 2 commits into from
Jun 15, 2018
Merged

Landmark Regions: Fix labeling requirement issue #453 #687

merged 2 commits into from
Jun 15, 2018

Conversation

jnurthen
Copy link
Member

@jnurthen jnurthen commented May 21, 2018 •
edited by pr-preview bot

@jnurthen jnurthen requested a review from mcking65 May 23, 2018 18:41
@mcking65 mcking65 self-assigned this Jun 1, 2018
@mcking65 mcking65 changed the title Fix for #453 Landmark Regions: Fix labeling requirement issue #453 Jun 14, 2018
@jnurthen
Copy link
Member Author

Looks good.

@mcking65
Copy link
Contributor

@jnurthen, thanks, will go ahead then.

@mcking65 mcking65 merged commit e8e10ea into master Jun 15, 2018
@mcking65 mcking65 deleted the Issue453 branch June 15, 2018 17:45
mcking65 pushed a commit that referenced this pull request Jun 24, 2018
@jnurthen @mcking65
Landmark Regions: Fix labeling requirement issue #453 (#687)
87d5739 
Editorial clarification to landmark labeling guidance to explain when unique labels are needed and when duplicate labels may be appropriate.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@mcking65 mcking65 Awaiting requested review from mcking65

Assignees

@mcking65 mcking65

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

None yet
2 participants
@jnurthen @mcking65