We need your help writing parsers for new locations for Cadpage. Please contact us through firstname.lastname@example.org.
Please understand that Cadpage is continually in development and maintenance. We are planning an update of our website, so your patience is much appreciated. Some of the information that you will find in our website may not be accurate.
If you have questions or problems with Cadpage, please email email@example.com.
Thanks so much for support, your great comments and especially the work that you do as emergency responders for our communities!
Location updates and new parsers are constantly being added, so check back at the Locations
The Google Map
of those locations is similarly updated. Check to see if your location is supported.
And, if you find any discrepancies or errors, please comment and let us know.
There are now 2 versions of CadPage on the android market. One is called Cadpage (free) and is just that. Free forever with all the features and abilities that CadPage has had. It will continue to receive updates and new locations but will be slightly behind the main version on release dates. The standard version of Cadpage is also in the android market and will continue to receive weekly updates including fixes and new locations. This version also has additional functionality of now supporting CodeMessaging.net and Active911.com messaging services. These services now work with CadPage and do not use SMS for delivering messages.
For the Latest news and headlines please check the facebook page. We update this page as often as we can but the facebook page gets the immediate updates when a new version goes out.
Also for those that keep asking and begging Ken has started working on an IPhone version with some other helpful people. So when that is available we will post more information here.
Namely there are two people involved in CadPage. Myself and Ken. I started cadpage as something I wanted for my use as a volunteer in my local area. Being a part time developer I was able to cobble something together based on another app and released the first version of cadpage for our local members. It was placed on the google market for ease of access, this was a bit over a year ago. Since then more and more locations have requested that the app be made to work for their area. At first this seemed simple and I started adding locations in my spare time. Shortly after that Ken who is an actual java developer and volunteer came on board to help out. Without getting into boring details we quickly learned a harsh fact. Each locality, even if using the same cad vendor, has very different formats for their pages. When you read the page you are very quickly and easily able to understand the address part. Doing that reliably in java and making it map over to google maps is a very different thing.
Ken and I tried hard and for 8 months we were able to keep adding locations, but not features, to the cadpage baseline. As much as we both wanted to keep this application free harsh reality set in. We now have over 379 supported or requested locations that have been formally requested. In all that time we have seen less than 10 that were identical and able to use the same parser.
On average it takes 2-8 hours to write a test case, parser, and updates for a single location. For almost all locations the small set of samples we work with are not detailed enough and so for the first few weeks after deployment there are another 2-6 hours per location of coding time to troubleshoot and fix that previous location. Occasionally locations change CAD vendors and the whole process starts over again.
At this time CadPage now consists of over 103,000 (yes that thousands) lines of java code and test cases covering 34 States in the US. All of this is because of primarily 1.5 people. Ken is our primary programmer and besides writing code there is the daily answering of over 100 emails regarding issues, new locations, and questions. We have a good write up on our other page Financial Support
that goes into more details about the financial issues.
If we had an option we would absolutely keep this app free. However for the past year many of the features that everyone has been asking for have been neglected because adding new locations was the priority. It is our hope that with funding we can continue to not only add new but also add features. We have a long list of features including schedule based alerting, ability to add notes to addresses, ability to better forward calls, increased features in selecting alert sounds and methods, along with a longer list of features listed on the website. We also want to add support for non sms messaging and things like tablets and other devices. But all of this takes time.
We have only a few options to make this happen in a realistic timeframe. We would love to see CAD vendors come to the table and support this app. Then they could distribute it to their users and centralize formats and remove the cost burden from the individual users. If you know the Cad vendors please send them our way as our requests to them have gone unanswered.
We could do location based sponsorship. This is something we are working on. And while it removes the cost burden from the user it only goes for supporting the costs of a single locations and not towards the time for new features. We are still working on this but should have something available in the near future.
We could get 2 full time developers to donate their time. If you know of these developers please send them our way :)
We could do in-app advertising. I am really against this as I feel CadPage is not a good app to do in-app advertising on, and realistically we would never have a high enough user base to have in-app ads work.
At this time we are continually working on different ideas but the end goal is the same, to try and keep adding locations and at the same time start adding features again (you saw how long the widget feature took to get in place). Ken has laid out the specific details on this site, no one is getting rich off this app and as Fire/Rescue volunteers ourselves we understand and have tried as best we could to keep this app free. We welcome your comments and suggestions on how we can improve.
Modify Nassau Bay, TX location to also handle League City, TX
Madison County, NY
Add League City and Webster, TX locations
Genesee County, NY
Erie County, PA (alternate)
St Clair County, AL
Parsing problem with Ray County, MO
Parsing problem with Porter County, IN
Parsing problem with Humble, TX
Parsing problem with Cayuga County, NY
Parsing problems with Suffolk County (B), NY
Parsing problems with Dothan, AL
Parsing problem with yet another message prefix
Parsing problem with Deschutes County, OR
Parsing problem with Mobile Medical Response, MI
New call code for Bucks County, PA
This version is being released to fix a crash bug with MMS message processing.
Windham County, CT
Gaston County, NC
Split message merge logic doesn't work when text messages are out of sequence
New city codes for Montgomery County, TX location
Smart address parser gets confused by street names that start with "ST"
Parsing problem with Anderson County, TN
More city codes for Porter County, IN
Fixed parsing problem with Surry County, NC
Force close reported in Billing logic
Fixed parsing problem with Prince Georges County, MD
Parsing problem with Orleans County, NY
Parsing problem with St Marys County,MD
Parsing problem with Anderson County, SC
Parsing problem with Deschutes County, OR
Parsing problem with Cumberland County, PA
Fixed parsing problem with Durham County, NC
Parsing problem with Nassau County, NY (B)
Mid-Week release to resolve a crash issue with one location.
New District: Jefferson County, MO
Force close shutting down Cadpage
App crashes with any attempt to use Erie
Parsing problem with Jefferson
County, NY location
Parsing problem with Humble COunty, TX
Parsing problem with Alexander County, NC
Parsing problem with Frederick County, MD
Fixed parsing problem with Sonoma County,
Parsing problem with Humble County, TX
Parsing problem with Hamilton County, OH
Parsing problem with Marshall County, IN
New District: Erie County, PA (alternate)
New District: Greensboro, NC
New District: Ozark, AL
New District: Venango County, PA
New District: Kent County, DE (Alternate)
New District: Douglas County, CO
New Districts: Candler County and Evans County, GA
New District: Erie County, NY
Parsign problem with Gloucester County, NJ
Parsing problem with Sussex County, NJ
Parsing problems with Worcester County, MD
Force close shutting down Cadpage
Clermont County, OH dispatch sender addres has changed
App crashes when parsing invalid MMS PDU content
Parsing problem with Harris County, TX (B)
New FRNKLN city code not recognized for Chester County, PA (B)
Over 50 changes in this release.
North East, MD
Mecklenburg County, NC (Alternate)
Henry County, GA
Hamilton County, TN
Flathead County, MT
Monterey County, CA
Knox County, OH
St Francois County, MO
York County, PA
Woodford County, IL
St Charles County, MO
Tioga County, PA
Marshall County, IN
Florence County, SC
Randolph County, NC
Wyoming County, NY
Loudon County, TN
Make Cadpage work on Android 1.6 again.
Improved Stueben County, NY location to handle 2ndCall tag
Parsing problem with Watauga County, NC
Parsing problem with Sonoma County, CA
Parsing problem with Oneida County, NY
App can crash in Alexander County, NC parser
Parsing problem with Albemarle County, VA
Parsing problem with Erie COunty, PA
Minor issues with Anoka County, MN
Parsing problem with Sonoma County, CA
New sender address for Anne Arundel County, MD (fire)
Google won't map address containing the word "NEAR"
Parsing problem with Tolland County, CT
Parsing problem with Howard County, MD
Parsing problem with Davidson County, NC
Parsign problem with Anne Arundel Count, MD (EMS)
Pasrsing problem with Mecklenburg County, NC
Alleganey County, MD has switched CAD systems
New SMS address
Parsing problem with Orange County, NC
Parsing problem with Chester County, PA (B)
Parsing problem with Rockland County, NY (A)
New station codes needed for Sonoma County, CA
Parsing problem with Nassau County, NY (Firetracker)
Smart address parser missinterpretting street name
App crash and other problems with Madison County, AL
Parsing problem with Nash County, NC
Parsing problem with Minnehaha County, SD
Parsing problem with Charleston County, SC
Parsing problemwith Harris County ESD1, TX (B)
Cadpage not available for Samsung Galaxy 10.1
Bell County, TX
Johnson County, MO
Colbert County, AL
New Haven County, CT
Pike County, GA
Alexander County, NC
Hamilton County, OH
Caldwell County, NC
Denton County, TX
Parsing problem with Bucks County, PA
Sender has changed for Minnehaha County, SD
Parsing problem with Anne Arundel County, MD
Parsing problem with Linn County, OR
Parsing problem Brunswick County, NC
Parsing problem with Guilford County, NC
Parsing problem with Somerset County, NJ
Parsing problem with Suffolk County, NY (C)
Parsing problem with all Red Alert parsers (Suffolk County, NY (C) in particular)
Parsing problem with Clermont County, OH
Parsing problem with Chester County (B), PA
Parsing problem with Lake County, FL
Parsing problem with El Dorado County, CA
Force close in Lexington Rockridge County, VA location parser
Mapping problem reported at Harford, MD
Missing city code for Montgomery County, TX