shakedown.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
A community for live music fans with roots in the jam scene. Shakedown Social is run by a team of volunteers (led by @clifff and @sethadam1) and funded by donations.

Administered by:

Server stats:

282
active users

#fuzzymatch

0 posts0 participants0 posts today

Need to match and merge two messy spreadsheets? Comparing products prices from multiple vendors? Customer lists cluttered with duplicates? Product catalogs inconsistent across systems? Real estate records fragmented and unreliable?

Ready to transform your data chaos into harmony? 
Contact Matasoft now and unlock the full potential of your data! 

#entity-resolution #EntityResolution #FuzzyMatch #fuzzy-match #fuzzy-matching #data-management #data-matching

matasoft.hr/qtrendcontrol/inde

@igor_chubin, I think I may have found a #bug in your wttr.in service.

I ran ```curl wttr.in/desmoines```, but instead of returning the weather report for Des Moines, Iowa, USA, it returned the weather report for Ptolemaida, Greece.

Does your app fall back to a #FuzzyMatch #algorithm when it doesn't recognize the city name? If so, I think that's the cause of this issue. There's a street in Ptolemaida called "Desmoinis," and that's where the GPS coordinates at the bottom of that weather report point. Similar issue with wttr.in/losangeles, which returns results for a street address in Brazil.

After some tinkering, I discovered that inserting a hyphen between the words in multi-word city names (e.g., ```curl wttr.in/des-moines``` or ```curl wttr.in/fort-collins```) returns the expected weather reports.

However, some multi-word city names don't require hyphens. Ex: ```curl wttr.in/sanfrancisco``` (San Francisco, California, USA), ```curl wttr.in/newyork``` (NYC, New York, USA), etc.