-
-
Notifications
You must be signed in to change notification settings - Fork 696
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
Obtain licence copyright from extratags #1738
base: master
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The approach looks okay in general but I'm not yet decided if that is something we'd want in the mainline Nominatim or not. If we take it it definitely needs to be configurable. Even if we don't take it here, there might still be ways to ensure that the patch is minimal for you and maintainable. At the moment there are a lot of format changes in the PR which makes it hard to judge how invasive the whole thing is. Can you separate out the format changes into its own PR, then they can simply be merged and this PR is left with the functional changes.
lib/PlaceLookup.php
Outdated
$licence_copyright_content = $this->oDB->getRow( | ||
"SELECT extratags -> 'data_licence' AS licence, extratags -> 'data_copyright' AS copyright FROM placex where place_id = :placeid", | ||
array(':placeid' => $aPlace['place_id']) | ||
); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You should enable returning extratags per default ($this->bExtratags) and then extract the information from there instead of running another query on the database.
c5f939e
to
2740974
Compare
I modify this PR into the functional change. |
The change obtains the licence and copyright content from the customized data which are imported as "extratags" of "data_licence"and "data_copyright". It is related to resolve #1699.
Thanks a lot for your review!