NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
Go modules · #2057 by repository stars
Last release 7 years ago
no release in 18 months
Ships unpredictably
gaps range from 2 weeks to 3.0 years
Nearly every release is documented
notes for 19 of 19 stable releases
Nothing withdrawn
no release was ever pulled
13 years old
35 releases · first in 2013
Nothing published for this version
Nothing published for this version
Nothing published for this version
One column per quarter.
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Adds the ability for points to be marshalled an unmarshalled via a binary protocol (gob).
Nothing published for this version
Nothing published for this version
Ensures that the Google Geocoder operates over HTTPS.
Introduces the (p *Point) MidpointTo(other *Point) function.
(p *Point) MidpointTo(other *Point) function.Removes unneeded private methods that were a bit clunky to test
Implments a Mapquest Data Transfer Object for decoding JSON responses from the MapQuest API.
Removes some uncessary pointer logic when unmarshalling various structs from provider responses.
Resolves an issue with the Google Geocoder that would panic when attempting to Reverse Geocode some Points with no results.
Exposes GoogleGeocoder.HttpClient so that clients may be able to swap out underlying http client implementations.
GoogleGeocoder.HttpClient so that clients may be able to swap out underlying http client implementations.- Improves geocoder testing.
Introduces the OpenCage Geocoder
Fixes some inconsistent documentation.
Resolves an issue where Reverse Geocoding with a google Geocoder was panicing unexpectedly.
Cleans up some implementation details of how geo.GoogleGeocoder query results are handled.
geo.GoogleGeocoder query results are handled.Introduces geo.Polygon, which is composed of many geo.Points. (Thanks, @mish15!)
geo.Polygon, which is composed of many geo.Points. (Thanks, @mish15!)
geo.Polygon with NewPolygon by passing in []*geo.Point*geo.Polygon.Contains*geo.Polygon.IsClosed which determines if a polygon is a closed shape or not.json.Marshaler and json.Unmarshaler interface!Introduces some bugfixes for google maps and mapquest api error handling
Introduces *Point.BearingTo, which finds the initial bearing (or forward azimuth) from one point to another
*Point.BearingTo, which finds the initial bearing (or forward azimuth) from one point to anotherIntroducing geo.NewSQLMapper, which creates and returns a pointer to a new geo.SQLMapper. This solved issues where users had to create extraneous *sql
geo.NewSQLMapper, which creates and returns a pointer to a new geo.SQLMapper. This solved issues where users had to create extraneous *sql.DB in order to perform Mapper operations. The introduction of this method signature marks geo.HandleWithSQL a canidate for removal in a Major Patch verison.
geo.SQLMapper.SqlDBConn, which returns the database connection of the geo.SQLMapper for inspection purposes.geo.GetSQLConfFromFile, which accepts the pathname to the desired configuration file. This was necessary in order for NewSQLMapper to allow users to supply different pathnames to create new SQLMappers.EARTH_RADIUS logic in querying points in SQL databases.Change EARTH_RADIUS to comply with the information published in wikipedia.
EARTH_RADIUS to comply with the information published in wikipedia.
- First tagged release.
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Your coding agent can read these notes before it upgrades. Set up the MCP server →