I have millions of Bangladesh address data. They are clean and well structured ( Poi, House,Road,Area,Postcode,latitude,longitude,etc )
Now I want to load them into pelias geocoder. Can you help me by suggesting the steps with installation process.
Note: I also have my own pbf
You can use the csv-import component.
See: https://github.com/pelias/csv-importer
An example I've used in the csv file:
name,source,layer,lon,lat,number,street,unit,city,district,region,postcode,id,addendum_json_custom
123 JACKSON AVE,custom,address,-86.66,40.7666,344,JACKSON AVE,,PERU,,IN,46970,651ds651d651,"{ ""customInfo"":""Something Custom"" }"
123 S 600 E,custom,address,-86.66,40.7666,4503,S 600 E,,PIERCETON,,IN,46562,651ewd2332e,"{ ""customInfo"":""Something Custom"" }"
Be sure to use the double quotes in the addendum json as specified in the documentation.
If you are doing Points of Interest, then you may choose a different layer like venue.
You will have to configure the pelias.conf with the source of the files for inport and the api target to specify the source > layer.
As for installation, I've found the dockerized situation to be best for getting started.
https://github.com/pelias/docker
I am using Freemarker version 2.3.28. I don't specify my output format (output_format) anywhere in my templates or in configuration. Does that mean output format for all templates is set to HTML by default? If that's the case I believe ${value} will be always escaped?
By default the output_format of templates is undefined so, no auto-escaping will happen. It's like that for backward compatibility. To enable HTML auto-escaping, do one of these:
Set the incompatible_improvements configuration setting to at least 2.3.24 (but generally the higher the better), and the use ftlh file extension for your template files, instead of the traditional ftl. Then the ftlh files will have HTML auto-escaping.
If you keep using ftl file extension, you can just set the output_format configuration setting to HTML. So then that will be the default for all templates. If only some templates need auto-escaping, you can use the template_configurations setting to map different output formats depending on template path patterns.
See also: https://freemarker.apache.org/docs/pgui_config_outputformatsautoesc.html
If anyone know where can see different values (settings) of a parameter? For example, if we need to change a default value, which other options do we have to set.
Thanks
The default settings are located in the according .ned file of your module. If you have a setup for your simulation you're usually changing your parameters in the omnetpp.ini file.
The TicToc tutorial gives you all information according to this, especially TicToc 7 might be useful for you.
I tried in two ways，
1.I write properties file like sonar.language=php,go it didn't work.
2.I tried to change to sonar.languages=php,go and it scan all kinds of languages inculdes js,python and so on.
how can I make it to scan only specific several languages.
Thanks!
The best way is to configure sonar.inclusions and sonar.exclusions in a way that it will only include files you want to analyze. See documentation here https://docs.sonarqube.org/display/SONAR/Narrowing+the+Focus
I am trying to figure out the best way to organize a bunch of Ruby scripts to make it easier on the next person. One key thing is that there are multiple constant variables that need to be used across all scripts. Where should these be stored? Do I keep a separate file for these constants? Should I use YAML? I've never had to create a project with multiple Ruby source files interacting with each other, so I'm not sure as to what the best method of approach is here.
Thanks for the help.
I like to use a config.yaml file for all my constants. This makes it easy to set and change variables that are going to be used across different files. Then all you need to do is read in the file and set the variables. You can keep this file anywhere really, so long as anyone using the file has read permissions. All you have to do then is set the file path.
Hope this helps.
I like to do a config.yml or settings.yml, but I also allow the variables defined in config.yml to be overloadable by ENV variables (might be overkill in your situation).
It's might also be a good idea to set some defaults in your config loading/setting code.
As far as common functions/methods go... common.rb is a pretty good name or maybe shared.rb.