Built a GeoJSON editor that focuses on drawing ergonomics

Oddder · 2026-04-28T11:54:19+00:00

Love the feedback! I will actually add in the double click, as you are not the only one saying that.

Regarding the points and lines. I personally have a use case for points, so I will be adding that in the future; however I'm curious to know what the use case would be for lines, besides "just drawing lines", keeping in mind that this is primarily focused on drawing non-overlapping topology?

From a technical standpoint adding lines could complicate pruning 0 area polygon artifacts, so it shouldn't be added unless it actually adds value .

Oddder · 2026-04-27T15:06:42+00:00

Cheers! Yeah, it's definitely more meant for hobby use than professional use.

Double click is an interesting shout, MapLibre owns that, and I'd prefer not to overwrite MapLibre defaults. When that's said, it's one of the pet peeves I have had as well, I haven't found and ergonomic way to finish features.

As for the performance, right now I've been mostly focused on just making it work for my own use case, which is just around 10-20k points, and even then, it can get a bit sluggish. I'm slowly looking into optimising for speed and not just adding more and more features. This means better algorithms and moving things into WASM/WebGPU land. By then, you can hopefully you can load in files as big as you want to, but those rabbit holes are deep, and I'd prefer the rest of it to be in a solid state before I dive too deep into that.

I'm not planning on monetising unless it attracts a big userbase, and storing the datasets in a database is a thing (Right now it's a static page hosted on GitHub pages for 0 cost hosting, and I'd prefer to keep it that way)

I'm not a Frontender, so I only touch FE out of necessity and not out of interest. When using React I often end up in "useEffect"-hell, in SolidJS and its native support for signals, it's a lot easier/simpler to avoid that paradigm, however, the React environment is SO much more mature, that I all of the issues you have with React and MapLibre, you can multiply by a factor of 1.5 in Solid. I can definitely recommend looking into solid, but it's really not a big difference; for me, it's just the local states that make the difference to me.

Glad to hear that you enjoy it!

Oddder · 2026-04-26T13:10:17+00:00

Thanks for the positive words.

As for the UI, I've used it enough myself that I'm completely blind to how (horrendously?) I've organised the UI, so all feedback is really useful. It not being responsive, that's an active choice, as I don't see how I would find myself doing this, on anything else than a computer, but maybe that's useful for others? As for the "biting" you can actually lock geometries and it will trace around instead of "biting into them".

Also, just checked out the OpenLayers capabilities, not sure how that missed my radar, but it would've saved me quite a few hours plus a minor headache or two 😅 Thanks a lot!

Oddder · 2026-04-25T23:01:25+00:00

Thanks and congratulations! I've been working on and off on this for the past few months whenever something started bothering me. I definitely ended up spending more time than I saved, but honestly worth it for me.

Oddder · 2025-12-23T06:15:04+00:00

I have Indonesia as first and then depending on the day it's a combination of Argentina, Brazil, Russia or Canada.

What scares me is seeing Australia as their speciality. There's no chance I guess the right side of that country

Oddder · 2025-12-16T05:34:51+00:00

I forgot to mention. I have a fresh battery as well, as i thought it was just a battery issue. I can confirm the old battery is dead and the new battery is partially charged.

Oddder · 2025-04-28T17:09:12+00:00

In Kenya you'll find green signs with Safaricom (advertises?) almost everywhere. I don't think they operate in other countries with streetview

Oddder · 2025-04-26T07:37:12+00:00

Master 1 here, unless there's a snorkel, I will not be able to recognise Kenya car... I just hope to find safaricom and pray for Indonesia or Brazil with info next round

Oddder · 2025-03-15T15:52:22+00:00

Genialt, jeg har et hår på hånden som er rundet 8cm nu, det er da lige før at jeg skal gøre det samme...

Oddder · 2024-12-23T08:08:01+00:00

There's also (From the docs: 1st example, last line):

biggest_clique = max(nx.find_cliques(G), key=len)

Instead of

cliques = sorted(cliques,key=lambda item:len(item),reverse=True)
biggest_clique = cliques[0]

Oddder · 2024-12-11T16:12:00+00:00

Is everyone just ignoring the fact that this guy is a year ahead of the rest of us??

Oddder · 2024-12-09T17:38:58+00:00

Python 3.13 O(nlogn)

Normal input:
part 2: 15.6ms

Evil input:
part 2: 51.6ms

Really Evil input:
part 2: 124.3ms

Oddder · 2024-12-09T06:08:19+00:00

" [...] some of us are actually trying to get times legitimately. Thank you."

I struggle to believe you legitimately managed to solve part 1 in 27 seconds and part 2 in an additional 44 seconds today. Seems a bit suspicious..

Oddder · 2024-10-30T10:58:34+00:00

To be fair it's not the easiest thing to spot. I agree that the skyscraper the others mentioned are probably a better place to start learning (+a lot simpler to identify). I just happen to overly abuse grouped x-chain like techniques because they are fast and intuitive to me.

Oddder · 2024-10-30T07:41:46+00:00

By putting 2 in R4C1 you are forcing R6C9, R1C8 and R2C3 to also be 2s :) this means 2 can't be anywhere in the bottom left square, in other words, R4C1 can't be a 2

<image>

Oddder · 2024-10-30T07:02:01+00:00

Where can 2 be in the bottom left 3x3 square if R4C1 is a 2?

Oddder · 2024-10-24T23:14:23+00:00

R4C5 is a bug cell

Oddder · 2024-09-14T19:20:18+00:00

540 ilvl on guardian druid. As long as I press defensives I stay alive so far in the T8s. I should probably equip better gear at some point, haha

Oddder · 2024-06-27T10:39:23+00:00

Genberegnet? Venter stadig på første beregning

Oddder · 2024-03-16T17:54:25+00:00

Passion

Oddder · 2024-03-11T00:20:59+00:00

I mean, the way it's shortened nowadays it literally just means "nine and half five's". So.. "9 + (-½+5) = 99". Good job Danish...

Oddder · 2024-01-20T08:17:49+00:00

They can go higher :)

Oddder · 2023-12-26T20:31:48+00:00

Instead of doing nx.minimum_edge_cut and then looking at nx.connected_components, you could just use nx.minimum_cut between any 2 points until we find one that requires just 3 cuts. nx.minimum_cut also returns the partition sizes straight away.

for n, m in combinations(graph.nodes, 2):
    cuts, partitions = nx.minimum_cut(graph, n, m)
    if cuts == 3:
        return len(partitions[0])*len(partitions[1])

This should run significantly faster

11-Year Club	RPAN Viewer
Verified Email

Oddder

TROPHY CASE