I write this in english as I do not understand Esperanto.
I don’t know exactyl what you are about to achiev, but the map localisation code I use in Mapnik German will certainly work for esperanto as well if target language is set to “eo”.
I want vector data. I do not want to have a big dataset of raster data. So I have script which is downloading data from Overpass.
Not only name:eo, but also some places https://github.com/dotevo/esperantmapo/tree/gh-pages/eo
Another languages like Ido, Lojban are because it was easy to add.
The fact, that I currently use my l10n code for rendering raster-tiles does not make it raster-data only.
It is however limited to PostgreSQL/Postgis as a data source, which might be a showstopper for using it in conjunction with vector tiles, where PostgreSQL might not be used anymore.
I already thought about reimplementing the PL/pgSQL parts in python to get rid of the PostgreSQL dependency.
BTW, my code is way more sophisticated than just using a name: approach. See
the videos of my talks (english and german) for details
Discussion
Comment from giggls on 4 May 2017 at 11:41
Hello,
I write this in english as I do not understand Esperanto.
I don’t know exactyl what you are about to achiev, but the map localisation code I use in Mapnik German will certainly work for esperanto as well if target language is set to “eo”.
https://github.com/giggls/mapnik-german-l10n
Regards
Sven
Comment from Dotevo on 4 May 2017 at 12:00
I want vector data. I do not want to have a big dataset of raster data. So I have script which is downloading data from Overpass. Not only name:eo, but also some places https://github.com/dotevo/esperantmapo/tree/gh-pages/eo
Another languages like Ido, Lojban are because it was easy to add.
Comment from giggls on 4 May 2017 at 12:46
The fact, that I currently use my l10n code for rendering raster-tiles does not make it raster-data only.
It is however limited to PostgreSQL/Postgis as a data source, which might be a showstopper for using it in conjunction with vector tiles, where PostgreSQL might not be used anymore.
I already thought about reimplementing the PL/pgSQL parts in python to get rid of the PostgreSQL dependency.
BTW, my code is way more sophisticated than just using a name: approach. See the videos of my talks (english and german) for details
https://github.com/giggls/mapnik-german-l10n/wiki
Sven
Comment from Gabri1953 on 7 May 2017 at 08:42
very interesting.