FDOT Emergency Travel Alert: For information on the current situation, please visit the following
page - 
Engineering/CADD Systems Office
Do I still use PEDDS if I’m not electronically signing / sealing?
A:
Yes -- PEDDS will still be used to SECURE a project (usually on a CD-ROM) for
delivery to FDOT. The data on that CD-ROM (or other delivery media) will
AUTHENTICATED as original using PEDDS. Signing / Sealing is just but one of
PEDDS’ functions – and PEDDS will be used even if data is not electronically
signed / sealed.
What is synchronization in PEDDS?
A:
The synchronization process involves a "requestor" (the one who wants to be
synchronized) and a "responder" (the one who has the version of a project that
in the end, will update the requestor).
The process starts where the requestor has opened an active project, and creates a synchronization request package. This is essentially nothing more than a zip file of his Manifest. It is a good idea if the requestor has just secured his version of the project before creating the synchronization request package. The resulting package file (*.pkg) may be transmitted to the responder, and is usually small enough to send even by e-mail.
Likewise, the responder should start with a freshly secure project. The responder receives, then opens the request package. PEDDS compares the requestor's Manifest with the local responder's Manifest. All files modified or added (different than the requestor's) are zipped into a response package, along with instructions for PEDDS to delete any files from the requestor's version of the project the responder doesn't have.
The response package is then sent back to the requestor (this is also a .pkg file, but is larger because it may contain many additional or modified files the requestor doesn't have).
The requestor opens the response package and is given a chance to review what is about to take place on his version of the project before continuing. If the requestor continues, files in the response package are added to his project and files the responder didn't have are removed from the requestor's project until both projects (requestor's and responder's) are synchronized (made exactly the same), that is matching the responder's version of the project.
For more information please visit the following links:
PEDDS Synchronization Presentation
PEDDS Synchronization Summary
The process starts where the requestor has opened an active project, and creates a synchronization request package. This is essentially nothing more than a zip file of his Manifest. It is a good idea if the requestor has just secured his version of the project before creating the synchronization request package. The resulting package file (*.pkg) may be transmitted to the responder, and is usually small enough to send even by e-mail.
Likewise, the responder should start with a freshly secure project. The responder receives, then opens the request package. PEDDS compares the requestor's Manifest with the local responder's Manifest. All files modified or added (different than the requestor's) are zipped into a response package, along with instructions for PEDDS to delete any files from the requestor's version of the project the responder doesn't have.
The response package is then sent back to the requestor (this is also a .pkg file, but is larger because it may contain many additional or modified files the requestor doesn't have).
The requestor opens the response package and is given a chance to review what is about to take place on his version of the project before continuing. If the requestor continues, files in the response package are added to his project and files the responder didn't have are removed from the requestor's project until both projects (requestor's and responder's) are synchronized (made exactly the same), that is matching the responder's version of the project.
For more information please visit the following links:
PEDDS Synchronization Presentation
PEDDS Synchronization Summary
How can I get PEDDS to show the county name (for 1-9) in the ProjectID report?
A:
The county/section data (for counties 1-9) in ProjectID.xml must be corrected to read 01-09.
Correcting ProjectIDReport.xsl or Counties.xml does not correct the data, only the hard copy report. You can use notepad to make the changes.
Single digit county reference
County with correct reference
Correcting ProjectIDReport.xsl or Counties.xml does not correct the data, only the hard copy report. You can use notepad to make the changes.
- Open ProjectId.xml with Notepad
- Find each "<County>"
- Replace the single digit county reference
- Do not eliminate the control characters on either side of the data (Linefeeds)
Single digit county reference
County with correct reference
