Skip to content

Conversation

kuzvac
Copy link
Contributor

@kuzvac kuzvac commented Mar 15, 2016

Added ArcGis geocoding service which support geocode, reverse geocode and autocomplete.
Docs can be found on https://developers.arcgis.com/rest/geocode/api-reference/geocoding-find-address-candidates.htm and https://developers.arcgis.com/rest/geocode/api-reference/geocoding-reverse-geocode.htm
Have a good day! :)

src/index.js Outdated
Photon = require('./geocoders/photon'),
Mapzen = require('./geocoders/mapzen');
Mapzen = require('./geocoders/mapzen'),
AcrGis = require('./geocoders/acrgis');
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks like a typo here, you're referring the variable ArcGis below. Did you build and test the code to check that it works?

@perliedman
Copy link
Owner

Please rename the file acrgis.js to arcgis.js, and I think there's a related problem that I mentioned as a code comment above.

@kuzvac
Copy link
Contributor Author

kuzvac commented Mar 16, 2016

Ah, yes, thank you. Now it's working properly.

@perliedman
Copy link
Owner

Can you squash these commits into one, to make the history look a bit cleaner?

@kuzvac
Copy link
Contributor Author

kuzvac commented Mar 16, 2016

I do not know how to do it correctly :(

@perliedman
Copy link
Owner

No worries, it's (like many things with git) a bit tricky the first time.

I'm sure there's like a million tutorials on how to do it, but here's a short summary:

The idea of "squashing" commits is to bunch together a number of commits into a single one. Often to avoid a lot of "fixed this/that" commits that are just confusing in the repo history.

To do it, you use the command git rebase -i, which means "interactive rebase". You need to give the commit hash of the commit you want to "start" your rebase at. In your case, you probably want:

git rebase -i b83b2cfbee69e4bf48f723f5b24e5143ba89760b

This will bring up an editor, where all commits following b83b2cf are listed. By default, they will all have the command pick in front of them. Commits with pick in front of them will not be altered, but if you change pick into squash (or fixup), will squash this commit together the previous commit.

After you save and exit the editor, git will perform the modifications. Beware that it's actually possible to remove commits from the history in this interface, if you remove lines from the file.

After squashing, you can push your changes again, but you will have to use git push -f, to force changes to previous commits.

Feel free to try it out, it's a good thing to know about. If you don't want to, no worries, just tell me and I'll try to find the time and fix up the last bits.

@kuzvac
Copy link
Contributor Author

kuzvac commented Mar 16, 2016

Thank you for help, i try to squash commit a bit later.

@perliedman perliedman merged commit 1c7025d into perliedman:master Apr 14, 2016
@perliedman
Copy link
Owner

GitHub now allows squashing as part of accepting a PR, so this was solved automatically.

Again, thanks for contributing this code! 😸

@kuzvac
Copy link
Contributor Author

kuzvac commented Apr 14, 2016

Community FTW! :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants