Using the poppler library can convert PDF into plain text, and it will probably work on this PDF.
Saikrishna Arcot On Tue 14 Jan 2014 05:37:08 PM EST, Tod Fitch wrote: > Looking at that PDF, it is not obvious to me how to script the data for mass > input. Probably would take less time to print out a copy of the PDF and sit > down with JOSM checking off each description as you enter it by hand. Maybe > it is my deficient scripting skills, but things like this don't look easy to > automatically parse: > > "The speed limit shall be twenty-five miles per hour on Pacific Avenue > (County Road No. 4241) between 24th Street (County Road No. 4241) northerly > to Ocean Boulevard (County Road No. 4256) (Ord. 1225 § 10, 1972: Ord. 831 § 1 > (part) 1965: prior code § 10-006.4(15))." > > But sitting down with JOSM it would be reasonable for a human to enter the > data as long as the underlying roads were already in JOSM. Only 12 entries > for 25 MPH, 17 for 30 MPH, 36 for 35 MPH, 18 for 40 MPH, 21 for 45 MPH and 7 > for 50 MPH. I can't believe that there are only 90 named streets in SLO > county, so I'm guessing it is not listing the ones in incorporated cities nor > ones for which the default state speed limit (residential area, etc.) is > assumed. > > -Tod > > > > On Jan 14, 2014, at 2:14 PM, Richard Welty wrote: > >> On 1/14/14 4:51 PM, Dave Oksner wrote: >>> I can certainly enter data manually--like I said, I've made several edits >>> here and there over the last couple of years--but I was hoping to find >>> someone who is somewhat authoritative about mass changes. I'm pretty >>> good with scripting and can probably not only extract the useful info >>> from the PDF (the document is here: >>> http://www.slocounty.ca.gov/Assets/PW/Traffic/Traffic+Codes.pdf ) but >>> could probably also parse an OSM extract to match up the ways and nodes >>> that need to be changed. But I don't know what to do with the information >>> or how to get it back into OSM in a "safe" way. >>> >>> >> for any sort of "mass" project, you probably want to interact with the >> US import committee first. mass/mechanical edits are something we are >> concerned with. we meet in a google hangout every other monday >> evening; Serge should be able to supply details. the mailing list is >> imports...@openstreetmap.org >> >> richard >> >> -- >> rwe...@averillpark.net >> Averill Park Networking - GIS & IT Consulting >> OpenStreetMap - PostgreSQL - Linux >> >> >> >> _______________________________________________ >> Talk-us mailing list >> Talk-us@openstreetmap.org >> https://lists.openstreetmap.org/listinfo/talk-us > > > > _______________________________________________ > Talk-us mailing list > Talk-us@openstreetmap.org > https://lists.openstreetmap.org/listinfo/talk-us _______________________________________________ Talk-us mailing list Talk-us@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk-us
