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

fix follow/preceed filters after place->venue rename #115

Merged
merged 1 commit into from
Aug 8, 2020
Merged

fix follow/preceed filters after place->venue rename #115

merged 1 commit into from
Aug 8, 2020

Conversation

blackmad
Copy link
Contributor

It seems like the new VenueClassification broke some rules in AddressParser, but it basically only caused changes at position 1 and higher, so it wasn't much of a regression.

Diff on 1000 random addresses is attached, rename to .html and open in a browser to see.

venue-fix-html.txt

Copy link
Member

@Joxit Joxit left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@Joxit Joxit merged commit a65218d into pelias:master Aug 8, 2020
orangejulius added a commit to pelias/api that referenced this pull request Aug 12, 2020
Improvements include:
- Better support for Romanian language: pelias/parser#114
- Remove some minor cases of incorrect venue classification in addresses: pelias/parser#115
- Remove "art" as street type: pelias/parser#116
orangejulius added a commit to pelias/api that referenced this pull request Aug 25, 2020
Improvements include:
- Better support for Romanian language: pelias/parser#114
- Remove some minor cases of incorrect venue classification in addresses: pelias/parser#115
- Remove "art" as street type: pelias/parser#116
orangejulius added a commit to pelias/api that referenced this pull request Oct 14, 2020
Improvements include:
- Better support for Romanian language: pelias/parser#114
- Remove some minor cases of incorrect venue classification in addresses: pelias/parser#115
- Remove "art" as street type: pelias/parser#116
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants