RFE: `GeoJSON` format - Githubissues

fvasco / pinpoi

Import and manage point of interest

GNU General Public License v3.0

27 stars 5 forks source link

RFE: `GeoJSON` format #34

Closed Lee-Carre closed 2 years ago

Lee-Carre commented 2 years ago

One of my uses for PinPoi is with map surveying.

In the OSM realm, GeoJSON is a commonly-used format.

Sometimes, a dataset isn't published (or a tool doesn't output) in any format which PinPoi can parse (i.e. only GeoJSON).

Thus, it would be most helpful to use this format in PinPoi.

fvasco commented 2 years ago

It looks interesting. Unfortunately this standard misses some important attribute, can you provide me an example?

Lee-Carre commented 2 years ago

can you provide me an example?

GeoJSON.org cites RFC 7946, which includes RFC 7946 § 1.5 Example.

I'll have to hunt for a good (correct / accurate, and feature-complete) example.

In the meantime, a meta-example; some tools which generate GeoJSON:

GeoJSON.io
OSM2GeoJSON
Overpass Turbo (after generating a query, look under “Export”)

fvasco commented 2 years ago

Take a look to the version 1.8.0.

Lee-Carre commented 2 years ago

can you provide me an example?

[…]

I'll have to hunt for a good (correct / accurate, and feature-complete) example.

While imperfect (not necessarily (although still likely) strictly valid & correct (spec-compliant), or feature-complete), some real-world samples (that're well-used) are to be found at

USGS § Earthquakes § Data Feeds
- GeoJSON Summary Format
- GeoJSON Detail Format

[Edit to add:] An OSM-centric sample (generated, depending on the area viewed / selected) is

@rjw62's #SurveyMe tool
- working example (simplified / minimal): //osm.mathmos.net/survey/data.cgi?lat=49.2&lon=-2.1 (fmt seems to default to GeoJSON, without a value to explicitly force it)

[…] some tools which generate GeoJSON:

FYI; I added another to the list.

Take a look to the version 1.8.0.

Will do! 🙂 Waiting for F-Droid to build & publish. I'll report back after installing & testing.

fvasco commented 2 years ago

@Lee-Carre should be closed this issue?

Lee-Carre commented 2 years ago

should be closed this issue?

Apologies for my recent absence.

technical difficulties
health issues

I have not yet had chance to test, and am unsure of when I'd be able to.

I'm sure that you did decent testing as part of your implementation process.

So, yes, closing this issue is probably best. It can always be re-opened if needed.

I do intend to report back, eventually, if only to confirm that GeoJSON functions as expected. Else with suggestions for tweaks.

Once again, thankyou for your prompt efforts, @fvasco. 🙂👍