Re: [OSM-dev-fr] test osmose pour junction=roundabout sans highway= ?
2011/8/19 Hendrik Oesterlin hendrikmail2...@yahoo.de: Bonjour, Je suis tombé dernièrement sur un rond point (ou giratoire...) qui portait bien junction=roundabout mais aucun highway= Je crois que osmose ne détecte pas cela, peut-être que ca vaut le coup de vérifier? Je viens de regarder, et c'est normalement bien détecté par osmose. Il s'agit de l'item 3040 (highway roundabout), visible là: http://osmose.openstreetmap.fr/map/cgi-bin/index.py?item=3010 http://osmose.openstreetmap.fr/cgi-bin/info.py?item=3010 J'espère que ton rond-point était bien détecté par cet item. Merci, Jocelyn ___ dev-fr mailing list dev-fr@openstreetmap.org http://lists.openstreetmap.org/listinfo/dev-fr
Re: [osmosis-dev] keyValueList option, and latest node versions
On 19 August 2011 16:10, Andrew Byrd wrote: Hi Simon, Yes, the tag filter is intended to provide more flexible filtering all within one task, but I think there was a decision not to unnecessarily remove any existing tasks. Ah, yes of course that does make sense not to break existing systems using that option. If the presence of several tag-based filtering tasks might cause confusion, we could always update the documentation to explain this situation without removing any tasks. The --tag-filter is much more clearly documented (e.g. the escape sequences) and does seem to provide a super-set of the --(node|way)-key(-value)? filter tasks. I wonder if the key and value tasks are internally re-written as a tag-filter class ? If so, the documentation could say that., and whether it is preferred to use --tag-filter? -Andrew On 08/18/2011 11:58 AM, Simon Nuttall wrote: Catching up with this old email... To me it looks like the --tag-filter task makes the --node-key --node-key-value --way-key --way-key-value tasks redundant as these appear to me to be equivalent: osmosis ... --node-key keyList=k1,k2,... osmosis ... --tag-filter accept-nodes k1=*,k2=*,... and osmosis ... --node-key-value keyValueList=k1.v1,k1.v2,k2.v3,... osmosis ... --tag-filter accept-nodes k1=v1,v2,k2=v3,... Should have been: osmosis ... --node-key-value keyValueList=k1.v1,k1.v2,k2.v3,... osmosis ... --tag-filter accept-nodes k1=v1,v2 k2=v3,... (i.e. a space rather than comma in the tag-filter option between v2 and k2) similarly for way-key and way-key-value options. If this is so, I think it would be worth deprecating the --(node|way)-key(-value)? tasks, and updating the wiki to say so. http://wiki.openstreetmap.org/wiki/Osmosis/Detailed_Usage#--node-key-value_.28--nkv.29 Simon / CycleStreets Thread started: http://lists.openstreetmap.org/pipermail/osmosis-dev/2010-July/thread.html Simon ___ osmosis-dev mailing list osmosis-dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/osmosis-dev
Re: [OSM-dev] Free OSM tag queries, WMS and WFS
Hi, Probably only Mapserver supports exactly this out-of-the-box. I mean the combination where user can do free SQL selections from PostGIS hstore column and WMS and WFS are working hand in hand so that the selected data can be either visualised on a map (WMS) or downloaded as vector data (WFS). But it is mainly hstore that is special. On the other hand, with the OSM data model the only comprehensive way to find data in to go to the tags. Because all that is needed is to tranfer the user input into the SQL that is made against PostGIS it should be easy to add hstore query support for other WMS servers as vendor option. I understand if developers do not want to do it. It opens the system for SQL injection danger and hstore is a specific PostgreSQL feature and same system would not work with Oracle or other data sources. I have used the variable subsititution/runtime substitution mechanism http://mapserver.org/cgi/runsub.html http://mapserver.org/mapfile/variable_sub.html The sql parameter in the request is used as a SQL WHERE clause which selects the data from the PostGIS table. If sql parameter is not given the default values are used - amemity=toilets, highway=motorway, and building=yes for OSM points, lines, and polygons, respectively. I have made a simple validation rule for the sql parameter but I am pretty sure it is not good enough for some clever SQL injection. Sql parameter can naturally be used for all the data that exists in the database and not only for OSM data. When it comes to the vector data downloads, Mapserver 6.0 gives interesting possibilities for that. In addition to the compulsory GML that WFS services are generating by default, Mapserver should now be able to send the output data in any of the vector formats supported by OGR for writing. They are marked as Creation=Yes on this list http://gdal.org/ogr/ogr_formats.html Moreover, one of those formats is GPSBabel http://gdal.org/ogr/drv_gpsbabel.html This means that Mapserver WFS can be configured to output WFS data in any of the formats which are marked as Write=yes on this list http://www.gpsbabel.org/capabilities.shtml can be used. I have had no time yet to play with GPSBabel output yet but if it works as documented it should be rather easy to make a service that lets user to select OSM POIs with amenity=resturant and cuisine=pizza and get the output as a Garmin POI file with coordinates, restaurant names and phone numbers. Or all the noname streets or FIXMEs. As I said, apart from the hstore and tags using filters with WMS map layers is nothing special. It is also a non-mandatory feature of the standard. Same OGC filters can be used both for WMS and WFS and the most simple example looks like this filter= Filter xmlns:ogc=http://www.opengis.net/ogc; PropertyIsEqualTo PropertyNametows:amenity/PropertyName Literalwaste_basket/Literal /PropertyIsEqualTo/Filter Because OGC filters are not so nice to write some WMS servers have an alternative for those. Geoserver is using an much-easier-to-write CQL_QUERY system, and QGis Mapserver seems to use FILTER. I know for sure that Geoserver cannot query anything from hstore column. I do not know if QGis Mapserver can use stuff like sql=(tags @'highway=primary') AND not (tags ? 'maxspeed') in FILTER and I have never tried Mapnik OGC server. -Jukka Rahkonen- BG wrote: hej, that's great and usable. does it work only with the mapserver wms or does it too with any other wms? On 18.08.2011 16:37, Jukka Rahkonen wrote: Hi, This is not invented here and thus perhaps not so interesting, but anyway. By using copy-paste and a browser it is possible 1. Select by OSM tags all the primary highways and show them on a map 188.64.1.61/cgi-bin/ms_ows?REQUEST=GetMapSERVICE=WMSVERSION=1.1.1WIDTH=563HEIGHT=437LAYERS=sea,borders,osm_viivatTRANSPARENT=TRUEFORMAT=image/pngBBOX=-369151.98300283286,6597900.0,1511076.628895184,8057331.444759207SRS=EPSG:3067STYLES=sql=(tags @ 'highway=primary') 2. Select by OSM tags all the primary highways without maxspeed tag. Hint for a mappers to improve quality? 188.64.1.61/cgi-bin/ms_ows?REQUEST=GetMapSERVICE=WMSVERSION=1.1.1WIDTH=563HEIGHT=437LAYERS=sea,borders,osm_viivatTRANSPARENT=TRUEFORMAT=image/pngBBOX=-369151.98300283286,6597900.0,1511076.628895184,8057331.444759207SRS=EPSG:3067STYLES=sql=(tags @ 'highway=primary') AND not (tags ? 'maxspeed') 3. Download the data that was used for rendering the previous primary way without maxspeed tag map. 188.64.1.61/ms_ows?service=wfsversion=1.0.0request=getfeaturetypename=osm_viivatsql=(tags @ 'highway=primary') AND not (tags ? 'maxspeed') No own development done, just playing with existing possibilities of MapServer WMS and WFS and osm2pgsql with hstore. Actually data interoperability without imports is demostrated as well because layers sea and borders are not OSM data. It is a live service, feel free to try other free tag queries. -Jukka Rahkonen- ___ dev
Re: [OSM-dev] Free OSM tag queries, WMS and WFS
Jukka Rahkonen jukka.rahko...@latuviitta.fi wrote: No own development done, just playing with existing possibilities of MapServer WMS and WFS and osm2pgsql with hstore. Would you mind sharing your Mapfile? Sven -- How to prevent Java from forking? Use a spoon. (Found on http://slashdot.org) /me is giggls@ircnet, http://sven.gegg.us/ on the Web ___ dev mailing list dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/dev
[OSM-dev] How to check for database updates after minutely Mapnik Installation?
Hello All, I have installed minutely mapnik which I think is working and updating database of postgresql. But can anyone help me in checking that How to check the last and latest updates in the database, and when and what changes has been made last time. also minutely mapnik is updating the database, I have installed OSM Tile Server but I am not using mod_tile or tirex. So I want to know how tiles will be generated automatically.? Do I need to write any script for it or is there any procedure available? -- Parveen Arora www.parveenarora.in E-Mail: m...@parveenarora.in ___ dev mailing list dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/dev
Re: [OSM-dev] How to check for database updates after minutely Mapnik Installation?
Am 19.08.2011 13:29, schrieb Parveen Arora: Hello All, I have installed minutely mapnik which I think is working and updating database of postgresql. But can anyone help me in checking that How to check the last and latest updates in the database, and when and what changes has been made last time. Well, the obvious think may be: change sth. in your area and check it gets distributed to your database. You may also open one of the latest osc files on planet.osm.org and take a look if is reflected in your database. also minutely mapnik is updating the database, I have installed OSM Tile Server but I am not using mod_tile or tirex. So I want to know how tiles will be generated automatically.? Well, they won't. You can instruct osm2pgsql to create a so-called dirty-tile-list which then gets fed to another tool that modifies the mtime of the tiles on disk. mod_tile sends tiles that have been modified like this to tirex where they get re-rendered. If your tileset is small, you may go another route. Peter ___ dev mailing list dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/dev
Re: [OSM-dev] How to check for database updates after minutely Mapnik Installation?
On Fri, Aug 19, 2011 at 5:10 PM, Peter Körner osm-li...@mazdermind.de wrote: Well, the obvious think may be: change sth. in your area and check it gets distributed to your database. You may also open one of the latest osc files on planet.osm.org and take a look if is reflected in your database. Is there any query to check the latest changes in the database? You can instruct osm2pgsql to create a so-called dirty-tile-list which then What is the meaning of dirty tiles this term always confuses me. gets fed to another tool that modifies the mtime of the tiles on disk. Which tool will do this work? mod_tile sends tiles that have been modified like this to tirex where they get re-rendered. Actually I am making a package to install OSM Tile Server automatically in which I have not included tirex. So Can I do that without using tirex or I need to include it and use it? If your tileset is small, you may go another route. means something like to write a script and put that in corn for automatic updates. Thank You. -- Parveen Arora www.parveenarora.in E-Mail: m...@parveenarora.in ___ dev mailing list dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/dev
Re: [OSM-dev] How to check for database updates after minutely Mapnik Installation?
On Fri, Aug 19, 2011 at 1:10 PM, Parveen Arora m...@parveenarora.in wrote: You can instruct osm2pgsql to create a so-called dirty-tile-list which then What is the meaning of dirty tiles this term always confuses me. A dirty tile is a map image that has been marked as being out-of-date, and therefore needs to be redrawn when the system gets the chance. Mod_tile does this by having a file (/var/lib/mod_tile/planet-import-complete) whose modification timestamp is the last time the planet database was updated. When it serves a tile, it checks the timestamp on the tile and makes sure the tile is newer than the timestamp on planet-import-complete. If it is older, it asks renderd or tirex to re-render the tiles. When you are running minutely updates, it's common to use the expiry lists generated by osm2pgsql to expire the tiles that need changing. Either the tiles are rendered directly, or they can be marked dirty. A tile can be marked as dirty by changing the timestamp to be really old (amusingly, in OSM terms this means somewhere in 2000, which may as well be the start of all time for us) so that it appears to be older than the database import. That way it'll get re-rendered automatically next time it's viewed. When you make your own system not using tirex or renderd, you will want to only re-render the tiles that need to be (rather than them all). You'll need to take the list the osm2pgsql outputs, and then either re-render them all in a script, or keep track of which ones are needing re-rendering and do it later. If you update every minute then sometimes you won't be able to keep up, hence the more complicated approaches involving timestamps. Cheers, Andy ___ dev mailing list dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/dev
Re: [OSM-dev] update tiles - wmsc/wmts
i thought the expire-list works only with mod_tile?! I have tirex and mod_tile running but i also try to use the ogc standard tiled map service - and here i thought it couldn't work because of different tiles and tilesizes. Am i wrong? i think so ... (I am sorry because of my stupid questions but this theme is a unknown world for me, please forgive :) ) On 19.08.2011 16:14, Peter Körner wrote: Shouldn't it be enough to delete old tiles? The wmsc should then refetch the tile, shouldn't it? You can get a list of affected tiles using the osm2pgsql expire-list ___ dev mailing list dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/dev
[OSM-dev] Optimizing map tile trees
I am relaying this question by Michael Katz from help.openstreetmap.org: --- quote -- I am building my own map tiles using the OSM data, with PostGIS and Mapnik (as explained, for instance, here). I am going to be serving these tiles from my own server, so I have a lot of flexibility in how I process a request for a tile. I have a few closely related questions: (1) When I'm running the script to generate the tiles (generate_tiles_multiprocess.py, in my case), for a huge percentage of the output tiles it writes Empty Tile to the script output line. My understanding is that Empty Tile actually means a tile of just one color. So it might be all blue in a water area, or all green in a park area, or all gray in some other area. My question is whether there is a deeper meaning to Empty Tile, specifically whether it means that all sub-tiles generated at higher levels will also be empty? For instance, if I generate a level 16 tile that is a gray Empty Tile, does it mean when I generate level 17, and I am generating the four level 17 tiles that correspond to that one level 16 tile, that those four tiles will also be gray Empty Tile, and the same for the 16 sub-tiles at level 18? Or, in contrast, is it possible for features that weren't visible in the level 16 tile to appear in that area at level 17 or level 18? Another way of saying it: Does Empty Tile mean that the tile is empty all the way down? (2) Regardless of the answer to question to (1) above, suppose I have generated a full tree of tiles for a given area, all the way to level 18. Suppose there is a tile on level 15 that is all gray, and it turns that the four corresponding tiles on level 16, the 16 corresponding tiles on level 17, and the 64 corresponding tiles on level 18, are also all gray. A natural optimization of the tree is just to delete those level 16, 17, and 18 tiles (84 total tiles) from the tree altogether. Then, when the server goes to serve a tile and it's not present in the tree, it knows to look up to the parent levels of the tree as far as necessary until it finds a tile, and it knows that that tile (the all gray tile in this case) is good to use for the originally requested tile. My questions are: what is that optimization called? Is it commonly used? Is it discussed somewhere? (3) Finally, I notice that many of the output tiles are very simple. First of all there is the huge number of one-color tiles. But there are also many two-color tiles with a very simple shape, such as a single line dividing a blue area from a gray area. I see that the one-color tiles are 103 byte .png files. The simple two-color tiles are typically anywhere from 1.0k to 1.5k. So it seems like a natural compression technique for these would be to use just three bytes ( R, G, B ) for the one-color files, and a simple run-length encoding scheme for the two-color files. Of course, to make this really save space on the disk it would be necessary to combine lots of these small files into some kind of multi-file that would be cached in memory on the server. But anyway for both storage and transmittal (as well as helping reduce cache missing when actually serving the data) it seems like there are many optimizations like this that could be employed. Can you tell me if these optimizations make sense, and where I can find documentation of how others have implemented stuff like this? -- Frederik Ramm ## eMail frede...@remote.org ## N49°00'09 E008°23'33 ___ dev mailing list dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/dev
Re: [OSM-dev] Optimizing map tile trees
... For instance, if I generate a level 16 tile that is a gray Empty Tile, does it mean when I generate level 17, and I am generating the four level 17 tiles that correspond to that one level 16 tile, that those four tiles will also be gray Empty Tile, and the same for the 16 sub-tiles at level 18? Or, in contrast, is it possible for features that weren't visible in the level 16 tile to appear in that area at level 17 or level 18? Another way of saying it: Does Empty Tile mean that the tile is empty all the way down? This of course depends entirely on how you have written the style definitions. Even if they are designed such that no new features are defined at subsequent zoomlevels starting at a certain scale (and I'm quite sure that the Mapnik XML powering OSM.org tiles is not designed this way), it would be difficult to determine whether an empty tile is really empty all the way down. You would still have situations where new objects are rendered due to different collision detection results at different scales. Say Mapnik prevented a label or something from being rendered on a tile at zoom level 16 because of another nearby label and it happened to result in an empty tile. Zoom in to 17, the scale is different and there is no longer a collision and a piece of the previously-unrendered label could render on a sub-tile of an empty tile. Avoiding this would probably require separate check of the full data for each tile, including a buffer region around the tile. Or perhaps this could be a rare enough situation that a few cut-off labels and icons are a reasonable risk. -- AJ Ashton ___ dev mailing list dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/dev
[josm-dev] Strange re-use of nodes
Hi, these changsets by user max60watt (who hasn't yet responded to an inquiry) http://www.openstreetmap.org/browse/changeset/9052036 http://www.openstreetmap.org/browse/changeset/8726790 are strange. In the first changeset, a roundabout is drawn with much more detail than usual, and the nodes used for that are all version 2 - and version 1 of the node is somewhere far away, sometimes in Africa. Strangely this does not have an adverse effect on the original place, probably because the node wasn't in use. I'll have a look at the history to try and get to the bottom of this but maybe someone here has an idea? Could the user have been working with a buggy plugin? Bye Frederik -- Frederik Ramm ## eMail frede...@remote.org ## N49°00'09 E008°23'33 ___ josm-dev mailing list josm-dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/josm-dev
