Re: [Talk-us] [OSM-talk] Addressing Question
On Thu, 2009-11-12 at 10:28 -0600, Ian Dees wrote: Give everyone a chance to work in a constructive way and don't expect others to clean the mess bad import left behind. No wonder there are only few motivated mappers in US. In Canada they do a much better job in integrating the community and don't import every shape file blindly just because it's available. Not to start a holy war over what community is better, but there weren't a whole lot of mappers in the US (at least on talk or talk-us) when we started doing the TIGER import... People were being actively told not to map in the US because we had TIGER coming and it would replace any work you ended up doing. The standard OSM user tries to find their street first. The typical US OSM experience has gone from, My street isn't there to My street is crooked. -- Dave ___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us
Re: [Talk-us] [OSM-talk] Addressing Question
On Thu, 2009-11-12 at 11:40 -0800, Apollinaris Schoell wrote: On 12 Nov 2009, at 11:29 , Anthony wrote: On Thu, Nov 12, 2009 at 9:14 AM, Andy Allan gravityst...@gmail.com wrote: It's a fairly well established convention that in OSM it's the houses/plots, not the road centrelines, that are addressed. But that doesn't always reflect reality. The reality, at least in many parts of the world, is that the streets are given blocks of potential addresses, and the houses/plots/whatever are given actual addresses from those potential address blocks. Don't know any place except in US where this has been done. So, should we ignore the US for addressing entirely since it is different? Or, should US addressing use a different scheme than the rest of the world? We like being different. -- Dave ___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us
Re: [Talk-us] Possible destructive bug in JOSM build 2417 - need someone to duplicate
On Wed, 2009-11-11 at 21:01 -0500, Chris Hunter wrote: My apologies if this has already been reported to the dev mailing list, but I've been running up against a critical/showstopper bug in JOSM 2417 for the past few days. I just tried with 2439 and can't seem to reproduce this. -- Dave ___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us
Re: [Talk-us] Possible destructive bug in JOSM build 2417 - need someone to duplicate
On Wed, 2009-11-11 at 23:01 -0500, Chris Hunter wrote: Thanks. Is 2439 available on the server yet, or is it still in alpha? I re-downloaded the latest beta a couple hours ago and the josm-latest.jar link was still pointing at 2417. I checked it out of SVN and built it myself. I can send along a copy if you wan to give it a shot. -- Dave ___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us
Re: [OSM-talk] [Talk-us] proposal for deletion: talk-us-ga and
On Wed, 2009-10-21 at 19:40 -0400, Richard Weait wrote: On Wed, Oct 21, 2009 at 7:34 PM, Sarah Manley sarah.m.man...@gmail.com wrote: What is the status of the forum: http://forum.openstreetmap.org? Would building this out more maybe solve some of our problems? Preference for email vs web forum varies from community to community. In my limited experience, more-technical groups tend towards email but there are certain to be counter-examples. An interface that merges email and web forum might be ideal. I believe that the Linux Kernel Mailing List uses such a system but I don't know what the drawbacks and compromises are in that system. There are web interfaces to LKML, but they're all tacked on after the fact to the mailing list. Email is still the main mechanism, although there are some nice web gateways, to be sure. -- Dave ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk
Re: [Talk-us] proposal for deletion: talk-us-ga and
On Wed, 2009-10-21 at 19:40 -0400, Richard Weait wrote: On Wed, Oct 21, 2009 at 7:34 PM, Sarah Manley sarah.m.man...@gmail.com wrote: What is the status of the forum: http://forum.openstreetmap.org? Would building this out more maybe solve some of our problems? Preference for email vs web forum varies from community to community. In my limited experience, more-technical groups tend towards email but there are certain to be counter-examples. An interface that merges email and web forum might be ideal. I believe that the Linux Kernel Mailing List uses such a system but I don't know what the drawbacks and compromises are in that system. There are web interfaces to LKML, but they're all tacked on after the fact to the mailing list. Email is still the main mechanism, although there are some nice web gateways, to be sure. -- Dave ___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us
Re: [Talk-us] US-based Server
On Thu, 2009-10-22 at 01:34 +0200, Frederik Ramm wrote: Adam Schreiber wrote: I would hope that and in the future a mapping mirror. The database ought to move to being on more than one server. I am interested to hear your proposals on conflict resolution, or failing that, segmentation of our data. Surely distributed databases are a solved problem these days. :) Having an API mirror that's read-only to users, but kept within a minute or two of the real thing should be OK for most people. There's nothing fundamentally different between that and somebody on a slow connection doing a download of a large area. By the time they have the data, it may be out of date. Writes could quite easily just be proxied (even at the HTTP layer) back to the master machine. I'd bet that OSM is skewed pretty darn heavily to readers anyway. That much could be done with HTTP and minutely planet dumps. -- Dave ___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us
[OSM-talk] Changing the account that uploaded the TIGER data
So, I just noticed that this map: http://matt.sandbox.cloudmade.com/?lat=45.528599lng=-122.885771zoom=15layer=2 has my own street listed as unedited TIGER data. I think someone is just using user==DaveHansen as a test for edited vs. uneditied TIGER data. So, I changed the display name. It is now DaveHansenTiger, with an email of osm-ti...@sr71.net. I created a new account 'DaveHansen' with my regular d...@sr71.net email. I promise not to use DaveHansenTiger any more. If I do a new upload, I'll use DaveHansenTiger2009 or something. Cool? -- Dave ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk
[Talk-us] Changing the account that uploaded the TIGER data
So, I just noticed that this map: http://matt.sandbox.cloudmade.com/?lat=45.528599lng=-122.885771zoom=15layer=2 has my own street listed as unedited TIGER data. I think someone is just using user==DaveHansen as a test for edited vs. uneditied TIGER data. So, I changed the display name. It is now DaveHansenTiger, with an email of osm-ti...@sr71.net. I created a new account 'DaveHansen' with my regular d...@sr71.net email. I promise not to use DaveHansenTiger any more. If I do a new upload, I'll use DaveHansenTiger2009 or something. Cool? -- Dave ___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us
[OSM-talk] TIGER Addressing Import
Is this the most up to date way of keeping addresses? http://wiki.openstreetmap.org/wiki/Proposed_features/House_numbers/Karlsruhe_Schema Well, I have some perl code that will parse the 2007/2008 TIGER data files. My goal is to get the addresses imported into OSM this time around. Here's some ugly sample output of what I have now. http://sr71.net/~dave/osm/tiger/sherman.osm I don't need any suggestions on it, I just wanted to show people what I have so far. Issues: * I currently have the way combination code turned off. This means that OSM ways are represented 1:1 with the TIGER TLIDs. * Some multi-segment TIGER roads have only a single address range. Do we create segments for each road segment and evenly divide the addresses? Or, do we draw a single address segment going from the first to last node? And, yes, I saw the 2009 data come out. I'll make sure my code works with it. -- Dave ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk
Re: [OSM-talk] TIGER Addressing Import
On Sun, 2009-10-04 at 02:24 +1000, John Smith wrote: 2009/10/4 Dave Hansen d...@sr71.net: Is this the most up to date way of keeping addresses? http://wiki.openstreetmap.org/wiki/Proposed_features/House_numbers/Karlsruhe_Schema Well, I have some perl code that will parse the 2007/2008 TIGER data files. My goal is to get the addresses imported into OSM this time around. Here's some ugly sample output of what I have now. http://sr71.net/~dave/osm/tiger/sherman.osm I don't need any suggestions on it, I just wanted to show people what I have so far. Issues: * I currently have the way combination code turned off. This means that OSM ways are represented 1:1 with the TIGER TLIDs. * Some multi-segment TIGER roads have only a single address range. Do we create segments for each road segment and evenly divide the addresses? Or, do we draw a single address segment going from the first to last node? And, yes, I saw the 2009 data come out. I'll make sure my code works with it. Wouldn't these questions be better going to the import mailing list? There's an imports list? ;) -- Dave ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk
[Talk-us] TIGER Addressing Import
Is this the most up to date way of keeping addresses? http://wiki.openstreetmap.org/wiki/Proposed_features/House_numbers/Karlsruhe_Schema Well, I have some perl code that will parse the 2007/2008 TIGER data files. My goal is to get the addresses imported into OSM this time around. Here's some ugly sample output of what I have now. http://sr71.net/~dave/osm/tiger/sherman.osm I don't need any suggestions on it, I just wanted to show people what I have so far. Issues: * I currently have the way combination code turned off. This means that OSM ways are represented 1:1 with the TIGER TLIDs. * Some multi-segment TIGER roads have only a single address range. Do we create segments for each road segment and evenly divide the addresses? Or, do we draw a single address segment going from the first to last node? And, yes, I saw the 2009 data come out. I'll make sure my code works with it. -- Dave ___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us
Re: [Talk-us] TIGER Addressing Import
On Sun, 2009-10-04 at 02:24 +1000, John Smith wrote: 2009/10/4 Dave Hansen d...@sr71.net: Is this the most up to date way of keeping addresses? http://wiki.openstreetmap.org/wiki/Proposed_features/House_numbers/Karlsruhe_Schema Well, I have some perl code that will parse the 2007/2008 TIGER data files. My goal is to get the addresses imported into OSM this time around. Here's some ugly sample output of what I have now. http://sr71.net/~dave/osm/tiger/sherman.osm I don't need any suggestions on it, I just wanted to show people what I have so far. Issues: * I currently have the way combination code turned off. This means that OSM ways are represented 1:1 with the TIGER TLIDs. * Some multi-segment TIGER roads have only a single address range. Do we create segments for each road segment and evenly divide the addresses? Or, do we draw a single address segment going from the first to last node? And, yes, I saw the 2009 data come out. I'll make sure my code works with it. Wouldn't these questions be better going to the import mailing list? There's an imports list? ;) -- Dave ___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us
Re: [Talk-us] Systematic errors in the Maui, Hawaii Data
On Mon, 2009-09-28 at 23:23 -0700, Scott Atwood wrote: However, as nearly as I can tell, very little work seems to have been done on Maui beyond the initial Tiger upload. The problem is, this Tiger data seems to have some large systematic errors, a translation to the north-northwest. I started to manually correct a few ways based on the satellite photos and GPS tracks, but I realized it would probably be far better to either reimport the Maui data with a correction, or apply some automated process to the existing data to translate it to more-or-less the correct location. I'd really prefer not to reimport it. Could you point us to a few areas where we can look at your tracks and the existing data together that exemplify this behavior? Can you quantify large systematic errors? I really don't want to blow it away and re-upload. -- Dave ___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us
Re: [Talk-us] Systematic errors in the Maui, Hawaii Data
On Tue, 2009-09-29 at 10:40 -0700, Scott Atwood wrote: The GPS tracklog I uploaded includes data from Wailuku in central Maui, all along the Hana Highway as far as Waianapana State Park near Hana. In all the locations I spot checked (including the ones mentioned above), there appears to be a consistent displacement of approximately 500 meters to the north-northwest of all ways associated with streets. The shoreline ways appear to be more or less accurate. It was pretty easy using JOSM to fix the first example. The second one appears a little less clear cut to me. My best suggestion at this point would be to give JOSM a try. It lets you grab much more interesting sets of data and move them around as a group. I'm a bit hesitant to go moving large swaths of data around in an automated way. First, I don't have any good tools to do it and it'll take some time to code them up. Also, I'm unsure about exactly how widespread and precise the 500m offset is. Does anybody know of any better tools that might help with this? -- Dave ___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us
Re: [Talk-us] Systematic errors in the Maui, Hawaii Data
On Tue, 2009-09-29 at 11:20 -0700, Scott Atwood wrote: I spot checked a number of locations all around Maui, and in all the locations I checked, they seem to be affected by the same or highly similar offset to the NNW. Here is another example from the Lahaina area: http://www.openstreetmap.org/?lat=20.88606lon=-156.68522zoom=15layers=B000FTF If you can look into formalizing this, I'd be willing to take a look at it. What I mean is to take some precise measurements from a wide set of samples across the island, probably 20 or 30. Figure out what the displacement vector is at each point, and ensure that it *is* consistent. The worst thing we could do would be to perform such an edit and later realize that we've hurt more than we've helped. I'm just really hesitant to go moving an entire island worth of data based on the problem I've seen so far. The prospect of manually shifting every single street on the entire island of Maui (even in batches within JOSM) is extremely daunting, and strongly inhibits me from wanting to do any work on Maui. And the fact that such enormous errors persist suggests to me that few if any people have done much non-automated work on Maui yet. The question is whether it will take longer for people to do it manually or if doing it in an automated way will be more efficient. Believe me, the prospect of doing a mass edit like that is pretty daunting as well. Can we verify how much editing has been done on Maui? If it is as little as I think, there is little to loose by throwing away the existing data and starting over. I still think re-importing (or some kind of automated batch editing) might be a faster and easier way to fix the problems with Maui. Sure. Just download the entire island and see how many objects have been touched by people other than DaveHansen. JOSM can tell you this pretty quickly. -- Dave ___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us
[Talk-us] Another shot at a whole-US Garmin map
I decided to try another approach. I used the tile picker from here: http://ulrichkuester.de/OSM/CoordinateToOSMTile.html and got the tiles from here: http://osm.ammit.de/osm/latest/img/ with a little wget and a bash script. I then used the mkgmap commands what Lambertus talks about here: http://forum.openstreetmap.org/viewtopic.php?id=2625p=10 java -Xmx2048M -jar mkgmap.jar --series-name='OSM World Routable' --latin1 --code-page-1252 --description='OSM World Routable' --product-id=53 --tdbfile --gmapsupp *.img The result is here: http://dev.openstreetmap.org/~daveh/garmin/USA-fromtiles.09-06-2009.gmapsupp.img.bz2 It looks quite a bit better than the previous one that I posted. I think those tiles have a bit more detail and don't have the error annotations that the Cloudmade ones do. It still doesn't want to do real routing on my Nuvi, but at least the map looks OK. -- Dave ___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us
[Talk-us] Garmin OSM map for whole US
For those of you that don't know, Cloudmade has some really cool ready-made maps available for download. I know they work on Garmin devices, but there are probably some others. http://downloads.cloudmade.com/north_america/united_states The problem is that they're made one state at a time. I'm lazy, so I buy large cards for my GPSes and load the whole country on them so I don't ever have to reload maps. But, with the Cloudmade maps, I have to only load a single state at a time. If I want another state, I have to take the card out (or plug the GPS in) and move another state's gmapsupp.img file in. Well, mkgmap has come to the rescue: http://www.mkgmap.org.uk/index.html It allows you to combine several gmapsupp.img files. I've downloaded all of the US states (plus a few territories), and fed them through mkgmap. The result is a single file you can put on your Garmin GPS for the whole country. I've also stuck the bash script in here so you can see how I did it: http://dev.openstreetmap.org/~daveh/garmin/ Just download, bunzip2, rename USA.$DATE.gmapsupp.img to plain 'gmapsupp.img' and move it over to your device. There are a couple of little issues with the way roads get drawn. Some little residential roads get drawn in bold red (is this from the OSM.err stuff?). So, if you know the Cloudmade people who are working on this, I'd like to get in touch with them to make a few minor tweaks. I'd also like to get this off of the dev server and put somewhere a bit better for downloading such a big file. Can anybody at Cloudmade want to share the scripts/programs that are creating these files? Does anybody else have some nice USA extracts that could be used for making garmin maps? -- Dave ___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us
Re: [Talk-us] Removing duplicates nodes in Iowa/US
On Fri, 2009-08-21 at 08:54 -0500, Travis Rayhons wrote: 3. Does anyone know where I can find the source code to the validator plugin for JOSM? I was thinking I could take that code and replicate the procedure into my script. The code is in SVN: http://svn.openstreetmap.org/applications/editors/josm/plugins/validator/src/org/openstreetmap/josm/plugins/validator/tests/DuplicateNode.java One thing I would encourage you to do is to ensure that nodes are compatible before merging them. I went to some trouble in the original TIGER import to create duplicate nodes for some situations. They're also OK in a number of cases, like where there's an interstate overpass. We may have a single point for the intersection, but we need two nodes since the roads don't actually touch. So, please don't merge *all* duplicate nodes. Check to see, for instance, if they're in different counties. Or, make sure that you're not merging a motorway to a residential street. Sounds like a fun project! -- Dave ___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us
Re: [Talk-us] Deletion of unnecessary TIGER node tags will commence this week-end
On Thu, 2009-08-06 at 21:34 +0200, Frederik Ramm wrote: Allan has made a convincing case about superfluous node tags in this posting on dev: http://lists.openstreetmap.org/pipermail/dev/2009-June/016009.html Huh, I never actually saw that message. I'm OK with this, but mostly because the most useful tag is the tiger:tlid one, and it is actually buggy. I had a bug in the original script that made a big chunk of them worthless. If I ever needed to use that tag, I'd end up having to regenerate them anyway. I'm OK with this. Thanks for letting everyone know. -- Dave ___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us
Re: [Talk-us] Data Upload
On Sat, 2009-07-18 at 20:07 -0700, Andrew Ayre wrote: I tried bulk_upload.py and it gave me a 404 error. I've used this in the past: http://wiki.openstreetmap.org/wiki/Bulk_upload.pl Evidently it hasn't been updated to 0.6 yet. But, honestly, that shouldn't be *that* hard to do. -- Dave ___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us
Re: [Talk-us] Data Upload
On Sat, 2009-07-18 at 22:16 -0700, Andrew Ayre wrote: Thanks. How would I test it without risking putting dummy data or partial data on the public server? I've tried to use another upload script with api06.dev.openstreetmap.org and mysql.dev.openstreetmap.org but they don't appear to be functional (server error 500). Those are the two that I would have tried. Perhaps try the dev@ list and ask for suggestions there. You'll probably have a more broad and smarter audience than us poor US folks. ;) -- Dave ___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us
Re: [Talk-us] Proposed automated motorway_link mass edit
On Fri, 2009-07-17 at 15:46 +0200, Frederik Ramm wrote: This brings down the number of proposed changes from 28k to 26k. The new list is at the same place: http://www.remote.org/frederik/tmp/us-motorway-link-downgrade/ Some of these at least are from a botched TIGER county that I screwed up during the upload in Lane county. It's probably another good example why that we should stay far far away from these in the automatic downgrade. -- Dave ___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us
Re: [Talk-us] Proposed automated motorway_link mass edit
On Fri, 2009-07-17 at 08:10 -0700, Russ Nelson wrote: On Jul 17, 2009, at 2:24 AM, Frederik Ramm wrote: I'd also like to look into some gluing back together of the TIGER counties and I wonder how suitable this would be. My gut feeling is that this calls for a semi-automated process in which a script suggests certain changes but humans still have to confirm them individually. This will be technically possible when third-party web applications can make API changes in the name of others by using OAuth (soon to be deployed on osm.org). Not something you'll write over a weekend that's for sure! Some of it can definitely be automated. If you have a way that stops at a node, and there is another node at the same location attached to a different way, the nodes should be merged. Well, with appropriate checks of course. We wouldn't want to do this with interstates and regular roads, power lines or other incompatible ways. But I agree in general. Another fix I'd like to see is to look at all the Interstate Highways, and if there is a road connected to it at any angle between 45 and -45, disconnect it. An even more aggressive fix would be to disconnect everything that isn't a motorway_link. That's probably correct, but more aggressive than I would choose to implement. Yep. I've even got a JOSM validator plugin test to check motorway intersections. It doesn't do the angles, but just ensures motorways only touch other way types at their endpoints. -- Dave ___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us
Re: [Talk-us] Proposed automated motorway_link mass edit
On Fri, 2009-07-17 at 10:27 -0500, David Lynch wrote: On Fri, Jul 17, 2009 at 10:10, Russ Nelsonr...@cloudmade.com wrote: An even more aggressive fix would be to disconnect everything that isn't a motorway_link. That's probably correct, but more aggressive than I would choose to implement. Not a good idea at all, IMO. I can think of numerous places within 50 miles of my home where, due to existing highways being upgraded to motorway or towns being bypassed by freeway/motorway-grade highway, there are nodes which have both motorway and non-motorway ways connected, because the motorway lanes empty directly onto the old highway Yeah, you definitely have to be careful. It's OK for a motorway to touch: 1. another motorway 2. a motorway_link 3. a non-mototorway, but only at its *END* node. Not at its beginning node 4. service roads. Our friendly police officers love to use these little spurs to hide for speed traps in Oregon. :) Here's where I-72 ends, for instance. This really is a full motorway and I wouldn't call it a motorway_link even up until the point where it runs into a stoplight: http://www.openstreetmap.org/?lat=40.12193lon=-88.28141zoom=15layers=B000FTF -- Dave ___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us
Re: [Talk-us] Proposed automated motorway_link mass edit
On Fri, 2009-07-17 at 09:19 -0700, Apollinaris Schoell wrote: Yep. I've even got a JOSM validator plugin test to check motorway intersections. It doesn't do the angles, but just ensures motorways only touch other way types at their endpoints. very useful, can you share? Here are my current jars: http://sr71.net/~dave/osm/josm/07172009/ The problem is that I need a few core changes in JOSM. I got a few of them upstream, but I need my ReverseLookup code integrated. -- Dave ___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us
Re: [Talk-us] Proposed automated motorway_link mass edit
On Fri, 2009-07-17 at 10:35 -0700, Russ Nelson wrote: On Jul 17, 2009, at 9:29 AM, David Lynch wrote: Because I and numerous other mappers have put a hell of a lot of time and effort into getting things right, and I don't want anyone breaking it because an algorithm assumes it isn't right. Well, I guess that's an argument for only editing data still owned by that DaveHansen character. I appreciate that you have invested significant time and effort into getting a particular area into good shape. But it seems to me that being able to fix 50 times the area you've already edited, at the cost of some damage to your area, is something that you would appreciate is a good thing. Or is your concern not the map as a whole, but instead the portion of it that you've edited. This argument really rings true to me. With the TIGER import, there were certainly areas of higher-quality data that got destroyed. But, certainly the map benefited overall. There was also another curious side-effect: the areas that *had* personal attention given to them were actually the ones that it was easiest to make decisions about overwriting things. They already had a loving and caring human to fix them up if anything went wrong. -- Dave ___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us
Re: [Talk-us] Proposed automated motorway_link mass edit
On Fri, 2009-07-17 at 03:41 +0200, Frederik Ramm wrote: Preliminary analysis shows that there would be roughly 28k changes across the whole US. I have prepared a full list of all proposed changes, arranged by state and county, here: http://www.remote.org/frederik/tmp/us-motorway-link-downgrade/ Frederik, that's exceedingly cool stuff. I have a validator plugin test to do this which I was testing last weekend, but yours is on a completely different scale. Notice the lack of edits in Washington, county, OR :). Yours is very nice work. Can you share some of the scripts and methods you used for this? I do think that some automated fix-bots would be nice to have run periodically for cleanups like this that are pretty easy to verify. I'd also like to look into some gluing back together of the TIGER counties and I wonder how suitable this would be. Again, very, very cool stuff. -- Dave ___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us
Re: [Talk-us] TIGER corrections
On Wed, 2009-07-08 at 17:55 -0700, Dave Hansen wrote: On Wed, 2009-07-08 at 17:08 -0700, Alan Mintz wrote: 1. Short road N Laurel Ave (way 7497408) ending at a T-intersection into W 18th St (way 7516644). TLID is 144674357. The node at the T has TLIDs 144674357:144674376:144986081, which is fine - the two segments of W 18th St that join the T are 376 and 081. However, the node at the south (dead) end of the road has the same TLIDs (144674357:144674376:144986081) instead of just 357. It looks like you found a genuine bug in the way I stored the tlids. Lemme see if I can track it down and figure out how to work around it. Man, this was a crappy bug. Basically I used a reference when I should have used a copy of each node's tags. This causes all nodes that are created as part of a feature to share a copy of tags. Any nodes that were created as part of older features will have the new tags merged into them. But *all* of the nodes that were part of the older feature are inadvertently modified. Urg. It *is* fixable to some degree. I can re-run the generation scripts and remove the superfluous TLIDs from the nodes. But, that's going to be quite a bit of work. I probably need to think about better solutions than that. -- Dave ___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us
Re: [Talk-us] Fixing TIGER
On Tue, 2009-07-07 at 10:23 -0700, Apollinaris Schoell wrote: it's bad if you don't have a 4WD but your navi thinks it's perfect to use :( but even tomtom, google, ... have the same errors in these areas. if we want osm to be better there is no easy way to get it right without checking the reality. mass imports give a good starting point but it's really hard to remove the old invalid data and there not many mappers in remote areas to verify it. Amen to that! If I had it to do all over again, I'd make a unique user-id for each upload instance. The upload-uuid helps, but it's not volatile upon edits. It would probably be smart for any navigation system using OSM to check for tiger:reviewed=no. Perhaps I should go thorough and retag the TIGER data which is so far been unmodified. -- Dave ___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us
Re: [Talk-us] Fixing Alignments in JOSM
On Tue, 2009-06-23 at 11:57 -0700, Andrew Ayre wrote: So I need to split the North-South way into two pieces and it intersects the East-West way in two places. I cannot figure out how to do this in JOSM. I've tried everything - splitting a way at nodes, ungluing, etc. The way always remains joined. Can someone please give me a step by step guide to fixing this alignment problem? Sounds like a fun intersection. :) Could you give us some coordinates for it? I'll go take a look and see if I can explain what best to do. -- Dave ___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us
[OSM-talk] Strange synthentic GPS tracks spelling out words
We had a super-cool mapping party in Portland, OR this weekend. But I noticed some really werid GPS traces. Somebody has spelled out things like ATM and SUSHILAND in the GPS tracks, and they weren't walking around spelling things. ;) Take a look around 45.524613, -122.694281. I'm just curious who uploaded these. They seem pretty harmless and kinda funny, but I wonder why someone would go to this trouble. Or did someone's GPS automatically translate waypoints into these things? Any ideas? -- Dave atm.gpx Description: XML document ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk
[Talk-us] Strange synthentic GPS tracks spelling out words
We had a super-cool mapping party in Portland, OR this weekend. But I noticed some really werid GPS traces. Somebody has spelled out things like ATM and SUSHILAND in the GPS tracks, and they weren't walking around spelling things. ;) Take a look around 45.524613, -122.694281. I'm just curious who uploaded these. They seem pretty harmless and kinda funny, but I wonder why someone would go to this trouble. Or did someone's GPS automatically translate waypoints into these things? Any ideas? -- Dave atm.gpx Description: XML document ___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us
Re: [Talk-us] Tidying up TIGER data
On Thu, 2009-06-04 at 00:36 -0600, Ted Percival wrote: Its functions are: - Strip St suffix from grid-named streets (eg. South 500 West) - Collapse multiple spaces into a single space (lots of TIGER) - Expand abbreviated directions (eg. S 500 E to South 500 East) - Expand abbreviated suffixes (Rd - Road, St - Street, etc) So, I looked at doing this when I originally converted the TIGER data. The issue is that I'm too dumb to come up with anything that worked universally across the entire country. This kind of script is useful for small areas that you've looked at manually, but please don't apply it too widely. It does the right actions for sanely-named things, but TIGER is full of goofy stuff. Consider: St. Helens St.. There are also plenty of semi-mistakes or weird abbreviations in TIGER that appear to be mistakes. I wouldn't be surprised to see Saint Street entered somewhere as name: St. type: St. We don't want to make that Street Street. That makes it even worse. :) Again, these can work in limited areas where the naming is nice and consistent, but it's really really hard to make it work on a large scale where things are *NOT* consistent. -- Dave ___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us
Re: [Talk-us] TIGER Data in Wrong Place
On Wed, 2009-05-06 at 19:08 +0100, Andrew Ayre wrote: Hi! When I load OSM data into my GPS unit using mkgmap for a place in the UK then it is accurate. When I load OSM data for Tucson, Arizona then it is off by perhaps 100ft. I would like to make the maps for Tucson usable, so my questions are: - how do I tell where this problem begins and ends? You probably can't do this on a large scale. - how do I fix it? In JOSM, you can select and move large numbers of objects at once. My neighborhood was off by a couple hundred meters. I went and fixed it all back up manually. I don't have the time to manually move everything, so there must be some kind of automated solution? Does this problem exist for the whole of the US? Is it well understood? No, it doesn't exist for the whole US. It is well understood. TIGER is a collection of data from many, many sources. Some of these were from local governments that were themselves aggregating data from multiple sources. Sometimes, the data were off from one of these sources. It was not collected for the sole purpose of mapping, so nobody really cared. Also if you look at the diagonal (NW-SE) part of the Arizona-Mexico border there are streets in the US that appear in Mexico - the whole border area appears to be a mess. How do I know what needs to be done to fix this? The error looks larger than 100ft. You really need some good GPS traces of the streets, or you can try to align it on yahoo imagery. -- Dave ___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us
Re: [Talk-us] Blame me for JOSM yellowness
On Mon, 2009-04-27 at 09:50 -0700, Apollinaris Schoell wrote: tiger data is that the quality is from excellent to really bad in accuracy tiger data is old and contains abandoned roads tiger has no level info, no direction for oneways, no turn restrictions, or any other fancy info which we add in osm all this requires rework for most freeways, but it is good enough for lot of residential areas. As others pointed out the reviewed tag is too crude to mean anything we can all agree on. My personal view on TIGER is that it is like GPS tracks on steroids. GPS tracks are an excellent source of mapping data to help build OSM. They have good information about where roads are, what their shapes are, etc... But they generally can't tell you about an intersection's layout, turn restrictions or other surface features. But, they can't be relied upon universally. People have bad GPSes, they also forget to turn off their lock to road feature, etc... TIGER is a wonderful skeleton on which to build but it along is not a complete or *good* map. -- Dave ___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us
Re: [Talk-us] Tool to fix Tiger data
On Fri, 2009-05-01 at 08:32 -0700, Apollinaris Schoell wrote: this one is way more useful than maplint. but it's europe only at the moment Anyone with plans to provide a US version? Tiger doesn't have directions on (some?) motorways, motorway_link and may of them are wrong. this service can flag dead ends. http://keepright.ipax.at Ugh. Those are all written in sql. :( I've been using the JOSM validator plugin to fix this stuff on a small scale. I've had dreams of using the same code to do fixing of TIGER stuff outside of JOSM, but haven't ever gotten around to it. -- Dave ___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us
Re: [Talk-us] Blame me for JOSM yellowness
On Fri, 2009-04-24 at 09:40 -0700, Alan Millar wrote: If you don't like the tag, you don't have to use it. But I have been waiting for this highlighting feature for a long time, but never got around to figuring out enough in JOSM, so I am happy to see it. To each his own; there is room for all of us in this project. I'd also be very happy if JOSM flipped the tag for me when I edit a tiger object. It seems reasonable enough that if I'm editing something that we can consider it reviewed. I certainly don't want to have to go flip it manually every time I go fixing some minor road details. -- Dave ___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us
Re: [Talk-us] Blame me for JOSM yellowness
On Fri, 2009-04-24 at 10:26 -0700, Apollinaris Schoell wrote: forcing every josm user to accept it is somewhere between ignorance and dictatorship Hi Apollinaris, I'd be happy to code up a custom version of JOSM for you that doesn't have the yellowness. I'd also be happy to looking into making it a persistent option so you can turn it off once in your preferences and never worry about it again. I can't guarantee anything about the base version of JOSM, but I can certainly customize it and share whatever I do with you. -- Dave ___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us
Re: [Talk-us] Duplicate TIGER imports
On Tue, 2009-04-14 at 15:41 -0700, Minh Nguyen wrote: A few weeks after DaveHansen imported the TIGER data for Ohio [1], RSatterf reimported the data for Greene County, Ohio [2]. As a result, every single way in the county is duplicated. On top of that, RSatterf's import also added a loose node (not connected to any way) for every node of every way in the county. Here's an example at the Montgomery–Greene county line [3]. It's a real mess, and it looks like we just need to delete every node or way last edited by RSatterf. We should keep ways that've been edited by another user since then, because in some cases DaveHansen's motorways etc. have probably been deleted in favor of RSatterf's. So does anyone have a handy mass deletion script? Urg. That's too bad. Actually, on the counties that I screwed up on and had to remove and re-apply, I just did it with pieces in JOSM I think. The scripts that I do have to do it are pretty tied to the BerkeleyDB format that I used for my cache. -- Dave ___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us
Re: [Talk-us] Duplicate TIGER imports
On Tue, 2009-04-14 at 19:22 -0500, Chris Lawrence wrote: On Tue, Apr 14, 2009 at 5:41 PM, Minh Nguyen m...@1ec5.org wrote: A few weeks after DaveHansen imported the TIGER data for Ohio [1], RSatterf reimported the data for Greene County, Ohio [2]. As a result, every single way in the county is duplicated. On top of that, RSatterf's import also added a loose node (not connected to any way) for every node of every way in the county. Here's an example at the Montgomery–Greene county line [3]. It's a real mess, and it looks like we just need to delete every node or way last edited by RSatterf. We should keep ways that've been edited by another user since then, because in some cases DaveHansen's motorways etc. have probably been deleted in favor of RSatterf's. So does anyone have a handy mass deletion script? It probably wouldn't be too hard to whip up something that uses the extended API to query the database and generate an OSM XML file you could churn through using the bulk uploader script (probably just an XSLT transform of the returned XML would do it). The only issue is that you might have some shared nodes that are in-use by ways that you don't want to delete. I used the xapi interface and I'm already running through them to clean out the duplicates. Minh, I seee 27 standalone nodes of yours that you've fixed up. Do you mind if we just delete these? -- Dave ___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us
Re: [OSM-talk] Statistics and TIGER import question: What happened in August 2007?
On Mon, 2009-03-16 at 20:05 -0500, Ian Dees wrote: I'm sure DaveH will be able to chime in on this with more clarity, but I think that the original TIGER import had some data consistency problems and so all of its data removed before the second import happened. Oddly enough, I never participated in the deletion of the old data. Maybe someone else did it in anticipation of my import starting. Dunno. -- Dave ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk
Re: [Talk-us] Tags for US Forest Service GIS Trail Data
On Thu, 2009-03-05 at 10:48 -0500, Russ Nelson wrote: Also, are there tags to keep information about metadata like the data source (i.e. gps, digitized, etc)? Chris and Dave have set a standard for imports that says that existing metadata should be preserved. As long as you do that, anybody who comes along later can turn that metadata into OSM tags. Yeah, I'd say please preserve as much as you can *especially* so people can track the origin of the data. -- Dave ___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us
Re: [Talk-us] Tags for US Forest Service GIS Trail Data
On Thu, 2009-03-05 at 08:11 -0800, Matt Maxon wrote: Here in SoCal parking most anywhere with in a National Forest requires paying a fee $5 daily or $30 annual ($80 Public Lands pass too) Same basic system in Oregon and Washington. Some trailheads are special, usually when they're really busy for some reason. There are also entry requirements for some trails. For instance, each group needs to have a filled-out form when entering a national forest around here. Groups are also limited to 12 heartbeats. That stuff is good to capture in some way. -- Dave ___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us
Re: [Talk-us] TIGER 2008 Data is Out
On Thu, 2008-12-25 at 23:22 +1100, Justin Adler wrote: Hi folks, quick question about this Tiger lines and OSM. 1) Are there any import scripts out there which are not rails or php? something in .NET maybe? No. 2) Do the tiger lines have the following data (which could then be imported into OSM) : a) State shapes (eg. California, New York (state), Illinois, etc) b) County shapes (eg. Cook County (IL), DuPage County (IL) etc) c) City shapes (eg. San Fran, Boston, Chicago, etc.) d) Suburbs (eg. Oak Brook (Chicago), Naperville (Chicago), etc) e) Neighbourhoods (eg. Tribeca (NYC), Chelsea (NYC) Yes. 3) Does OSM have this data? Yes. -- Dave ___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us
Re: [Talk-ca] Tiger data as a slippy map option
On Fri, 2008-12-19 at 03:15 -0800, Sam Vekemans wrote: Where one option is to use an OpenLayers slippy map, where users could use a rendered version of all the Tiger data, and trace with it, just as they would with the Yahoo imagery layer? I'd really rather just import the data rather than be in a position to trace 170 million nodes and 13 million way. Tiger roads are done, at least anyway. -- Dave ___ Talk-ca mailing list Talk-ca@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-ca
Re: [Talk-ca] GeoBase and OpenStreetMap
On Wed, 2008-12-17 at 00:26 -0800, Dan Putler wrote: One way has the TIGER TLID attribute, the other way does not (the person doing the editing of the way missing the TLID probably didn't understand the relevance of it, and didn't think it mattered). There are several concerns here. First, as you pointed out, is that we have virtually no control over what other users in OSM do. There are no access controls or integrity constraints beyond some very simple ones. If we decided to strongly preserve the tiger TLIDs (or their GeoBase equivalent), I'm not even sure it would be possible without some serious changes to how OSM works. Moreover, in looking through the data in this area, I determined that a _large_ number of ways cover multiple block faces (so can't have a single TLID). Yes, virtually all TIGER objects represented as a single TLID were merged into larger ways in the OSM import. In these cases, the only way I can see to attach the TLIDs back on to them is to import them into GRASS, clean and break the ways at intersections, and then attempt to match them back to the original TIGER data using a combination of street name, proximity, and bearing. It can likely be done to an acceptable level of precision, but what a pain! If you have the tools to deal with these issues already, and do so on a regular basis, my concerns are misplaced. If not, then they are legitimate concerns. Oh, I don't have the tools to do it. I haven't had the need to write them. If you really want to track the GeoBase ways after they are imported, what about looking at the planet diffs? You could keep a record of what happened to each object as it gets modified by users. There would be no need to match up data because you would know how each piece got there. -- Dave ___ Talk-ca mailing list Talk-ca@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-ca
Re: [Talk-ca] GeoBase and OpenStreetMap
On Thu, 2008-12-11 at 15:02 -0500, Mepham, Michael wrote: My first question has to be “Why are you doing this?”. I have spent some time looking through the OSM web site and I understand the rational for building street maps where none exist or at least are not generally available but that is not the case here. I know of at least two other complete downloads of the GeoBase data for redistribution but still do not fully understand the reasons for replication / duplication. The basic reason is that we need to be able to edit it. We can't simply put data back into GeoBase, so we need a copy on which to work. Is there a way we even could get changes back to the owners of the data? I think the core of it is that OpenStreetmap isn't your normal user. We don't want to just take the data and put it on a map, or figure out where all the residents in an area live. One of our core goals is to be able to update and change the map. Secondly – How does this group expect maintenance to work? When the data suppliers pass updates to the GeoBase portal team and those updates are made available then GeoBase and OSM will be out of sync. What are the expectations on how or when they will be brought back into sync? For the US TIGER data, we are simply diverging. There is no plan that I know of, and relatively little need right now, to bring things back into sync. It is just a huge problem with no easy solutions. The easiest solution that I see is what we're doing now: leave the data, and let the users improve it, just like the rest of the world. These huge government databases have, in effect, been a jump start for OSM. But, I'm afraid they're a one-time thing. -- Dave ___ Talk-ca mailing list Talk-ca@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-ca
Re: [Talk-ca] Scripts to import GeoBase/GeoGratis into OSM
On Wed, 2008-12-10 at 13:35 -0500, Richard Degelder wrote: By the way do you know what they did with the AND import? Did they also just load up the map and leave it to the local mappers to correct and discrepancies and fix any errors as well? I realize that within places like China and India the AND import was working with a virtually clean slate but the mapping in the Netherlands was somewhat more advanced and so they would have run into the same problems we are encountering. Do you know who handled the AND import into OSM? I think they just did the same thing as me. I don't remember exactly who it was. If you can't find it in the wiki somewhere, I'll dig in my email for you. -- Dave ___ Talk-ca mailing list Talk-ca@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-ca
Re: [Talk-us] Tiger Data 2007
On Tue, 2008-10-28 at 15:46 -0700, Alan Brown wrote: If those 10% are located where someone has poured their heart into making a carefully constructed map - you could disillusion some of your most active contributors. Yup, I completely agree. But, one of the nice things is that the active contributors are the ones that tend to read mailing lists and see the OSM site regularly. They should be the easiest to contact and be the most flexible about finding the best ways to get this data imported. If somebody owns 95% of the edits in a county, I don't really *ever* think it is OK to overrule them, certainly not in some automated way. But, we surely have to distinguish those users from the ones that popped up, moved one road in potlach to match Yahoo, and were never heard from again. -- Dave ___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us
Re: [Talk-us] Tiger 2007 data
On Sat, 2008-10-25 at 10:37 +1100, Nick Hocking wrote: I'm firmly convinced that automatic uploads should only go into areas where there are NO user edited nodes or ways. Other updates need to be done manully to avoid data corruption. You have absolutely shown a number of cases where there was no merging and the TIGER data was simply splatted over existing data. This is certainly one of the downsides of the approach that was tried before. I uploaded Oregon first because I had already talked to all the mappers in my own state. I then proceeded to upload all the states that were completely empty. After that, I used this map: http://ted.mielczarek.org/code/osm/counties/ and uploaded only counties that were virtually empty. Interestingly, people started contacting me pretty quickly saying you missed my county! That's because the areas with the most data were also the places with the most active mappers! Almost all the prolific mappers knew that they could never compete with the pure amount of TIGER data and went to the heroic effort of merging their existing work with it. In the end, I think there was only a single county (out of ~3000) in the US that didn't get TIGER data in one way shape or form, and I gave people plenty of time to decline. So, I completely disagree that the merging can and should be done manually. There's simply too much data. It's also not feasible to blacklist every county that has *ever* had a single edit. But, I don't want to corrupt anything. Just as before, I'm going to let all the decisions be made by the local mappers. If you're concerned, please stay on this list because I'll always announce things here (at least). -- Dave ___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us
Re: [Talk-us] Tiger 2007 Data
On Fri, 2008-10-24 at 22:09 +1100, Nick Hocking wrote: Can you confirm that any bulk upload of Tiger 2007 date will not erase or be overlaid over/under/alongside any existing user edits. On my last US trip I've got about 6000 miles of gps tracks. I've only edited in a few hundred miles of them so far but am reluctant to do any more work if the Tiger 2007 data will destroy what I've done so far. Dude. Chill. :) I don't know what's going to happen. I don't even really have working data to look at, yet. Let's say there's a county with a single node set to reviewed=yes. the rest of the 4 million nodes in the county aren't set as reviewed. That county has much improved TIGER data. Should we leave it alone? What about 10 nodes? 100? We need to answer those questions at some point. Personally I don't really care where we draw the line. Destroying (or corrupting) existing edits would nullify the current efforts by Cloudmade to enhance a US community (IMHO). Again, let's calm down a little bit. Were you around for the last import? Did you see how I handled data conflicts in that one? Was there a problem there that needs fixing this time around? -- Dave ___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us
Re: [OSM-talk] [Talk-us] TIGER 2007, first OSM data
On Tue, 2008-10-21 at 22:58 -0500, Chris Lawrence wrote: On Mon, Oct 20, 2008 at 8:16 PM, Dave Hansen [EMAIL PROTECTED] wrote: You can run it like this: perl tiger-shp-to-osm.pl data/ftp2.census.gov/geo/tiger/TIGER2007FE/41_OREGON/41055_Sherman/fe_2007_41055_edges.zip out-dave.osm Don't count on any more tarball releases. I think I'll just stick it in a git repo and forget about it. Dave - Thanks! A couple of small problems so far: - The tarball doesn't include daveperl.pm; I found it elsewhere on your site. - Latitude and longitude seem to be reversed in the output, at least when I use the data for Webb County, Texas (FIPS 48479) as the input. This *really* confuses JOSM (e.g. it hangs). Heh, I noticed that too once I ran it on my county. I think you're the only other one to notice. :) I fixed this problem using: sed -e 's/lat=/xxx=/g' -e 's/lon=/lat=/g' -e 's/xxx=/lon=/' TX-webb.osm | TX-webb-fixed.osm As the accuracy improvement project hasn't affected this area yet, the shapefiles aren't any improvement over the existing data (and are worse than the manual edits a few of us have made), but hopefully the effort will be worthwhile elsewhere! If you know of another county that has had improvements that you want to check, let me know. I'll run it on any new counties, too. -- Dave ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk
Re: [Talk-us] TIGER 2007, first OSM data
On Tue, 2008-10-21 at 22:58 -0500, Chris Lawrence wrote: On Mon, Oct 20, 2008 at 8:16 PM, Dave Hansen [EMAIL PROTECTED] wrote: You can run it like this: perl tiger-shp-to-osm.pl data/ftp2.census.gov/geo/tiger/TIGER2007FE/41_OREGON/41055_Sherman/fe_2007_41055_edges.zip out-dave.osm Don't count on any more tarball releases. I think I'll just stick it in a git repo and forget about it. Dave - Thanks! A couple of small problems so far: - The tarball doesn't include daveperl.pm; I found it elsewhere on your site. - Latitude and longitude seem to be reversed in the output, at least when I use the data for Webb County, Texas (FIPS 48479) as the input. This *really* confuses JOSM (e.g. it hangs). Heh, I noticed that too once I ran it on my county. I think you're the only other one to notice. :) I fixed this problem using: sed -e 's/lat=/xxx=/g' -e 's/lon=/lat=/g' -e 's/xxx=/lon=/' TX-webb.osm | TX-webb-fixed.osm As the accuracy improvement project hasn't affected this area yet, the shapefiles aren't any improvement over the existing data (and are worse than the manual edits a few of us have made), but hopefully the effort will be worthwhile elsewhere! If you know of another county that has had improvements that you want to check, let me know. I'll run it on any new counties, too. -- Dave ___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us
Re: [OSM-talk] Tiger 2007 Data
On Mon, 2008-10-20 at 09:21 +0200, Lambertus wrote: Any idea about the differences between the Tiger data in the OSM db and this new set? By that I mean: is it just road network updates or is the data also better defined? The current tiger data in the db may look alright on a map, but routing wise it is a real mess. I have no idea since I can't even convert it to OSM format quite yet. I'm in the process of converting the old ruby code over to perl. I hate ruby with a passion, and I think it slowed me down horribly last time. In the newer code, I will make a substantial effort to fix up some of the things that were wrong with the old code: 1. No braided streets. My old code just tried to make individual ways with the same name as long as possible. I need to be more careful at 3/4-way *intersections* when the ways have the same name. 2. Follow motorway_links and ensure they hit motorways. TIGER only has one 'onramp' tag, and it got converted wholesale to highway=motorway_link, even when it is nowhere near a motorway 3. Pay more attention to connections. Don't let motorways and highway=residential share nodes as easily. Anyone want to add to my list? How about put it on the wiki for me? ;) -- Dave ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk
Re: [OSM-talk] Tiger 2007 Data
On Mon, 2008-10-20 at 09:43 +0200, vegard wrote: On Sun, Oct 19, 2008 at 10:54:55AM -0700, Dave Hansen wrote: Has anyone looked at importing the TIGER 2007 data yet? I was going to start coding up the conversion utilities to get started. It appears that this shapefile format may have existing OSM converters out there. Anyone want to admit to having one? ;) I see it like this: What could be very useful to have, is a mapping between tiger data (old set) and OSM data. It could be to late for this round, but an external_id:tiger = that you'd *never* remove, is a good thing. That'll help when updating. Umm. We have this. It's called a tlid, and it's already in the data set. When TIGER objects got combined into a single OSM object, I preserved this tag. I *also* submitted patches to JOSM to preserve this tag when merging points and ways. -- Dave ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk
[OSM-talk] TIGER 2007, first OSM data
I'm trying to share early and often. :) Here's the first output from my new TIGER 2007 script. I used shp2osm.pl from SVN and added a perl port of a chunk of the ruby code from the original TIGER import. http://dev.openstreetmap.org/~daveh/tiger/2007/OR-Sherman.osm.bz2 This doesn't have any of the right OSM tags, but it *is* data of some kind and opens in JOSM. Here's the code that I used: http://dev.openstreetmap.org/~daveh/tiger/2007/tiger2007-tools-001.tar.gz You can run it like this: perl tiger-shp-to-osm.pl data/ftp2.census.gov/geo/tiger/TIGER2007FE/41_OREGON/41055_Sherman/fe_2007_41055_edges.zip out-dave.osm Don't count on any more tarball releases. I think I'll just stick it in a git repo and forget about it. -- Dave ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk
[Talk-us] TIGER 2007, first OSM data
I'm trying to share early and often. :) Here's the first output from my new TIGER 2007 script. I used shp2osm.pl from SVN and added a perl port of a chunk of the ruby code from the original TIGER import. http://dev.openstreetmap.org/~daveh/tiger/2007/OR-Sherman.osm.bz2 This doesn't have any of the right OSM tags, but it *is* data of some kind and opens in JOSM. Here's the code that I used: http://dev.openstreetmap.org/~daveh/tiger/2007/tiger2007-tools-001.tar.gz You can run it like this: perl tiger-shp-to-osm.pl data/ftp2.census.gov/geo/tiger/TIGER2007FE/41_OREGON/41055_Sherman/fe_2007_41055_edges.zip out-dave.osm Don't count on any more tarball releases. I think I'll just stick it in a git repo and forget about it. -- Dave ___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us
[OSM-talk] Tiger 2007 Data
Has anyone looked at importing the TIGER 2007 data yet? I was going to start coding up the conversion utilities to get started. It appears that this shapefile format may have existing OSM converters out there. Anyone want to admit to having one? ;) -- Dave ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk
Re: [OSM-talk] [Talk-us] Tiger 2007 Data
On Sun, 2008-10-19 at 11:10 -0700, Karl Newman wrote: On Sun, Oct 19, 2008 at 10:54 AM, Dave Hansen [EMAIL PROTECTED] wrote: Has anyone looked at importing the TIGER 2007 data yet? I was going to start coding up the conversion utilities to get started. It appears that this shapefile format may have existing OSM converters out there. Anyone want to admit to having one? ;) -- Dave What were you looking to import? I thought your TIGER import was a one-shot deal. I *wish* it was a 1-shot deal. That darn Steve C. seems to think that maps should be both accurate *and* up to date. The nerve! Anyway, it seems that the new data is substantially better than the old in some places. What I'd like to do is twofold: 1. regenerate .osm files for all the new TIGER data 2. Compare new .osm files to old TIGER data plus stuff edited in OSM Then, decide how if/when it is appropriate to write over the old TIGER stuff with new. Or, to merge it somehow. -- Dave ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk
Re: [OSM-talk] [Talk-us] Tiger 2007 Data
On Sun, 2008-10-19 at 11:25 -0700, Karl Newman wrote: Ah. Quite a trick... I seem to recall that somebody had wanted to do that earlier, but I think they got discouraged by the difficulty. Well, time may have made me forget what a pain the original import was. We'll see how far I get this time. :) -- Dave ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk
Re: [OSM-talk] [Talk-us] Tiger 2007 Data
On Sun, 2008-10-19 at 14:29 -0400, Russ Nelson wrote: Dave Hansen writes: Then, decide how if/when it is appropriate to write over the old TIGER stuff with new. Or, to merge it somehow. I've updated it in some cases. Perhaps only update if the data is unchecked? Sure, that would be one reasonable thing. But, for now, I'm just trying to get an idea of the scale of the problem. That's going to be a challenge in and of itself. -- Dave ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk
[Talk-us] Tiger 2007 Data
Has anyone looked at importing the TIGER 2007 data yet? I was going to start coding up the conversion utilities to get started. It appears that this shapefile format may have existing OSM converters out there. Anyone want to admit to having one? ;) -- Dave ___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us
Re: [Talk-us] Tiger 2007 Data
On Sun, 2008-10-19 at 11:33 -0700, Alan Brown wrote: Then, decide how if/when it is appropriate to write over the old TIGER stuff with new. Or, to merge it somehow. Be very, very careful here. Conflation is a difficult thing. I used to work at Tele Atlas, and there was a major project to conflate Tele Atlas North American data and GDT data (a company they just acquired). They had at least a hundred people committed full time to completing the task in a year (I don't know the exact number), with tens of millions in funding - and they failed in a big way. The head of the North American division got axed as a result. It's not a difficult thing if nothing has been changed since the last import. My goal for now is simply to overwrite the things that haven't been updated by people since the last time I touched them. -- Dave ___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us
Re: [Talk-us] using city data?
On Wed, 2008-08-20 at 17:36 -0700, Alan Brown wrote: I think this is a case of where, if I get clarification from them further, it *might* be okay, but the wording is too fraught with ambiguity to be safe. Here's the part I'm worried about - I explained in an e-mail what OpenStreetMap is about, they said sure!, sign this and we'll get it to you for free - and sent me this: Oh, boy! :) Personally, I'd probably want a lawyer to look at it. Mostly to make sure that what you've given the city to describe OpenStreetmap is in legal terms and done very tightly, legally speaking. *Especially* with political organizations, their loyalties can turn in 4 seconds. I wonder if OSM has any friendly attorneys like other Free Software communities do. -- Dave ___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us
Re: [Talk-us] TIGER 2007 files
On Thu, 2008-07-17 at 21:10 +, [EMAIL PROTECTED] wrote: Is the Census Bureau going to continue to make regular (ie. annual or semi-annual) data releases of street centerline data, or does the 2007 TIGER/Line Shapefile release represent the end of the project? I can't imagine this will be their last release. I'm sure they'll continuei If they plan on releasing incremental updates, is there an OSM plan in place for pulling from their updated information each time they release? or was the 2006 data intended to be a baseline that would then be improved and maintained only by OSM users? It was a real pain to import one static data set onto a blank slate. I can't even imagine trying to: 1. Read the new features 2. Find out what those were mapped as in 2006 when we pulled the TIGER data 3. Figure out where those features went in OSM 4. Figure out if those features have been updated 5. Which copy is better 6. Update those features in a safe manner and at a speed that would allow us to complete by the time the next data set is out. Seriously, I always saw TIGER as a one-time thing. If someone is really interested in doing this, I don't want to stop them. But, as the dude who did a pretty big chunk of the work for the original import, I can say that I don't really even have the time to begin on this one. :) What we might be able to do is find holes in the original data and see if those holes have been filled in. That might be a reasonably simple place to start if someone is interested. -- Dave ___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/cgi-bin/mailman/listinfo/talk-us
Re: [Talk-us] Portland data
On Wed, 2008-07-16 at 07:57 +0100, SteveC wrote: Can anyone (especially anyone local to Portand but it's not crucial) take some time to look and see? Adam says: I called Metro today, and they say their data is not public domain, so I think that makes it unusable on OSM. Oh well. Adam :) -- Dave ___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/cgi-bin/mailman/listinfo/talk-us
Re: [Talk-us] Adding Public Domain GIS data from Allegheny County (Pittsburgh) Pa
On Mon, 2008-07-07 at 16:10 -0400, Morgan Ress wrote: * High School Students that are working here for the summer, in a program designed to teach them about GIS and community planning. Currently, they are working on detailed maps of our neighborhood using QGIS - I'd like to make our work available to our community via OSM. Just curious, but what kind of data is this? We have some road data from TIGER, already. What would this add? -- Dave ___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/cgi-bin/mailman/listinfo/talk-us
Re: [Talk-us] bulk upload of data to OSM: roads, water, and orthos
On Wed, 2008-06-25 at 12:42 -0400, John Callahan wrote: Spatially it's no contest. I've attached just a few simple images to show what I mean. These show our new dataset in red vs TIGER 2007 in purple. Remember that the red lines match the hi-res photography. Wow. Hard to argue with that! It does look great. Attributes are also an improvement for geocoding, routing, and naming. True. We do have addresses in the TIGER data, but I chose not to upload them for now. OSM didn't have relations when I was doing the original TIGER upload, and I'm still not sure there is any consensus on how to do address data. Probably good to bring up on dev@ or [EMAIL PROTECTED] Good question about contacting OSM editors of this data. I can easily contact most of the GIS data professionals and govt'/consultant/University people who typically with transportation data. However, that does leave out the single individual, say at home, who modifies the data. Not sure how often that happens. I can always keep an copy of the current OSM data before uploading the new data set and replace parts of needed. Or is there a way to find any edits made since the intial loading of the TIGER? My suggestion would be to get a planet file, and try to extract the areas that you care about. http://wiki.openstreetmap.org/index.php/Planet.osm You could just about download the entire thing in JOSM, too. It's a pretty dinky^Wmodestly sized state. ;) Once you have a copy of the existing .osm data, just grep through the XML to look for authors, or look at the authors panel in JOSM. -- Dave ___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/cgi-bin/mailman/listinfo/talk-us
Re: [OSM-talk] Please restore deleted suburb
On Thu, 2008-05-22 at 11:34 -0400, Christopher Schmidt wrote: More seriously, I can try and find some time to fix up the code so that it parses braintree correctly. I guess we could also just cut the appropriate TIGER area out and upload that as well. Let me know if this interests anyone. -- Dave ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/cgi-bin/mailman/listinfo/talk
Re: [OSM-talk] TIGER mapping party
On Fri, 2008-05-09 at 07:05 +0900, Jeffrey Martin wrote: Why are there so many problems with the TIGER data? Because we're not using it for its intended purpose. It really is great data. Where do the extra roads come from? Are they planned roads? Ask your local government. They gave the data to the census bureau. They might be planned. Ask your local government. Will they be releasing new data? What happens then? I don't think we'll ever import TIGER again, unless something drastic happens. -- Dave ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/cgi-bin/mailman/listinfo/talk
Re: [Talk-us] US Hydrographic Data
On Wed, 2008-05-07 at 10:51 -0500, Ian Dees wrote: I was going to modify Matthew's script here: http://perrygeo.googlecode.com/svn/trunk/gis-bin/nhd_to_osm.py to try and fix the issues that he described in the header: - support holes in water bodies (islands) - tag OSM data with all available NHD data - split long ways in the resulting OSM data Dave, maybe you could point us to the script you used to import the TIGER data? That way we can try and do a similar thing for the NHD data? It was written in ruby. I inherited most of it from someone else. I think ruby sucked. :) http://sr71.net/~dave/osm/tiger/ -- Dave ___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/cgi-bin/mailman/listinfo/talk-us
Re: [Talk-us] US Hydrographic Data
On Thu, 2008-05-01 at 10:17 -0700, Karl Newman wrote: That would be awesome. Maybe we could rip out the TIGER hydrographic features and replace them with the NHD stuff. Maybe coastlines, too? I guess we'd have to be careful about duplicating/overwriting people's work, though. Uh. There are no TIGER hydrographic features in OSM. :) -- Dave ___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/cgi-bin/mailman/listinfo/talk-us
Re: [OSM-talk] TIGER unbraid tool now available
On Fri, 2008-04-25 at 14:46 -0700, Alan Millar wrote:
Unfortunately, it is in perl because that's what I know; I've never done
anything in Java yet. I've been wondering if this may be just the time to
learn it. I'm not sure if a JOSM plugin is a good place to start learning
Java or if that is biting off too much to start.
Any advice? Thanks
Thankfully, the validator tests don't require *too* much java. You can
basically cut 'n paste from an existing one with very little trouble.
I hadn't touched Java in about 10 years before I started looking at
JOSM. I do a lot of C on a daily basis, but no Java. It wasn't hard to
pick back up.
Here's an example validator test:
http://svn.openstreetmap.org/applications/editors/josm/plugins/validator/src/org/openstreetmap/josm/plugins/validator/tests/DuplicateNode.java
You basically examine all the Osm Primitives in a couple of visit
functions like this:
@Override
public void visit(Node n)
{
nodes.add(n.coor, n);
}
Usually, you just collect them into a structure like that 'nodes' list.
Then, in the endTest() function you go an examine all of them. I've
been keeping custom versions of JOSM around that have some really nice
helpers for writing JOSM plugins.
http://dev.openstreetmap.org/~daveh/josm/018/
Like this:
for (Way wtmp : Main.ds.rl.waysUsingNode(n)) {
That iterates over a list of all the ways using Node 'n'. You probably
recognize this operation. I think you do it a bit in your perl script.
-- Dave
___
talk mailing list
talk@openstreetmap.org
http://lists.openstreetmap.org/cgi-bin/mailman/listinfo/talk
Re: [Talk-us] [OSM-talk] TIGER unbraid tool now available
On Fri, 2008-04-25 at 14:46 -0700, Alan Millar wrote:
Unfortunately, it is in perl because that's what I know; I've never done
anything in Java yet. I've been wondering if this may be just the time to
learn it. I'm not sure if a JOSM plugin is a good place to start learning
Java or if that is biting off too much to start.
Any advice? Thanks
Thankfully, the validator tests don't require *too* much java. You can
basically cut 'n paste from an existing one with very little trouble.
I hadn't touched Java in about 10 years before I started looking at
JOSM. I do a lot of C on a daily basis, but no Java. It wasn't hard to
pick back up.
Here's an example validator test:
http://svn.openstreetmap.org/applications/editors/josm/plugins/validator/src/org/openstreetmap/josm/plugins/validator/tests/DuplicateNode.java
You basically examine all the Osm Primitives in a couple of visit
functions like this:
@Override
public void visit(Node n)
{
nodes.add(n.coor, n);
}
Usually, you just collect them into a structure like that 'nodes' list.
Then, in the endTest() function you go an examine all of them. I've
been keeping custom versions of JOSM around that have some really nice
helpers for writing JOSM plugins.
http://dev.openstreetmap.org/~daveh/josm/018/
Like this:
for (Way wtmp : Main.ds.rl.waysUsingNode(n)) {
That iterates over a list of all the ways using Node 'n'. You probably
recognize this operation. I think you do it a bit in your perl script.
-- Dave
___
Talk-us mailing list
Talk-us@openstreetmap.org
http://lists.openstreetmap.org/cgi-bin/mailman/listinfo/talk-us
Re: [OSM-talk] OSM TIGER-based map quality
On Fri, 2008-04-04 at 13:51 -0400, Christopher Schmidt wrote: On Fri, Apr 04, 2008 at 10:31:11AM -0700, Dave Hansen wrote: On Fri, 2008-04-04 at 09:12 -0400, Christopher Schmidt wrote: That is exactly what I am suggesting, based on an examination of the objects in the area you're looking at: all of them have been updated several times (as the history URL above demonstrates) by a single user in what seems to clearly be a cleanup effort. (This was based on using an OpenLayers map to select 10 different streets based on the lonlat I observed in your JOSM instance and view the history for each.) If this is true, then we can probably go back and fix it. We have all of the TIGER tlid (unique ids) for all of the uploaded data. Have those remained the same in the new TIGER data? Fix... what? OSM is correct here... perhaps you mean We can improve TIGER 2007 with OSM data? Did I misunderstand what's going on? I assumed that the TIGER '07 data is better than the TIGER '05 (or so) data that we populated OSM with. If it is better, we can update OSM from TIGER '07. -- Dave ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/cgi-bin/mailman/listinfo/talk
Re: [OSM-talk] OSM TIGER-based map quality
On Fri, 2008-04-04 at 11:04 -0700, Dan Putler wrote: Not all counties have been improved through the MAF/TIGER Accuracy Improvement Project (MTAIP). Here is a link to the counties that have not been improved in the 2007 TIGER data: http://www.census.gov/geo/www/tiger/tgrshp2007/tgrshp07nomtaip.txt Cool, thanks for the pointer. That looks like ~1100 of the ~3500 total counties in the US. -- Dave ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/cgi-bin/mailman/listinfo/talk
Re: [OSM-talk] [josm-dev] Coastline checker / fixer
On Thu, 2008-04-03 at 00:18 +0100, Mark Williams wrote: Can anyone tell me why Validator (the normal one) chokes on this http://www.openstreetmap.org/?lat=51.49219lon=0.27476zoom=17 please? I can reverse the way all I like, it's not duplicated, it's clockwise whichever way the arrows go though! The problem is that the validator looks at only one of the segments to determine whether or not it is clockwise. It just checks to see if a particular pair of nodes is a certain direction away from the others. This works for perfectly round bodies of water, but not for all weird shapes. It's just broken. I rewrote this particular check. Look at WronglyOrderedWays.java in here: http://dev.openstreetmap.org/~daveh/josm/016/plugins-16.diff -- Dave ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/cgi-bin/mailman/listinfo/talk
Re: [Talk-us] highway tags in the US
On Mon, 2008-03-03 at 19:36 -0600, Alex Mauer wrote: Dave Hansen wrote: I'm pretty sure I know one when I see one these days. http://wiki.openstreetmap.org/index.php/Map_Features A restricted access major divided highway, normally with 2 or more running lanes plus emergency hard shoulder. Equivalent to the Freeway, Autobahn etc.. Bingo. It's truly restricted access. No access except from onramps. It's divided. It also has emergency shoulders. Is is effectively an interstate. There are many roads that fit those definitions, but have, for example, too-sharp curves, too-low bridges, perhaps too-narrow shoulders, etc. to meet the legal definition of an interstate. Of course, it's very possible that they've simply not been designated as Interstate, but my point is that it's not easy to tell at a glance. Yep, you're probably right. So, go submit a proposal and get the motorway definition changed. Right now, I'm following it to the letter. It doesn't matter that motorway!=interstate. It's easy to tell an interstate from its name anyway. -- Dave ___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/cgi-bin/mailman/listinfo/talk-us
Re: [Talk-us] highway tags in the US
On Mon, 2008-03-03 at 23:23 -0500, Bone Killian wrote: certainly a highway that meets the standards without being designated should be tagged as motorway, but as IMHO the only thing that qualifies a road as a motorway (in the US) is the big red and blue signage identifying it as part of the interstate highway system. Have you actually read the highway definition on the map features page? http://wiki.openstreetmap.org/index.php/Map_Features It has zero to do with shiny red signs. :) In fact, there are even stretches of interstate in this country which aren't technically motorways. http://en.wikipedia.org/wiki/Interstate_93 : I-93 passes through Franconia Notch State Park as a Super-2 parkway, the only instance of a two-lane Interstate highway in the United States. This stretch carries a 45 mile per hour speed limit. For the trip through Franconia Notch, I-93 and U.S. Route 3 run concurrently. -- Dave ___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/cgi-bin/mailman/listinfo/talk-us
Re: [Talk-us] highway tags in the US
On Fri, 2008-02-29 at 11:02 -0600, Alex Mauer wrote: Dave Hansen wrote: For instance, OR217 and US26 west of Portland are both divided, multi-lane, limited access highways. Despite not being interstates, they *ARE* motorways. Hmm, are you sure? maybe they just look like motorways; there are a lot of almost-motorway roads I'm pretty sure I know one when I see one these days. http://wiki.openstreetmap.org/index.php/Map_Features A restricted access major divided highway, normally with 2 or more running lanes plus emergency hard shoulder. Equivalent to the Freeway, Autobahn etc.. Bingo. It's truly restricted access. No access except from onramps. It's divided. It also has emergency shoulders. Is is effectively an interstate. -- Dave ___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/cgi-bin/mailman/listinfo/talk-us
Re: [Talk-us] highway tags in the US
On Thu, 2008-02-28 at 20:18 -0600, Ian Dees wrote: I have a hard time deciding which value to use based on the UK-centric descriptions on the wiki. They're not hard and fast rules, honestly. You also can't completely say all (US/State/County) highways are primary/secondary/tertiary, etc... For instance, OR217 and US26 west of Portland are both divided, multi-lane, limited access highways. Despite not being interstates, they *ARE* motorways. As for primary/secondary/tertiary. I basically think that primaries are those really big roads that happen once every mile or two. They're the ones where WalMart is. :) -- Dave ___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/cgi-bin/mailman/listinfo/talk-us
Re: [Talk-us] How accurate is Tiger data vs Yahoo Aerial?
On Fri, 2008-02-22 at 12:23 -0800, [EMAIL PROTECTED] wrote: Hi- I've just joined up and I'd like to help out cleaning up the map for my area in Beaverton/Portland Oregon. It looks like it is completely covered already by the Tiger data. But I've noticed many displacement problems where the Tiger data doesn't line up with the Yahoo aerial photos. Hey!! Another Portland mapper!! I see the same displacement of the TIGER data. Some of it is really bad. Cornell road out by my house: http://www.informationfreeway.org/index.php?lat=45.53651932780694lon=-122.89710601634569zoom=15layers=F0B0F was about 100 yards off, and *RIGHT* on top of another road. It was really confusing to look at those traces. -- Dave ___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/cgi-bin/mailman/listinfo/talk-us
Re: [OSM-talk] Error while uploading with JOSM
On Wed, 2008-01-30 at 09:00 -0800, Cristiano Giovando wrote:
I confirm what Rob said, it actually resumed from where it left. But
it's also true it took many tries before I was able to upload the
entire dataset. I suspect this problem is more likely with large
datasets, and it may just be something could be tweaked in JOSM to
extend the connection timeout limit.
Attached is a patch to JOSM to do server retries as well as do some
crude prediction of how long an upload might take. I've been using it
for months and it works quite well for me.
I _think_ gabriel just applied it to JOSM's svn. So you might want to
try the latest JOSM and see if it is there.
-- Dave
--- src/org/openstreetmap/josm/io/OsmServerWriter.java (revision 528)
+++ src/org/openstreetmap/josm/io/OsmServerWriter.java (working copy)
@@ -12,6 +12,7 @@
import java.net.HttpURLConnection;
import java.net.URL;
import java.net.UnknownHostException;
+import java.net.SocketTimeoutException;
import java.util.Collection;
import java.util.LinkedList;
@@ -56,6 +57,27 @@
* Send the dataset to the server. Ask the user first and does nothing if he
* does not want to send the data.
*/
+ private static final int MSECS_PER_SECOND = 1000;
+ private static final int SECONDS_PER_MINUTE = 60;
+ private static final int MSECS_PER_MINUTE = MSECS_PER_SECOND * SECONDS_PER_MINUTE;
+
+ long uploadStartTime;
+ public String timeLeft(int progress, int list_size) {
+ long now = System.currentTimeMillis();
+ long elapsed = now - uploadStartTime;
+ if (elapsed == 0)
+ elapsed = 1;
+ float uploads_per_ms = (float)progress / elapsed;
+ float uploads_left = list_size - progress;
+ int ms_left = (int)(uploads_left / uploads_per_ms);
+ int minutes_left = ms_left / MSECS_PER_MINUTE;
+ int seconds_left = (ms_left / MSECS_PER_SECOND) % SECONDS_PER_MINUTE ;
+ String time_left_str = Integer.toString(minutes_left) + :;
+ if (seconds_left 10)
+ time_left_str += 0;
+ time_left_str += Integer.toString(seconds_left);
+ return time_left_str;
+ }
public void uploadOsm(CollectionOsmPrimitive list) throws SAXException {
processed = new LinkedListOsmPrimitive();
initAuthentication();
@@ -65,13 +87,18 @@
NameVisitor v = new NameVisitor();
try {
+ uploadStartTime = System.currentTimeMillis();
for (OsmPrimitive osm : list) {
if (cancel)
return;
osm.visit(v);
-Main.pleaseWaitDlg.currentAction.setText(tr(Upload {0} {1} ({2})..., tr(v.className), v.name, osm.id));
+int progress = Main.pleaseWaitDlg.progress.getValue();
+String time_left_str = timeLeft(progress, list.size());
+Main.pleaseWaitDlg.currentAction.setText(tr(Upload {0} {1} (id: {2}) {3}% {4}/{5} ({6} left)...,
+ tr(v.className), v.name, osm.id, 100.0*progress/list.size(), progress, list.size(), time_left_str));
osm.visit(this);
Main.pleaseWaitDlg.progress.setValue(Main.pleaseWaitDlg.progress.getValue()+1);
+Main.pleaseWaitDlg.progress.setValue(progress+1);
}
} catch (RuntimeException e) {
e.printStackTrace();
@@ -149,23 +176,25 @@
* @param addBody codetrue/code, if the whole primitive body should be added.
* codefalse/code, if only the id is encoded.
*/
- private void sendRequest(String requestMethod, String urlSuffix,
- OsmPrimitive osm, boolean addBody) {
+ private void sendRequestRetry(String requestMethod, String urlSuffix,
+ OsmPrimitive osm, boolean addBody, int retries) {
try {
+ if (cancel)
+return; // assume cancel
String version = Main.pref.get(osm-server.version, 0.5);
URL url = new URL(
Main.pref.get(osm-server.url) +
/ + version +
/ + urlSuffix +
/ + (osm.id==0 ? create : osm.id));
- System.out.println(upload to: +url);
+ System.out.print(upload to: +url+ ... );
activeConnection = (HttpURLConnection)url.openConnection();
activeConnection.setConnectTimeout(15000);
activeConnection.setRequestMethod(requestMethod);
if (addBody)
activeConnection.setDoOutput(true);
activeConnection.connect();
-
+ System.out.println(connected);
if (addBody) {
OutputStream out = activeConnection.getOutputStream();
OsmWriter.output(out, new OsmWriter.Single(osm, true));
@@ -180,25 +209,45 @@
activeConnection.disconnect();
if (retCode == 410 requestMethod.equals(DELETE))
return; // everything fine.. was already deleted.
- if (retCode != 200) {
-// Look for a detailed error message from the server
-if (activeConnection.getHeaderField(Error) != null)
- retMsg += \n + activeConnection.getHeaderField(Error);
+ if (retCode != 200 retCode != 412) {
+if (retries = 0) {
+ retries--;
+ System.out.print(backing off for 10 seconds...);
+ Thread.sleep(1);
+ System.out.println(retrying (+retries+ left));
+ sendRequestRetry(requestMethod, urlSuffix, osm, addBody, retries);
+} else {
+ // Look for a detailed error message from the server
+ if
Re: [OSM-talk] [Talk-us] TIGER Map Updates
On Mon, 2007-12-31 at 04:01 -0800, Alex S. wrote: John Wolter wrote: TIGER depicts motorways as a single way It depicts almost all dual-carriageway roads as a single way. And sometimes it doesn't even say when it does. These are widespread enough that I do think we probably need to teach the renderer about them, at least for now. -- Dave ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/cgi-bin/mailman/listinfo/talk
Re: [OSM-talk] [Talk-us] TIGER Map Updates
On Mon, 2007-12-31 at 00:30 -0500, Paul Fox wrote: dave wrote: Yeah, that's the trouble with the TIGER data. Its coverage is excellent, but the quality can be worse than what's there. So, do you wow. i'm beginning to realize that we in new england must be very lucky. sure, tiger shows a lot of non-existent roads, but those that are there have always seemed very accurate to me. i'm sorry to hear that the rest of it is so bad. They're not *that* bad in most places. I get the idea that there were many kinds of mapping sources integrated into TIGER. If some were aerial photos, I think the distortion at the edges of the frames is probably to blame for a bunch of the problems. My own street is ~20m off. It sucks. :) But, most of the surrounding area is much, much better. -- Dave ___ talk mailing list talk@openstreetmap.org http://lists.openstreetmap.org/cgi-bin/mailman/listinfo/talk
