and to the list, sorry ---------- Forwarded message ---------- From: Martijn van Exel <[email protected]> Date: Wed, Mar 28, 2012 at 3:25 PM Subject: Re: [Talk-us] PostGiS Queries To: Hilton Long <[email protected]>
Interesting. By eliminating too close nodes you mean generalization? That should not be too difficult to do using ST_Simplify. Automatically detecting gaps is something that I am currently looking into (also for routing purposes). I was going to look at all endpoints of motorways, trunks , primaries and secondaries and look at the distance between them and the closest way of the same type or the corresponding _link type. Does that sound like a good approach to you? I guess much of this was done around the original TIGER import (for example the 250 cities project[1]) but I wasn't around then to know how that was done and the wiki does not reveal very much about the processes either. Martijn [1] https://wiki.openstreetmap.org/wiki/TIGER_fixup/250_cities On Wed, Mar 28, 2012 at 1:58 PM, Hilton Long <[email protected]>wrote: > Thanks, Martijn.**** > > From a quick look at the links below, they seem to be routing engines. > What I’m interested in is automating a review of road networks from Tiger > and other data to fill gaps, eliminate too close nodes, and generally get > the data so that mkgmap or cgpsmapper can handle it with a minimum of > errors. I figured since all that Tiger data was uploaded there must have > been an automated way to check and correct those errors. I’ve gotten > PostGIS to do a lot of it, but not all, and I was hoping to find a library > of routines that would save me working it all out for myself.**** > > ** ** > > Thanks again,**** > > Hilton**** > > 1082 N 4200 W**** > > Parowan, UT**** > > ** ** > > *From:* [email protected] [mailto:[email protected]] *On Behalf Of *Martijn > van Exel > *Sent:* Wednesday, March 28, 2012 12:06 PM > *To:* Hilton Long > *Cc:* [email protected] > *Subject:* Re: [Talk-us] PostGiS Queries**** > > ** ** > > That would have to be a pretty elaborate set of PostGIS operations. > This is the OSM list, so we deal with OSM data here mainly (even though > TIGER is a primary data source for OSM in the US). There's several ways to > make OSM data routable. See for example http://project-osrm.org/ or > https://wiki.openstreetmap.org/wiki/Gosmore - it depends on what you want > to do with it. Same goes for 'managing attributes'. > > Best > Martijn > > -- > martijn van exel > geospatial omnivore > 1109 1st ave #2 > salt lake city, ut 84103 > 801-550-5815 > http://oegeo.wordpress.com**** > -- martijn van exel geospatial omnivore 1109 1st ave #2 salt lake city, ut 84103 801-550-5815 http://oegeo.wordpress.com -- martijn van exel geospatial omnivore 1109 1st ave #2 salt lake city, ut 84103 801-550-5815 http://oegeo.wordpress.com
_______________________________________________ Talk-us mailing list [email protected] http://lists.openstreetmap.org/listinfo/talk-us
