-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Frederik Ramm wrote:
| I'd be happy to hear from you about such areas of bad rendering,
| whether they are bugs in there renderer(s) or just things that are
| ugly for some reason.
It's kind of been mentioned already, but Dual carriageways should
Frederik Ramm skrev:
For super bonus points, do all this in XSLT.
Or while undergoing dental surgery.
Bye
Frederik
You surely misswrote that, Frederik ? You must have meant an instead
of dent ? ;) Having tried both, I can assure you the former is more
painfull - and for a longer
2008/3/21, Mike Collinson [EMAIL PROTECTED]:
Close roughly parallel ways, where the rendering of one way makes the other
way disappear. Swedish cycleways (God's gift to mankind) next to roads are
my nightmare, but I see other examples such as roads and railways/canals,
big roads next to little
I'm sure each of you must have some pet peeve with our map
rendering, some area you have mapped but which never looks right,
Render name of peaks curved (I think on Mapnik they do not get
rendered at all...).
Make use of the paved/unpaved attribute. Osmarender seems to deal
with this but I d
On Fri, Mar 21, 2008 at 12:23:57PM +0100, Frederik Ramm wrote:
I suggested to look into the rendering topic: Where are our current
problems in rendering
For me it's the routemap problem - how to represent multiple routes
sharing the same street/line/etc, for example bus routes, named or
Frederik Ramm wrote:
Hi,
I've been approached by a student of Geoinformatics who wants to
write her Master's Thesis about something OSM related.
I suggested to look into the rendering topic: Where are our current
problems in rendering, can they be solved by simply improving the
Hi,
I've been approached by a student of Geoinformatics who wants to
write her Master's Thesis about something OSM related.
I suggested to look into the rendering topic: Where are our current
problems in rendering, can they be solved by simply improving the
renderer(s) or will they need
Label placement. Sometimes the 'wrong' label gets precedent and one is
hidden. Use spring-force placement on the labels to jiggle them until
a fit is found.
Anchor a virtual spring to the lat/lng of a node with place:city,
name:Foo. The other end on to the label itself. Repeat with all the
Frederik Ramm wrote:
I'd be happy to hear from you about such areas of bad rendering,
whether they are bugs in there renderer(s) or just things that are
ugly for some reason.
Label placement (as Steve's flagged) and generalisation (i.e.
stretching the geographical truth to convey the
Frederik Ramm schrieb:
I'd be happy to hear from you about such areas of bad rendering,
whether they are bugs in there renderer(s) or just things that are
ugly for some reason.
I'm sure you are alluding to the redundant captions of ways that are
split up for bridges or of dual carriageways.
Maybe routing is an interesting area to research as it is related to
rendering and hinting or additional input from mappers.
This is all AFAIK, sorry if I'm wrong here:
So far we've seen a few examples of routing using OSM data but no real
'measurement' of how 'good' this routing actually is.
11 matches
Mail list logo
