Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted almost 4 years ago

IP tracker with simple Map functionality using leaflet js and mapbox.

Rahul kumar Gautam•655
@RahulKumarGautam1636
A solution to the IP Address Tracker challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


I wanted it to be more than just a IP tracker, so tried to add some basic functions of a map.

  1. Tap and mark a location/place on the map with your desired name.
  2. Double tap on the markers to zoom in to that place for a closer view.
  3. Get satellite view by tapping layer icon.
  4. Added a slide Bar to see the list of marked places in the current map. tap on these list names to visit that place on map.
  5. Added a recenter button. click on it to recenter the map to your current location.

I tried ipify to get location details with ip address but it always shown me wrong location. the difference was in thousands of kilometers, don't know if its ok or not. so i used ipinfo.io which was more accurate but still was wrong by few kilometers. hence i added the option for Geolocation to get users location which uses GPS to give most possible accurate location. mobiles work perfectly with geolocation.

  1. Double tap on the Recenter button to activate the GPS and you will see your GPS location on the map.
  2. I've used local storage to save the list items so the marked places will not vanish even if you refresh the page.

please share your views about this and let me know if you have any suggestion or idea to improve this. Feedbacks are always welcome.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Obinneji Chibuzor Francis•270
    @obinneji
    Posted almost 3 years ago

    This work is great and works well. The only thing is that your active state for the button is not working. Add Hover properties to the submit button using CSS

  • bunee•2,020
    @buneeIsSlo
    Posted almost 4 years ago

    @Rhaul, This is honestly the best solution I've seen to this challenge! You've done an incredible job on this one. There's a couple of things I'd like to address...

    • The Layer and Zoom controls can be positioned at a better place(bottomright/bottomleft), Since it becomes un-usable at screen sizes below 700px.(Here's my Solution if you wish to take a look at it.)
    • There's no focus style on any of your input elements Which is needed for accessibility.
    • The form input needs to be reset back to emty.

    Apart from these, You did Amazing!

Join our Discord community

Join thousands of Frontend Mentor community members taking the challenges, sharing resources, helping each other, and chatting about all things front-end!

Join our Discord
Frontend Mentor logo

Stay up to datewith new challenges, featured solutions, selected articles, and our latest news

Frontend Mentor

  • Unlock Pro
  • Contact us
  • FAQs
  • Become a partner

Explore

  • Learning paths
  • Challenges
  • Solutions
  • Articles

Community

  • Discord
  • Guidelines

For companies

  • Hire developers
  • Train developers
© Frontend Mentor 2019 - 2025
  • Terms
  • Cookie Policy
  • Privacy Policy
  • License

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

How does the accessibility report work?

When a solution is submitted, we use axe-core to run an automated audit of your code.

This picks out common accessibility issues like not using semantic HTML and not having proper heading hierarchies, among others.

This automated audit is fairly surface level, so we encourage to you review the project and code in more detail with accessibility best practices in mind.

How does the CSS report work?

When a solution is submitted, we use stylelint to run an automated check on the CSS code.

We've added some of our own linting rules based on recommended best practices. These rules are prefixed with frontend-mentor/ which you'll see at the top of each issue in the report.

The report will audit 1st-party linked stylesheets, and styles within <style> tags.

How does the HTML validation report work?

When a solution is submitted, we use html-validate to run an automated check on the HTML code.

The report picks out common HTML issues such as not using headings within section elements and incorrect nesting of elements, among others.

Note that the report can pick up “invalid” attributes, which some frameworks automatically add to the HTML. These attributes are crucial for how the frameworks function, although they’re technically not valid HTML. As such, some projects can show up with many HTML validation errors, which are benign and are a necessary part of the framework.

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub