Skip to content

Code Institute - Milestone Project #2 (Interactive Front-End Development) || Score: 93.5%

Notifications You must be signed in to change notification settings

TravelTimN/ci-milestone02-ifd

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

93 Commits
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Demo IATA Map

Open-Source IATA Map

Code Institute / Interactive Front-End Development

For this project, we could choose from one of the following scenarios:

  • Create a single-page app that relies heavily on one or more APIs.
  • Create a Memory Game similar to Simon.
  • Create a Data Dashboard.
  • Create your own project with a scope similar to the examples.

I decided to combine the use of a mapping API with data in the form of an open-source map of global IATA codes, as my current profession is in the travel industry.

IATA stands for International Air Transport Association. IATA Codes are often seen when booking travel arrangements and on luggage tags, which represent global airport codes. Examples: Dublin DUB, London Heathrow LHR, Los Angeles LAX, Sydney SYD, etc.

Currently it's free to search the IATA Database, but doesn't list the thousands of other transport locations that have their own code, such as train stations, heliports, bus stations, etc. You really need to know what you're looking for, and it's not visually interactive to use.

I wanted to make this project open-source and fully interactive, so I have decided to use Leaflet instead of Google Maps due to the Google pricing implementation as of 16 July 2018. The majority of the airport data is open-source already from OurAirports, but again, it's not interactive, only available in .csv format.

amiresponsive mockup

UX

USER STORIES

  • Users should be able to pan to any specific country based on selection.
  • Users should be able to select mode of transportation (all, none, some).
  • Users should be able to choose a map style (dark, light, satellite).
  • Users should be given the appropriate Wikipedia link, and if not available, perform a Google search instead.

FRAMEWORK

  • CSS Grid: Personally, I prefer the dynamic flexibility and use of CSS Grid, which is why I've decided to build this project using Grid, without the use of Bootstrap or Flexbox.

COLOR SCHEME

