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

Modifications in project.yaml #47

Closed
Quintus opened this issue Nov 24, 2019 · 3 comments
Closed

Modifications in project.yaml #47

Quintus opened this issue Nov 24, 2019 · 3 comments

Comments

@Quintus
Copy link

@Quintus Quintus commented Nov 24, 2019

INSTALL-de.md says:

If l10n is not needed it is also possible to slightly modify either project.yaml or the database views provided in the views_osmde directory.

What kind of modifications are required? I'm only rendering maps for places in Germany, so I assume I don't need the l10n extension (whose dependencies I'd like to avoid -- I don't want to install an entire llvm toolchain just for this).

@giggls

This comment has been minimized.

Copy link
Owner

@giggls giggls commented Nov 24, 2019

Really? Are these modifications that complicated, that they need explanation?
I did not think so that's why I don't have a detailed manual.

In project.mml you need to replace all occurances of localized_name_second, localized_name_first, localized_name_without_brackets and localized_streetname by name only.

Changing the views instead you would add something like this instead of the osml10n function calls:

name as localized_name_second,
name as localized_name_first,
name as localized_name_without_brackets,
name as  localized_streetname

This will also disable the code for generating streetname abbreviations because this is also part of osml10n.

@Quintus

This comment has been minimized.

Copy link
Author

@Quintus Quintus commented Nov 24, 2019

Really? Are these modifications that complicated, that they need explanation?

I did not intend to offend you. I asked a genuine question, and you reply with a personal attack. I don't think you're doing yourself a favour with this attitude, but I take your point. I don't work with OSM data on a daily base like you do, and I don't even touch much SQL at all.

Thank you for the advice, though. I'll try it, and if it works out, it's okay. If not, I'll just go with the official OSM style.

@Quintus Quintus closed this Nov 24, 2019
@giggls

This comment has been minimized.

Copy link
Owner

@giggls giggls commented Nov 24, 2019

OK, you consider my reply an offence. I don't. So don't expect any further help from me then.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants
You can’t perform that action at this time.