Re: [Talk-us] Fwd: Mapping error
On Wed, May 19, 2010 at 8:33 PM, SteveC st...@asklater.com wrote: Anyone near Carlsbad, CA? The guy sent me an image too showing where the bug is. Yours c. Steve Begin forwarded message: From: Gerry Sikora gerrysik...@mac.com Date: May 19, 2010 9:51:11 MDT To: st...@asklater.com Subject: Mapping error Sorry I can't correct an error, but I hoping that you can pass this along. There is a relatively new housing development in Carlsbad California. The open map shows what I believe is a road proposal of the developer and not the as built map. Some of the names are correct but that's about it. I've added Gerry's report to OpenStreetBugs. Anybody in / near Carlsbad care to check this out? http://openstreetbugs.schokokeks.org/?lat=33.10058lon=-117.29969zoom=15layers=B00T ___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us
[Talk-us] Cloudmade california.osm: dups or osmosis bug?
Is it the dataset or osmosis that is giving me a single 2-node duplicate for each postGIS table created by osmosis? Or PEBCAK? ___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us
Re: [Talk-us] Appalachian Trail data
Yup, Then it's a good reason to go an physically survey it. It's fine to load the .gpx file onto your device... as long as your physically hiking/waking/driving to the TrailHeads, it's fine to use... then you manualy update OSM that way. ... just because the AT data is Official doesn't mean that it is actually accurate to the physical land. I am finding the same with the Trans Canada Trail gpx data. In some cases, the source data was collected a long time ago and local area trail groups have changed the trail but didn't tell the Master Source of Trans Canada Trail that it's been updated. (and sometimes the origional data was collected when the trail is along railbeds that are in Canyons so the GPS recieves a poor signal. In those area's i see a 20 meter difference. And in other areas i found that the route is changed. Happy Hiking :-) You can also post your trail/route over on GPSies.com that system will donate your GPS tracks to OSM. So it's a Win-win. (GPSies.com also uses OpenCycleMap as a background map so that's great too) Cheers, Sam Vekemans Across Canada Trails ... PS. Im getting ready to bike the entire Trans Canada Trail. but there is one problem. .. the Trans Canada Trail is a Greenway and not a Biking Trail nor is it a hiking trail ... LOL :-) ... at least the Appalachian Trail is actually a designated Hiking Trail, PPS. yes, im also working on the National Hiking Trail (unfortunately the folks working on it have sold their sole to the Trans Canada Trail) :( ... so that knowone will be able to actually use the TCT end-to-end oh well, more work for me :-) (see above username) :-) but 1st I need a detailed basemap. So for you, it's a good thing that TIGER has already been imported, so its just a matter of correcting as you go. On Thu, May 20, 2010 8:10 PM, Eric Christensen e...@christensenplace.uswrote: I'm getting ready to hike a small portion of the Appalachian Trail (AT) and was looking for data to put into my GPS. It appears that portions of the AT have been added to OSM with some missing sections. The Appalachian Trail Conservancy has some interesting information on their website[1] which looks like good information for OSM but I don't see any licensing information, at first glance. Has anyone contacted them about possible inclusion of their data into OSM? If not, I could try to work with them so we could include their data. It would be a great asset to have. [1] http://www.appalachiantrail.org/site/c.mqLTIYOwGlF/b.4805623/k.438D/Appalachian_Trail_GIS_and_GPS_Data.htm Thanks, Eric Christensen ___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us ___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us
[Talk-us] Address Lookup
On Wed, 2010-05-19 at 08:54 -0500, Lord-Castillo, Brett wrote: If someone were to use OSM for dispatching, dispatching software generally requires a destination address to be associated with a corresponding street in order to dispatch to an address point (as opposed to dispatching to an interpolated street geocode). That would be one reason for associating objects with the streets they are on. It is also useful for non-USPS situs addresses (for example, parcel lot addresses for office buildings or condos). Brett Lord-Castillo Information Systems Designer/GIS Programmer St. Louis County Police Office of Emergency Management 14847 Ladue Bluffs Crossing Drive Chesterfield, MO 63017 Office: 314-628-5400 Fax: 314-628-5508 Direct: 314-628-5407 -Original Message- Date: Tue, 18 May 2010 23:00:45 -0400 From: David ``Smith'' vidthe...@gmail.com Subject: Re: [Talk-us] Street Naming Conventions To: talk-us@openstreetmap.org Message-ID: aanlktinvugzsb2fsxicwduebb6ip7wdk7smi1o-2p...@mail.gmail.com Content-Type: text/plain; charset=UTF-8 On Tue, May 18, 2010 at 10:39 AM, Phil! Gold phi...@pobox.com wrote: * David ``Smith'' vidthe...@gmail.com [2010-05-14 23:58 -0400]: 5) The value of addr:street=* should contain the abbreviated form of the street name according to USPS standards, regardless of the way the street name is signed. The point of addr:street is to associate the address to a particular road, so its value needs to match the name of the road. ?(There's also the associatedStreet relation, but more people use the addr:street tag.) As Frederik already asserted, that's incorrect. But if for some reason you need to associate an object with a street without using an AssociatedStreet relation, you could always give the street its own addr:street tag with the same value as all of the objects along it, which uses the same USPS-based abbreviation. But I'm not sure what is accomplished by associating objects with the street they're on. (As far as I know, the original point of the associatedStreet relation was to automatically imply addr:street values for all of the objects by using the street's name or addr:street value. What you said is kind of backwards from that.) The goal of Open Street Map is to eventually do everything that commercial map products do. This would include address lookup. I've looked around and the way of associating addresses with streets doesn't seem to work very well. The simplest way (requiring the fewest nodes) still requires a lot of work. For instance, for an example I've picked a street around my area: West 2550 North. This is just the ways needed for the streets themselves. (I didn't include the names on the cross streets because they don't matter for this example.) AB C D E || | | | || | | | +--+-+--+---+---+---+---+-- || | | | | || | | | | FG H From what I understand, next to each place where another street intersects this street I will have to create another node (on each side of the street) tagged with addr:street and addr:housenumber. I will need to connect the nodes on each side of the street with a relation. The relation I will need to tag with addr:interpolation and even/odd, as appropriate. This makes the simple street above now look like this: AB C D E || | | | || | | | **--*---*---*---*---*-* +--+-+--+---+---+---+---+-- **--*---*---*---*---*-* || | | | | || | | | | FG H This is a LOT of data to manually add. Is there a simpler way? No, I don't have a better idea. - Val - ___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us
