Hi there,
I updated my bicycle-layer:
http://toolserver.org/~ti/map.png
slow-speed-areas:
- highway=living_street OR maxspeed<=30 get a lime background
access restrictions:
- forbidden ways are rendered in red, allowed ways in green and
designated ways in blue
- oneway-streets with two-way traffic for cyclists are rendered with
turquoise dots
- motorroad=yes/no is rendered with red/green squares
surface:
- paved/asphalt/cobblestone/paving_stones/concrete: thin black line
- unpaved/compacted/pebblestone/wood: thin white line
- gravel/ground/grass/dirt/sand/earth: thin red line
The style-file can be found at the old location:
/home/ti/styles/bicycle_combined.xml
Secondly, I'd like to renew my request for rendering the access-styles
in /styles/qa/ and /styles/qai/ that would help to improve routing in
OSM.
Regards,
Thomas
2010/11/6 Colin Marquardt <cmarqu42(a)googlemail.com>:
> previously, the hikebike style did not render islands, like in
> http://hikebikemap.de/?zoom=15&lat=51.11922&lon=17.02644&layers=B0000TTFFF
> This is now fixed in /home/cmarqu/hikebike_hstore.xml - please deploy.
> I think it's not necessary to dirty any tiles explicitly for this.
Mappers from two different countries have asked for support for hiking
symbols with black bars, and I finally implemented them in
/home/cmarqu/hikebike_hstore.xml
Cheers
Colin
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
As I understand it, our database/tile server (ptolemy) is higher spec than the
equivalent hardware at OSM.org, yet it performs much worse (e.g. at rendering
tiles). Is this correct?
If so, has anyone compared the indices on ptolemy's database to OSM's?
If that is not the problem, I would like to test performance without VxVM
between the filesystem and the disk. While Vx doesn't hurt performance with
MySQL, I noticed during testing that it significantly reduced import
performance with Postgres. I believe that was fixed by putting pg_xlog on a
separate (non-Vx) disk, but it may still be hurting read performance.
Testing this will require some downtime for conversion; based on the amount of
data, I would estimate about 8 hours to copy the data off and back again.
- river.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.16 (FreeBSD)
iEYEARECAAYFAkzmWEkACgkQIXd7fCuc5vLqAQCguzjEGzMXZTcRfQFKKISsw0hI
8ggAoMDmU+HOp4VPZBIp9SBuWrdY/Ua7
=TpV4
-----END PGP SIGNATURE-----
Hi,
Is there somewhere an accessible, up-to-date planet.osm on toolserver?
The only reference I found says 'no' but maybe that has changed in the
mean time:
https://wiki.toolserver.org/view/OpenStreetMap_server/Setup_notes
I have neither yet a concrete idea what to do with it (just some vague
thoughts), nor do I know how ressource-consuming osmosis is..
Regards,
Thomas
Hello,
I see that we are running in a problem if we integrate OSM-map in many,
many language versions of WP (with copies of JavaScript) and must than
change something like moving the script to an other server or want to
integrate some additional parameters like "pagename"... So it would be
nice to link to one central file. I get a hint that this is possible and
other extensions like hotcat goes also this way[1].
So, for testing I wrote:
var osm_proj_map='mapa';
var osm_proj_lang='pl';
importScriptURI
('http://de.wikipedia.org/w/index.php?title=Benutzer:Kolossos/Gadget-OSM.js&a…');
in my vector.js in pl.wp[2] and it works with full localisation and
reference to my Gadget-OSM.js[3] version in german WP.
The right place for the central file would be offcourse en.wp or de.wp
in the safe MediaWiki namespace.
Some things I don't know:
*Get we trouble with this centralise way? (Other geotemplates ... ?)
*Need we an maxage-parameter in the url?
*Do we need support of https like under [1]? I don't believe so.
*Is there perhaps a performance problem?
*Is there a way to work without the hard coding of project language?
I think we would have a big benefit especially for smaller language
versions, they have really problems to stay up-to-date, as example I can
find there for the geohack old URLs like http://stable.toolserver.org
and also http://tools.wikimedia.de/ .
But also the clean-up of the commons.js would be a benefit.
Comments?
Greetings Kolossos
[1]http://commons.wikimedia.org/wiki/Help:Gadget-HotCat#Installing_HotCat_on…
[2]http://pl.wikipedia.org/wiki/Wikipedysta:Kolossos/vector.js
[3]http://de.wikipedia.org/wiki/Benutzer:Kolossos/Gadget-OSM.js
Hi
We already have a lot of munin graphs about what tirex is doing:
<http://munin.toolserver.org/OSM/ptolemy/index.html#tirex>
But sometimes it's a good idea to have a deeper look at what tirex is
really doing right now (eg what all those missing tiles are that it
renders currently).
To do this, one usually needs login access to ptolemy to run
tirex-status. I now created a small util that pushes the current
insights to the web: <http://toolserver.org/~mazder/tirex-status/>
Have fun watching it rendering all those bw-* tiles :=)
Peter
Hi
I extended the render command line tool to support zoom level calculation:
/home/project/o/s/m/osm/bin/render \
--style /home/project/o/s/m/osm/p_osm/styles/bw-mapnik/osm-bw.xml \
--bbox 8.17,50.04,8.36,49.95 \
--zoom 12
To make Style-Designers life easier it's better to add
/home/project/o/s/m/osm/bin/ to the path by placing the following lines
into the .bashrc file in your home dir:
PATH=$PATH:/home/project/o/s/m/osm/bin
export PATH
STYLES=/home/project/o/s/m/osm/p_osm/styles
export STYLES
Also its good to have some bboxes as shell variables. I have a file
bboxes in my homedir that looks like this:
BBOX_DEUTSCHLAND=5.56,55.04,15.35,47.15
BBOX_EUROPA=-17.14,56.37,27.61,35.34
BBOX_MAINZ_WIESBADEN=8.08,50.11,8.44,49.95
BBOX_MAINZ=8.17,50.04,8.36,49.95
BBOX_BERLIN=12.88,52.67,13.8,52.35
BBOX_ALZEY=8.03,49.79,8.21,49.7
BBOX_ERBENHEIM=8.27,50.07,8.32,50.04
with areas I'm interested in. This file is loaded on login using a line
like this in my .bashrc:
you can then do
render --style $STYLES/bw-mapnik/osm-bw.xml --bbox $BBOX_MAINZ --zoom 12
and get your map.
Peter
Hello,
we are now live with OpenStreetMap-integration in no-, fr- and de.wp.
A first version of english documentation can be found here:
http://de.wikipedia.org/wiki/Hilfe:OpenStreetMap/en
The interface is now translated over translatewiki:
http://svn.wikimedia.org/viewvc/mediawiki/trunk/extensions/ToolserverTools/…
So you can help to localize the application.
You can choose for the interface an other language (uselang) than for
the map:
http://toolserver.org/~kolossos/openlayers/kml-on-ol.php?lang=de&uselang=te…
(german map with interface in well-known telugu language ;-))
The language selection under options is going over 190 languages (all
Wikipedias with >1000 articles)
If the zoom level is between 0 and 6 you get automatically an osm-map
with your locale names.
We have now JIRA for bug reports/feature requests:
https://jira.toolserver.org/browse/WPONOSM
It's also in the pipeline to activate the map in en.wp:
http://en.wikipedia.org/wiki/Wikipedia:Gadget/proposals#OSM
(At the beginning only as gadget because we want to have time for
optimisation on server side.) We should also talk about what's the
better way: Little OSM-Link now or something bigger like maps-extension
later?
----
So perhaps it's the right time to expand the tool in more wikipedia
versions.
If you want to have it in your wikipedia language we have some wishes
and hints for maximum success:
*Inform the other admins and people from projects like
Wikipedia:WikiProject_Geographical_coordinates
* Write in your Wikipedia a little help-page under
[[Help:OpenStreetMap]] (use local name for namespace "Help") so we can
link from the map to this page. Please set an interwikilink on german
helppage:
http://de.wikipedia.org/wiki/Hilfe:OpenStreetMap
*Have in mind that it depends on the browser cache of the user until
they see something from the change in Commons.js . So on the first day
not everybody see something without clearing cache.
*If the Wikipedia is larger than 100.000 articles please give us an
information on this list so we are not so surprised by additionally load
and can spread the dates of turning-on.
*Please use this chance to make a little bit advertisement for Wikipedia
coordinates and OpenStreetMap.
**Bring a little notice to the main page
**Set perhaps the first days a red "new!" beside the map link.
**Perhaps you have contact to local press...
(We will profit if OpenStreetMap would be more popular and not all
wikipedia users known that there can be something useful behind the
coordinates in Wikipedia)
Greetings Kolossos
(Thanks to all Supporters: Peter Körner, River, AlexRK, Magnus,
dispenser, Raymond, 32X, Markus B., ALE!, ... and the "Verein")
