Hello People! <br>I have a question. <br><br>This summer I met someone of use-it <a href="http://www.use-it.be/">http://www.use-it.be/</a> belgium at the OpenStreetMap State of the Map. <br><br>Use-IT creates free paper maps for youth-hostels targeting a specific audience. Currently they are using the tool chain: <br>
OpenStreetMap website -> export svg -> import in Illustrator -> lots and lots of manual labour and finally produce eye candy like this: <br><a href="http://www.use-it.be/_files/inlineuploads/pages/MAP_O_Brussels.pdf">http://www.use-it.be/_files/inlineuploads/pages/MAP_O_Brussels.pdf</a> <br>
<br>Recently, the contact reached out to me. He could not find a solution within the OpenStreetMap community or it's related technology partners. Now I am helping him out looking at new ways to speed up their labour process.<br>
<br>I am investigating the qGIS pdf export and it looks promising in combination with the OpenStreetMap plugin but texts come out as letter-outlines instead of fonts and the PDF layers structure is hard to work with. I would like to know if the developers of the layouter/export would be interested in about 2 weeks of work to enhance the layout manager to something that creates pdf that is perfectly fit for post-processing. <br>
<br><font class="Apple-style-span" color="#009900"><span class="Apple-style-span" style="color: rgb(0, 0, 0); ">****************</span>*1. PROCESSING PROBLEM*<br> This remains almost impossible - only supercomputers are able to<br>
deliver an svg-file of a city of reasonable size, and even that is<br> still only a 50% shot. It took us a full night to render a city, and<br> were able to get there only with one of about ten available<br> xml-rulesheets (called z12). How could this be tackled?</font><div>
<font class="Apple-style-span" color="#3333FF"><br></font></div><div>This one is tackled with the OSM plugin in combination with the PDF export. As far as I can see, the way osm data is presented in qGIS is simplified, but this is good! We don't need shading, outlines and a whole lot of fencies in this fase. The eye-candy will be created in Illustrator. So, as far as I can see; qGIS tackles this issue.</div>
<div><br></div><div><font class="Apple-style-span" color="#009900"><span class="Apple-style-span" style="color: rgb(0, 0, 0); ">****************</span>*2. LAYER PROBLEM*<br> The svg does not contain separate layers with a clear content (like<br>
'parks', 'roads', 'rivers'). Only the layers 'Map' and 'Map<br> Decoration' appear, but all the information is thrown together in<br> the layer 'Map'. You say it's a matter of someone finding the time<br>
to improve this - but who is the best person to address?</font></div><div><br></div><div>In the OpenStreetMap data format, there are basically 3 layers: points, lines and polygons. The "real" layering is organised in attributes called tags. To be more generic; It would be good to push elements to a pdf layer based upon grouping by attribute. In case of openstreetmap data, it would mean applying some rules to strip out the tags into the required attributes and then in the layout manager tell the pdf export to "group by attribute column A"<br>
<br></div><div><br><font class="Apple-style-span" color="#009900"><span class="Apple-style-span" style="color: rgb(0, 0, 0); ">****************</span>*3. TYPOGRAPHICAL PROBLEM*<br> Layouters prefer to work with Adobe Illustrator to make maps. It's<br>
what they know best, and Inkscape is just not as good yet.<br> Osmarender renders svg files. It is possible to open an svg-file in<br> Illustrator, but then you get typographical problems, illustrated<br> below. Our question: could Osmarender be made to deliver an eps-file<br>
(always works in Inkscape AND Illustrator) instead of an svg?</font><br><br><font class="Apple-style-span" color="#009900"> This is what happened to a small part of Antwerp (Belgium):</font></div><div><font class="Apple-style-span" color="#009900"><br>
SVG IN INKSCAPE<br> > opens fine<br> > text is fully editable<br> > see image 'svg_inkscape'<br><br> SVG IN ILLUSTRATOR<br> > opens upside down and with mistakes<br> > text is still editable as text (so it's not flattened), but does<br>
not appear on a horizontal path in the street. Furthermore, every<br> letter is on a different path, so it's impossible to select an<br> entire word.<br> > see images 'svg_illustrator' and 'svg_illustrator_detail'<br>
<br> SVG SAVED AS EPS IN INKSCAPE AND THEN OPENED IN ILLUSTRATOR<br> > opens fine<br> > text is flattened and not editable anymore, and therefore useless<br> for layout<br> > see images 'eps_illustrator' and 'eps_illustrator_detail'</font></div>
<div><font class="Apple-style-span" color="#009900"><br></font>**************</div><div>Again; as far as I can see, it is qGIS to the rescue! The whole process of going from svg through inkscape to Adobe Illustrator is greatly smartened by using PDF export instead. Only one thing is needed here: to export fonts as text and not as letter contours. Horizontal text would be excelent. In that way, the designers can throw away what they do not need and use Illustrators smart tools to make text follow lines and so on.</div>
<div><br></div><div>Now, what I would like to know (my contact has some funds to spend on this topic):</div><div><br></div><div>- Who can I address with my enhancement questions?</div><div>- Who would be willing to spend about 40 hours on this and at what rate?</div>
<div>- Would this fit the roadmap of qGIS development?</div><div>- Would others like to join up and provide extra funding for this?</div><div><br></div><div>I am curious to see what responses will be coming!</div><div><br>
</div><div>Kind regards,</div><div><br></div><div>Milo van der Linden</div><div>+31616598808</div><div><br></div><div><br></div><div><br></div>