Skip to content

determine whether "map error" is detectable #41

Closed

Description

@davidchambers

#33 (comment):

If they forget latitude and longitude or don't know how to do it: Could we display a grey area/div? Because otherwise we get this "map error" thing which is not so nice 😰 :
screen shot 2017-04-24 at 19 46 37

Activity

  1. davidchambers commented on Jun 1, 2017

    @davidchambers
    ContributorAuthor

    I don't think detecting a "map error" is possible, but an even better approach would be to validate the latitude and longitude values provided in the Markdown file. According to Google Static Maps Developer Guide:

    Latitude and longitude values must correspond to a valid location on the face of the earth. Latitudes can take any value between -90 and 90 while longitude values can take any value between -180 and 180. If you specify an invalid latitude or longitude value, your request will be rejected as a bad request.

    It should be possible to write some Ruby code to validate these values. If invalid values are provided, Travis would fail the pull request.

  2. vsmart commented on Jul 3, 2018

    @vsmart
    Member

    I see that the latitude/longitude values as min/max are encoded in the validate-file logic :
    https://github.com/ClojureBridge/clojurebridge.github.io/blob/master/validate-yaml.cljs#L20-L21

    I think this means that the build would fail if incorrect values are given and that we can close here. cc @davidchambers

  3. davidchambers commented on Jul 3, 2018

    @davidchambers
    ContributorAuthor

    Good point, Franka. :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions