cogran

cogran copied to clipboard

This method / project / blogpost could be interesting to you: https://supaplexosm.github.io/strassenraumkarte-neukoelln/posts/2021-03-13-opendata I describes the process that Alex used to break down data that was available on LOR level to...

tordans

Output's prettiness leads to huge filesize

1

The resulting geojson is "pretty" formatted which leads to a vastly increased filesize. Removing all occurances of " " from a 11MB file shrank it to just 3MB.

fnorf

# The non-relative example: node index.js -d -i testdata/berlin/kriminalitaet_bezirksregionen.geojson \ -t testdata/berlin/447_lor_planungsraeume.geojson \ -o testdata/berlin/binaryDasymetricWeighting_kriminalitaet_bezirksregionenToPlanungsraeume.geojson \ --attr Alle_2012 --mask testdata/berlin/wohnbloecke.geojson \ --mode binaryDasymetricWeighting intersects for a while then errors with...

kannes

testdata/hamburg/binaryDasymetricWeightingRelative_wohnflaeche_stadtteileToBezirke.geojson has all 0s for the WFl_m2 field. It should have the calculated values instead (I think?).

kannes

npm test did not show errors for areal-weighting when I accidentally returned the whole sourceFeatures list from getIntersectingFeatures instead of only the filtered sourceList. ``` sourceList = sourceFeatures; return [sourceList,...

fnorf

Utilise spatial indexing to make things fast

1

Use https://github.com/mourner/rbush to create a spatial index that can be utilised for all the intersection tests and operations. Something like: - Get the extends of each feature and use some...

fnorf

I worked with rtree in Python recently so the logic was easy to transfer. Don't judge my code, I *hate* JavaScript and have no idea about anything. **Please don't merge...

fnorf