HNHacker News
TopNewBestAskShowJobs

juliansimioni

1,797 karma · joined June 25, 2012

Founder of Geocode Earth (https://geocode.earth): open source geocoding hosted services and consulting

San Francisco -> Berlin -> NYC

Core Maintainer, Pelias Geocoder (http://github.com/pelias/pelias/)

Formerly of Mapzen

https://juliansimioni.com

submissionscomments
juliansimioni··on Mantle – Serverless Maps Using Lambda or Cloudflare Workers
(Co-maintainer of Pelias and co-founder Geocode Earth here)

Thanks Brandon for yet another one of your shout outs.

I'd just like to underline one thing you said, Pelias/Geocode Earth are based on OSM _plus other data_: that last part is pulling a lot of weight.

OSM data is great, in fact the POI data in OSM is best-in-class in many parts of the world. But OSM in general doesn't have great address coverage. It's very difficult to manually map low density rural or suburban areas, as is the preferred method with OSM. Bulk address imports are possible, but rare. However there are a huge number of local governments that publish up to date, relatively complete and accurate address lists, and we heavily lean on those for good address coverage.

So to anyone looking for a geocoder who has been put off from Pelias or Geocode Earth because you saw it uses OSM, give it a try anyway. OSM data is a crucial piece of the puzzle, but not the only one.

juliansimioni··on Chernobyl power plant captured by Russian forces
I would imagine that even a small conventional bomb landing anywhere within a few miles of Chernobyl would unearth and spread contamination.

I remember reading somewhere that all the ground was full of small radioactive particles in the area surrounding Chernobyl. So basically what they had to do was dig up the first few feet of dirt and flip it over, burying the contaminated dirt. Any small bomb would undo that. Then the wind would carry it and we'd have a whole mess.

juliansimioni··on Positionstack (by APILayer) Geocoding-API down for over 14 days, with no ETA
If anyone comes across this looking for an alternative, we can help at Geocode Earth (https://geocode.earth).

We're a small independent company that has been working on geocoding since 2013, first as part of Mapzen(https://mapzen.com), and then with our own self-funded business after Mapzen shut down at the start of 2018.

Our core software, the Pelias Geocoder (https://pelias.io) is open source, and ironically we understand it to be the primary geocoder in use by Positionstack.

We're biased of course, but we think that as the primary authors of the open source project, and with a high-volume service that has had _zero_ major outagee, we're a great option for anyone who needs forward or reverse geocoding, addresss parsing, place or address autocomplete, etc.

juliansimioni··on Should you contribute open data to OpenStreetMap?
That's amazing! I know that lots of local and regional governments are trending towards using OSM as their source of truth for data about their area, but hadn't heard that particular story. Love it!
juliansimioni··on Should you contribute open data to OpenStreetMap?
Here is why you should contribute to OSM even though there are major players profiting from it:

OSM is big enough and good enough that all the tech giants (except Google) would do better to start with OSM and improve it to meet their needs than to start a new, completely proprietary map from scratch.

That means that we are in an amazing place where in addition to the substantial volunteer OSM community, there are contributions from Amazon, Apple, Facebook, and hundreds or thousands of smaller companies all coming back in to a single global map that everyone can use. It's very worth it to do work that strengthens OSM, as it increases the number of companies that will use it, and possibly contribute back, rather than doing work the world at large won't benefit from.

P.S. As a disclaimer, I am co-founder of Geocode Earth (https://geocode.earth) a small business that does indeed profit from OSM (and other open) data. We also contribute back both through OSM contributions and by releasing our core software as the Pelias geocoder (https://pelias.io)

juliansimioni··on AWS Ground Station
As an individual who certainly doesn't have any satellites in orbit and really doesn't have any space-specific skills beyond KSP, but who has enough money to blow on $10/minute fees, is there anything I could do with this?

Not illegal or nefarious things either, but could I do something like listen in on data being transmitted down by an existing satellite (say something like Hubble or Landsat that will eventually result in public data anyway)?

juliansimioni··on Takeaways from looking for a new senior role in tech
Phil is a great person and previously had director of engineering/product roles at Digital Ocean, Meetup/Wework, and Soundcloud. It's not worth dismissing his advice out of hand :)
juliansimioni··on Scaling Kafka at Honeycomb
I'm not a Kafka user but it seems very similar to my experience running Elasticsearch clusters tuned for low latency response time.

There's a complicated mix of requirements for CPU, memory, disk, _and_ network speed, and meeting all of them cost effectively is a real challenge.

Similarly, it's easy to build a cluster that performs well until a single node fails. The increased load per node plus the CPU and network cost of replicating data to a replacement instance can really cause trouble.

Elasticsearch also runs on the JVM so I'm hoping the new EC2 instance types will work for us too. They look to be really great.

juliansimioni··on Amazon EC2-Classic Is Retiring
As someone who first used AWS in mid-2009 (just a few weeks before VPCs were announced!), but hasn't used an EC2 Classic enabled AWS account now since around 2012, it's hard to remember just how far the service has come.

There were only a few instance types, and they were all slow and small (by todays standards). Everyone's EC2 instances were mostly publicly pingable/ssh-able from the internet. EBS was horribly horribly slow (our DBAs set up a super convoluted RAID 0+1 configuration for our MySQL databases and even then we needed massive sharding to keep up with growth). EC2 instances were, in general, very unreliable (I recall something like 1 in 500 instances failing _per week_), and especially so in the leadup to Christmas (where the rumor was AWS kept the best instances for themselves).

This is pretty much the first time I've heard of AWS really deprecating something, so I have a feeling it will _hugely_ simplify things on their end. From reading the post I also get the idea that it won't be _that_ hard of an operation from their side. I bet few people (by AWS standards) are still using EC2 classic heavily.

juliansimioni··on Disinformation Evolved in 2020
To my knowledge there were no major changes in the abacus industry in 2020.
juliansimioni··on Programmers, teach non-geeks the true cost of interruptions (2014)
>because they have never done any real work

A good sales person can make the business money (you know, the thing that keeps them from disappearing) without _any_ product yet existing at all. Programmers who build something rarely bring in money by its mere existence.

Be careful who you insult because its unlikely you could do what they do, and it's not guaranteed that you'd keep your job ahead of them if it comes to it.

juliansimioni··on The collapse of the IRON stable coin
No, much different:

In a ponzi scheme, the perpetrators will not willingly directly reveal that it's a ponzi scheme.

In cryptocurrency, the perpetrators are honest and transparent about it being a ponzi scheme, but surround it in so much techno-babble that they make it sound like a ponzi schme is what you WANT.

juliansimioni··on My EC2 Wishlist
Agreed. Google Cloud seems to do a better job of this, you can simply pick how many CPUs your VM will have.

For me personally, it's the jump from c5d.4xlarge (16 core) to c5d.9xlarge (36 core) that's a bit hard to work around, but there are surely others.

juliansimioni··on ST3000DM001
Does anyone remember the DeskStar aka DeathStar drives? I had to look it up but apparently that was around 2001.

As I recall that pretty much killed the IBM brand when it came to hard drives.

https://en.wikipedia.org/wiki/Deskstar

juliansimioni··on Open letter from researchers involved in the “hypocrite commit” debacle
This apology fails from the 5th word:

"We sincerely apologize for any harm..."

While there are other requirements, a sincere apology cannot in any way entertain doubt about the fact that there WAS harm.

Truly acknowledging the harm done is foundational to a real apology, and most of us (myself included) end up sneaking in weasel words or phrases like this.

Psychologically, its nice for the apologizer, since it allows one to think "i'm being good by apologizing, but maybe I didn't do anything bad after all?".

But from the apologizee standpoint, these phrases are often devastating and can make it clear that the apologizer has no real recognition or care of what happened.

Personally I've worked pretty hard to try to remove these sorts of phrases from my apologies. It's not easy. It makes you feel much more vulnerable and you really have to let whatever you did sit with you in a very uncomfortable way. But it's worth it.

juliansimioni··on Netlify Status – CDN Issues
The main advantage that AWS will have for us over anything else is that, since AWS already manages our DNS, we are going to be able to offer our visitors the best performance by using geo-specific IP addresses.

The static site in question for us lives at the apex record (mywebsite.com), so it's generally not possible for other providers to do this without having them manage our entire DNS infrastructure, which we aren't willing to do.

In fact I think this is part of why we've had so many issues with Netlify. It's clear their preferred way to host apex domain sites is to manage the DNS completely.

juliansimioni··on Netlify Status – CDN Issues
This has been the third major outage for Netlify in the last few weeks.

I like the company, they have good people on their team, and their interface and functionality is great (deploy previews are so nice!).

But this is probably the last straw, as the static portion of our company's website has been down for 45 minutes now.

Fortunately, the beauty of a static site is they're quite easy to host anywhere.

We're already on AWS, and it's easy enough to set up CloudFront. It won't be _quite_ as quick to deploy but it will probably rarely if ever break. Guess that's my task for the day :(

juliansimioni··on OpenStreetMap proven to be a highly accurate map in top US cities
One of the under-appreciated advantages OSM has here is that they have a fairly well enforced convention of using fully expanded abbreviations in addresses and street names.

It's _much_ easier for automated comparison to replace `street` with `st` than it is to guess which one of many possible expansions to replace `st` with (is it saint? street? sankt? strasse?).

This isn't foolproof but much of the "authoritative" data out there has no such convention, making analysis much more dangerous.

juliansimioni··on OpenStreetMap proven to be a highly accurate map in top US cities
Hi, founder of Geocode Earth (https://geocode.earth), another geocoding service that _does_ use OpenAddresses and only other open data sets.

Mapbox purchases data from, I believe, TomTom, and other proprietary sources. That's why they have cheap(er) pricing if you want to get results without the legal ability to store them, and much more expensive pricing if you do want to store it. I'm sure negotiating that arrangement with the proprietary address data vendors was...fun.

juliansimioni··on Openstreetmap’s product fails to compete with Google Maps
(Former Mapzen employee here).

I _think_ you're talking about Eraser Map(https://github.com/mapzen/eraser-map) right?

It was awesome! It's the closest I know of to "Google Maps, but open source and based on open data". It was an app built for _end users_, not OSM editors. And it worked pretty darn well. When it didn't, any problems could (at least theoretically) be addressed with improvements to OSM data or the Mapzen open-source projects.

There was a team of at least two people working on it full time, plus lots of work on the design, product, and integration with geocoding, routing, transit etc. The multi-modal (switching from walking to transit to car, etc) transit directions were particularly awesome.

I used it as my daily driver for much of my navigation around NYC, and as time went on only had to fall back to Google Maps maybe 25% of the time, usually for missing POI data.

Unfortunately I think it's one of the few Mapzen projects that hasn't seen new life after the company shut down, and like you said it would take quite a bit of work (read: money) to keep it going. It might be possible with some work to find grant money through a couple organizations. The OSMF has done some awesome work lately with the micro-grants, but this would definitely be a level we haven't seen (yet).

juliansimioni··on Openstreetmap’s product fails to compete with Google Maps
Hi! Pelias core maintainer and former Mapen employee here. It is not gone :)

After Mapzen shut down a co-worker and I founded Geocode Earth(https://geocode.earth/) to continue working on the Pelias project, funded by consulting and, primarily, a SaaS much like Mapzen Search.

Over the past 3 years the project has improved quite a bit, and Geocode Earth has had solid growth (50% SaaS revenue in 2020). We've been fully bootstrapped this whole time and plan on continuing this well...indefinitely!

In fact, intersection support is already present in Pelias and will be rolling out to Geocode Earth soon :)

juliansimioni··on Google Maps' Moat Is Evaporating
my guess/understanding is that every team at Google is under significant pressure to monetize. Unlike the old days where there was more of a strategy of "build anything that brings people in, search/ads will monetize those eyeballs".

The 2018 google maps price increase could have given some execs HUGE bonuses under that new model, even if it isn't ideal from a Google-wide standpoint

Before the 2018 price increase I was convinced Google didn't care to have lots of little customers paying for Google Maps. It was all peanuts compared to their main income

juliansimioni··on Amazon Location Service
Thanks for the mention John.

Co-maintainer of Pelias here so I'll chime in with some more background info.

Pelias came out of Mapzen which (sadly) shut down about 3 years ago, but we had a great team of people working on it for 4 years before that, and the project has continued to grow since then. We have contributions from my company, Geocode Earth, which I plugged in another thread so I won't repeat, other contributors like Jawg(https://www.jawg.io/), and of course individuals and teams from many other places.

The core architecture uses Elasticsearch, Node.js, SQLite and some Go to build a fully featured, modular geocoder.

Geocoding is both a fascinating and incredibly frustrating challenge so we are always looking for more people reporting bugs and contributing fixes or other improvements. We truly believe a quality geocoder can't be built outside the large bankrolls of Google, etc without growing a strong open-source community around it.

juliansimioni··on Amazon Location Service
Speaking as co-founder of Geocode Earth(https://geocode.earth) where we do provide autocomplete geocoding, it's a much, _much_ harder problem than regular geocoding (not that any geocoding is exactly...easy).

For one, the latency requirements are much more strict. People type fast and if results don't come in within about 100ms or so, the interface doesn't feel responsive. We spend a ton of time ensuring our servers are as fast as possible. There's always more work to do here, since obviously network latency matters, so where your servers are matters too.

Second, the queries themselves are much harder. If someone has typed "India", did they want the country? Or have they not yet finished typing Indiana? The answer probably depends on their location, which may not always be available. That's a simple example, obviously there are much more subtle queries that don't always have as clear an answer.

Anyways, we enjoy the challenge of autocomplete and hope to continue to do a better and better job, even after Amazon inevitably releases their own :)

juliansimioni··on Mapbox-gl-js is no longer under the 3-Clause BSD license
Great, glad they worked!

Thanks for the good feedback on our pricing. We plan to roll out pay-as-you-go pricing in 2021 that should help with that. In the meantime feel free to reach out to us at hello@geocode.earth and we can set you up with a smaller plan to get you started, if you'd like.

juliansimioni··on Mapbox-gl-js is no longer under the 3-Clause BSD license
Try us out at Geocode Earth! (https://geocode.earth)

We wrote and maintain the open-source Pelias geocoder(https://github.com/pelias/pelias) at Mapzen and have been continuing to improve it in the 3 years since Mapzen's shutdown.

Geocode Earth is our hosted service built around Pelias so you can get started quickly, not worry about keeping data up to date, or doing all the fine tuning and optimization that we've had to do to get fast and reasonably accurate autocomplete outside of Google and Mapbox.

Using our hosted comparison tool you can see that we do a pretty decent job of finding two out of 3 of the Chipotles (the third might have been deduplicated or not in OSM): https://pelias.github.io/compare/#/v1/autocomplete?text=Chip...

Most our users end up passing a focus point, in which case the results are generally even better, although they're the same in this example https://pelias.github.io/compare/#/v1/autocomplete?focus.poi...

juliansimioni··on S3 Strong Consistency
Another, perhaps better link for the announcement: https://aws.amazon.com/blogs/aws/amazon-s3-update-strong-rea...
juliansimioni··on S3 Strong Consistency
One very common one is for situations where you might have a multi-step pipeline to process data

- step 1 generates/processes data, stores it in S3, overwriting the previous copy. triggers step 2 to run

- step 2 runs, fetches the data from s3 for its own processing. However, because only a few seconds have elapsed, step 2 fetches the old version of data from the S3 bucket

You can work around this by, for example, always using unique S3 object keys, but then you have to coordinate across the data processing steps, and it becomes harder to manage things like storing only the 10 latest versions.

The Argo workflow tool (https://argoproj.github.io/) is one example of a tool that can suffer from this problem.

juliansimioni··on Openstreetmap is having a moment
For sure, that's a legitimate concern if/when there's one major corporate contributor that doesn't have to play along with everyone else.

Part of what makes the current OSM situation work is that nobody is bigger than everyone else. If Facebook wants to do their own thing, they're going to be going against Microsoft, Apple, Amazon, and the rest of the community.

We've seen from both the world of capitalism in general and definitely the software world that consolidation eventually happens, so maybe this situation is inherently unstable and doomed to fail. But IMO the OSM community should work to make it last as long as possible.

juliansimioni··on Openstreetmap is having a moment
Isn't it potentially the opposite? If an independent, volunteer mapper contributes a poor edit, someone from the community has to reach out to them individually. This is hard since there's no prior relationship, and no expectation that the person will even take any advice on editing.

Contrast that to a major corporate contributor: the people leading these corporate mapping teams are all talking. Both to each other, and to leaders in the community like prominent volunteers, OpenStreetMap Foundation board members, etc. If a corporate contributor makes a bad edit, one of those _existing relationships_ can be used to help put processes in place that might prevent not just that one individual, but any other contributor paid by that company from making the same error again.

IMO at least, that process scales a lot better. And as OSM continues to grow that will be even more valuable than it already is today.

← PreviousPage 2 of 4Next →