| WeeSofty:tm2 r$ npm install mapnik | |
| npm WARN package.json [email protected] No repository field. | |
| npm WARN package.json [email protected] 'repositories' (plural) Not supported. | |
| npm WARN package.json Please pick one as the 'repository' field | |
| npm http GET https://registry.npmjs.org/mapnik | |
| npm http 304 https://registry.npmjs.org/mapnik | |
| npm http GET https://registry.npmjs.org/mapnik-vector-tile | |
| npm http 304 https://registry.npmjs.org/mapnik-vector-tile | |
| > [email protected] install /Users/r/gh/mapbox/tm2/node_modules/mapnik/node_modules/mapnik-vector-tile |
| unit | colors | |
|---|---|---|
| Cba | #ffebeb,#99b380 | |
| Cm | #ebebcc,#ffccde | |
| Ct | #ffb3cc,#ccde66 | |
| Dtb | #664dff | |
| H20 | #ebffff | |
| IPMs | #99ebde | |
| Jc | #ccffde | |
| Je | #cccc00 | |
| Jk | #99de99 |
| function onEachFeature(feature, layer) { | |
| /* From the perspective of reading this function, it would be easier if you think about it in a linear fashion | |
| What does this function do? | |
| 1) get a single feature | |
| 2) parse some specific properties out of the feature | |
| 3) use those properties to generate a string of HTML | |
| 4) build a popup from that HTML | |
| Right now its a little hard to read because you're jumping around between those steps a bit | |
| */ |
| { | |
| "license_title": "License Not Specified", | |
| "maintainer": "", | |
| "relationships_as_object": [], | |
| "private": false, | |
| "maintainer_email": "", | |
| "revision_timestamp": "2013-11-21T00:22:03.676324", | |
| "id": "f1a90774-c8d0-4c73-947b-63803c2d7525", | |
| "metadata_created": "2013-11-21T00:21:38.099774", | |
| "owner_org": null, |
I imported tucson.osm.pbf, a 3.4MB OSM extract.
| Where is PostgreSQL | Machine Specs | Import time |
|---|---|---|
| Local | 4 CPU, 16GB RAM Macbook Pro | 18 seconds |
| Local | i2.4xlarge EC2 | 76 seconds |
| Remote | m1.medium EC2 > db.m1.large 500GB : 2000 IOPS | 112 seconds |
| Remote | i2.4xlarge EC2 > db.m2.4xlarge 1000GB : 10000 IOPS | 82 seconds |
You're going to start up a Linux EC2, set up its firewall rules, and connect to it.
If you're not doing production work always try and use the sandbox account, so log into sandbox account.
The first thing you need is an AMI, which is like a snapshot that is the starting point for your machine. Go to https://cloud-images.ubuntu.com/locator/ec2/ to find ubuntu AMIs. These are like from-scratch instances that are kept up-to-date with security patches. If you search for 14.04 that'll be the latest stable ubuntu release, then you're looking for one that's in the right region (generally that's us-east-1), the right architecture (usually amd64) and the right instance type (usually that's instance-store). Copy the
Clicking on one of the ami-12345 links will pop you over to the AWS EC2 console and start you down the road of creating the instance.
First you'll have to choose an instance type. You'll want the smallest (i.e. cheapest) one th
| | | | |
| | | | |
|--------- really no time at all -----------|------------ 7 to 14 days -------------|-------------- really no time at all ----------------|----------------- shouldn't be too long -----------------|
| | | | |
| | | | |
A CloudFormation stack that you can run in your AWS account to host up a dedicated Satisfactory server.
Thanks to https://github.com/wolveix/satisfactory-server for the Docker image!
The dedicated server application runs on ECS Fargate, so you get a more-or-less "serverless" setup. It uses Fargate Spot, which allows you to get the cheapest possible setup, though AWS may choose to stop and restart your server. FWIW I've never actually observed that happening.