Re: [josm-dev] josm, changelogs and release processes
On Fri, 30 Mar 2012 01:30:47 +0200, Simon Legner wrote: Hi! On 30/03/12 01:06, shirish शिरीष wrote: Is it possible to get summarized blogs from 2k5 onwards when JOSM started its development [2] ? Of course it is possible, but it requires someone performing this task. I would like to note that one the one hand it is very cumbersome (as one has to go through every revision and figure out its relevance), and on the other hand the use of changes from 2005 are very limited. My guess is that nobody will step in for this task. For the Debian report, you could comment that the changelog is available since 2012 and will (most likely) be continued. I'm not sure whether that suffices. If the changelog was available in the SVN repositories, like most projects do, I'd surely install it. But, I don't really want to have headaches trying to parse a wikipage and generate a nicely formatted text file. David (the maintainer who negated the bugreport) -- . ''`. Debian developer | http://wiki.debian.org/DavidPaleino : :' : Linuxer #334216 --|-- http://www.hanskalabs.net/ `. `'` GPG: 1392B174 | http://deb.li/dapal `- 2BAB C625 4E66 E7B8 450A C3E1 E6AA 9017 1392 B174 signature.asc Description: PGP signature ___ josm-dev mailing list josm-dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/josm-dev
Re: [josm-dev] josm, changelogs and release processes
On Fri, 30 Mar 2012 10:36:49 +0200, Simon Legner wrote: Hi David! No need to CC me :) On 30/03/12 09:28, David Paleino wrote: If the changelog was available in the SVN repositories, like most projects do, I'd surely install it. But, I don't really want to have headaches trying to parse a wikipage and generate a nicely formatted text file. A plain text version is available under [1]. Yes, but that contains hyperlinks, which make no sense when out of context. Sure, that's not a showstopper, but it would be better if I don't have to make sure I update the changelog at each new release I package (I might forget it). David -- . ''`. Debian developer | http://wiki.debian.org/DavidPaleino : :' : Linuxer #334216 --|-- http://www.hanskalabs.net/ `. `'` GPG: 1392B174 | http://deb.li/dapal `- 2BAB C625 4E66 E7B8 450A C3E1 E6AA 9017 1392 B174 signature.asc Description: PGP signature ___ josm-dev mailing list josm-dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/josm-dev
[Taginfo-dev] New taginfo -- segfault
Hello people, I just updated the Italian instance of taginfo [0], and now tagstats segfaults. [0]: http://taginfo.hanskalabs.net/ While I could drop all my customizations, and put them into the config.json, my limited C++-fu doesn't let me understand what's going on here: $ ./tagstats -d -t 47.2 -l 6.4 -b 35.2 -r 18.6 ~/osm-dumps/italy.osm.pbf taginfo-db.db sizeof(value_hash_map_t) = 88 sizeof(Counter) = 12 sizeof(key_combination_hash_map_t) = 88 sizeof(user_hash_map_t) = 88 sizeof(GeoDistribution) = 16 sizeof(KeyStats) = 320 string_store: chunk_size=10MB chunks=1 memory=10MB bytes_in_last=0kB VmPeak: 125592 kB VmSize: 125592 kB init done Errore di segmentazione $ (roughly, Segmentation error). Running it through gdb gives this, which is quite obscure to my eyes: Program received signal SIGSEGV, Segmentation fault. 0x00408555 in std::__uninitialized_fill_n_agoogle::sparsegroupunsigned short, (unsigned short)48, google::libc_allocator_with_reallocunsigned short *, unsigned long, google::sparsegroupunsigned short, (unsigned short)48, google::libc_allocator_with_reallocunsigned short , google::libc_allocator_with_reallocgoogle::sparsegroupunsigned short, (unsigned short)48, google::libc_allocator_with_reallocunsigned short() (gdb) bt full #0 0x00408555 in std::__uninitialized_fill_n_agoogle::sparsegroupunsigned short, (unsigned short)48, google::libc_allocator_with_reallocunsigned short *, unsigned long, google::sparsegroupunsigned short, (unsigned short)48, google::libc_allocator_with_reallocunsigned short , google::libc_allocator_with_reallocgoogle::sparsegroupunsigned short, (unsigned short)48, google::libc_allocator_with_reallocunsigned short() No symbol table info available. #1 0x00418e31 in std::vectorgoogle::sparsegroupunsigned short, (unsigned short)48, google::libc_allocator_with_reallocunsigned short , google::libc_allocator_with_reallocgoogle::sparsegroupunsigned short, (unsigned short)48, google::libc_allocator_with_reallocunsigned short ::_M_fill_insert(__gnu_cxx::__normal_iteratorgoogle::sparsegroupunsigned short, (unsigned short)48, google::libc_allocator_with_reallocunsigned short *, std::vectorgoogle::sparsegroupunsigned short, (unsigned short)48, google::libc_allocator_with_reallocunsigned short , google::libc_allocator_with_reallocgoogle::sparsegroupunsigned short, (unsigned short)48, google::libc_allocator_with_reallocunsigned short , unsigned long, google::sparsegroupunsigned short, (unsigned short)48, google::libc_allocator_with_reallocunsigned short const) () No symbol table info available. #2 0x00419446 in google::sparsetableunsigned short, (unsigned short)48, google::libc_allocator_with_reallocunsigned short ::resize(unsigned long) () No symbol table info available. #3 0x00424309 in TagStatsHandler::node(boost::shared_ptrOsmium::OSM::Node const const) () No symbol table info available. #4 0x00426cf5 in void Osmium::Input::PBFTagStatsHandler::parse_dense_node_groupvoid (TagStatsHandler::*)(boost::shared_ptrOsmium::OSM::Node const const)(OSMPBF::PrimitiveGroup const, OSMPBF::StringTable const, void (TagStatsHandler::*)(boost::shared_ptrOsmium::OSM::Node const const)) () No symbol table info available. #5 0x00429801 in Osmium::Input::PBFTagStatsHandler::parse() () No symbol table info available. #6 0x00412118 in void Osmium::OSMFile::readTagStatsHandler(TagStatsHandler) () No symbol table info available. #7 0x0040676b in main () No symbol table info available. (gdb) Any hint on what could've gone wrong? I'm currently at ab2cca4d45f61071402c7e644f70d66a386b421e. Thank you very much, David -- . ''`. Debian developer | http://wiki.debian.org/DavidPaleino : :' : Linuxer #334216 --|-- http://www.hanskalabs.net/ `. `'` GPG: 1392B174 | http://deb.li/dapal `- 2BAB C625 4E66 E7B8 450A C3E1 E6AA 9017 1392 B174 signature.asc Description: PGP signature ___ Taginfo-dev mailing list Taginfo-dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/taginfo-dev
[Taginfo-dev] Resizing the map tab (was: Re: New taginfo -- segfault)
On Sun, 22 Jan 2012 20:25:42 +0100, David Paleino wrote: Hello people, I just updated the Italian instance of taginfo [0], and now tagstats segfaults. [..] Never mind, I had a process eating up all my ram, and tagstats used all the available swap.. so it was killed :) Now it works beautifully. The only problem I see is that the Map tab doesn't get the same height as the contained image. http://taginfo.hanskalabs.net/keys/source%3Amaxspeed?filter=all#map David -- . ''`. Debian developer | http://wiki.debian.org/DavidPaleino : :' : Linuxer #334216 --|-- http://www.hanskalabs.net/ `. `'` GPG: 1392B174 | http://deb.li/dapal `- 2BAB C625 4E66 E7B8 450A C3E1 E6AA 9017 1392 B174 signature.asc Description: PGP signature ___ Taginfo-dev mailing list Taginfo-dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/taginfo-dev
Re: [josm-dev] new package repository for Ubuntu
On Mon, 26 Dec 2011 04:30:27 +0100, colliar wrote: Am 25.12.2011 09:42, schrieb David Paleino: On Sun, 25 Dec 2011 05:59:17 +0100, Paul Hartmann wrote: On 12/25/2011 02:01 AM, David Paleino wrote: On Tue, 13 Dec 2011 14:19:25 +0100, Paul Hartmann wrote: [..] Therefore the Ubuntu distribution model with fixed versions for half a year isn't really suitable for our project. (May be different on Debian, where you can install from unstable (?).) or testing ( or backports ?) It depends -- from unstable you always get the latest JOSM. In testing you have a version of josm which makes the josm-plugins package installable. Personally I don't use it myself (while I maintain it), because I use the packaged josm + plugins downloaded from inside the program. I cannot speak for backports, see below. Truly speaking, you could this in Ubuntu too -- just add the newest repository, and pin josm to be installed from there. In unstable I upload the package as soon as I get some spare time _and_ I notice there is a new version -- that usually means that JOSM in Debian can be at most 2-3 days delayed from upstream. Unless major problems happen :) +1 Only problem I have is with stable (squeeze). It is really outdated. Is there any change of updating ? Maybe use backports ? Stable doesn't -- generally speaking -- accept new versions of packages. The only way josm could be upgraded in stable is when OSM changes API to 0.7 (or it becomes otherwise unusable). Also then, the preferred form of upgrade would be a minimal patch to support the new API -- so no new JOSM, really ;) (hey, it's called stable for a reason). Yes, backports could be a solution. But we severely lack manpower -- I basically maintain myself most of OSM-related things in Debian, as even my usual josm co-maintainer is busy atm. If we had more people helping, probably josm could be packaged in backports :) (that's the main reason of my first message: spending manpower when there's no real need doesn't seem too wise ;)) (also notice that, to be in backports, we need to make sure that all the needed lib*-java packages are there, at the right versions. So it could be an easy task, or a daunting one.) Have a nice evening, David -- . ''`. Debian developer | http://wiki.debian.org/DavidPaleino : :' : Linuxer #334216 --|-- http://www.hanskalabs.net/ `. `'` GPG: 1392B174 | http://deb.li/dapal `- 2BAB C625 4E66 E7B8 450A C3E1 E6AA 9017 1392 B174 signature.asc Description: PGP signature ___ josm-dev mailing list josm-dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/josm-dev
[josm-dev] Make josm use .mo files
Hello people, it would be nice if JOSM used .mo files (installed as /usr/share/locale/code/LC_MESSAGES/josm.mo), instead of jar-embedded .lang files. Please read further. I can only see advantages with that method (and one disadvantage, which really seems to be a missing feature of Java). The pros are that external tools can handle those files (I think at localepurge in Debian, which removes locales you're not going to use -- thus saving space), and the fact that .mo files can be packaged separately from main josm (so that if you want an English-only interface, you don't need the locales installed). The only con is that, AFAIK, there is no easy method of using them within Java. Or, probably, I haven't been able to find it. What I've found is: http://java2s.com/Open-Source/Java-Document-2/Swing/gtkjfilechooser/com/google/code/gtkjfilechooser/GettextResource.java.htm It doesn't seem too difficult, but it's not straightforward either. What do you think about this? Thanks, David -- . ''`. Debian developer | http://wiki.debian.org/DavidPaleino : :' : Linuxer #334216 --|-- http://www.hanskalabs.net/ `. `'` GPG: 1392B174 | http://deb.li/dapal `- 2BAB C625 4E66 E7B8 450A C3E1 E6AA 9017 1392 B174 signature.asc Description: PGP signature ___ josm-dev mailing list josm-dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/josm-dev
Re: [josm-dev] Make josm use .mo files
On Tue, 27 Dec 2011 00:24:35 +0100 (CET), Dirk Stöcker wrote: On Mon, 26 Dec 2011, David Paleino wrote: it would be nice if JOSM used .mo files (installed as /usr/share/locale/code/LC_MESSAGES/josm.mo), instead of jar-embedded .lang files. Please read further. We dropped gettext files as they are wasting a lot of space in the translation. The lang files only carry each string once and not multiple times like .mo does. What do you mean? A gettext .mo file carries each string once -- a msgid + a msgstr. Maybe I didn't understand what you meant? :) (but I didn't notice .lang files were more compact than .mo, at least in size, I admit it) What do you think about this? Nothing, as it actually would be a step back. Thought as always Debian packagers can do what they want to do. Sure, but it would really be best if I didn't have to patch the l10n system at each release ;) Most of the advantages you describe can be reached by simply renaming the lang files to .mo and install them in different locations. Is that doable? Maybe some property to pass to ant during the build? If you're ok with that, I can try doing it (if I'm able to ;)). The only difference to mo is the file format (which does not matter, as most tools will not look into the files) Probably there's no need to rename the files, but I need to check what FHS says (btw I don't think it mandates translations to be gettext mo's) and the fact that en.lang must remain in any situation. That's a minor drawback :) Thanks for your reply, David -- . ''`. Debian developer | http://wiki.debian.org/DavidPaleino : :' : Linuxer #334216 --|-- http://www.hanskalabs.net/ `. `'` GPG: 1392B174 | http://deb.li/dapal `- 2BAB C625 4E66 E7B8 450A C3E1 E6AA 9017 1392 B174 signature.asc Description: PGP signature ___ josm-dev mailing list josm-dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/josm-dev
Re: [josm-dev] new package repository for Ubuntu
On Sun, 25 Dec 2011 05:59:17 +0100, Paul Hartmann wrote: On 12/25/2011 02:01 AM, David Paleino wrote: On Tue, 13 Dec 2011 14:19:25 +0100, Paul Hartmann wrote: there's now a JOSM apt repository for Ubuntu. It provides two packages: josm The tested version Replaces the package from the official Ubuntu repository. Why would one need such a package? Isn't the official josm package good enough? What problems does it have? I'm not aware of any problems. The repository on josm.openstreetmap.de is only for users who want the latest josm‑tested.jar, the very next day after it's release. It is an alternative to the various update scripts. ..or you can just join the Debian OpenStreetMap Team, and co-maintain josm with me ;) From time to time we have to react to events in the OSM world (new imagery, license change, ...). In these cases people rely on the new features pretty soon. JOSM is developing fast - I would never start a version that is one year old, except for bisecting a bug. :) Therefore the Ubuntu distribution model with fixed versions for half a year isn't really suitable for our project. (May be different on Debian, where you can install from unstable (?).) Truly speaking, you could this in Ubuntu too -- just add the newest repository, and pin josm to be installed from there. In unstable I upload the package as soon as I get some spare time _and_ I notice there is a new version -- that usually means that JOSM in Debian can be at most 2-3 days delayed from upstream. Unless major problems happen :) PS: I borrowed the start script, man page and menu file from the Debian package, hope that's Ok. As long as your debian/copyright contains the right information, sure :) Have nice holidays, David -- . ''`. Debian developer | http://wiki.debian.org/DavidPaleino : :' : Linuxer #334216 --|-- http://www.hanskalabs.net/ `. `'` GPG: 1392B174 | http://deb.li/dapal `- 2BAB C625 4E66 E7B8 450A C3E1 E6AA 9017 1392 B174 signature.asc Description: PGP signature ___ josm-dev mailing list josm-dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/josm-dev
Re: [josm-dev] new package repository for Ubuntu
On Tue, 13 Dec 2011 14:19:25 +0100, Paul Hartmann wrote: there's now a JOSM apt repository for Ubuntu. It provides two packages: josm The tested version Replaces the package from the official Ubuntu repository. Why would one need such a package? Isn't the official josm package good enough? What problems does it have? David -- . ''`. Debian developer | http://wiki.debian.org/DavidPaleino : :' : Linuxer #334216 --|-- http://www.hanskalabs.net/ `. `'` GPG: 1392B174 | http://deb.li/dapal `- 2BAB C625 4E66 E7B8 450A C3E1 E6AA 9017 1392 B174 signature.asc Description: PGP signature ___ josm-dev mailing list josm-dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/josm-dev
Re: [osmosis-dev] Osmosis 0.40 Released
On Thu, 1 Dec 2011 17:59:29 +0100, Igor Podolskiy wrote: I've just released Osmosis 0.40. http://bretth.dev.openstreetmap.org/osmosis-build/osmosis-0.40.tgz http://bretth.dev.openstreetmap.org/osmosis-build/osmosis-0.40.zip http://dev.openstreetmap.de:23457/hudson/job/osmosis-release/1/ Would you please mind creating a tag at http://svn.openstreetmap.org/applications/utils/osmosis/tags development migrated to github some time ago, SVN is deprecated/out of date. On https://github.com/openstreetmap/osmosis there is also a 0.40 tag :) Oh, nice! Thanks, David -- . ''`. Debian developer | http://wiki.debian.org/DavidPaleino : :' : Linuxer #334216 --|-- http://www.hanskalabs.net/ `. `'` GPG: 1392B174 | http://deb.li/dapal `- 2BAB C625 4E66 E7B8 450A C3E1 E6AA 9017 1392 B174 signature.asc Description: PGP signature ___ osmosis-dev mailing list osmosis-dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/osmosis-dev
Re: [OSM-dev] Filename extensions for OSM files
(no need to CC me, thanks) On Wed, 11 May 2011 11:13:37 +0200, Peter Körner wrote: osm-files have an osm ../-tag, osc-files start with osmChange ../ but osh-files are, currently, only osm-files with a visible-attribute on each entity - so no way to distinguish them from osm-files. Unless we have files with mixed elements (with and without visible attribute), one could distinguish .osh by looking at visible= :) David -- . ''`. Debian developer | http://wiki.debian.org/DavidPaleino : :' : Linuxer #334216 --|-- http://www.hanskalabs.net/ `. `'` GPG: 1392B174 | http://deb.li/dapal `- 2BAB C625 4E66 E7B8 450A C3E1 E6AA 9017 1392 B174 signature.asc Description: PGP signature ___ dev mailing list dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/dev
Re: [OSM-dev] Filename extensions for OSM files
On Tue, 10 May 2011 20:58:40 +0200, Peter Körner wrote: Frederik mentioned mime-types, I'd suggest (not knowing if I'd break any convention using multiple + symbols): application/x-osm+xml for .osm [..] I'd suggest we should also implement some magic(5) lines for file(1). $ file -i mazara_20110202.osm mazara_20110202.osm: application/x-osm+xml; charset=utf-8 $ file mazara_20110202.osm mazara_20110202.osm: OpenStreetMap XML dump, API 0.6 (I never worked with /etc/magic, but as it is a first try, it seems nice :) -- here's the code: ---8--- 0 string ?xml 0 search/400 =\osm OpenStreetMap XML dump 20 search/400 version= 0 regex [']0.3 \b, API 0.3 0 regex [']0.4 \b, API 0.4 0 regex [']0.5 \b, API 0.5 0 regex [']0.6 \b, API 0.6 !:mime application/x-osm+xml ---8--- ) -- . ''`. Debian developer | http://wiki.debian.org/DavidPaleino : :' : Linuxer #334216 --|-- http://www.hanskalabs.net/ `. `'` GPG: 1392B174 | http://deb.li/dapal `- 2BAB C625 4E66 E7B8 450A C3E1 E6AA 9017 1392 B174 signature.asc Description: PGP signature ___ dev mailing list dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/dev
Re: [OSM-dev] MoNav 0.3 Released
On Sat, 23 Apr 2011 16:16:22 +0200, Christian Vetter wrote: Hello everyone, Hello Christian, I am pleased to announce the release of the 0.3 version of MoNav [1][2][3] just in time for your favorite Easter holiday trip. [..] Where did the source code go? http://code.google.com/p/monav/wiki/Downloads http://code.google.com/p/monav/source/list Also, would you please stop distributing unofficial .deb packages? MoNav is already in Debian [1], and will be synced in Ubuntu as soon as they release Natty (i.e. really soon now). I'd really hate receiving bugs from users with such versions installed :) Kindly, David [1]: http://packages.debian.org/sid/monav -- . ''`. Debian developer | http://wiki.debian.org/DavidPaleino : :' : Linuxer #334216 --|-- http://www.hanskalabs.net/ `. `'` GPG: 1392B174 | http://deb.li/dapal `- 2BAB C625 4E66 E7B8 450A C3E1 E6AA 9017 1392 B174 signature.asc Description: PGP signature ___ dev mailing list dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/dev
Re: [OSM-dev] MoNav 0.3 Released
Everybody, please don't CC me, I'm subscribed to the list. On Sat, 23 Apr 2011 16:38:25 +0100, Kevin Peat wrote: On 23 April 2011 15:35, David Paleino da...@debian.org wrote: Also, would you please stop distributing unofficial .deb packages? So if I want to use the latest version of something I have to wait for Mark Shuttleworth Co. to package it up for me No, usually the maintainer packages the latest released tarball. Or even a snapshot, like the current Debian package is. If you really need some newer version of some software -- which the maintainer forgot to prepare --, or some feature backported, just file a bug to the package maintainer. and then do a complete distribution upgrade to get it. I don't think so. That's plain wrong. You don't need to upgrade the whole distribution to get ONE package. Google for APT pinning, or similar methods, to stay up-to-date on some package. Please, don't get me wrong. But I really don't want to have bugs filed for unofficial packages. Christian can obviously provide whatever he wishes. But then I can't assure it will work with the rest of the distribution. That said, do what you prefer. Next time I receive a bug about a unofficial package, I'll point people to this thread. Kindly, David -- . ''`. Debian developer | http://wiki.debian.org/DavidPaleino : :' : Linuxer #334216 --|-- http://www.hanskalabs.net/ `. `'` GPG: 1392B174 | http://deb.li/dapal `- 2BAB C625 4E66 E7B8 450A C3E1 E6AA 9017 1392 B174 signature.asc Description: PGP signature ___ dev mailing list dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/dev
Re: [OSM-dev] MoNav 0.3 Released
On Sat, 23 Apr 2011 17:49:24 +0200, Christian Vetter wrote: On Sat, Apr 23, 2011 at 4:35 PM, David Paleino da...@debian.org wrote: On Sat, 23 Apr 2011 16:16:22 +0200, Christian Vetter wrote: Where did the source code go? Were are currently switching from SVN to Mercurial, you might just have visited the site at the wrong moment. Ah! :) Also, would you please stop distributing unofficial .deb packages? MoNav is already in Debian [1], and will be synced in Ubuntu as soon as they release Natty (i.e. really soon now). I'd really hate receiving bugs from users with such versions installed :) The map packages we offer will not work for 0.2, therefore it seemed to us as if this would be the best solution for people who just want to try it out now ( and not want to wait 6 months ). If you can offer a better solution it would be greatly appreciated. I'm not saying you can't offer .deb packages on your site. I'm saying that it would be best if you offered the same packages we're offering officially. That is, Debian sid always has the latest version of $software (apart from when Debian is frozen, but then we can agree that I upload packages to experimental at that time, or kinda). So you could just mirror those packages. If it happens that Ubuntu packages must diverge from Debian, I usually take care of Ubuntu as well. So you could just mirror Ubuntu packages too. As you see, the solution is mirror. And if you release source tarballs, maintainers can do their job more effectively :) On Sat, Apr 23, 2011 at 5:38 PM, Kevin Peat ke...@kevinpeat.com wrote: So if I want to use the latest version of something I have to wait for Mark Shuttleworth Co. to package it up for me and then do a complete distribution upgrade to get it. I don't think so. Thanks Christian for doing a good job. Actually it is Christoph Eckert[1] who deserves all the credit for building binaries and map packages. I find map packages useful too, btw :) Thanks, David -- . ''`. Debian developer | http://wiki.debian.org/DavidPaleino : :' : Linuxer #334216 --|-- http://www.hanskalabs.net/ `. `'` GPG: 1392B174 | http://deb.li/dapal `- 2BAB C625 4E66 E7B8 450A C3E1 E6AA 9017 1392 B174 signature.asc Description: PGP signature ___ dev mailing list dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/dev
Re: [OSM-dev] MoNav 0.3 Released
On Sat, 23 Apr 2011 16:38:25 +0100, Kevin Peat wrote: On 23 April 2011 15:35, David Paleino da...@debian.org wrote: Also, would you please stop distributing unofficial .deb packages? So if I want to use the latest version of something I have to wait for Mark Shuttleworth Co. to package it up for me [..] MoNav 0.3 is in sid: http://packages.qa.debian.org/m/monav/news/20110423T180419Z.html It might take a while before all architectures get built, but I uploaded i386 (and will be available in a couple of hours), and amd64 should be there by tomorrow, if no problem arises. Enjoy, David -- . ''`. Debian developer | http://wiki.debian.org/DavidPaleino : :' : Linuxer #334216 --|-- http://www.hanskalabs.net/ `. `'` GPG: 1392B174 | http://deb.li/dapal `- 2BAB C625 4E66 E7B8 450A C3E1 E6AA 9017 1392 B174 signature.asc Description: PGP signature ___ dev mailing list dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/dev
Re: [osmosis-dev] one node ways
On Fri, 8 Apr 2011 20:55:43 +0400, Kirill Bestoujev wrote: You may have a look at way 35966868 to see the problem by yourself. That's non-sense to me. Why on Earth one would want to draw a one-node way? A *way* is composed by at least two nodes. That's a mapping error, IMHO. -- . ''`. Debian developer | http://wiki.debian.org/DavidPaleino : :' : Linuxer #334216 --|-- http://www.hanskalabs.net/ `. `'` GPG: 1392B174 | http://deb.li/dapal `- 2BAB C625 4E66 E7B8 450A C3E1 E6AA 9017 1392 B174 signature.asc Description: PGP signature ___ osmosis-dev mailing list osmosis-...@openstreetmap.org http://lists.openstreetmap.org/listinfo/osmosis-dev
Re: [OSM-dev] osmosis, bounding boxes and updating
On Tue, 22 Mar 2011 15:55:03 +0100, Martijn van Exel wrote: I think I found the answer to my own question: http://www.mail-archive.com/dev@openstreetmap.org/msg03530.html In short: it's not possible to combine change streams with bounding boxes / polygons. Right? No. With some hackery, I did it once :) 1. download an initial complete dump of the area you want, and call it complete.osm 2. in a crontab, to be run each minute (if you want minutely diff): $ osmosis \ --read-replication-interval workingDirectory=... \ --simplify-change \ --write-xml-change changes.osc.gz $ osmosis \ --read-xml-change changes.osc.gz \ --read-xml file=complete.osm \ --ac \ --bounding-polygon file=yourpolygon.poly \ --write-xml complete_new.osm $ osm2pgsql \ --merc \ --extra-attributes --style $BASE/osm2pgsql.style \ complete_new.osm \ mv complete.osm complete.osm.bak \ mv complete_new.osm complete.osm Check the manpage/web/--help for what to put in the workingDirectory= parameter of --read-replication-interval. Also, the last osm2pgsql acts on complete_new.osm, which is renamed to complete.osm (so that it's ready for the next crontab run) only if everything goes well. In case of errors, there's always complete.osm.bak :) This worked one month ago. I didn't check now, because I shut my app down, so can't tell if anything changed; but I don't think so. Also, my app originally had two (or more) different polygons imported and rendered, and the script put in crontab is a bit more complicated (and generalized) than this. But this should be sufficient to do what you want :) Kindly, David -- . ''`. Debian developer | http://wiki.debian.org/DavidPaleino : :' : Linuxer #334216 --|-- http://www.hanskalabs.net/ `. `'` GPG: 1392B174 | http://deb.li/dapal `- 2BAB C625 4E66 E7B8 450A C3E1 E6AA 9017 1392 B174 signature.asc Description: PGP signature ___ dev mailing list dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/dev
Re: [OSM-dev] How to delete metatiles?
On Sun, 16 Jan 2011 20:25:55 +0100, Stephan Knauss wrote: On 16.01.2011 20:11, Jon Burgess wrote: Does anyone use the existing scheme with max_zoom 18? If not the changes could only effect higher zooms, perhaps as a compatibility mode. I do with zoom 19. And until a few minutes ago I felt fine doing it. Now I feel confused. ...and I'm having small dumps rendered at z21: http://map.hanskalabs.net/ol.html However, render_expired just segfaults when passed a list with tiles z18. -- . ''`. Debian developer | http://wiki.debian.org/DavidPaleino : :' : Linuxer #334216 --|-- http://www.hanskalabs.net/ `. `'` GPG: 1392B174 | http://deb.li/dapal `- 2BAB C625 4E66 E7B8 450A C3E1 E6AA 9017 1392 B174 signature.asc Description: PGP signature ___ dev mailing list dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/dev
Re: [OSM-dev] Fwd: [OpenStreetMap] ODbL
On Mon, 10 Jan 2011 21:41:30 +1000, John Smith wrote: What's it going to take to stop people spamming me about the ODBL? The current CTs conflict with data I've edited or derived so I can't agree to the license change even if I wanted to. Just a list of users who explicitly did not accept the switch. -- . ''`. Debian developer | http://wiki.debian.org/DavidPaleino : :' : Linuxer #334216 --|-- http://www.hanskalabs.net/ `. `'` GPG: 1392B174 | http://deb.li/dapal `- 2BAB C625 4E66 E7B8 450A C3E1 E6AA 9017 1392 B174 signature.asc Description: PGP signature ___ dev mailing list dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/dev
Re: [OSM-dev] error when compiling osm2pgsql
On Mon, 20 Dec 2010 20:06:48 +0100, Peter wrote: I have all of the below packages installed: libprotobuf-c0 libprotobuf-c0-dev libprotobuf-dev libprotobuf5 protobuf-c-compiler protobuf-compiler Still doesn't work... Your version of Ubuntu doesn't have the required version of libprotobuf-c0-dev. You need 0.14, which is available in Natty (the upcoming 11.04), or Debian sid. -- . ''`. Debian developer | http://wiki.debian.org/DavidPaleino : :' : Linuxer #334216 --|-- http://www.hanskalabs.net/ `. `'` GPG: 1392B174 | http://deb.li/dapal `- 2BAB C625 4E66 E7B8 450A C3E1 E6AA 9017 1392 B174 signature.asc Description: PGP signature ___ dev mailing list dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/dev
[OSM-dev] Delta-encoding in PBF
Hello people,
I'm writing a parser in C# for PBF dumps. However, I'm having issues with the
Delta-{en|de}coding.
I thought I succesfully implemented the decoding when I saw correct
latitudes/longitudes, with the following (pseudo-)code:
---8---
function decode(delta) {
ret = []
for (i=0; i delta.Count; i++) {
if (i == 0) {
ret.append(delta[0])
continue
}
ret.append(delta[0] + delta[i])
}
return ret
}
---8---
This worked great with latitudes/longitudes, which I converted with the
OUT = IN * granularity / 10**9
formula I found in the .proto.
However, it seems that I can't understand the way user_sid is encoded. I tried
to apply the same function, but it returned negative numbers at a certain
point, and I obviously had an OutOfRange exception.
I must also say that I originally thought that the delta-encoding worked like
this:
1) write the first number, at list[0]
2) at position n, write the result of list[n-1] - list[n]
Did I just miss the correct documentation?
Thank you,
David
--
. ''`. Debian developer | http://wiki.debian.org/DavidPaleino
: :' : Linuxer #334216 --|-- http://www.hanskalabs.net/
`. `'` GPG: 1392B174 | http://deb.li/dapal
`- 2BAB C625 4E66 E7B8 450A C3E1 E6AA 9017 1392 B174
signature.asc
Description: PGP signature
___
dev mailing list
dev@openstreetmap.org
http://lists.openstreetmap.org/listinfo/dev
Re: [OSM-dev] Delta-encoding in PBF
On Sat, 18 Dec 2010 13:28:09 +0100, Stefan de Konink wrote:
Op 18-12-10 11:53, David Paleino schreef:
Hello people,
I'm writing a parser in C# for PBF dumps. However, I'm having issues with
the Delta-{en|de}coding.
http://git.openstreetmap.nl/index.cgi/pbf2osm.git/tree/src/main.c#n588
Maybe that helps?
Aha, yes! :)
From that code, it seems like you're using what I thought before, i.e. given x,
x1 and x2, the delta-coded list would contain x, x1-x, x2-x1. And then you're
reconstructing them just by summing up.
So I found my bug. I was summing up deltas between them, instead of
previous result + current delta.
Thank you!,
David
--
. ''`. Debian developer | http://wiki.debian.org/DavidPaleino
: :' : Linuxer #334216 --|-- http://www.hanskalabs.net/
`. `'` GPG: 1392B174 | http://deb.li/dapal
`- 2BAB C625 4E66 E7B8 450A C3E1 E6AA 9017 1392 B174
signature.asc
Description: PGP signature
___
dev mailing list
dev@openstreetmap.org
http://lists.openstreetmap.org/listinfo/dev
Re: [josm-dev] Microsoft gains access to aerial imagery
On Thu, 25 Nov 2010 12:27:57 -0600, Ian Dees wrote: On Wed, Nov 24, 2010 at 9:47 PM, Paul Johnson ba...@ursamundi.org wrote: On 11/24/2010 04:44 AM, Frederick Rama wrote: For the end-user, there's no difference in WMS and slippy map anyway, it only confuses them. Well, Slippy Map supports tiles, wmsplugin doesn't. wmsplugin fetches images from WMS in a tiled format. Slippymap supports TMS, wmsplugin doesn't, AFAICT. What wsmplugin does is a pseudo-tiling, to improve performance. But it does request several small bboxes from WMS servers. They're different technologies. Which yes, could be merged together in an imagery plugin, but keep in mind they're *different*. So you need to handle multiple cases in this yet-to-be-born plugin. My 2c, David -- . ''`. Debian developer | http://wiki.debian.org/DavidPaleino : :' : Linuxer #334216 --|-- http://www.hanskalabs.net/ `. `'` GPG: 1392B174 | http://deb.li/dapal `- 2BAB C625 4E66 E7B8 450A C3E1 E6AA 9017 1392 B174 signature.asc Description: PGP signature ___ josm-dev mailing list josm-dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/josm-dev
Re: [josm-dev] Problem compiling mod_tile with mapnik2
On Mon, 20 Sep 2010 09:33:54 +0200, Maria Arias de Reyna wrote: [..] gen_tile.cpp: In function âvoid* render_thread(void*)â: gen_tile.cpp:547: error: âgettimeofdayâ was not declared in this scope make: *** [renderd] Error 1 Open that file, and add #include sys/time.h with the other includes at the beginning. David -- . ''`. Debian developer | http://wiki.debian.org/DavidPaleino : :' : Linuxer #334216 --|-- http://www.hanskalabs.net/ `. `'` GPG: 1392B174 | http://deb.li/dapal `- 2BAB C625 4E66 E7B8 450A C3E1 E6AA 9017 1392 B174 signature.asc Description: PGP signature ___ josm-dev mailing list josm-dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/josm-dev
