Re: [OSM-dev] Nearest way for a location
Stephan Plepelits sk...@xover.htu.tuwien.ac.at writes: On Sun, Jun 27, 2010 at 07:11:53PM -0500, Nolan Darilek wrote: 3. In dusting off my disused (and never that good to begin with :) math skills from over a decade in my past, I'm thinking that a vector-based solution might work. I am already calculating a node's neighbors if it is on one or more ways, so I think that if I create vectors between the nearest node and each of its neighbors, then determine which segment has the least distance to the user's current location, then I've figured out the user's new way with minimal complexity. Before I go off and implement this (or rather, before I figure out which vector operations apply here and *then* implement this :) can anyone tell me why this may be a bad idea? I think this is a very good idea :) Check out the Hesse normal form[5] how to calculate the distance of a point to a line. The nearest road does not need to have a node near your location. Matthias ___ dev mailing list dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/dev
[josm-dev] Extending Undo
Upliner wrote: By the way, what do you think about making merge layers operation undonable? I think I can implement it, there is some groundwork for in reverter and fuzzer(ext_tools) plugins. Cool. I see 2 paths here: First would be to have an undo stack for each data layer. Normally there is no reason you have to first undo all later operations on layer b before you can undo things on layer a. (Although I never had that problem.) Second, make higher level layer operations undoable. (Only thing that should be excluded is toggle of active layer and visibility.) Undo of merge layer would probably the most useful extension here. The first would be similar to a text editor where you can undo for each document and second would be like photoshop or gimp, where layers interact more closely. Maybe both is compatible? E.g. a checkbox in command stack to show only the operations on the current data layer. Sebastian ___ josm-dev mailing list josm-...@openstreetmap.org http://lists.openstreetmap.org/listinfo/josm-dev
Re: [OSM-dev] Apache + mapnik + mod_python problem
On 28-6-2010 18:18, yvecai wrote: I had just run generate_xml.py again to change some rendering rules. Don't know about the other things, but this remark peeked my interest. What rendering rules had changed, and why would you feel the need to rerun generate_xml.py for them? -- Lennard ___ dev mailing list dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/dev
[josm-dev] Color schemes / hide yellow nodes
Hi all, I've noticed the Color Schemes tab in the Preferences-Display Settings dialog. Does anybody know how does that work? I am trying to find a way to hide the yellow nodes on the map as they clutter the map when zoomed out. Any suggestions on this? Cheers, Attila ___ josm-dev mailing list josm-dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/josm-dev
Re: [josm-dev] Color schemes / hide yellow nodes
El día Monday 28 June 2010 12:51:02, Attila Szász dijo: I am trying to find a way to hide the yellow nodes on the map as they clutter the map when zoomed out. Any suggestions on this? Filter them out. Open up the filter pane, and add a rule for type:node untagged. Then switch on that rule, and click the checkbox that hides the elements (instead of graying them out). Best, -- Iván Sánchez Ortega i...@sanchezortega.es Un ordenador no es una televisión ni un microondas: es una herramienta compleja. ___ josm-dev mailing list josm-dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/josm-dev
Re: [josm-dev] Color schemes / hide yellow nodes
Wonderful, thank you. I've seen the greying effect of the filter, but not the Hide one. Thanks, Attila 2010/6/28 Iván Sánchez Ortega i...@sanchezortega.es El día Monday 28 June 2010 12:51:02, Attila Szász dijo: I am trying to find a way to hide the yellow nodes on the map as they clutter the map when zoomed out. Any suggestions on this? Filter them out. Open up the filter pane, and add a rule for type:node untagged. Then switch on that rule, and click the checkbox that hides the elements (instead of graying them out). Best, -- Iván Sánchez Ortega i...@sanchezortega.es Un ordenador no es una televisión ni un microondas: es una herramienta compleja. ___ josm-dev mailing list josm-dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/josm-dev ___ josm-dev mailing list josm-dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/josm-dev
[josm-dev] important for tablepc-users
hi ! i know that i write a wish-ticket by josm.openstreetmap.org for the following feature - but i hope there are some more people in this mailinglist who like to have the feature. i NEED a pan-funktion to move the drawing area by using without a mouse (TABLETC). can anyone make this in the next ??? regards Jan :-) ___ josm-dev mailing list josm-dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/josm-dev
Re: [josm-dev] important for tablepc-users
On Mon, 28 Jun 2010, Jan Tappenbeck wrote: i know that i write a wish-ticket by josm.openstreetmap.org for the following feature - but i hope there are some more people in this mailinglist who like to have the feature. i NEED a pan-funktion to move the drawing area by using without a mouse (TABLETC). http://josm.openstreetmap.de/wiki/Plugins Plugin touchscreenhelper Ciao -- http://www.dstoecker.eu/ (PGP key available) ___ josm-dev mailing list josm-dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/josm-dev
Re: [josm-dev] Extending Undo
Sebastian Klein basti...@googlemail.com writes: Upliner wrote: By the way, what do you think about making merge layers operation undonable? I think I can implement it, there is some groundwork for in reverter and fuzzer(ext_tools) plugins. Cool. I see 2 paths here: First would be to have an undo stack for each data layer. Normally there is no reason you have to first undo all later operations on layer b before you can undo things on layer a. (Although I never had that problem.) Second, make higher level layer operations undoable. (Only thing that should be excluded is toggle of active layer and visibility.) Undo of merge layer would probably the most useful extension here. A layer merge is essentially two operations: first merge the data into the target layer and then delete the source layer. The first part would be covered by the target layer's undo stack. The second could be left to the user. JOSM could simply not delete the source layer. The problem with making such operations undoable is that this potentially requires a lot of memory if there is a lot of data involved. We might need to think about storing such things on disk. Matthias ___ josm-dev mailing list josm-dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/josm-dev
