You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have added a test that loops through the City enum and checks if the Discovery request is valid.
Through this test, I get a pretty solid insight on the endpoints that have a PRODUCTION endpoint available.
Summary:
Washington DC seems to have left the open311 scene
SeeClickFix has altered their endpoint structure.
This is the result:
Processing City: TORONTO
Skipped GIESSEN, error: java.lang.IllegalStateException: Expected BEGIN_ARRAY but was BEGIN_OBJECT at line 1 column 215 path $.endpoints
Processing City: BONN
Processing City: ROSTOCK
Processing City: HELSINKI
Skipped LAMIA, error: null
Processing City: BALTIMORE
Processing City: BLOOMINGTON
Processing City: BOSTON
Processing City: BROOKLINE
Processing City: CHICAGO
Processing City: COLUMBUS
Processing City: GRAND_RAPIDS
Skipped PEORIA, error: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
Processing City: SAN_FRANCISCO
Skipped WASHINGTON, error: java.lang.IllegalStateException: Expected BEGIN_OBJECT but was STRING at line 2 column 1 path $
Processing City: EINDHOVEN
Processing City: QUEBEC
Processing City: SURREY
Skipped ZURICH, error: null
Skipped ZARAGOZA, error: null
Skipped LISBOA, error: null
Processing City: PHILADELPHIA
[Fatal Error] :1:1: Content is not allowed in prolog.
Skipped ALPHARETTA, error: Content is not allowed in prolog.
Skipped BAINBRIDGE_ISLAND, error: Content is not allowed in prolog.[Fatal Error] :1:1: Content is not allowed in prolog.
[Fatal Error] :1:1: Content is not allowed in prolog.
Skipped CORONA, error: Content is not allowed in prolog.
[Fatal Error] :1:1: Content is not allowed in prolog.
Skipped DELEON, error: Content is not allowed in prolog.
Skipped DUNWOODY, error: Content is not allowed in prolog.[Fatal Error] :1:1: Content is not allowed in prolog.
[Fatal Error] :1:1: Content is not allowed in prolog.
Skipped HUNTSVILLE, error: Content is not allowed in prolog.
Skipped NEWBERG, error: Content is not allowed in prolog.
[Fatal Error] :1:1: Content is not allowed in prolog.
[Fatal Error] :1:1: Content is not allowed in prolog.
Skipped NEW_HAVEN, error: Content is not allowed in prolog.
Skipped RICHMOND, error: Content is not allowed in prolog.[Fatal Error] :1:1: Content is not allowed in prolog.
[Fatal Error] :1:1: Content is not allowed in prolog.
Skipped RUSSELL_SPRINGS, error: Content is not allowed in prolog.
[Fatal Error] :1:1: Content is not allowed in prolog.
Skipped TUCSON, error: Content is not allowed in prolog.
Skipped DARWIN, error: Content is not allowed in prolog.
[Fatal Error] :1:1: Content is not allowed in prolog.
[Fatal Error] :1:1: Content is not allowed in prolog.
Skipped FONTANA, error: Content is not allowed in prolog.
[Fatal Error] :1:1: Content is not allowed in prolog.
Skipped HOWARD, error: Content is not allowed in prolog.
Skipped MANOR, error: Content is not allowed in prolog.
[Fatal Error] :1:1: Content is not allowed in prolog.
[Fatal Error] :1:1: Content is not allowed in prolog.
Skipped NEWNAN, error: Content is not allowed in prolog.
[Fatal Error] :1:1: Content is not allowed in prolog.
Skipped OLATHE, error: Content is not allowed in prolog.
[Fatal Error] :1:1: Content is not allowed in prolog.
Skipped RALEIGH, error: Content is not allowed in prolog.
[Fatal Error] :1:1: Content is not allowed in prolog.
Skipped ROOSEVELT, error: Content is not allowed in prolog.
[Fatal Error] :1:1: Content is not allowed in prolog.
Skipped HILLSBOROUGH, error: Content is not allowed in prolog.
The text was updated successfully, but these errors were encountered:
I have added a test that loops through the City enum and checks if the Discovery request is valid.
Through this test, I get a pretty solid insight on the endpoints that have a PRODUCTION endpoint available.
Summary:
This is the result:
The text was updated successfully, but these errors were encountered: