If you can think it, you can build it. Use Esri's ArcGIS platform APIs and SDKs and bring your world into view.

Esri is sponsoring an internal developer hackathon. Tell us what the Science of Where™ means to you through your project solution. This hackathon is open to Esri employees, distributors, and partners.

This is an opportunity for you to put together a project team and bring to life your ideas utilizing ArcGIS APIs and SDKs. Present a workflow and a solution that will help new and existing enterprise developers solve real-world problems they are facing everyday by using the ArcGIS Platform and the Science of Where. The solution should illustrate how easy and effective it is to use the different parts of the ArcGIS platform to solve a problem and what makes ArcGIS technology great.

It’s not just about building fancy desktop or mobile apps, it’s about showing how to use our platform in a simple, clear way to solve real-world problems. We want your app to help sell the platform! Ultimately, we would like to use the app you create as showcase/model apps on Esri labs, Example Apps, or the developers site.

View full rules

Eligibility

Open to employees of Esri, including Esri Int'l Distributors and partners.

Esri employees are required to have their manager’s approval. There are specific charge codes for this event.

Participants must be able to appear in-person at Esri headquarters or via Skype/Lync over Esri's VPN.

Participants can form teams of up to 6 individuals.

Teams must declare participation by the Team Entry Deadline (Friday, January 11, 2019, at 11:00 AM PST) with an entry in Devpost submitted to our hackathon.

Requirements

Submissions will be judged on content developed during the hackathon submission period only. Any component developed before the hackathon submission period is not eligible for judging.

All teams must declare their participation by the Team Entry Deadline by completing the team entry form and submitting it to the hackathon on Devpost.

All code must be submitted to a public Github repository and available for the judges and event organizers to access.

The submitted solution must build and run in a standalone app on a PC or Mac computer, mobile device, or in a simulator running on a PC or Mac computer.

All projects submitted must use the ArcGIS platform APIs in some way. Projects submitted that do not use ArcGIS developer technology are not eligible for judging and prizes.

All submissions must use only publically released APIs, SDKs, software and services. Since the submissions are made to public github repositories, and our ultimate goal is to show your project off on a public facing website, we cannot accept submissions that use proprietary or internally available non-public components. 

All submitting teams must be able to perform a 5-minute presentation of their solution. Teams may present in-person, via videoconference, or by submitting a video of their presentation. When presenting in-person at least one team representative must be on site during the presentation period at the specific time requested. When presenting via video conference at least one team representative must be online during the presentation period at the specific time requested. When submitting a video the video must be submitted with the project by the submission deadline.

All submissions must include: title, elevator pitch (short description), technology used, link to public github repository, all contributing team members, project description, 3 screenshots. Video, additional screenshots, project thumbnail are optional.

If any additional hardware is used it will not be considered in the judging. If additional hardware is required it is the team's responsibility to make it available to the judges during the judging period.

If you are an Esri employee, Esri maintains full rights to the resulting project and maintains the right to continue further development of the idea.

If you are an Esri employee, Esri maintains ownership of all code, designs, and all components of each project submission worked on as part of this event.

Esri will have the right to include the project on its website and marketing material.

How to enter

In order to enter the hackathon individuals must complete the following:

  • Please review and agree to the Official Rules.
  • Participants must meet the prerequisites that are described in the official rules, and agree to Esri’s code of conduct.
  • Create your account (or login) on Devpost.
  • Join our Slack team at https://hackthemap.slack.com (open to anyone with an esri.com email address. Anyone else will need an invite.) Slack is used for all real-time updates.
  • One team member creates a project on Devpost, and adds all team members to that project.
  • The team entry must meet the eligibility requirements described in the Official Rules.
  • Come to M1 Triplex on Friday morning at 9:00 AM PST, on join via Zoom, to get last minute details, network with other teams, and work on your project.
  • Declare participation by the Team entry deadline of Friday, January 11, at 11:00 AM PST. To do this, post a new project on Devpost, then submit that project to the Hack the Map 3 hackathon.
  • For final project submission, complete the project, update your team entry form on Devpost, and prepare your presentation. The completed entry must be submitted on or before the submission deadline of Monday, January 14, at 2:00 PM PST.

Judges

Rex Hansen

Rex Hansen
Esri

Greg Pleiss

Greg Pleiss
Esri

John Gravois

John Gravois
Esri

Sathya Prasad

Sathya Prasad
Esri

Judging Criteria

  • Applicability
    Applies to category: Enterprise, Civic, or Consumer. Applies to event theme: leverages The Science of Where.
  • Usefulness
    Real world applicability and usefulness (as it applies to its intended category).
  • ArcGIS Integration
    Application of ArcGIS technology and utilization of ArcGIS APIs and SDKs.
  • Design
    User experience and design, including the map’s effectiveness.
  • Submission quality
    How well the project adheres to the submission guidelines and the overall presentable quality of the project, completeness of the solution, project components. Project quality based on clear architecture and code organization of the solution.
  • Presentation
    Quality of the final presentation. How well the product is represented and its purpose and usefulness conveyed through the presentation.