|
ATGeo WG: Next meeting 25 Sep 2025 1900 UTC
|
|
2
|
16
|
September 13, 2025
|
|
ATProto Location Data Store: A Source-Aware, Federated Approach to Location Data
|
|
2
|
29
|
September 5, 2025
|
|
Any wisdom about collecting practical Lexicon applications/use cases? (for Geo & beyond)
|
|
1
|
31
|
September 4, 2025
|
|
Prototypes – go-whosonfirst-spatial-atproto
|
|
0
|
10
|
September 3, 2025
|
|
Prototypes - whosonfirst-external-duckdb
|
|
0
|
5
|
September 3, 2025
|
|
What is the Difference Between a “Federated Location Data Store” and a “Gazetteer”?
|
|
5
|
35
|
September 2, 2025
|
|
Location Data Providers and ATProto Development Patterns
|
|
8
|
26
|
September 2, 2025
|
|
Formalization Meeting: ATgeo Working Group
|
|
6
|
48
|
August 30, 2025
|
|
Licensing Considerations for Location Data
|
|
7
|
18
|
August 29, 2025
|
|
Broadly speaking, the applications of location data in ATProto
|
|
3
|
20
|
August 22, 2025
|
|
ATGeo WG: How do we represent place names?
|
|
5
|
20
|
August 16, 2025
|
|
ATGeo WG: How should we refer to place objects from off-protocol reference datasets?
|
|
3
|
24
|
August 16, 2025
|
|
ATGeo WG: What to do with reference place objects that have extra attribute data?
|
|
0
|
7
|
August 13, 2025
|
|
ATGeo WG: more geometry types
|
|
0
|
22
|
August 10, 2025
|
|
ATGeo WG: Documentation for existing Lexicons
|
|
2
|
20
|
August 10, 2025
|
|
ATGeo WG: Designing for interoperability with a common data model for places
|
|
5
|
42
|
August 7, 2025
|
|
ATgeo WG: Next Steps for Garganorn and Geographic Data in ATProtocol
|
|
7
|
56
|
August 7, 2025
|
|
Some ideas for a checkin record, need input!
|
|
18
|
58
|
June 29, 2025
|