Allowing users to select from a few different map options, I knew I needed to select colors that would compliment each other for each of the map layers. I first established which map-tiles I wanted to use for the project, and really liked the color blue which is used to identify bodies of water on the map [#018FC3]. From there, I used a color calculator to get complimentary colors to match my primary blue for airports.

Due to the size of this project, I felt the simplicity of it didn't require preprocessors (ie: Sass, SCSS), therefore all transport layer colors are set at :root level within my CSS.

  • #018FC3 #018FC3 (airports)
  • #FF5100 #FF5100 (bus stations)
  • #FFD000 #FFD000 (ferry ports)
  • #FF1100 #FF1100 (heliports)
  • #A602FF #A602FF (seaplane bases)
  • #03FF42 #03FF42 (train stations)

The remaining aesthetics were my own preference, to match the three different map-tile layers that I've incorporated for user-selection, which keeps the site looking both modern and professional.

WIREFRAMES

I've used Adobe XD to create my wireframe / mock-up. To allow for visual representation on GitHub, I have also included a .png file.

Testing as .png

FEATURES

EXISTING FEATURES

Leaflet Plugins: Since I have approximately 11,350 markers, I've incorporated the use of a couple Leaflet plugins in order to avoid significant payloads to the server.

FEATURES TO BE IMPLEMENTED

Search by Location: Ideally I'd like to allow the user to search by location, which subsequently pans to the user-selected location. UPDATE: fully implemented and functional.

Search by IATA Code: I would also like the user to be able to search by 3-letter IATA code, which would populate on the map once found. UPDATE: fully implemented and functional.

  • These have both been accomplished by using an additional plugin: Leaflet.Search

Additional Markers: I am aware of roughly 1,500-2,000 IATA codes that could potentially be added, but would require a significant amount of manual work to obtain the appropriate latitude/longitude for each. A large majority of these are train and bus stations. 90% of the current non-airport markers were added by me manually. Scratch that... I spent a few extra days ploughing through the remaining IATA codes, and finally ended with a grand total of 11,349 individual IATA codes - Woohoo! (sincere thanks to my accountability partner, Chris Quinn for helping gather some of the latitude/longitude locations!)

TECHNOLOGIES USED

Brief overview of the languages, frameworks, and other tools I've used on this project:

  • HTML5: Semantic markup language as the shell of the site.
  • CSS3: Cascading Style Sheets as the design of the site.
  • CSS Grid: Allows for a responsive layout across various platforms.
  • JavaScript: Primary function of the site for all user interaction.
  • jQuery: Used to simplify some of the DOM minipulations.
  • Leaflet: An open-source JavaScript library for interactive maps.
  • Leaflet Plugins: Plugins to allow better functionality of Leaflet.
  • ConvertCSV.com: Used to convert data from CSV to GeoJSON.
  • Adobe Photoshop CS6: To create all custom markers, and image modifications.

LEAFLET PLUGINS

TESTING

To view all testing documentation, please refer to TESTING.md

DEPLOYMENT

Deployment and source control was entirely done via GitHub. My repository can be found here:

I've published the source code built from the master branch using GitHub Pages.

The live site can be found here:

There are no difference between the deployed version and the development version.

Local Deployment

In order to make a local copy of this project, you can clone it. In your IDE Terminal, type the following command to clone my repository:

  • git clone https://github.com/TravelTimN/ci-milestone02-ifd.git

Alternatively, if using Gitpod, you can click below to create your own workspace using this repository.

Open in Gitpod

CREDITS

CONTENT

The majority of the data used is from OurAirports.com, specifically the airports.csv free download file. However, a large majority of that data is for airports that don't have their own IATA code, and I purely wanted locations that have a valid IATA code. It also contained several useless columns which weren't relevant to my project, and the file contained thousands of invalid Unicode UTF-8 characters, so I did a massive update to a locally saved version for my own use. My cleaned-up version can be found here as .xlsx format.

Once I had the appropriate data required, I used an online converter to convert my CSV data into the appropriate GeoJSON format, which is saved as iataData.js and can be found here.

Approximately 90% of the non-airport markers have been manually added by me, having obtained the valid IATA code from a system at work called Amadeus (used by travel agents), and Google Maps to obtain the appropriate latitude/longitude. A lot of manual work, as you could imagine!

MEDIA

The images used on the buttons are all royalty free vector graphics obtained through a simple Google search. I then used Adobe Photoshop CS6 to create my own markers for the various transportation type.

The images for the map layers (dark, light, earth) were screenshots from my actual project, which I once again used Photoshop to create the actual images used.

I decided not to use Font Awesome just for two tiny icons in the footer, so the GitHub and LinkedIn images were obtained through their respective branding pages. UPDATE: Font-Awesome is used in lieu of branded logo images.

Due to the nature of wanting this project to be entirely open-source, I didn't want to use any CDNs, so downloaded all relevant .css and .js files for Leaflet and jQuery locally. UPDATE: CDN links are used to keep the app up-to-date without manually having to override each file. Exception in place for ESRI-Leaftlet-Geocoder, as they now require an API key for the simple use of my tiny requirement for searching.

ACKNOWLEDGEMENTS

A huge thanks to my [temporary] mentor James Timmins for his time, suggestions, and constructive feedback for this project!

Also where credit is due, the concept of getting the animated counter came from Codepen: jQuery Animated Number Counter From Zero To Value - Javascript Animation by Pouya Saadeghi. I got the code to work on my own, but with some quick assistance from my mentor, I was able to eliminate nearly 100 lines of repetitive code to accomplish the same concept in only 18 lines.

To remain open-source, I also ensured my project used open-source map-tiles that don't require any API Keys or activation. I'm thankful for Alex Urquhart's Free Tile Services which allowed me to easily implement 3 base map layers, and a single overlay layer.

Finally, thanks to Chris Quinn, my accountability partner for all projects, for his feedback and support.

Releases

No releases published

Packages

No packages published

Languages